DB2 - Problem description
Problem IT05744 | Status: Closed |
RUNSTATS RESULTS IN DB2 CRASH WHEN USER DROPS THE EXISTING TABLE COLUMNS BETWEEN SET PROFILE AND USE PROFILE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Runstats 'USE PROFILE' option results in DB2 crash due to memory corruption. The memory corruption happens if user has set the profile with explicit column names for basic and distribution statistics collection and an 'ALTER TABLE' to drop the existing columns has been performed between SET PROFILE and USE PROFILE execution. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * See SYSROUTE APARs to see where this APAR is addressed * **************************************************************** | |
Local Fix: | |
As a workaround, user can set the profile once again after performing 'alter table drop column' ensuring only existing columns are specified in runstats set profile command. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.11.2014 09.05.2017 09.05.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.7 |