|
Problem IT00883
|
Status: Closed |
COLUMN-ORGANIZED TABLE WITH WRONG DATETIME STRING SYNTAX OUTPUTS A RECORD RESULT INSTEAD OF ERROR |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Issue 1: Column-organized table with an incorrect datetime
string syntax outputs a record result instead of an error code.
For example: 2009-11-11 11-11-11 or 11:11:11
Issue 2: Column-organized table doesn't support YYYYMMDDHHMMSS
format |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* BLU table might accept wrong datetime string syntax *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to product db2 v105 fixpack 4 *
**************************************************************** |
| Local Fix: |
Do not use invalid timestamp format in the application |
| available fix packs: |
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
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.04.2014
10.09.2014
10.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
