DB2 - Problem description
Problem IC63006 | Status: Closed |
ROLLBACK OF A SET OF MODIFICATIONS TO A DGTT CAUSES MEMORY CORRUPTION | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
If a series of modifications to the definition of a declared global temporary table are made in the same transaction (e.g. create or drop index and/or runstats) and one of the create index statements fails, the rollback of the transaction may cause memory corruption. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Any. Requires use of Declared Global Temporary Tables * **************************************************************** * PROBLEM DESCRIPTION: * * If a series of modifications to the definition of a declared * * * * global temporary table are made in the same transaction * * (e.g. * * create or drop index and/or runstats) and one of the create * * * * index statements fails, the rollback of the transaction may * * * * cause memory corruption. * * * * Memory corruption may result in various traps/ABENDS either * * during rollback processing or subsequently. * **************************************************************** * RECOMMENDATION: * * Apply version 9.7 fixpack 1. * **************************************************************** | |
Local Fix: | |
Avoid errors on CREATE INDEX on declared global temporary tables; avoid issuing more than 1 create index/drop index and runstats on a declared global temporary table in a single transaction. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
DB2 Version 9.7 fixpack 1 includes the fix | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC69160 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 06.09.2009 04.01.2010 04.01.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP1 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |