DB2 - Problem description
Problem IC64462 | Status: Closed |
UPDATE/DELETE OPERATION FROM A TABLE AFTER ONLINE TABLE MOVE CAUSES DB2 TO CRASH | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
After an Online Table Move following migration from V91 or V95 to V97, any update/delete operation from the table causes DB2 to crash. This occurs only if the V91 or V95 table contains XML documents that are validated with XML indexes defined on them. The message in db2diag.log indicated the key was not found: RETCODE : ZRC=0x8709002C=-2029453268=SQLI_NOKEY "Key not found within node" DIA8541C The index key could not be found, the value was "". Stack trace in FODC shows the following: 0x00002B38C56E2917 sqloDumpEDU + 0x0037 (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C6E20004 address: 0x00002B38C6E20004 ; dladdress: 0x00002B38C1EF8000 ; offset in lib: 0x0000000004F28004 ; (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C6E18CFB _Z8sqlischdP7SQLI_CBP11SQLI_SDGLOBtj + 0x0ecd (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C6D9AEB9 _Z8sqlidelkP8sqeAgentP9SQLD_IXCBP10SQLI_IXPCRP8SQLD_KEY8SQLZ_RID mP16SQLB_OBJECT_DESC + 0x0c55 (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C7317D25 address: 0x00002B38C7317D25 ; dladdress: 0x00002B38C1EF8000 ; offset in lib: 0x000000000541FD25 ; (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C7316BE7 _Z26xmlsProcessValuesKeyBufferP8sqeAgentP13SQLD_DFM_WORK8SQLZ_RI DPP14SQLP_LOCK_INFOmmP16SQLD_TABLE_CACHE + 0x0203 (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C385BEEE _Z13sqldKeyDeleteP13SQLD_DFM_WORKP8SQLD_TCBP13SQLD_TDATAREC8SQLZ _RIDim + 0x0b1a (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C385CE81 _Z13sqldRowDeleteP8sqeAgentP8SQLD_CCBm + 0x0b13 (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C5F2AD23 _Z8sqlridelP8sqlrr_cb + 0x068f (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C5E71FB1 _Z15sqlriExecThreadP8sqlrr_cbP12sqlri_opparm + 0x0561 (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C5F1D083 _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x051b (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C5ACE0B0 _Z23sqlrr_execute_immediateP8sqlrr_cbi + 0x12c8 (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C5AA2550 _Z14sqlrr_execimmdP14db2UCinterfaceP16db2UCprepareInfo + 0x01d6 (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C3E6E3C5 _Z19sqljs_ddm_excsqlimmP14db2UCinterfaceP13sqljDDMObject + 0x0199 (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C3E4525E _Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U Cinterface + 0x0242 (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C3E46260 _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface + 0x019c (/home/singgih/sqllib/lib64/libdb2e.so.1) 0x00002B38C3E3CEDE address: 0x00002B38C3E3CEDE ; dladdress: 0x00002B38C1EF8000 ; offset in lib: 0x0000000001F44EDE ; This problem is not limited to Online Table Move. A LOAD from the migrated table, or INSERT-SELECT from the migrated table will also cause the same problem during update/delete operation. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users migrating from V9.1 or V9.5 to V9.7. * **************************************************************** * PROBLEM DESCRIPTION: * * After an Online Table Move following migration from V91 or * * V95 * * to V97, any update/delete operation from the table causes * * DB2 to * * crash. This occurs only if the V91 or V95 table contains * * XML * * documents that are validated with XML indexes defined on * * them. * * * * * * * * * * * * * * The message in db2diag.log indicated the key was not found: * * * * * * * * * * * * RETCODE : ZRC=0x8709002C=-2029453268=SQLI_NOKEY "Key not * * found * * within node" * * * * DIA8541C The index key could not be found, the * * value * * was "". * * * * * * * * Stack trace in FODC shows the following: * * * * * * * * 0x00002B38C56E2917 sqloDumpEDU + 0x0037 * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C6E20004 address: 0x00002B38C6E20004 ; dladdress: * * * * 0x00002B38C1EF8000 ; offset in lib: 0x0000000004F28004 ; * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C6E18CFB _Z8sqlischdP7SQLI_CBP11SQLI_SDGLOBtj + * * 0x0ecd * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C6D9AEB9 * * * * _Z8sqlidelkP8sqeAgentP9SQLD_IXCBP10SQLI_IXPCRP8SQLD_KEY8SQLZ_R * mP16SQLB_OBJECT_DESC * * * * + 0x0c55 * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C7317D25 address: 0x00002B38C7317D25 ; dladdress: * * * * 0x00002B38C1EF8000 ; offset in lib: 0x000000000541FD25 ; * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C7316BE7 * * * * _Z26xmlsProcessValuesKeyBufferP8sqeAgentP13SQLD_DFM_WORK8SQLZ_ * DPP14SQLP_LOCK_INFOmmP16SQLD_TABLE_CACHE * * * * + 0x0203 * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C385BEEE * * * * _Z13sqldKeyDeleteP13SQLD_DFM_WORKP8SQLD_TCBP13SQLD_TDATAREC8SQ * _RIDim * * * * + 0x0b1a * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C385CE81 _Z13sqldRowDeleteP8sqeAgentP8SQLD_CCBm + * * * * 0x0b13 * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C5F2AD23 _Z8sqlridelP8sqlrr_cb + 0x068f * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C5E71FB1 * * _Z15sqlriExecThreadP8sqlrr_cbP12sqlri_opparm * * + 0x0561 * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C5F1D083 * * _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm * * + 0x051b * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C5ACE0B0 _Z23sqlrr_execute_immediateP8sqlrr_cbi + * * * * 0x12c8 * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C5AA2550 * * * * _Z14sqlrr_execimmdP14db2UCinterfaceP16db2UCprepareInfo + * * 0x01d6 * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C3E6E3C5 * * * * _Z19sqljs_ddm_excsqlimmP14db2UCinterfaceP13sqljDDMObject + * * * * 0x0199 * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C3E4525E * * * * _Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db * Cinterface * * * * + 0x0242 * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C3E46260 * * * * _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface + 0x019c * * * * (/home/singgih/sqllib/lib64/libdb2e.so.1) * * * * 0x00002B38C3E3CEDE address: 0x00002B38C3E3CEDE ; dladdress: * * * * 0x00002B38C1EF8000 ; offset in lib: 0x0000000001F44EDE ; * * * * * * * * This problem is not limited to Online Table Move. A * * * * LOAD from the migrated table, or INSERT-SELECT from the * * migrated * * table will also cause the same problem during update/delete * * * * operation. * **************************************************************** * RECOMMENDATION: * * Upgrade to fix pack 1 * **************************************************************** | |
Local Fix: | |
Run REORG INDEX after Online Table Move is completed, or run Online Table Move with the REORG option. Warning: Running reorgs on large tables may be time consuming. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
This is fixed in V9.7 Fix pack 1. | |
Workaround | |
Run REORG INDEX after Online Table Move is completed, or run Online Table Move with the REORG option. Warning: Running reorgs on large tables may be time consuming. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.11.2009 18.01.2010 18.01.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 |