DB2 - Problem description
Problem IC91020 | Status: Closed |
LOG FULL DURING REORG INDEX(ES ALL) WITH THE CLEANUP ONLY ALL OPTION | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When running REORG INDEX(ES ALL) with the CLEANUP ONLY ALL option, DB2 will issue an internal commit after each index is cleaned. However, when dealing with very large indexes on a volatile database (i.e. a database that writes a large amount of data to the database transaction logs), this may not be frequent enough. If all of the active log space is consumed, then applications writing to this database may fail with log full error (SQLCODE SQL0964C). | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.7 FP9. * **************************************************************** | |
Local Fix: | |
Configure the database to allow more active log files. For example, you can enable infinite active logspace by setting the LOGSECOND database configuration parameter to -1. For more information on database logging, see the document titled "Configuration parameters for database logging" in the DB2 Information Center. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
Fixed in DB2 v9.7 FP9. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC91894 IC95277 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.03.2013 23.12.2013 23.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 |