home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT01930 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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)
Lösung
Problem was first fixed in DB2 Version 10.1 and Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.05.2014
13.07.2015
13.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList