|
Problem IT40539
|
Status: Closed |
DB2IUPDT FAILS TO UPDATE THE FENCED ID. IT UPDATES PARTIALLY.
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
When using db2updt to update fenced userid, user may experience
that its updated only partially.
Example:
DB21085I This instance or install (instance name, where
applicable: "tinst")
uses "64" bits and DB2 code release "SQL11050" with level
identifier
"0601010F".
Informational tokens are "DB2 v11.5.0.0", "s1906101300",
"DYN1906101300AMD64",
and Fix Pack "0".
Product is installed at "/opt/ibm/db2/V11.5.0".
Fence user is tinst
db2pd -fmp | grep -i fence
Trusted Path: /home/tinst/sqllib/function/unfenced
Fenced User: tinst
cat sqllib/ctrl/.fencedID
tinst
ls -l sqllib/ctrl/.fencedID
-rw-rw-r-- 1 tinst tinst 6 Apr 6 07:14 sqllib/ctrl/.fencedID
Now trying to Update fenced user to tfence.
/opt/ibm/db2/V11.5.0/instance/db2iupdt -u tfence tinst
Existing instances to configure:
Instance name: tinst
Instance user information:
User name: tinst
Fenced user information:
User name: tfence
Setting default global profile registry variables
:.......Success
Initializing instance list :.......Success
The instance "tinst" has been updated successfully.
Configuring DB2 instances :.......Success
Updating global profile registry :.......Success
Checking:
04/06/2022 07:23:05 0 0 SQL1063N DB2START processing
was successful.
SQL1063N DB2START processing was successful.
Db2pd still shows fenced user as tinst
db2pd -fmp | grep -i fence
Trusted Path: /home/tinst/sqllib/function/unfenced
Fenced User: tinst
However in the files we can see tfence is updated correctly.
cat sqllib/ctrl/.fencedID
tfence
ls -l sqllib/ctrl/.fencedID
-rw-rw-r-- 1 tfence tfence 7 Apr 6 07:22 sqllib/ctrl/.fencedID |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* 250 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 11.5.6 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* 250 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 11.5.6 *
**************************************************************** |
| Comment |
Fixed in 11.5.6 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.04.2022
06.04.2022
11.04.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
