|
Problem IC86862
|
Status: Closed |
DB2ICRT -P OPTION DOES NOT UPDATE THE SVCENAME CONFIGURATION PARAMETER WHEN PORT NUMBER IS A NUMERIC VALUE |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
db2icrt -p option does not update the SVCENAME configuration
parameter when port number used is a numeric value
./db2icrt -a server -u db2fenc1 -p DB2_db2inst1 db2inst1
The above command successfully updates the SVCENAME dbm cfg
parameter as expected
TCP/IP Service name (SVCENAME) =
DB2_db2inst1
But if we use a numeric value for the port number the parameter
does not get updated
./db2icrt -a server -u db2fenc1 -p 60008 db2inst1
TCP/IP Service name (SVCENAME) =
Trace shows that we do not enter the following function
## Entering: set_portnum
## Exiting: set_portnum |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Db2 V10.1 FP2 and below *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V10.1 FP3 *
**************************************************************** |
| Local Fix: |
Manually update the configuration parameter SVCENAME |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in V10.1 FP3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.09.2012
04.10.2013
04.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
