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 IC99559 Status: Geschlossen

INGEST INCORRECTLY TRUNCATES FRACTIONS BEYOND TIMESTAMP(6), WHEN NO FORMAT
IS SPECIFIED BY INGEST.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When INGEST reads TIMESTAMP values from the input source, a 
format can be specified to the TIMESTAMP field on the INGEST 
field list. 
If the TIMESTAMP field format is not specified, then INGEST 
wrongly truncates a TIMESTAMP value to precision 6 (SQL3131W), 
if the TIMESTAMP value has a precision greater than 6. 
 
Example: 
 
Input data (data.del): 
1111-10-2-23.00.00.000000123456 
2222-10-2-23.00.00.000123456789 
3333-10-2-23.00.00.001234567 
 
Test: 
CREATE TABLE T1( C1 TIMESTAMP(12) ) 
 
INGEST FROM FILE data.del FORMAT DELIMITED ($field1 TIMESTAMP) 
RESTART OFF INSERT INTO T1(C1) VALUES($field1) 
 
SQL2922I  The following warning or error occurred while 
formatting data from 
line "1" of input file "data.del". 
SQL3131W  The field containing "1111-10-2-23.00.00.000000123456" 
in row "1" and 
column "1" was truncated into a TIMESTAMP field because the data 
is longer 
than the database column. 
 
SQL2922I  The following warning or error occurred while 
formatting data from 
line "2" of input file "data.del". 
SQL3131W  The field containing "2222-10-2-23.00.00.000123456789" 
in row "2" and 
column "1" was truncated into a TIMESTAMP field because the data 
is longer 
than the database column. 
 
SQL2922I  The following warning or error occurred while 
formatting data from 
line "3" of input file "data.del". 
SQL3131W  The field containing "3333-10-2-23.00.00.001234567" in 
row "3" and 
column "1" was truncated into a TIMESTAMP field because the data 
is longer 
than the database column. 
 
Output: 
SELECT C1 FROM T1 ORDER BY C1 
 
C1 
---------------------------------------- 
1111-10-2-23.00.00.000000000000 
2222-10-2-23.00.00.000123000000 
3333-10-2-23.00.00.001234000000
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW, INGEST command.                                     * 
* Serial, DPF, SD or in any mode.                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v 10.5 FP4.                                       * 
****************************************************************
Local-Fix:
The INGEST command must set by default the precision the maximum 
(12). This way, the values ingested into the table will adhere 
to the precision defined on the target table column. 
 
CREATE TABLE T1( C1 TIMESTAMP(12) ) 
 
INGEST FROM FILE data.del FORMAT DELIMITED ($field1 TIMESTAMP) 
RESTART OFF INSERT INTO T1(C1) VALUES($field1) 
 
Output: 
SELECT C1 FROM T1 ORDER BY C1 
 
C1 
---------------------------------------- 
1111-10-2-23.00.00.000000123456 
2222-10-2-23.00.00.000123456789 
3333-10-2-23.00.00.001234567000
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
When INGEST reads TIMESTAMP values from the input source, a 
format can be specified to the TIMESTAMP field on the INGEST 
field list. 
If the TIMESTAMP field format is not specified, then INGEST sets 
default precision to the maximum (i.e. 12). This way, the values 
ingested into the table will adhere 
to the precision defined on the target table column, rather than 
wrongly truncates a TIMESTAMP value to precision 6 (SQL3131W), 
when the TIMESTAMP value has a precision greater than 6.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.02.2014
09.09.2014
09.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList