|
Problem IC65695
|
Status: Closed |
INSTANCE CAN PANIC OR HANG AFTER 'LRB HAS BEEN PREVIOUSLY REMOVED FROM TRANSACTION CHAIN' DB2DIAG.LOG MESSAGE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In rare circumstances, when a transaction is rolling back it may
encounter an benign issue which results in a db2diag.log message
indicating that "LRB has been previously removed from
transaction chain". It is possible for this message to be
followed by a severe error message "unlocking an unlatched lock"
which will cause the instance to panic. db2diag.log entries
will resemble these:
2009-08-28-02.25.43.825343+000 I99625110A1616 LEVEL: Info
PID : 172342 TID : 1 PROC :
db2agent (DB1) 1
INSTANCE: db2inst1 NODE : 001 DB : DB1
APPHDL : 1-1099 APPID: xxx.xxx.xxx.xx.xxxxx
AUTHID : DB2INST1
FUNCTION: DB2 UDB, lock manager, sqlplUpdateTranEntry, probe:120
MESSAGE : LRB has been previously removed from transaction chain
...
CALLSTCK:
[0] 0x09000000028E5890
sqlplrl__FP20sqle_agent_privatecbP14SQLP_LOCK_INFO + 0x31C
[1] 0x09000000035DF770
sqldmclo__FP20sqle_agent_privatecbPP8SQLD_CCBi + 0x18
[2] 0x0900000003669900 sqlriclo__FP8sqlrr_cbP9sqlri_taoi +
0x9C
...
2009-08-28-02.25.43.826219+000 I99626727A1423 LEVEL: Severe
PID : 172342 TID : 1 PROC :
db2agent (DB1) 1
INSTANCE: db2inst1 NODE : 001 DB : DB1
APPHDL : 1-1099 APPID: xxx.xxx.xxx.xx.xxxxx
AUTHID : DB2INST1
FUNCTION: DB2 UDB, SQO Latch Tracing,
sqlo_xlatch::releaseConflict, probe:10
DATA #1 : String, 27 bytes
unlocking an unlatched lock
...
DATA #3 : String, 104 bytes
{
lock = { 0x00000000 [ unlocked ] }
identity = SQLP_LTRN_CHAIN::entry_latch (20)
}
...
CALLSTCK:
[0] 0x09000000027D2FCC sqloSpinLockReleaseConflict + 0xEC
[1] 0x09000000036C4A00
@49@3@sqloexcs_notrack__FP12sqloSpinLock + 0x0
[2] 0x09000000028E58AC
sqlplrl__FP20sqle_agent_privatecbP14SQLP_LOCK_INFO + 0x338
[3] 0x09000000035DF770
sqldmclo__FP20sqle_agent_privatecbPP8SQLD_CCBi + 0x18
... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* INSTANCE CAN PANIC OR HANG AFTER 'LRB HAS BEEN *
* PREVIOUSLYREMOVED FROM TRANSACTION CHAIN' DB2DIAG.LOG *
* MESSAGE *
****************************************************************
* RECOMMENDATION: *
* Upgrade to FixPak2 or later *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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 |
First fixed in V9.7 FixPak 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.01.2010
10.06.2010
10.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
