|
Problem IC89202
|
Status: Closed |
ADDING A MEMBER/CF USING DB2IUPDT -ADD MAY GENERATE AN ERROR IN THE DB2IUPDT LOG |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When adding a member/CF using the command "db2iupdt -add" in a
DB2 pureScale environment, you may observe an error "ERROR: An
error occurred while configuring the instance" in the db2iupdt
log closing to the end of the installation.
For example, below are the messages extracted from the db2iupdt
log:
<db2iupdt log>
....
ERROR: An error occurred while configuring the instance
"db2inst1".
The shared file system cluster has been setup properly for DB2
usage.
Configuring DB2 instances :.......Failure
Updating global profile registry :.......Success
Post Install Recommendations
-----------------------------
Required steps:
There were some errors detected during DB2 installation. To
collect the information files from the system, run the
"db2support -install" command with the proper options before
reporting the problem to IBM service. For information regarding
the usage of the db2support tool, check the DB2 Information
Center.
...
</db2iupdt log>
The error occurs because DB2 installer was attempting to update
the dbm cfg parameter SVCENAME using an empty string value. The
issue has been seen occurring when
1) a pureScale instance was manually created and then the dbm
cfg parameter SVCENAME was manually set to a port number rather
than a service name, and
2) there was no mapping in the /etc/services from the port
number to a service name when db2iupdt -add was run.
Although the error was reported in the db2iupdt log, it can be
ignored as the member/CF should have already been successfully
added and the functionality of the instance won't be affected. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 4 or newer *
**************************************************************** |
| Local Fix: |
To avoid the error:
1) update the dbm cfg SVCENAME to use a service name, instead of
the port number before running db2iupdt -add
2) Or alternatively, adding a mapping from the port number to a
service name in /etc/service before running db2iupdt -add. |
| 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 DB2 Version 10.1 Fix Pack 4 |
| Workaround |
See above Local Fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.12.2012
11.02.2014
11.02.2014 |
| 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
|
|
