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

DB2PREREQCHECK MIGHT REPORT DBT3589W EVEN IF IOCP IS AVAILABLE IN LOCALES
OTHER THEN ENGLISH.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
The db2prereqcheck utility might report DBT3589W even if IOCP is 
available in locales other then English. 
 
The following steps illustrate the problem. 
 
1. Set LANG to non-English locale, for example: 
export LANG=Ja_JP 
note: the target locale needs to be installed on the machine. 
 
2. Run db2prereqcheck 
./db2prereqcheck 
Validating "IOPORTS" ... 
The input/output completion Port (IOCP) is installed on host 
"host1". 
DBT3589W  The db2prereqcheck utility failed to validate that the 
IOCP is enabled on the following host machine: "host1".
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use db2prereqchk in non-English AIX systems.       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V10.5 FixPack 7 or later.              * 
****************************************************************
Local-Fix:
Please set LANG=C before running db2prereqcheck, for example: 
export LANG=C 
db2prereqcheck
Lösung
This problem was first fixed in DB2 V10.5 FixPack 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.04.2015
03.02.2016
03.02.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList