|
Problem IT00883
|
Status: Geschlossen |
COLUMN-ORGANIZED TABLE WITH WRONG DATETIME STRING SYNTAX OUTPUTS A RECORD RESULT INSTEAD OF ERROR |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* 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 |
| 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 |
|
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 07.04.2014
10.09.2014
10.09.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.4
|
 |
