|
Problem IC64447
|
Status: Closed |
INDEX MANAGER INCORRECTLY WRITES LOG RECORD FOR CGTT INDEX CREATION |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
During index (re)creation on a created temporary table (CGTT),
index manager may erroneously write a log record for the
requisite transaction. By design, index (re)creation should not
be logged for CGTTs. Doing so has a potential to impact
concurrency. Namely, logging puts the transaction into WRITE
mode. If index recreation becomes too long or gets held up for
some reason, the transaction could hold up the active log
causing it to become full. This, in turn, could halt transaction
processing until index recreation is completed. |
| Problem Summary: |
The problem has been corrected such that index (re)creation log
records will not be written for CGTT tables. |
| Local Fix: |
n/a |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
This APAR fix is targetted for Fix Pack 2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.11.2009
08.01.2010
08.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
