|
Problem IC99757
|
Status: Closed |
AVOID TRAPS WITH TCB FIX COUNT != 1 |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in DB2 Version 10.5 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.02.2014
24.03.2015
24.03.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.5
|
 |
