Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT07496 Status: Geschlossen

ADMIN_MOVE_TABLE MIGHT FAIL WITH SQL0601N

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 Fix Pack 7 or higher.            * 
****************************************************************
Local-Fix:
Retry ADMIN_MOVE_TABLE
Lösung
Problem first fixed in DB2 version 10.5 Fix Pack 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.03.2015
28.01.2016
28.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList