home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC99757 Status: Geschlossen

AVOID TRAPS WITH TCB FIX COUNT != 1

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
DB2 might crash with the following message in db2diag.log: 
 
2012-09-01-17.05.07.064218+120 I683330A561        LEVEL: Severe 
 
PID     : 30951                TID  : 4412533568032PROC : 
db2sysc 0 
INSTANCE: db2instx             NODE : 000         DB   : XXXX 
 
APPHDL  : 0-24246              APPID: *LOCAL.db2instx.nnnnnnnnn 
 
AUTHID  : DB2INSTX 
 
EDUID   : 7112                 EDUNAME: db2agent (XXXX) 0 
 
FUNCTION: DB2 UDB, data management, sqldDropObj, probe:415 
 
MESSAGE : TCB fix count != 1 when dropping data object! 
 
DATA #1 : Hexdump, 8 bytes 
 
0x0000040224C8BFE0 : 0000 0000 0000 0002 
 
Often, when this message is dumped, the fix count was already 
decreased to 1. 
So it does not make sense to keep this kind of checking and 
crash the instance. 
 
The APAR fix will therefore remove the Panic from all code that 
does FixCount checking.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 5.                      * 
****************************************************************
Local-Fix:
Lösung
First fixed in DB2 Version 10.5 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.02.2014
24.03.2015
24.03.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.5 FixList