DB2 - Problem description
Problem IC66561 | Status: Closed |
INSPECT INDEXDATA CAN CRASH INSTANCE DURING INSPECTING AN UNCOMMITTED INDEX THAT ROLLBACKED AFTERWARDS | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
If a user creates uncommitted indexes while concurrently running INSPECT INDEXDATA, and then rolls back the created indexes, their instance may crash during INSPECT INDEXDATA. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * N/A * **************************************************************** * PROBLEM DESCRIPTION: * * If a user creates uncommitted indexes while concurrently * * running * * INSPECT INDEXDATA, and then rolls back the created indexes, * * * * their instance may crash during INSPECT INDEXDATA. * **************************************************************** * RECOMMENDATION: * * Upgrade to V97FP3 and above. * **************************************************************** | |
Local Fix: | |
Running INSPECT INDEXDATA only after indexes have been committed. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
V97FP3, with the fix, INSPECT INDEXDATA won't crash instance when uncommitted indexes being inspect is rolled back. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.02.2010 23.09.2010 23.09.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.3 | |
9.7.0.3 |