|
Problem IC95277
|
Status: Closed |
LOG FULL DURING REORG INDEX(ES ALL) WITH THE CLEANUP ONLY ALL OPTION |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - 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: *
* Update to 10.5.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.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem Fixed In 10.5.0.3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2013
04.03.2014
04.03.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
