DB2 FOR LUW / DB2FORLUW / B10 - DB2

If admin_move_table is called and COPY phase fails, the target
table might be left in LOAD PENDING status.
After the root cause (e.g. lack of diskspace, utill_heap_sz,
etc) for getting into the LOAD PENDING status has been removed,
ADMIN_MOVE_TABLE can be restarted with the COPY operation.

In case of a columnar target table, the restarted AMT COPY
operation might fail with SQL0668 while truncating the target
table. This is because the LOAD PENDING status is not
automatically fixed by AMT like in other similar situations.
This fix implements an automatic LOAD TERMINATE command and
retries the truncation of the target table, if such a situation
happens.

Alternatively, the user can manually issue the LOAD TERMINATE
command if such a situation happens.
e.g.:

CALL
SYSPROC.ADMIN_MOVE_TABLE(','',''
,'ALLOW_READ_ACCESS','INIT')
CALL
SYSPROC.ADMIN_MOVE_TABLE(','',''
,'ALLOW_READ_ACCESS','COPY')

*** The ADMIN_MOVE_TABLE copy step is interrupted and fails when
it is repeated ***

CALL
SYSPROC.ADMIN_MOVE_TABLE(','',''
,'ALLOW_READ_ACCESS','COPY')
SQL0668N  Operation not allowed for reason code "3" on table
".".  SQLSTATE=57016

*** Manually issue a LOAD TERMINATE command on the target table
***

LOAD FROM /dev/null of del TERMINATE INTO
"".""

*** The ADMIN_MOVE_TABLE copy step can be repeated ***

CALL
SYSPROC.ADMIN_MOVE_TABLE(','',''
,'ALLOW_READ_ACCESS','COPY')

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************

Manually issue a LOAD TERMINATE command on the target table if
such a situation happens. Refer to the error description to see
an example.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

26.10.2018
16.01.2020
16.01.2020