|
Problem IC62995
|
Status: Closed |
CONCURRENT RENAME TABLE STATEMENTS MAY DEADLOCK WHILE INVALIDATING PACKAGE CACHE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Concurrent RENAME TABLE statements on the same table may
deadlock while attempting to invalidate the package cache. To
identify this APAR, if you encounter a deadlock while running
rename table, the following type of entry may be seen in the
db2diag.log:
2009-07-28-09.44.18.334978-240 I157547161A508 LEVEL: Warning
PID : 1941504 TID : 11899 PROC : db2sysc
INSTANCE: svtdbm10 NODE : 000 DB : FITDB
APPHDL : 0-1142 APPID: *LOCAL.svtdbm10.090728134604
AUTHID : SVTDBM10
EDUID : 11899 EDUNAME: db2agent (FITDB)
FUNCTION: DB2 UDB, access plan manager, sqlra_find_pkg,
probe:700
RETCODE : ZRC=0x80100044=-2146435004=SQLP_LTIMEOUT
"LockTimeOut - tran rollback Reason code 68" |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 servers on Linux, Unix and Windows running DB2 *
* Version 9.7 GA. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Concurrent RENAME TABLE statements on the same table may *
* deadlock while attempting to invalidate the package cache. *
* To identify this APAR, if you encounter a deadlock while *
* running rename table, the following type of entry may be *
* seen in the db2diag.log: *
* *
* 2009-07-28-09.44.18.334978-240 I157547161A508 LEVEL: Warning *
* PID : 1941504 TID : 11899 PROC : db2sysc *
* INSTANCE: svtdbm10 NODE : 000 DB : FITDB *
* APPHDL : 0-1142 APPID: *LOCAL.svtdbm10.090728134604 *
* AUTHID : SVTDBM10 *
* EDUID : 11899 EDUNAME: db2agent (FITDB) *
* FUNCTION: DB2 UDB, access plan manager, sqlra_find_pkg, *
* probe:700 *
* RETCODE : ZRC=0x80100044=-2146435004=SQLP_LTIMEOUT *
* "LockTimeOut - tran rollback Reason code 68" *
****************************************************************
* RECOMMENDATION: *
* Apply DB2 Version 9.7 Fix Pack 1 or see Local Fix. *
**************************************************************** |
| Local Fix: |
Avoid renaming the same table concurrently from multiple
applications. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem is first fixed in DB2 Version 9.7 Fix Pack 1 and all
subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.09.2009
21.12.2009
21.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
