|
Problem IC85562
|
Status: Closed |
IN RARE CASE, A ROLLBACK TRANSACTION HITS MAX_LOG IN DB2 LUW DPF ENVIRONMENT CAUSING HANG OR MARK DATABASE BAD. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In DB2 LUW DPF environment, if a transaction hits MAX_LOG on
some partitions, DB2 forces it off and rolls back the
transaction. In rare case, this rollback may hang or mark
database bad.
If it hangs, you will notice the transaction is not rolled back
on some partitions and still consumes log space, and
associated application handle is in UOW-Waiting status.
If it marks database bad, DB2 may report bad table handle in
db2diag.log similar to the following messages:
2012-03-25-03.50.51.931961-300 I667503363E528 LEVEL: Severe
PID : 25925 TID : 46912724003136PROC :
db2sysc 28
INSTANCE: db2instance NODE : 028 DB :
SAMPLE
APPHDL : 0-34113 APPID:
*N0.db2instance.120325053102
AUTHID : SAMUSER
EDUID : 312 EDUNAME: db2agntp (SAMPLE) 28
FUNCTION: DB2 UDB, data management, sqldmclo, probe:948
RETCODE : ZRC=0x87040018=-2029780968=SQLD_BADH "BAD TABLE
HANDLE"
DIA8521C An incorrect table handle was encountered. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 7 *
**************************************************************** |
| Local Fix: |
Avoid hitting MAX_LOG, use NOT LOGGED INITIALLY feature if
possible. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Version 9.7 Fix Pack 7 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC88646
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.07.2012
10.12.2012
10.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.7
|
 |
