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 IT07495 Status: Closed

ADMIN_MOVE_TABLE MIGHT FAIL WITH SQL0601N

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
ADMIN_MOVE_TABLE might fail with: 
SQL0601N  The name of the object to be created is identical to 
the existing name "SYSTOOLS.ADMIN_MOVE_TABLE" of type "TABLE". 
SQLSTATE=42710 
 
This can happen when more than one ADMIN_MOVE_TABLE is being run 
on the database when this routine was never called before. When 
ADMIN_MOVE_TABLE procedure is run for the first time on given 
database, it creates protocol table ADMIN_MOVE_TABLE in SYSTOOLS 
schema as the very first step. If multiple ADMIN_MOVE_TABLE are 
started concurrently and SYSTOOLS.ADMIN_MOVE_TABLE hasn't been 
created yet, there is a small timing hole when one or more of 
those run might fail with SQL0601N error. 
This APAR will change that behavior and ADMIN_MOVE_TABLE will no 
longer fail in such scenario.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 5 or higher.            * 
****************************************************************
Local Fix:
Retry ADMIN_MOVE_TABLE
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 FixList