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

TO_CHAR CAN NOT HANDLE AM, MERIDIAN INDICATOR (MORNING OR EVENING)
CORRECTLY IN MULTI-BYTE ENVIRONMENTS.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Problem Reproducible Steps: 
On AIX. 
1.  db2 terminate 
2.  db2stop 
3.  export TZ=xxx ; see below Results 
4.  export LANG=xxx ; see below Results 
5.  db2start 
6.  db2 create db <testdb> 
7.  db2 connect to <testdb> 
8.  db2 "values TO_CHAR('2010-12-28-16.52.39.274000','AM')" 
    ==> should return 'PM' because 16.52 is PM. 
    ==> but it returns 'AM' incorrectly in some cases. 
9.  db2 terminate 
10. db2 drop db <testdb> 
 
Results: 
----------------------------------------------------------- 
LANG/TZ|JST-9|EST5EDT|JST-9JSTDT|KORST-9KORDT|TAIST-8TAIDT 
----------------------------------------------------------- 
Ja_JP  | AM  |  PM   |  AM      |   ..       |      .. 
en_US  | PM  |  PM   |  PM      |   ..       |      .. 
C      | PM  |  PM   |  PM      |   ..       |      .. 
ko_KR  | ..  |  ..   |  ..      |   AM       |      .. 
zh_TW  | ..  |  ..   |  ..      |   ..       |      AM 
----------------------------------------------------------- 
 
* On Windows 2008/ Windows 7 (Japanese multi-byte environment) 
  without setting TZ/LANG, it returns AM incorrectly. 
* On AIX, if we use TO_CHAR('2010-12-28-16.52.39.274000', 
  'A.M.')" instead of 'AM', it always returns 'P.M.' 
  expectedly. This may be a workaround for some users. 
* JST-9 is used in most of all AIX Japanese environment.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 10.2                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 FixPack 2.                           * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
Problem was first fixed in DB2 UDB Version 10.1 FixPack 2.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.07.2012
19.12.2012
19.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList