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 IC98154 Status: Closed

INSTANCE CREATION, UPGRADE, UPDATE FAILS IF UNABLE TO RESERVE 4 PORTS IN
/ETC/SERVICES FOR AN ESE INSTANCE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
During instance configuration (create/update/upgrade) the 
configuration will fail if it is not able to reserve a range of 
4 ports in /etc/services for an ESE instance and below error 
message appears in the log 
 
"The requested port number conflicts with existing values that 
have been previously specified."
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 10.1 fp3 and below                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Move to fp4                                                  * 
****************************************************************
Local Fix:
Customers can manually add these ports if necessary after 
instance configuration.
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Fixed in fp4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.12.2013
06.04.2015
06.04.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList
10.5.0.4 FixList