home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC84412 Status: Closed

IF ADMIN_MOVE_TABLE WITH CANCEL OPTION IS INTERRUPTED SUBSEQUENT CANCEL
WILL FAIL WITH SQL2104N RC=8

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If a call to sysproc.admin_move_table with an action to CANCEL 
is interrupted via CTRL C, and the command is re-issued again, 
it would fail with SQL2104N Rc=8.  This fix would make sure 
that a subsequent admin_move_table does not fail with this 
error and proceeds. 
. 
for example: 
. 
db2 "call sysproc.admin_move_table('schema1','tab1',tab1_new', 
'keep,copy_with_indexes,'CANCEL')" 
. 
And you interrupt this action and re-issue again the table 
would be stuck in this phase and no reorg/loads etc. would 
be possible against the original table.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using ADMIN_MOVE_TABLE function.                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP1 or subsequent fix pack.              * 
****************************************************************
Local Fix:
Do not cancel the cancel phase and let it complete.  It may 
take a bit of time for it to complete depending on how large 
the table is in this case. 
. 
If this happens and the state of the table is stuck in this 
phase, no subsequent loads/reorgs would be possible on the origi 
nal table and you would need to recreate the original table 
again.
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem First Fixed in DB2 Version 10.1 FP1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
07.12.2012
07.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList