|
Problem IC64144
|
Status: Closed |
RENAME TABLE DOES NOT UPDATE SYSCAT.TABLES STATISTICS_PROFILE WITH NEW NAME |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
RENAME TABLE does not update the SYSCAT.TABLES
STATISTICS_PROFILE column with the new renamed table name. The
STATISTICS_PROFILE registers the Runstats statement when the SET
PROFILE option is specified during Runstats.
Here is an example:
db2 create table chrisjg.test (c1 int)
DB20000I The SQL command completed successfully.
db2 runstats on table TABSCHEMA.test with distribution set
profile only
DB20000I The RUNSTATS command completed successfully.
db2 select 'before',char(tabschema,20) as sch, char(tabname,20)
as tab, substr(statistics_profile,1,40) as stat_profile from
syscat.tables where tabschema='TABSCHEMA'
1 SCH TAB STAT_PROFILE
------ -------------------- --------------------
----------------------------------------
before TABSCHEMA TEST RUNSTATS ON
TABLE "TABSCHEMA"."TEST" ON AL
1 record(s) selected.
db2 rename table TABSCHEMA.test to zzz
DB20000I The SQL command completed successfully.
db2 select 'after rename',char(tabschema,20) as sch,
char(tabname,20) as tab, substr(statistics_profile,1,40) as
stat_profile from syscat.tables where tabschema='TABSCHEMA'
1 SCH TAB
STAT_PROFILE
------------ -------------------- --------------------
----------------------------------------
after rename TABSCHEMA ZZZ
RUNSTATS ON TABLE "TABSCHEMA"."TEST" ON AL
1 record(s) selected.
: |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 Version 9.7 GA through Fix Pack 1 servers *
* onLinux,Unix and Windows platforms issuing RENAME *
* TABLEstatements. *
****************************************************************
* PROBLEM DESCRIPTION: *
* There was missing functionality in *
* updatingtheSTATISTICS_PROFILE column of the *
* catalogtableSYSIBM.SYSTABLES during a RENAME TABLE *
* statement,henceleaving the old table name in the profile. *
****************************************************************
* RECOMMENDATION: *
* Apply DB2 Version 9.1 Fix Pack 2, or re-run *
* RUNSTATScommandas noted in the local fix. *
**************************************************************** |
| Local Fix: |
Re-issue a Runstats command after RENAME TABLE with the SET
PROFILE option to re-initialize this field and gather the most
up-to-date statistics. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 Version 9.7 Fix Pack 2 and all
subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.10.2009
31.05.2010
31.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP2,
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
