|
Problem IC62381
|
Status: Closed |
sqldUpgradeLock probe 560 received when deleting a row from an MDC table while lock escalation is occurring |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
On a multi-node system on a multi dimension clustering (MDC)
table, if one DB2 agent is performing lock escalation, another
DB2 agent could abend with an error from sqlpUpgradeLock()
while trying to delete a row.
Messages similar to the following will be seen in the
db2diag.log:
2008-11-20-07.37.44.918025-300 I31144528A782 LEVEL: Error
PID : 3809518 TID : 120203 PROC :
db2sysc5
INSTANCE: svtdbm5 NODE : 005 DB : SLEE
APPHDL : 15-3780 APPID: *N5.svtdbm5.081120123549
AUTHID : SVTDBM5
EDUID : 120203 EDUNAME: db2agntp (SLEE) 5
FUNCTION: DB2 UDB, lock manager, sqlpUpgradeLock, probe:560
MESSAGE : Cannot find header!
DATA #1 : Hexdump, 64 bytes
0x0700000161BFD428 : 0008 0055 0000 0000 0006 0000 6200 0000
...U........b...
0x0700000161BFD438 : 0000 0000 0000 0000 0000 0002 0000 0002
................
0x0700000161BFD448 : 0000 0000 0000 0005 0000 0001 0000 6021
..............`!
0x0700000161BFD458 : 0000 0000 0000 0000 0000 0001 0000 0000
................
2008-11-20-07.37.44.937763-300 I31145311A492 LEVEL: Severe
PID : 3809518 TID : 120203 PROC :
db2sysc5
INSTANCE: svtdbm5 NODE : 005 DB : SLEE
APPHDL : 15-3780 APPID: *N5.svtdbm5.081120123549
AUTHID : SVTDBM5
EDUID : 120203 EDUNAME: db2agntp (SLEE) 5
FUNCTION: DB2 UDB, relation data serv, sqlrr_signal_handler,
probe:100
MESSAGE : DIA0505I Execution of a component signal handling
function has begun.
2008-11-20-07.37.44.938182-300 I31145804A702 LEVEL: Severe
PID : 3809518 TID : 120203 PROC :
db2sysc5
INSTANCE: svtdbm5 NODE : 005 DB : SLEE
APPHDL : 15-3780 APPID: *N5.svtdbm5.081120123549
AUTHID : SVTDBM5
EDUID : 120203 EDUNAME: db2agntp (SLEE 5
FUNCTION: DB2 UDB, relation data serv, sqlrr_signal_handler,
probe:125
MESSAGE : MASTER TIME INFO
DATA #1 : Hexdump, 40 bytes
0x070000084A5EF358 : 0000 0000 4924 4997 0363 0000 000D 3AC8
....I$I..c....:.
0x070000084A5EF368 : 0007 DC7A E5FB F043 0000 0000 0055 50AC
...z...C.....UP.
0x070000084A5EF378 : 8007 DC7A E5FB F042
...z...B
The error occurs in the following code path:
0x090000000042B5BC pthread_kill + 0x88
0x09000000053F6DA8 sqloDumpEDU + 0x24
0x0900000005920B3C
sqlpUpgradeLock__FP8sqeAgentP14SQLP_LOCK_INFO+ 0x1A60
0x0900000007290944sqldMDCLogAndDeleteRecord__FP13SQLD_DFM_WORKP8
SQLD_TCBiT3+0x498
0x09000000061C1554 sqldRemoveRow__FP13SQLD_DFM_WORKi + 0x558
0x09000000061D27A0 sqldDeleteRow__FP13SQLD_DFM_WORKPci + 0x274
0x09000000061E1CD0 sqldRowDelete__FP8sqeAgentP8SQLD_CCBUl +
0x28C
0x0900000006213930 sqlridel__FP8sqlrr_cb + 0x408
0x0900000006602BAC sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm
+0xE8
0x090000000773FDC4 sqlrr_dss_router__FP8sqlrr_cb + 0x8F0
0x0900000006C473DC
sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0xEBC
0x0900000006C436FC sqleSubRequestRouter__FP8sqeAgentPUiT2 +
0x7E0
0x0900000006C3F9F4 sqleProcessSubRequest__FP8sqeAgent + 0x120
0x0900000006628878 RunEDU__8sqeAgentFv + 0x330
0x0900000006687EA0 EDUDriver__9sqzEDUObjFv + 0x78
0x09000000066861D8 sqloEDUEntry + 0x3A0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DPF users with MDC tables *
****************************************************************
* PROBLEM DESCRIPTION: *
* In DPF environments where there are MDC tables and *
* lockescalations, there exists *
* the possibility that one of theDB2 agents could return an *
* error and end *
* prematurely dumping its stack. The db2diag.log message *
* would indicate this *
* error message. *
* *
* 2008-11-20-07.37.44.918025-300 I31144528A782 *
* LEVEL:Error *
* PID : 3809518 TID : 120203 PROC :db2sysc *
* INSTANCE: svtdbm5 NODE : 005 DB :SLEE *
* APPHDL : 15-3780 *
* APPID:*N5.svtdbm5.081120123549 *
* AUTHID : SVTDBM5 *
* EDUID : 120203 EDUNAME: db2agntp (SLEE) *
* FUNCTION: DB2 UDB, lock manager, sqlpUpgradeLock, probe:560 *
* MESSAGE : Cannot find header! *
* DATA #1 : Hexdump, 64 bytes *
* 0x0700000161BFD428 : 0008 0055 0000 0000 0006 0000 6200 *
* 000...U........b... *
* 0x0700000161BFD438 : 0000 0000 0000 0000 0000 0002 0000 *
* 0002................ *
* 0x0700000161BFD448 : 0000 0000 0000 0005 0000 0001 0000 *
* 6021..............`! *
* 0x0700000161BFD458 : 0000 0000 0000 0000 0000 0001 0000 *
* 0000................ *
* The stack dump would be as follows. *
* 0x090000000042B5BC pthread_kill + 0x88 *
* 0x09000000053F6DA8 sqloDumpEDU +0x24 *
* 0x0900000005920B3C *
* sqlpUpgradeLock__FP8sqeAgentP14SQLP_LOCK_INFO + 0x1A60 *
* 0x0900000007290944 *
* sqldMDCLogAndDeleteRecord__FP13SQLD_DFM_WORKP8SQLD_TCBiT3 *
* +0x498 *
* 0x09000000061C1554 sqldRemoveRow__FP13SQLD_DFM_WORKi + 0x558 *
* 0x09000000061D27A0 sqldDeleteRow__FP13SQLD_DFM_WORKPci *
* +0x274 *
* 0x09000000061E1CD0 sqldRowDelete__FP8sqeAgentP8SQLD_CCBUl *
* +0x28C *
* 0x0900000006213930 sqlridel__FP8sqlrr_cb + 0x408 *
* 0x0900000006602BAC *
* sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0xE8 *
* 0x090000000773FDC4 sqlrr_dss_router__FP8sqlrr_cb + x8F0 *
* 0x0900000006C473DC *
* sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0xEBC *
* 0x0900000006C436FC sqleSubRequestRouter__FP8sqeAgentPUiT2 *
* +0x7E0 *
* 0x0900000006C3F9F4 sqleProcessSubRequest__FP8sqeAgent +0x120 *
* 0x0900000006628878 RunEDU__8sqeAgentFv + 0x330 *
* 0x0900000006687EA0 EDUDriver__9sqzEDUObjFv + *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7 fp1 *
**************************************************************** |
| Local Fix: |
Avoid lock escalation through appropriate settings of the
database configuration parameters LOCKLIST and MAXLOCKS. |
| 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 6 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 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 |
Once this fix is installed in the DPF environment with MDC
tables, the lock escalations will proceed properly and all
agents will continue processing normally without the error as
seen previously. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.08.2009
12.02.2010
12.02.2010 |
| 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
|
 |
