|
Problem IC76828
|
Status: Closed |
"CTE0360 NO COMMON SECONDARY GROUP EXISTS " REPORTED WHEN FENCED USER AND INSTANCE OWNER SHARE A COMMON SECONDARY GROUP |
| product: |
DB2 NET SEARCH / 5765F3800 / 970 - 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.
But in certain cases , even when a common secondary group
exists, NSE reports "CTE0360 No common secondary group exists
". |
| Problem Summary: |
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.
But in certain cases , even when a common secondary group
exists, NSE reports "CTE0360 No common secondary group exists
". |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Upgrade to V97fp5 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC79359
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.06.2011
21.11.2011
21.11.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
