DB2 - Problembeschreibung
Problem IC62133 | Status: Geschlossen |
SQL10007N RC 5 ERROR WHEN CONNECTING TO A TURKEY TERRITORY DB AFTER OS LOCALE IS CHANGED TO TR_TR | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
Connecting to a database created with Turkey territory results in error SQL10007N Message "-1390" RC 5 when we change the OS locale to tr_TR from en_US Steps to recreate ------------------------ db2start db2 create db <dbname> using codeset utf-8 territory tr db2stop db2 terminate export LANG=tr_TR db2start db2 connect to db1254 SQL10007N Message "-1390" could not be retrieved. Reason code: "5". | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users prior to DB2 V9.5 FP 6 * **************************************************************** * PROBLEM DESCRIPTION: * * Connecting to a database created with * * Turkeyterritoryresultsin error SQL10007N Message "-1390" RC * * 5 whenwe change theOSlocale to tr_TR from en_USSteps * * torecreate------------------------db2startdb2 create * * db<dbname> using codeset utf-8 territory * * trdb2stopdb2terminateexport LANG=tr_TRdb2startdb2 connect * * todb1254SQL10007N Message "-1390" could not be * * retrieved.Reasoncode:"5". * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.5 FP6 * **************************************************************** | |
Local-Fix: | |
Workaround is to use a non-turkish locale, such as en_US | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Lösung | |
First Fixed in V9.5 FP6 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC62315 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 21.07.2009 22.06.2010 22.06.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP6 | |
Problem behoben lt. FixList in der Version |