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

DB2ICRT COMMAND SKIPS SOME OPEN PORTS RANGE IN /ETC/SERVICES DURING FCM
PORTS RESERVATION

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 tries to find the first four available ports after 60000 
and reserves them in /etc/services file for db2 FCM operation on 
creating an instance through db2icrt command. 
 
  But its command sometimes skips the open ports range and tries 
to reserve the next available ports.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 FixPack 4                            * 
****************************************************************
Local Fix:
Manually rearrange the open ports reservation in /etc/services 
for db2 FCM process and recycle the instance.  "netstat -na" and 
"grep" commands can be useful for checking the open ports.
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 FixPack 4
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC99238 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.10.2013
02.06.2014
02.06.2014
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