|
Problem IC73903
|
Status: Closed |
ADMIN_MOVE_TABLE CAN RUN OUT OF ACTIVE LOG SPACE IF COPY_USE_LOAD SPECIFIED |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When using ADMIN_MOVE_TABLE the use of the option COPY_USE_LOAD
can cause transaction log full, because of the way DB2 LOAD
works.
(DB2 LOAD creates log records that are not committed. If other
transactions create a huge amount of log records, the database
can run into a transaction log full situation during LOAD. ) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See problem description above *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.7 Fixpack 4 *
**************************************************************** |
| Local Fix: |
Avoid specifying the COPY_USE_LOAD option to avoid this problem |
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
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
|
| Solution |
First fixed in DB2 V9.7 Fixpack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.01.2011
17.06.2011
17.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
