Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC91476 Status: Closed

INCORRECT PERMISSIONS ON DB2NODES.CFG FILE AFTER FAILOVER

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Permissions on the db2nodes.cfg file should be r--r--r-- while 
the instance is up and rw-r--r-- while the instance is down. 
 
During a failover operation the permissions are changed to 
rw-r--r-- and aren't reverted back to r--r--r-- once the 
failover has completed processing. This APAR addresses this 
issue, the correct r--r--r-- permissions will be set on the 
db2nodes.cfg file after a failover has taken place.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 DPF HA(TSA) users                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 FP3                              * 
****************************************************************
Local Fix:
Manually revert the permissions on the file back to r--r--r-- 
after a failover has taken place.
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
Fixed in DB2 version 10.1 FP3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.04.2013
01.10.2013
01.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 FixList
10.1.0.3 FixList