|
Problem IC93806
|
Status: Closed |
LOG FILE CORRUPTION AND POSSIBLE PANIC WHILE DROPPING JUST THE GLOBAL INDEX FROM A RANGE PARTITIONED TABLE. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
On a range partitioned table, if we are dropping the global
index and not the partitioned table itself, there exists the
possibility that the internal table control blocks can become
out of sync with the target object table record. This can lead
to an incorrect log record being written and an eventual panic
condition.
There is no other identifiable external symptom or error message
associated with this issue. The log record will look normal and
still be incorrect. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.01.003 *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Corrected in db2 version 10.01.003 |
| Workaround |
N/A |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.06.2013
27.09.2013
27.09.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
