DB2 - Problem description
Problem IC73775 | Status: Closed |
SYSPROC.ADMIN_MOVE_TABLE MIGHT HANG IF YOU RUN IT MORE THAN ONCE CONCURRENTLY | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
The procedure SYSPROC.ADMIN_MOVE_TABLE might hang if all the following conditions are true: - Multiple SYSPROC.ADMIN_MOVE_TABLE operations run concurrently. - The operation parameter of at least one concurrent run of SYSPROC.ADMIN_MOVE_TABLE is SWAP or CLEANUP. - The operation parameter of at least one other concurrent run of SYSPROC.ADMIN_MOVE_TABLE is INIT, SWAP or CLEANUP. This defect might cause the SAP tool DB6CONV to hang because DB6CONV runs SYSPROC.ADMIN_MOVE_TABLE more than once concurrently. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of DB2 for Linux, UNIX and Windows * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * The fix for APAR IC73734, which describes the same defect * * for DB2 9.7, is in DB2 9.7 fixpak 4 and above. * **************************************************************** | |
Local Fix: | |
To prevent any possibility of the problem happening you can avoid running SYSPROC.ADMIN_MOVE_TABLE with the SWAP or CLEANUP operation at the same time as SYSPROC.ADMIN_MOVE_TABLE is running concurrently with the INIT, SWAP or CLEANUP operation. | |
Solution | |
module: dbappext. Permanent restriction | |
Workaround | |
To prevent any possibility of the problem happening you can avoid running SYSPROC.ADMIN_MOVE_TABLE with the SWAP or CLEANUP operation at the same time as SYSPROC.ADMIN_MOVE_TABLE is running concurrently with the INIT, SWAP or CLEANUP operation. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.01.2011 24.05.2011 24.05.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
Problem solved according to the fixlist(s) of the following version(s) |