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

IN VERSION 9.7 CLIENT YOU GET CLI0113E ERROR IF YOU TRY TO UPDATE A COLUMN
WITH A TIMESTAMP WITH TOO LARGE PRECISION.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
After upgrade to DB2 version 9.7 client you get CLI0113E error, 
with SQLSTATE 22007, if you try to update the database with a 
timestamp value with larger precision than what the column 
allow. 
 
With DB V9.5 client if you try to update/insert a column with 
timestamps that have a larger precision than what the column in 
the database allow the timestamp value will be truncated and 
inserted. For example a timestamp like this 
2010-12-01-08:57:25.1294461968 will be truncated to 
2010-12-01-08.57.25.129446 and then inserted successfully. With 
DB2 V9.7 client this doesn't work. On version 9.7 you will get 
errors looking like this: 
 
[IBM][CLI Driver] CLI0113E SQLSTATE 22007: An invalid 
datetime format was detected; that is, an invalid string 
representation or value 
was specified. SQLSTATE=22007
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users that use timestamps that have a larger precision than  * 
* what the column have in the database.                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* After upgrade to DB2 version 9.7 client you get CLI0113E     * 
* error,                                                       * 
* with SQLSTATE 22007, if you try to update the database with  * 
* a                                                            * 
* timestamp value with larger precision than what the column   * 
*                                                              * 
* allow.                                                       * 
*                                                              * 
*                                                              * 
*                                                              * 
* With DB V9.5 client if you try to update/insert a column     * 
* with                                                         * 
* timestamps that have a larger precision than what the column * 
* in                                                           * 
* the database allow the timestamp value will be truncated and * 
*                                                              * 
* inserted. For example a timestamp like this                  * 
*                                                              * 
* 2010-12-01-08:57:25.1294461968 will be truncated to          * 
*                                                              * 
* 2010-12-01-08.57.25.129446 and then inserted successfully.   * 
* With                                                         * 
* DB2 V9.7 client this doesn't work. On version 9.7 you will   * 
* get                                                          * 
* errors looking like this:                                    * 
*                                                              * 
*                                                              * 
*                                                              * 
* [IBM][CLI Driver] CLI0113E SQLSTATE 22007: An invalid        * 
*                                                              * 
* datetime format was detected; that is, an invalid string     * 
*                                                              * 
* representation or value                                      * 
*                                                              * 
* was specified. SQLSTATE=22007                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 fix pack 4.                              * 
****************************************************************
Local-Fix:
Change the database column to accept larger timestamps values or 
rewrite the application to use less precision.
verfügbare FixPacks:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Upgrade to DB2 v9.7 fix pack 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.01.2011
19.05.2011
19.05.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList