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

SHAPEFILE IMPORT AFTER SHAPEFILE EXPORT OF TIME AND TIMESTAMP VALUES
FAILS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The shapefile specification doesn't include support for TIME or 
TIMESTAMP fields.  When columns of these types are exported to a 
shapefile, the fields are exported as CHAR. 
 
If the user attempts to reload this data into a table with TIME 
and TIMESTAMP fields, it will fail with a message about 
incompatible types. This is an example message: 
GSE2106N  The data type of the column 
"DB2SE_FVT"."TIMETEST"."TIME_FIELD" is ""SYSIBM"."TIME"", which 
does 
not match the expected type ""SYSIBM"."VARCHAR"" for the data to 
be 
imported from file. 
 
We do not document this limitation and it is 
reasonable for the customer to expect that data which our 
utility exports should be importable. 
 
Import of CHAR fields into TIME and TIMESTAMP fields should be 
allowed to avoid this customer problem.  DB2 will do the 
appropriate conversions.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Spatial extender users working with TIME and/or TIMESTAMP    * 
* columns which need to be exported and then imported          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The shapefile specification doesn't include support for TIME * 
* or                                                           * 
* TIMESTAMP fields.  When columns of these types are exported  * 
* to a                                                         * 
* shapefile, the fields are exported as VARCHAR.               * 
*                                                              * 
*                                                              * 
*                                                              * 
* If the user attempts to reload this data into a table with   * 
* TIME                                                         * 
* and TIMESTAMP fields, it will fail with a message about      * 
*                                                              * 
* incompatible types. This is an example message:              * 
* GSE2106N  The data type of the column                        * 
* "DB2SE_FVT"."TIMETEST"."TIME_FIELD" is ""SYSIBM"."TIME"",    * 
* which does                                                   * 
* not match the expected type ""SYSIBM"."VARCHAR"" for the     * 
* data to be                                                   * 
* imported from file.                                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 FP3                                          * 
****************************************************************
Local Fix:
The work around is to create a table like the table to be 
imported into but creating CHAR columns instead of TIME and 
TIMESTAMP colums.  Import into this table and then select from 
this table and import into the desired target table.
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Upgrade to V9.7 FP3
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC69127 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.03.2010
16.09.2010
16.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList