DB2 - Problem description
Problem IT19733 | Status: Closed |
LONG RUNNING ADMIN_MOVE_TABLE SWAP PHASE DUE TO STATISTICS COLLECTION | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
It is possible that the runstats for the target table first run in the swap phase extending this phase. You can observe the following: - statistics collection gets performed for volatile tables - COPY_USE_LOAD does not collect statistics if target is row-based table - the RUNSTATS executed by ADMIN_MOVE_TABLE is issued without sampling | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 10.5 Fix Pack 9 or higher * **************************************************************** | |
Local Fix: | |
If you move volatile tables, use NO_STATS option to avoid statistics collection during SWAP phase. If you use COPY_USE_LOAD to a row-based target, apply a statistics profile to the source table before starting the move. Then LOAD will collect the statistics. If you want to avoid RUNSTATS while SWAP, then issue a RUNSTATS manually before entering the SWAP phase. | |
Solution | |
First fixed in Db2 10.5 Fix Pack 9 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 16.03.2017 29.09.2017 29.09.2017 |
Problem solved at the following versions (IBM BugInfos) | |
9.0. | |
Problem solved according to the fixlist(s) of the following version(s) |