| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IT25342 | Status: Closed |
ADMIN_MOVE_TABLE FORCE_ALL DOES NOT FORCE OFF APPLICATIONS HOLDING OTHER CONFLICTING LOCKS THAN TABLE LOCKS | |
| product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
| Problem description: | |
CREATE TABLE S1.T1(INT I NOT NULL, primary key(i)); Session 1: CREATE PROCEDURE S1.P1 INSERT INTO S1.T1 VALUES(1); -- NO COMMIT Session 1 holds now a package cache lock. Session 2: CALL ADMIN_MOVE_TABLE(S1,T1,'','','INIT'); CALL ADMIN_MOVE_TABLE(S1,T1,'','','COPY'); CALL ADMIN_MOVE_TABLE(S1,T1,'','FORCE_ALL','SWAP'); ADMIN_MOVE_TABLE hangs in package invalidation until lock timeout occurs. Expected behavior when using FORCE_ALL option is that session 1 fails and ADMIN_MOVE_TABLE completes without waiting for session 1 to complete. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ADMIN_MOVE_TABLE users that using FORCE_ALL option. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to next fixpack. * **************************************************************** | |
| Local Fix: | |
| Solution | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.06.2018 19.06.2018 19.06.2018 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
