home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC84594 Status: Geschlossen

RESOURCE GROUP LEFT IN A LOCKED STATE AFTER A FAILURE TO ASSOCIATE A CHILD
RESOURCE TO IT

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V10                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 FP1                              * 
****************************************************************
Local-Fix:
Manually unlock the resource group by issuing the following with 
root authority: 
rgreq -o unlock <resource group name>
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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

Lösung
Problem Fixed in DB2 Version 10.1 Fix Pack 1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.06.2012
07.11.2012
07.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList