DB2 - Problem description
Problem IC79931 | Status: Closed |
CTE0360 WILL BE REPORTED AT STARTUP IF SYSTEM GROUP IS INCLUDED IN COMMON SECONDARY GROUP OF FENCED USER AND/OR INSTANCE OWNER | |
product: | |
DB2 NET SEARCH / 5765F3800 / 950 - DB2 | |
Problem description: | |
When fenced user and instance owner are not the same user, NSE needs a shared common secondary group between the fenced user and instance owner. However, if the "system" group is included in the secondary group of either user or both the users, NSE reports "CTE0360 No common secondary group exists" at startup. Note: Starting from V9.7 FP5, the error code CTE0360 has been changed to CTE0312. | |
Problem Summary: | |
CTE0360 WILL BE REPORTED AT STARTUP IF SYSTEM GROUP IS INCLUDED IN COMMON SECONDARY GROUP OF FENCED USER AND/OR INSTANCE OWNER When fenced user and instance owner are not the same user, NSE needs a shared common secondary group between the fenced user and instance owner. However, if the "system" group is included in the secondary group of either user or both the users, NSE reports "CTE0360 No common secondary group exists" at startup. Note: Starting from V9.7 FP5, the error code CTE0360 has been changed to CTE0312. | |
Local Fix: | |
Remove the "system" group from either user or both. | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
When fenced user and instance owner are not the same user, NSE needs a shared common secondary group between the fenced user and instance owner. However, if the "system" group is included in the secondary Upgrade to V95fp9 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC87825 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.11.2011 30.01.2012 30.01.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.9 |