DB2 - Problem description
Problem IC89688 | Status: Closed |
ATM FAILED TO REORG SOME INDEXES WHICH EXCEEDED F4 AND F5 UNDER DB2_WORKLOAD=SAP | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Automatic Table Maintenance failed to reorg some indexes which exceeded F4 and F5 formula when DB2_WORKLOAD=SAP is set. In db2diag.log you might see REORG started messages: 2013-01-10-08.00.00.681617+060 I125863A374 LEVEL: Event PID : 60359078 TID : 1177 PROC : db2acd 0 INSTANCE: db2inst1 NODE : 000 EDUID : 1177 EDUNAME: db2acd 0 FUNCTION: DB2 UDB, Automatic Table Maintenance, db2AutoReorgExec, probe:10 START : Automatic reorg has started on table DB1 ."SAP "."DB6HISTBS" but there is never a matching ' Automatic reorg has completed successfully on table ...' and also no sign of an error. You will see such tables will be repeatable scheduled for automatic reorg. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 9. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7 Fix Pack 9. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC94959 IC95518 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.01.2013 17.12.2013 17.12.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.9 | |
9.7.0.9 |