|
Problem IC73942
|
Status: Closed |
IN VERSION 9.7 CLIENT YOU GET CLI0113E ERROR IF YOU TRY TO UPDATE A COLUMN WITH A TIMESTAMP WITH TOO LARGE PRECISION. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| 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 |
| Problem Summary: |
****************************************************************
* 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. |
| available fix packs: |
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
|
| Solution |
Upgrade to DB2 v9.7 fix pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.01.2011
19.05.2011
19.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
