DB2 - Problembeschreibung
Problem IC82006 | Status: Geschlossen |
INSTANCE MAY TRAP WHEN DROPPING OR RENAMING A TABLE THAT HAS XSR DEPENDENT OBJECTS | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
When dropping or renaming a table, if an error occur while updating the system catalog, the instance may trap. The table must have more than one XSR object referencing it in order to hit this problem. The instance may trap with the below db2diag.log message and stack: 2012-03-05-04.37.00.535510-300 I15236592A551 LEVEL: Error PID : 34668706 TID : 60824 PROC : db2sysc INSTANCE: svtdbm2 NODE : 000 DB : CC_FMT2 APPHDL : 0-7758 APPID: *LOCAL.svtdbm2.120305093602 AUTHID : SVTDBM2 EDUID : 60824 EDUNAME: db2agent (CC_FMT2) FUNCTION: DB2 UDB, catalog services, sqlrlCatalogScan::deleteRows, probe:50 RETCODE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock detected" DIA8002C A deadlock has occurred, rolling back transaction. -- 2012-03-05-04.37.00.535838-300 I15237144A1892 LEVEL: Severe PID : 34668706 TID : 60824 PROC : db2sysc INSTANCE: svtdbm2 NODE : 000 DB : CC_FMT2 APPHDL : 0-7758 APPID: *LOCAL.svtdbm2.120305093602 AUTHID : SVTDBM2 EDUID : 60824 EDUNAME: db2agent (CC_FMT2) FUNCTION: DB2 UDB, SQO Memory Management, sqloDiagnoseFreeBlockFailure, probe:10 MESSAGE : Possible memory corruption detected. DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 0x820F0002 DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8 bytes 0x0a00020007dfaac0 DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes 0x0A00020007DFAAA8 : FAB0 A000 2000 7DF0 0A00 0200 07DF A9C8 .... .}......... 0x0A00020007DFAAB8 : 0A00 0200 07DF FF28 .......( DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 0x0A00020007DFAAC0 : 0000 0000 0000 01C0 4500 0000 347E D98C ........E...4~.. 0x0A00020007DFAAD0 : 0000 0000 0000 0000 0000 0000 0000 0004 ................ 0x0A00020007DFAAE0 : 0100 0000 0000 0000 FAB0 A000 2000 7DF0 ............ .}. CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x090000000F95DEF0 pdLog + 0xE8 [1] 0x090000000B9B8D60 @78@sqloDiagnoseFreeBlockFailure__FP8SMemFBlkCb + 0x150 [2] 0x090000000FA112A4 sqlofmblkEx + 0x8C [3] 0x090000000C17583C sqlrltdp__FP8sqlrr_cbPUcsT2T3UcT6P15sqlrl_drop_infobiP11sqlrrstr ingT10_T6 + 0x694 [4] 0x090000000F581F0C sqlrldrt + 0x46BC [5] 0x090000000F5FD070 sqlrldrt@glue9BC + 0xD4 [6] 0x090000000C6EB354 @106@sqlnq_drop_db_object_end__F15sqlnq_ddlobjectP9sqlnq_qtbi19s qlnq_statementType + 0x7B4 [7] 0x090000000F7E9914 sqlnq_drop_db_object__FPP8stknode_i10actiontypePUcP3loc + 0x64C [8] 0x090000000F9AB2E0 sqlnp_smactn__FP8sqlnp_cbi + 0x374 [9] 0x090000000F9AB5C8 sqlnp_parser__FP8sqlnp_cb + 0x28C <StackTrace> -------Frame------ ------Function + Offset------ 0x090000000B9A79E4 sqloCrashOnCriticalMemoryValidationFailure + 0x30 0x090000000B9BA130 sqloCrashOnCriticalMemoryValidationFailure@glue6F5 + 0x78 0x090000000FA320D0 sqlofmblkEx + 0x44 0x090000000C17583C sqlrltdp__FP8sqlrr_cbPUcsT2T3UcT6P15sqlrl_drop_infobiP11sqlrrstr ingT10_T6 + 0x694 0x090000000F581F0C sqlrldrt + 0x46BC 0x090000000F5FD070 sqlrldrt@glue9BC + 0xD4 0x090000000C6EB354 @106@sqlnq_drop_db_object_end__F15sqlnq_ddlobjectP9sqlnq_qtbi19s qlnq_statementType + 0x7B4 0x090000000F7E9914 sqlnq_drop_db_object__FPP8stknode_i10actiontypePUcP3loc + 0x64C 0x090000000F9AB2E0 sqlnp_smactn__FP8sqlnp_cbi + 0x374 0x090000000F9AB5C8 sqlnp_parser__FP8sqlnp_cb + 0x28C 0x090000000FA0F264 sqlnp_main__FP12sqlnq_stringbP3locPP9sqlnq_qur + 0xB8 0x090000000FA30CB8 sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq lrr_cmpl_enviT7PP9sqlnq_qur + 0x198 0x090000000FB604AC sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq lrr_cmpl_env + 0x40 0x090000000FC7FDF4 sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP_ LOCK_INFOP16sqlra_cached_varPiPUl + 0x808 0x090000000FC7D148 sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313_T12_P14 SQLP_LOCK_INFOPP16sq lra_cached_varT12_PUlb + 0x5CC 0x090000000FC6EC60 sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0x6F0 0x090000000FC6E084 sqlri_ddl_get_section__FP8sqlrr_cb + 0xAC 0x090000000FC6DDE0 sqlri_ddl_common__FP8sqlrr_cb + 0x4C4 0x090000000FC6D830 sqlriddl__FP8sqlrr_cb + 0x3C 0x090000000FAC81C4 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x2C 0x090000000FC6C7A8 sqlrr_execute_immediate__FP8sqlrr_cbi + 0x540 0x090000000FC6C148 sqlrr_execimmd__FP14db2UCinterfaceP16db2UCprepareInfo + 0x268 0x090000000FC6BDE8 sqljs_ddm_excsqlimm__FP14db2UCinterfaceP13sqljDDMObject + 0x858 0x090000000FC6B520 sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC interface + 0xC 0x090000000FA7FFA4 .sqljsParse.fdpr.clone.63__FP13sqljsDrdaAsCbP14db2UCinterfaceP8s qeAgentb + 0x248 0x090000000FA7E640 @63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x2B0 0x090000000F88A11C @63@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA0 0x090000000F889D90 @63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x260 0x090000000F889870 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0xEC 0x090000000F90C998 RunEDU__8sqeAgentFv + 0x2A0 0x090000000F908858 EDUDriver__9sqzEDUObjFv + 0xE4 0x090000000F915268 sqloEDUEntry + 0x27C </StackTrace> | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description. * **************************************************************** * RECOMMENDATION: * * See Local Fix or upgrade to DB2 LUW Version 9.7 fixpack 6. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Lösung | |
Problem is first fixed in DB2 LUW Version 9.7 fixpack 6. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC84501 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.03.2012 05.06.2012 05.06.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP6 | |
Problem behoben lt. FixList in der Version | |
9.7.0.6 |