DB2 FOR LUW / DB2FORLUW / 970 - DB2

Before associating a resource with its parent resource 
group(RG), the parent RG is first locked. The newly created 
child resource is then associated with the parent RG, once this 
is complete the parent RG is unlocked. However, if an error is 
encountered when attempting to associate the resource with its 
parent RG, the parent RG will be left in a locked state. 
 
Locked RG example(snippet from lssam output): 
Online IBM.ResourceGroup:db2_db2inst1_0-rg Request=Lock 
Nominal=Online 
 
The following db2diag.log entry confirms this error: (although 
the DATA #6 entry may vary depending on the nature of the error) 
 
2012-01-01-00.00.00.000000-300 E345837A769        LEVEL: Error 
PID     : 5243370              TID  : 36244       PROC : db2sysc 
0 
INSTANCE: db2inst1          NODE : 000 
EDUID   : 36244                EDUNAME: db2bm.50489.0 (DBNAME) 0 
FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, 
sqlhaAddResource, probe:1600 
MESSAGE : 
ECF=0x90000542=-1879046846=ECF_SQLHA_CREATE_GROUP_FAILED 
          Create group failed 
DATA #1 : String, 35 bytes 
Error during vendor call invocation 
DATA #2 : unsigned integer, 4 bytes 
18 
DATA #3 : String, 17 bytes 
db2_db2inst1_0-rg 
DATA #4 : unsigned integer, 8 bytes 
1 
DATA #5 : signed integer, 4 bytes 
14 
DATA #6 : String, 95 bytes 
Line # : 6881---2621-014 Command not allowed - one or more 
related resource groups are online.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB V97                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to DB2 Version 97 Fix Pack 7                         * 
****************************************************************

Manually unlock the resource group by issuing the following with 
root authority: 
rgreq -o unlock <resource group name>

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
 

Problem Fixed in DB2 Version 97 Fix Pack 7

Manually unlock the resource group by issuing the following with 
root authority: 
rgreq -o unlock <resource group name>

Vorgänger  : APAR is sysrouted TO one or more of the following: IC84594 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

20.03.2012
29.01.2013
29.01.2013

9.7.FP7