DB2 - Problem description
Problem IC97967 | Status: Closed |
ADMIN_MOVE_TABLE GETS SLOWER IF PROTOCOL TABLE GETS LARGE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
ADMIN_MOVE_TABLE gets slower after moving a large number of tables. The root cause is inefficient SQL access to the protocol table. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All DB2 V9.7 users. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.7 Fix Pack 10 or higher. * **************************************************************** | |
Local Fix: | |
Workaround: delete all protocol entries of complete moves. DELETE FROM SYSTOOLS.ADMIN_MOVE_TABLE S1 WHERE EXISTS(SELECT 1 FROM SYSTOOLS.ADMIN_MOVE_TABLE S2 WHERE S1.tabschema = S2.tabschema AND S1.tabname = S2.tabname AND S2.key = 'STATUS' AND S2.value IN ('COMPLETE','COMPLETE_WITH_WARNINGS')) | |
Solution | |
First fixed in DB2 V9.7 Fix Pack 10. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.11.2013 13.11.2014 13.11.2014 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.10 |