DB2 FOR LUW / DB2FORLUW / 970 - DB2

A deadlock may occur, if alter sequence is executed at the same 
time. 
 
Terminal 1: 
db2 connect to sample 
db2 "ALTER SEQUENCE TESTSEQ RESTART WITH 1" 
 
Terminal 2: 
db2 connect to sample 
db2 "ALTER SEQUENCE TESTSEQ RESTART WITH 1" 
 
The "alter sequence" statement returned as below. 
 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0911N  The current transaction has been rolled back because 
of a deadlock 
or timeout.  Reason code "2".  SQLSTATE=40001

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.7 fixpack 9.                    * 
****************************************************************

DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 UDB Version 9.7 FixPack 9

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC95276 IC96262 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

07.04.2013
13.01.2014
13.01.2014

9.7.FP9