Fixes are available
DB2 Version 9.1 Fix Pack 4a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
APAR status
Closed as program error.
Error description
If an online reorganization of an index on a partitioned table fails, the metadata for that index is lost. Further operations on this table can result in errors; for example, updates to the table will not be reflected in that index, resulting in corruption. Subsequent reorg operations on the indexes could cause a crash on certain platforms. . Sample stacks that may be seen include (from a REORG INDEXES ALL): sqloEDUCodeTrapHandler + 0x0074 __libc_sigaction + 0x01a0 sqluInxRefreshTCB + 0x00a5 sqluInxRefreshTCB + 0x0294 sqluSwitchObject + 0x012a sqlu_process_pending_operation + 0x11b3 sqlptppl + 0x00c5 sqlpxcm1 + 0x04ea sqlrrcom_dps + 0x00a1 sqlrrcom + 0x0364 sqlrreorg_index_obj + 0x0050 sqlrreorg_indexes + 0x06be sqlrreorg_sendinfo + 0x148a sqlrr_reorg + 0x009e . or (from a REORG INDEXES ALL ... CLEANUP ONLY): sqloEDUCodeTrapHandler + 0x0074 __libc_sigaction + 0x0190 sqldCleanupIndexes + 0x00cc sqlrreorg_table + 0x143d sqlrreorg_indexes + 0x094f sqlrreorg_getinfo + 0x02db sqlrr_rpc_router + 0x0577 . Only online index reorganizations (that is, reorganizations that specify ALLOW READ ACCESS, which is the default, or ALLOW WRITE ACCESS) that specify a particular index by name on a partitioned table are at risk. This assumes the reorg failure did not crash the database or instance. REORG INDEXES ALL and REORG INDEXES CLEANUP ONLY operations are not affected. This problem only occurs after a failed REORG INDEX <indname> FOR TABLE <tbname> ALLOW READ/WRITE ACCESS. .
Local fix
For a partitioned table, use REORG INDEXES ALL FOR TABLE <tbname> or use REORG INDEX <indname> FOR TABLE <tbname> ALLOW NO ACCESS.
Problem summary
Users affected: all Problem description: Trap can occur after failed online reorganization of an index on a partitioned table. Problem summary: The failure of the index reorg results in the loss of index metadata, which can cause unpredictable problems including corruption and traps.
Problem conclusion
First fixed in DB2 UDB Version 9.1 fix pack 4a.
Temporary fix
Comments
APAR Information
APAR number
LI72700
Reported component name
DB2 EDE LINUX
Reported component ID
5724N7604
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2007-11-09
Closed date
2008-04-23
Last modified date
2008-04-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ENGN_SQX
Fix information
Fixed component name
DB2 EDE LINUX
Fixed component ID
5724N7604
Applicable component levels
Document Information
Modified date:
16 October 2021