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

ADMIN_MOVE_TABLE CAN FAILS DURING CLEANUP WITH SQL0204N

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
ADMIN_MOVE_TABLE CAN FAILS DURING CLEANUP WITH 
SQL0204N 
 
You can get the following: 
 
SQL0204N  "JSEIFERT.STAFFAAWIWmo" is an undefined name. 
SQLSTATE=42704 
 
 
db2start 
db2sampl 
db2 connect to sample 
db2 create table JSEIFERT.STAFF2 like JSEIFERT.STAFF 
db2 "CALL SYSPROC.ADMIN_MOVE_TABLE('JSEIFERT', 'STAFF', 
'STAFF2', '', 'INIT')" 
db2 "CALL SYSPROC.ADMIN_MOVE_TABLE('JSEIFERT', 'STAFF', '', '', 
'COPY')" 
db2trc on -crash DB2.DBAPPEXT_UTIL.adminotm_Otm_cleanup.entry 
db2 "CALL SYSPROC.ADMIN_MOVE_TABLE('JSEIFERT', 'STAFF', '', '', 
'SWAP,TRACE')" 
db2trc off 
db2start 
db2 connect to sample 
db2 'drop table JSEIFERT."STAFFAAWIWmo"' 
db2 "CALL SYSPROC.ADMIN_MOVE_TABLE('JSEIFERT', 'STAFF', '', '', 
'CLEANUP,TRACE')"
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.1 Fixpack 6 or Later.                 * 
****************************************************************
Local Fix:
Solution
First Fixed in DB2 LUW v10.1 Fixpack 6.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.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