|
Problem IC84154
|
Status: Closed |
LOAD CAN INSERT WRONG DATE VALUES AND / OR FAIL WITH SQL0181N |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
LOAD can insert wrong DATE vales and/or fail with SQL0181N, when
the following conditions are met:
* different client/server locale setting
* DPF environment with several nodes (at least 3):
* catalog node
* data node where the table resides
* coordinator node, where LOAD connects to
* LOAD data with DATE values in client locale format |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 1. *
**************************************************************** |
| Local Fix: |
The wrong DATE value conversion can be avoided with one of the
following workarounds:
* connect with LOAD coordinator to catalog node directly
* do a simple SELECT before the actual LOAD
* use LOAD option MODIFIED BY DATEFORMAT |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.06.2012
05.11.2012
05.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
