DB2 - Problem description
Problem IC87825 | 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 / A10 - 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: | |
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to V10.1 fp1 * **************************************************************** | |
Local Fix: | |
Remove the "system" group from either user or both. | |
Solution | |
Starting with V9.7 FP4 & V9.5 FP8, Net Search Extender (NSE) removes the restriction of having the fenced ID to be the same as DB2© instance owner ID.This solution requires a common group which is to be added as secondary group for both the instance owner and fenced user. However, in certain cases, if both these users have "system" as common secondary group, NSE becomes non-operational and will not start. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.11.2012 11.12.2012 11.12.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP8, 9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) |