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

CONTINUATION/CANCELLATION OF ADMIN_MOVE_TABLE AFTER HADR TAKEOVER NOT
POSSIBLE WITHOUT MANUAL INTERACTION

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Steps to reproduce: 
- issue HADR takeover while ADMIN_MOVE_TABLE is in progress. 
- on the new HADR primary calls to ADMIN_MOVE_TABLE for the same 
table may return: 
SQL2104N  The ADMIN_MOVE_TABLE procedure could not be completed 
at this time by this user.  Reason code: "9".  SQLSTATE=5UA0M
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* HADR users                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP1 or subsequent fix pack               * 
****************************************************************
Local Fix:
Workaround: 
Remove the LOCK from ADMIN_MOVE_TABLE protocol table manually. 
Then you can either continue or cancel the ADMIN_MOVE_TABLE that 
is still in progress.
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 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
13.11.2012
13.11.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