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 IT22587 Status: Closed

DB2LOOK FOR TIMESTAMP COLUMNS GENERATES TIMESTAMP(9) WHEN DEFINED ON DB2
FOR Z/OS

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
If you have defined TIMESTAMP columns on a DB2 for z/OS server 
and using db2look to get the definition of the tables, you may 
obtain an incorrect output as TIMESTAMP(9) instead of TIMESTAMP. 
 
for example : 
db2 "create table t1 ( col1 timestamp )" 
db2look -d dbname -t t1 -z schema -e -o db2look.out -i username 
-w password 
 
CREATE TABLE "SCHEMA"."T1" 
                ( 
                 "COL1"  TIMESTAMP (9)  DEFAULT NULL, 
                )
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Mod3 Fix Pack 3 or higher                * 
****************************************************************
Local Fix:
N/A
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in Db2 11.1 Mod3 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.09.2017
19.03.2018
19.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)