|
Problem IC91613
|
Status: Closed |
V10.1 ONLY: DB2IUPDT COMMAND OVERRIDES FENCEDID BY INSTANCE OWNER IF -U OPTION IS NOT SPECIFIED. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The db2iupdt command overrides fencedID by instance owner when
-u option is not specified.
This command should set fencedID as it is if user does not
provide -u option.
The following scenario illustrates the problem.
1. Create instance user and fenced user, then create a instance.
# db2icrt -u db2fenc db2inst1
2. Make sure expected fenced user is set.
$ cat $HOME/sqllib/ctrl/.fencedID
db2fenc
3. Update the instance.
# db2iupdt db2inst1
4. The command overrides fencedID by instance owner.
$ cat $HOME/sqllib/ctrl/.fencedID
db2inst1
Please note that installFixpack runs db2iupdt <instance_name>
implicitly. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who run db2iupdt command (including installFixpack). *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to V10.1 FixPack 3 or later. *
**************************************************************** |
| Local Fix: |
Please use -u option when running db2iupdt.
Users can also change current fencedID by db2iupdt with -u
option. |
| 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 |
This problem was first fixed in DB2 V10.1 FixPack 3. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC95316
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.04.2013
08.10.2013
08.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
|
|
