|
Problem IC84118
|
Status: Closed |
QUERYING A DETACHED PARTITION OF A RANGE-PARTITIONED/MDC TABLE RETURNS SQL0901N ERROR ON HADR STANDBY AFTER TAKEOVER |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When using a data-partitioned MDC table, detaching a partition
results in the following with regards to the resulting target
table (i.e. the detached partition):
- An empty index object is created
- The indexes are marked in error and as requiring rebuild
- The next access to the detached partition will drive index
rebuild and all of the block indexes will be recreated.
In an HADR system, if a takeover occurs before the next access
to the detached partition, then the index will no longer be
marked in error and as requiring rebuild. As a result, the next
query that is run on the new primary that requires the block
index will fail with an SQL0901N with the reason text "Unable to
find index on table!".
An example of error messages in db2diag.log is shown below:
2011-10-10-14.35.10.144742+660 I8706135A2169 LEVEL: Severe
PID : 843992 TID : 70421 PROC : db2sysc
0
INSTANCE: INSTNAME1 NODE : 000 DB :
DBNAME1
APPHDL : 0-25092 APPID:
*LOCAL.INSTNAME1.111010033438
AUTHID : INSTNAME1
EDUID : 70421 EDUNAME: db2agntp (DBNAME1) 0
FUNCTION: DB2 UDB, data management, sqldSetupIndexScan, probe:1
MESSAGE : Unable to find index on table! |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7.0.1. *
**************************************************************** |
| Local Fix: |
Take database offline and mark the index bad using db2dart's /mi
option. Then run restart the instance and run RESTART DATABASE
and run a SELECT against the problem table to rebuild the index. |
| 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 |
The problem is first fixed in DB2 9.7.0.1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.06.2012
14.11.2012
14.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.0.1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.7
|
 |
