DB2 - Problembeschreibung
Problem IC78466 | Status: Geschlossen |
DATABASE MARKED BAD AFTER HITTING "CHILD EDU UNEXPECTEDLY DIED OR WAS KILLED" ERROR DURING LOAD | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
This problem was found in 9.1(IC76755), but in 9.5 this has been already fixed in FP3 as part of APAR IZ32957. Currently, if a LOAD hit an unexpected error situation where one of its child EDU had died without notice, it wrote a db2diag.log entry like the following, and then proceed to mark the database bad. 2011-05-24-17.03.07.254471+540 I7616426E494 LEVEL: Error PID : 6590 TID : 183034520640PROC : db2agent (MYDB1) 0 INSTANCE: db2inst1 NODE : 000 DB : MYDB1 APPHDL : 0-303 APPID: 43.244.11.76.15340.110524080006 AUTHID : MYAUTHID FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 DATA #1 : String, 109 bytes LOADID: 6590.2011-05-24-17.01.26.076108.0 (3;6) , -2029059911, 0x1a0f, Detected in file:sqluvld.C, Line:3589 The LOAD should just fail, but should not be marking database bad. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users running LOAD. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error description field for more information. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.5 FixPack 3. * **************************************************************** | |
Local-Fix: | |
Lösung | |
Problem was first fixed in DB2 UDB Version 9.5 FixPack 3. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 02.09.2011 05.09.2011 05.09.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP3 | |
Problem behoben lt. FixList in der Version |