DB2 - Problembeschreibung
Problem IC68786 | Status: Geschlossen |
INSTANCE MAY GO DOWN WHEN DISK FULL OR OTHER CRITICAL ERROR APPEARS. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problembeschreibung: | |
If you encouter a disk full situation and db2diag.log has a message as similar as below, your instance may go down. ------ 2010-03-11-14.38.26.900973+540 E69461696A1212 LEVEL: Error (OS) PID : 663608 TID : 140612 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : xxx APPHDL : 0-307 APPID: 10.11.5.18.55236.100311052536 AUTHID : DWH EDUID : 140612 EDUNAME: db2lfrm0 0 FUNCTION: DB2 UDB, oper system services, sqlowrite, probe:70 MESSAGE : ZRC=0x850F000C=-2062614516=SQLO_DISK "Disk full." DIA8312C Disk was full. CALLED : OS, -, write OSERR : ENOSPC (28) "No space left on device" ------ The associated trap file may have a similar stack trace as below: . <StackTrace> . ?unknown + 0x0 . _gtraceExitVar + 0x400 . pdtExit2 + 0x118 . efTraceExit__FUiiPUlUlT4PPc + 0x1FC . eftExitEx__FUiPUlUlT3PiP6EFRuleN23e + 0x94 . eftExitEx__FUiPUlUlT3PiP6EFRuleN23e@glue14E + ... . sqlowrite + 0x70 ... . If there is no disk full condition, instance may not go down. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 9.8 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error description field for more information. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.8 FixPack 4. * **************************************************************** | |
Local-Fix: | |
Removing a disk full situation for preventing instance down by this problem. | |
verfügbare FixPacks: | |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux | |
Lösung | |
Problem was first fixed in DB2 UDB Version 9.8 FixPack 4. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 21.05.2010 31.07.2011 31.07.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.8.FP4 | |
Problem behoben lt. FixList in der Version | |
9.8.0.4 |