DB2 - Problembeschreibung
Problem IC89552 | Status: Geschlossen |
DPF LOAD MIGHT TRAP AND CRASH THE INSTANCE WHILE LOADING FROM AN ASC FILE WITH INVALID COLUMN POSITIONS | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Load might hit the problem when the following conditions are met: -- It's a Load in DPF environment, i.e. DPF Load. -- Load from an ASC data file. -- Column length specified by Method L is larger than specified reclen, i.e. invalid column positions specified. -- The column having invalid positions is part of distribution key You might see the following error messages in db2diag.log: FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 DATA #1 : String, 128 bytes LOADID: 227426.2013-01-02-07.13.45.536281.0 (134;65) Row found on wrong partition , 1, 0, Detected in file:sqluldat.C, Line:4151 FUNCTION: DB2 UDB, database utilities, sqluGetAndFormatRecords, probe:4154 MESSAGE : ZRC=0x8015006D=-2146107283=SQLU_CA_BUILT "SQLCA has already been built" DATA #1 : LOADID, PD_TYPE_LOADID, 52 bytes LOADID: 227426.2013-01-02-07.13.45.536281.0 (134;65) DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2769 sqlerrml: 0 sqlerrmc: sqlerrp : SQLULDAT sqlerrd : (1) 0x8015006D (2) 0x00000000 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000003 sqlwarn : (1) W (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: ... EDUID : 93087 EDUNAME: db2lpart 2 FUNCTION: DB2 UDB, SQO Memory Management, sqloDiagnoseFreeBlockFailure, probe:10 MESSAGE : ADM14001C An unexpected and critical error has occurred: "Panic". The instance may have been shutdown as a result. "Automatic" FODC (First Occurrence Data Capture) has been invoked and diagnostic information has been recorded in directory "/db2diag/FODC_Panic_<timestamp>/". Please look in this directory for detailed evidence about what happened and contact IBM support if necessary to diagnose the problem. FUNCTION: DB2 UDB, SQO Memory Management, sqloDiagnoseFreeBlockFailure, probe:999 MESSAGE : Memory validation failure, diagnostic file dumped. DATA #1 : String, 28 bytes Corrupt pool free tree node. DATA #2 : File name, 33 bytes 3211418.93087.mem_diagnostics.txt CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x0900000002E628F4 pdLog + 0xF8 [1] 0x090000000294B734 diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb + 0x2A4 [2] 0x090000000294B3B8 diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb@glue7 FD + 0x7C [3] 0x0900000002F71954 .MemTreePut.fdpr.clone.96__13SQLO_MEM_POOLFP8SMemNodeUlP17SqloCh unkSubgroup + 0x10 [4] 0x0900000002F9D7A8 sqlofmblkEx + 0x268 [5] 0x0900000004B46310 iCleanUp__18sqlusCPartSubAgentFv + 0x470 [6] 0x09000000033FBC90 sqlusSubAgentRouter__FP8sqeAgenti + 0x3FC [7] 0x09000000033F5B00 sqleSubRequestRouter__FP8sqeAgentPUiT2 + 0x754 [8] 0x09000000042B310C sqleProcessSubRequest__FP8sqeAgent + 0xB4 [9] 0x09000000029C6A98 RunEDU__8sqeAgentFv + 0x2F0 The instance traps with the following stack: 0x090000000294C7AC sqloCrashOnCriticalMemoryValidationFailure + 0x34 0x090000000294B73C diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb + 0x2AC 0x090000000294B3B8 diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb@glue7 FD + 0x7C 0x0900000002F71954 .MemTreePut.fdpr.clone.96__13SQLO_MEM_POOLFP8SMemNodeUlP17SqloCh unkSubgroup + 0x10 0x0900000002F9D7A8 sqlofmblkEx + 0x268 0x0900000004B46310 iCleanUp__18sqlusCPartSubAgentFv + 0x470 0x09000000033FBC90 sqlusSubAgentRouter__FP8sqeAgenti + 0x3FC 0x09000000033F5B00 sqleSubRequestRouter__FP8sqeAgentPUiT2 + 0x754 0x09000000042B310C sqleProcessSubRequest__FP8sqeAgent + 0xB4 0x09000000029C6A98 RunEDU__8sqeAgentFv + 0x2F0 0x0900000002DAEF08 EDUDriver__9sqzEDUObjFv + 0xF8 0x0900000003044EA0 sqloEDUEntry + 0x278 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW Version 9.7 Fix Pack 9 or higher levels. * **************************************************************** | |
Local-Fix: | |
Correct the invalid column positions and try to load again. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 LUW Version 9.7 Fix Pack 9. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 15.01.2013 17.12.2013 17.12.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP9 | |
Problem behoben lt. FixList in der Version | |
9.7.0.9 | |
9.7.0.9 |