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

DB2LOOK GENERATES INCORRECT SYNTAX FOR DISTINCT TYPE IF IT IS SOURCED FROM
TIMESTAMP DATATYPE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A db2look tool generates incorrect syntax for DISTINCT TYPE if 
it is sourced from TIMESTAMP datatype. 
As a consequence output generated with db2look, if DISTINCT TYPE 
was defined with TIMESTAMP usage, might report error during 
loading this data.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 10                       * 
****************************************************************
Local Fix:
Manual fix of extracted previously DDL statements with db2look 
utility is needed in order to prevent DB21034E error during 
loading inappropriate DDL. 
For example statement: 
  CREATE DISTINCT TYPE "MYSCHEMA"."MYTYPE" AS "SYSIBM 
".TIMESTAMP(10,6) 
can be changed to proper one: 
  CREATE DISTINCT TYPE "MYSCHEMA"."MYTYPE" AS "SYSIBM 
".TIMESTAMP(6)
Solution
Fixed in DB2 Version 9.7 Fix Pack 10
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.05.2014
19.12.2014
19.12.2014
Problem solved at the following versions (IBM BugInfos)
9.7.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.10 FixList