|
Problem IC96262
|
Status: Closed |
A DEADLOCK MAY OCCUR,IF ALTER SEQUENCE IS EXECUTED AT THE SAME TIME. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 10.1 fixpack 3. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 UDB Version 10.1 FixPack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.09.2013
08.10.2013
08.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
