DB2 - Problembeschreibung
Problem IC96745 | Status: Geschlossen |
IN A DPF, IF AGENTPRI IS CHANGED, DB2START GETS SQL1042C AND DB2 INSTANCE CAN'T START. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
When the problem happens, following error can be observed in db2diag.log. 2013-08-29-09.40.02.073501+600 E12276A1520 LEVEL: Severe (OS) PID : 14745630 TID : 1 PROC : db2star2 INSTANCE: db2inst NODE : 000 EDUID : 1 FUNCTION: DB2 UDB, oper system services, sqloWaitIPCWaitPost, probe:100 MESSAGE : ZRC=0x83000023=-2097151965 CALLED : OS, -, msgrcv OSERR : ENOMSG (35) "No message of desired type" DATA #1 : timeout value, 4 bytes 0 DATA #2 : String, 203 bytes { pc = 0x0 cs = { lock = { 0x10000000 [ locked ] } identity = sqlo_waitpost::cs (6) } state = 0x2 ((Empty)) guard = initialized flags = 0x2 numWaiters = 1 } DATA #3 : ipc waitpost, PD_TYPE_SQLO_IPCWAITPOST, 28 bytes 0x07800000000100C8 : 0000 0000 1000 0000 0006 0000 0000 0002 ................ 0x07800000000100D8 : 0000 ABFE 0002 0000 0000 0001 ............ DATA #4 : system V message queue identifier., PD_TYPE_SYSV_QUEUE_ID, 4 bytes 0x04800028 DATA #5 : Bitmask, 8 bytes 0x0000000000000000 CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x090000002C071AD4 pdLogSysRC@glueA + 0x174 [1] 0x090000002C088780 sqloWaitIPCWaitPost + 0x270 [2] 0x0000000100003B84 DB2StartMain + 0x3104 [3] 0x0000000100008670 main + 0x10 [4] 0x0000000100000320 __start + 0x98 [5] 0x0000000000000000 ?unknown + 0x0 [6] 0x0000000000000000 ?unknown + 0x0 [7] 0x0000000000000000 ?unknown + 0x0 [8] 0x0000000000000000 ?unknown + 0x0 [9] 0x0000000000000000 ?unknown + 0x0 2013-08-29-09.40.02.074697+600 I13797A390 LEVEL: Error PID : 14745630 TID : 1 PROC : db2star2 INSTANCE: db2inst NODE : 000 EDUID : 1 FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:660 MESSAGE : db2sysc exited prematurely. sqlcode : DATA #1 : Hexdump, 4 bytes 0x0FFFFFFFFFFF92F8 : 8300 0023 ...# | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All Users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V105FP4 or higher version. * **************************************************************** | |
Local-Fix: | |
Restart DB2 instance without AGENTPRI modification. | |
verfügbare FixPacks: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Lösung | |
Fixed on DB2 V105FP4 | |
Workaround | |
Restart DB2 instance without AGENTPRI modification. | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 09.10.2013 15.09.2014 15.09.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |