DB2 FOR LUW / DB2FORLUW / 970 - DB2

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).

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 FP9.                                     * 
****************************************************************

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.

DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Fixed in DB2 v9.7 FP9.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC91894 IC95277 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

21.03.2013
23.12.2013
23.12.2013

9.7.FP9