|
Problem IT01930
|
Status: Closed |
DB2LOOK GENERATES INCORRECT SYNTAX FOR DISTINCT TYPE IF IT IS SOURCED FROM TIMESTAMP DATATYPE |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - 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 10.1 and Fix Pack 5 *
**************************************************************** |
| 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 |
Problem was first fixed in DB2 Version 10.1 and Fix Pack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.05.2014
13.07.2015
13.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
