|
Problem IT07497
|
Status: Closed |
ADMIN_MOVE_TABLE WITH COPY_USE_LOAD AND WITHOUT COPY_WITH_INDEXE S LOADS DATA AND BUILDS ALL INDEXES IN ONE TRANSACTION |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When ADMIN_MOVE_TABLE is run with COPY_USE_LOAD and without
COPY_WITH_INDEXES, target table with primary key (if applicable)
is created, loaded an all indexes built in a single transaction.
When source table has multiple indexes, it will consume
signification transactional log space and my eventually fail
with -964 "transactional log full" error.
This APAR will change this behavior and transaction will be
committed after LOAD phase and index rebuilt phase will be
continued in a separate transaction. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1 Fix Pack 5 or higher. *
**************************************************************** |
| Local Fix: |
Do not use COPY_USE_LOAD or enable COPY_WITH_INDEXES option |
| Solution |
Problem first fixed in DB2 version 10.1 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.03.2015
13.07.2015
13.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
