home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT05801 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use db2prereqchk in non-English AIX systems.       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V10.1 FixPack 5 or later.              * 
****************************************************************
Local Fix:
Please set LANG=C before running db2prereqcheck, for example: 
export LANG=C 
db2prereqcheck
Solution
This problem was first fixed in DB2 V10.1 FixPack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.11.2014
14.07.2015
14.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList