DB2 - Problem description
Problem IC92514 | Status: Closed |
SQLCODE -901 IS CRASHING THE INSTANCE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
When the lock held issue happened we see the following events in db2diag.log before the instance crash: 2012-03-29-05.04.42.242792-360 I701458A871 LEVEL: Error PID : 1814768 TID : 25118 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-16614 APPID: 10.52.13.123.64516.120328213849 AUTHID : db2inst1 EDUID : 25118 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 24 sqlerrmc: lock not owned by caller sqlerrp : SQLPL00F sqlerrd : (1) 0x82100001 (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0xFFFFFE52 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 2012-03-29-05.04.42.242930-360 I702330A590 LEVEL: Error PID : 1814768 TID : 25118 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-16614 APPID: 10.52.13.123.64516.120328213849 D : db2inst1 EDUID : 25118 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, access plan manager, sqlra_close_sections, probe:1200 RETCODE : ZRC=0x82100001=-2112880639=SQLP_NONSEVERE_PRGERR "DPS detects non-severe programming error" DIA8532C An internal processing error has occurred. 2012-03-29-05.04.42.243107-360 I702921A597 LEVEL: Error PID : 1814768 TID : 25118 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-16614 APPID: 10.52.13.123.64516.120328213849 AUTHID : db2inst1 EDUID : 25118 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_cleanup_tran_before_DPS, probe:900 RETCODE : ZRC=0x82100001=-2112880639=SQLP_NONSEVERE_PRGERR "DPS detects non-severe programming error" DIA8532C An internal processing error has occurred. 2012-03-29-05.04.42.243891-360 I703519A470 LEVEL: Error PID : 1814768 TID : 25118 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-16614 APPID: 10.52.13.123.64516.120328213849 AUTHID : db2inst1 EDUID : 25118 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, access plan manager, sqlra_release_held_locks, probe:100 MESSAGE : held_locks discrepency with 0 locks held 2012-03-29-05.04.42.251246-360 I703990A1576 LEVEL: Severe PID : 1814768 TID : 25118 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-16614 APPID: 10.52.13.123.64516.120328213849 AUTHID : db2inst1 EDUID : 25118 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, SQO Latch Tracing, sqlo_xlatch::releaseConflict, probe:10 DATA #1 : String, 27 bytes unlocking an unlatched lock DATA #2 : Pointer, 8 bytes 0x07000000a00916f0DATA #4 : Hexdump, 8 bytes 0x07000000A00916F0 : 0000 0000 0168 0000 .....h.. CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x090000000AC0AB60 pdLog + 0xE4 [1] 0x0900000006C70F18 pdLog@glue409 + 0x12C [2] 0x090000000774A1AC sqloSpinLockReleaseConflict + 0x5C [3] 0x090000000AD450AC sqloSpinLockReleaseConflict@glue73 + 0x78 [4] 0x090000000AD454F4 sqloxult_track__FCP11sqlo_xlatchC14SQLO_LT_VALUES@glueC57 + 0x0 [5] 0x0900000007340190 sqlpxrbk__FP8sqeAgentP15SQLXA_CALL_INFOPiP9SQLP_GXIDPP11sqlo_xla tch + 0xAF8 [6] 0x090000000AD90944 sqlrrbck_dps__FP8sqlrr_cbiN22P15SQLXA_CALL_INFOP9SQLP_GXIDb + 0x1A4 [7] 0x090000000AD922A0 sqlrrbck__FP8sqlrr_cbiN32P15SQLXA_CALL_INFO + 0x1BC [8] 0x090000000AD914FC sqlrr_rollback__FP14db2UCinterface + 0x19C [9] 0x090000000AA1906C sqljsRollbackBeforeConnectReset__FP14db2UCconHandle + 0x150 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 UDB version 10.1FP2. * **************************************************************** | |
Local Fix: | |
Solution | |
Problem was first fixed in DB2 UDB Version 10.1 FP2. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.05.2013 23.05.2013 23.05.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |