|
Problem IC72889
|
Status: Closed |
INDEX RECREATE FAILS WITH SQLRLRECREATEINDEXOBJECT, PROBE:30 |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In heavy workload situations, a rare timing hole may cause index
recreation to fail with a message in db2diag.log similar to the
following:
2010-10-21-01.46.11.845112+480 I2267924A490 LEVEL: Severe
PID : 574054 TID : 18607 PROC : db2sysc
34
INSTANCE: db2inst1 NODE : 034 DB : SAMPLE
APPHDL : 0-1574 APPID:
10.238.100.51.25797.10102017410
AUTHID : ETL20
EDUID : 18607 EDUNAME: db2agntp (SAMPLE) 34
FUNCTION: DB2 UDB, catalog services, sqlrlRecreateIndexObject,
probe:30
RETCODE : ZRC=0x8404007E=-2080112514=SQLD_IXNOEX "INDEX DOES NOT
EXIST"
In such situations, the database may be marked bad. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* An issue with lock escalation during index recreate could *
* cause DB2 to trap and erroneously mark the database as bad. *
* In such cases, the data in the database is actually fine. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.7 Fix Pack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
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 |
This problem was first fixed in DB2 V9.7 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.11.2010
29.04.2011
29.04.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
