DB2 - Problembeschreibung
Problem IC84337 | Status: Geschlossen |
DB2 BACKEND PROCESS MIGHT CRASH WHEN EXPORTING WITH XMLSAVESCHEMA FROM AN UNDEFINED TABLE HAVING AN XML COLUMN. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
If you run an EXPORT with the XMLSAVESCHEMA parameter against an undefined table having an XML column, the db2 backend process (db2bp) might crash. Db2diag.log will have below SQL0204N, SQL3022N, "Possible memory corruption" and "Double free" messages. ... 2011-11-18-14.38.00.132050+540 I863395E465 LEVEL: Error PID : 2330 TID : 46982244293232PROC : db2bp INSTANCE: db2inst1 NODE : 000 APPID : *LOCAL.db2inst1.111118053759 FUNCTION: DB2 UDB, database utilities, sqluCheckSqlca, probe:298 MESSAGE : SQL0204N "DB2INST1.HOGE" is an undefined name. DATA #1 : String, 17 bytes sqluiDescribe.SQC DATA #2 : String, 44 bytes Error from Import/Export or Load Processing. 2011-11-18-14.38.00.132546+540 I863861E730 LEVEL: Error (Origin) PID : 2330 TID : 46982244293232PROC : db2bp INSTANCE: db2inst1 NODE : 000 APPID : *LOCAL.db2inst1.111118053759 FUNCTION: DB2 UDB, database utilities, sqlueAllocAndDescSqlda, probe:3625 MESSAGE : SQL3022N An SQL error "" occurred while processing the SELECT string in the Action String parameter. DATA #1 : String, 28 bytes Export SQL failed processing DATA #2 : Hexdump, 35 bytes 2011-11-18-14.38.00.136417+540 I864592E1544 LEVEL: Severe PID : 2330 TID : 46982244293232PROC : db2bp INSTANCE: db2inst1 NODE : 000 APPID : *LOCAL.db2inst1.111118053759 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 0x00002abaee0be580 DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes 0x00002ABAEE0BE568 : BEE0 AEAB 0200 B0FA 0000 0000 0000 0000 ................ 0x00002ABAEE0BE578 : 0000 0000 0000 0000 ........ DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 0x00002ABAEE0BE580 : 0001 0000 0000 0000 0200 0000 0000 0000 ................ 0x00002ABAEE0BE590 : 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00002ABAEE0BE5A0 : 0000 0000 0000 0000 BEE0 AEAB 0200 B0FA ................ CALLSTCK: [0] 0x00002ABAE43C7DC3 pdLog + 0x1FF [1] 0x00002ABAE4C18BFC /home/db2inst1/sqllib/lib64/libdb2.so.1 + 0xCF4BFC [2] 0x00002ABAE4492BC4 sqlofmblkEx + 0x8D4 [3] 0x00002ABAE43A457A _Z9sqlofmblkPv + 0x6 [4] 0x00002ABAE4B47900 _Z20sqluiDescribeCleanupPP17sqluiDescribeInfo + 0x16A [5] 0x00002ABAE4AF1879 _Z8sqluexpmPhP7sqluecbP5sqlcaP12db2ExportOutPiPS_h + 0xE61 [6] 0x00002ABAE4AD1E24 db2Export + 0x7F2 [7] 0x0000000000445C11 _Z19clpbp_exe_db2Exportv + 0x24F [8] 0x0000000000492780 _Z10clp_bp_conv + 0x71C [9] 0x0000000000492012 main + 0x1A2 2011-11-18-14.38.00.220045+540 I866137E332 LEVEL: Severe PID : 2330 TID : 46982244293232PROC : db2bp INSTANCE: db2inst1 NODE : 000 APPID : *LOCAL.db2inst1.111118053759 FUNCTION: DB2 UDB, SQO Memory Management, sqloDiagnoseFreeBlockFailure, probe:30 DATA #1 : String, 12 bytes Double free. ... You also find <PID>.<TID>.mem_diagnostics.txt file under sqllib/db2dump directory. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 10.1 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 10.1 FixPack 1. * **************************************************************** | |
Local-Fix: | |
Before executing EXPORT, terminate (not connect reset) the connection and reconnect to database may work around. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in DB2 UDB Version 10.1 FixPack 1. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.06.2012 03.11.2012 03.11.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.1 | |
10.5.0.1 |