|
Problem IC62498
|
Status: Closed |
DB2IUPDT FAILS TO UPDATE 9.7 INSTANCE WHEN DB2RSHCMD IS USING SSH. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
db2iupdt fails to update a 9.7 instance in DPF environment,
db2iupdt fails to recognize DB2RSHCMD is set to use ssh,
instead it uses rsh. Once db2iupdt finishes, the instance
profile is corrupted.
> ./db2iupdt -u db2fenc2 db2inst2
/opt/ibm/db2/V9.7/instance/db2iutil: line 5682: [:
integer expression expected
trying normal rsh (/usr/bin/rsh)
machine_name.domain.com: Connection refused
trying normal rsh (/usr/bin/rsh)
machine_name.domain.com: Connection refused
trying normal rsh (/usr/bin/rsh)
machine_name.domain.com: Connection refused
DBI1165E Instance db2inst2 is not accessible on the following
database partitions: machine_name.domain.com
DBI1383I You must update the DB2 registry for the current
instance
manually using the db2iset command, including the full path of
the db2iset command. For example:
/opt/ibm/db2/V9.7/instance/db2iset -d db2inst2.
DBI1079I Output is saved in the log file
/tmp/db2iupdt.log.1229.
Explanation:
All processed and failed operations have been saved into this
log file.
User response:
Do not modify this file in any way. This file is for IBM
Technical Support reference. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 V9.7 *
****************************************************************
* PROBLEM DESCRIPTION: *
* DB2IUPDT FAILS TO UPDATE 9.7 INSTANCE WHEN DB2RSHCMD *
* IS USING SSH. instead it uses RSH. Once db2iupdt finishes, *
* the *
* instance profile is corrupted. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7.1 or higher *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 LUW Version 9.7 Fix Pack 1 |
| Workaround |
not known / see Local fix |
| Comment |
Fix Release 9.7 FP1 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.08.2009
17.02.2010
09.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.1,
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
