DB2 - Problembeschreibung
Problem IC67574 | Status: Geschlossen |
RUNNING DB2PDCFG UTILITY WITHOUT ANY OPTION MAY CRASH INSTANCE IN WINDOWS PLATFORM | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
Run db2pdcfg without any option in Windows platform will cause db2syscs.exe crash. There's no error showing in db2diag.log file, no trap file created. D:\TEMP>db2start 03/30/2010 15:15:36 0 0 SQL1063N DB2START processing was successful. SQL1063N DB2START processing was successful. D:\TEMP>db2pdcfg Current PD Control Block Settings: All error catch flag settings cleared. db2cos is enabled for engine traps. PD Bitmap: 0x1000 Sleep Time: 3 Timeout: 300 Current Count: 0 Max Count: 255 Current bitmap value: 0x0 fopen failed with errno 5. fopen failed with errno 5. D:\TEMP>db2stop force 03/30/2010 15:16:10 0 0 SQL1032N No start database manager command was issued. SQL1032N No start database manager command was issued. SQLSTATE=57019 | |
Problem-Zusammenfassung: | |
Problem Description: RUNNING DB2PDCFG UTILITY WITHOUT ANY OPTION MAY CRASH INSTANCE IN WINDOWS PLATFORM Problem Summary: Run db2pdcfg without any option in Windows platform will cause db2syscs.exe crash. There's no error showing in db2diag.log file, no trap file created. D:\TEMP>db2start 03/30/2010 15:15:36 0 0 SQL1063N DB2START processing was successful. SQL1063N DB2START processing was successful. D:\TEMP>db2pdcfg Current PD Control Block Settings: All error catch flag settings cleared. db2cos is enabled for engine traps. PD Bitmap: 0x1000 Sleep Time: 3 Timeout: 300 Current Count: 0 Max Count: 255 Current bitmap value: 0x0 fopen failed with errno 5. fopen failed with errno 5. D:\TEMP>db2stop force 03/30/2010 15:16:10 0 0 SQL1032N No start database manager command was issued. SQL1032N No start database manager command was issued. SQLSTATE=57019 | |
Local-Fix: | |
n/a | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Lösung | |
Problem is first fixed in Version 9.5 Fix Pack 6 | |
Workaround | |
n/a | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC67581 IC67894 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 06.04.2010 13.05.2010 13.05.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP6 | |
Problem behoben lt. FixList in der Version |