home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC75187 Status: Closed

THE VALUE OF THE ALTER_TIME COLUMN OF SYSCAT.TABLES IS NOT CHANGED AFTER
ALTER TABLE DDL IS RUN

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
After an alter table DDL is run, the value of the alter_time 
column of syscat.tables may be not changed accordingly. 
 
For example: 
 
> db2 "create table TEST1(c1 char(10))" 
DB20000I  The SQL command completed successfully. 
 
 
>date 
Tue Feb 22 08:38:35 CST 2011 
 
 
>db2 "select create_time, alter_time from syscat.tables where 
TABNAME='TEST1'" 
 
 
CREATE_TIME                ALTER_TIME 
 
-------------------------- -------------------------- 
 
2011-02-22-08.38.29.354479 2011-02-22-08.38.29.354479 
 
 
 
  1 record(s) selected. 
 
 
 
>date 
Tue Feb 22 08:39:18 CST 2011 
 
//add a column here using alter table DDL 
>db2 "alter table TEST1 add column c2 char(10)" 
DB20000I  The SQL command completed successfully. 
 
 
>db2 "select create_time, alter_time from syscat.tables where 
TABNAME='TEST1'" 
 
 
CREATE_TIME                ALTER_TIME 
 
-------------------------- -------------------------- 
 
2011-02-22-08.38.29.354479 2011-02-22-08.38.29.354479 
 
 
//As the above shows, the timestamp value for ALTER_TIME column 
was still 2011-02-22-08.38.29.354479, which should have been 
changed. 
 
 
This issue only occurs in V9.7 or later, it doesn't occur in 
V9.5 version.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5                        * 
****************************************************************
Local Fix:
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in Version 9.7 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.03.2011
21.12.2011
21.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList