DB2 - Problem description
Problem IC82337 | Status: Closed |
CONTINUATION/CANCELLATION OF ADMIN_MOVE_TABLE AFTER HADR TAKEOVER NOT POSSIBLE WITHOUT MANUAL INTERACTION | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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 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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Using ADMIN_MOVE_TABLE in HADR environment. * * DB2 9.7 GA or later * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Remove ADMIN_MOVE_TABLE LOCK manually. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
ADMIN_MOVE_TABLE LOCK will get automatically removed after a HADR takeover as it done today after a database restart. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC84562 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.03.2012 05.06.2012 05.06.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |