home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC91894 Status: Closed

LOG FULL DURING REORG INDEX(ES ALL) WITH THE CLEANUP ONLY ALL OPTION

product:
DB2 FOR LUW / DB2FORLUW / A10 - 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 users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.3.                             * 
****************************************************************
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 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
The problem is first fixed in DB2 version 10.1.0.3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.04.2013
01.10.2013
01.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList