DB2 FOR LUW / DB2FORLUW / A10 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 5 or higher.            * 
****************************************************************

Do not use COPY_USE_LOAD or enable COPY_WITH_INDEXES option

Problem first fixed in DB2 version 10.1 Fix Pack 5.

keiner bekannt / siehe Local-Fix

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

04.03.2015
13.07.2015
13.07.2015