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 IC89722 Status: Geschlossen

HADR RESOURCE GROUP REMAINS LOCKED AFTER SUCCESSFUL HADR REINTEGRATION.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
After a successful HADR pair reintegration, the HADR resource 
group(RG) will be locked. In addition to this, there is a stray 
IBM.Test resource which does not get cleaned up: 
 
$ lsrsrc -Ab IBM.Test 
Resource Persistent and Dynamic Attributes for IBM.Test 
resource 1: 
        Name              = 
"db2_HADRDB__Reintegrate_DB2INST1_db2inst1" 
        ResourceType      = 0 
        AggregateResource = "0x3fff 0xffff 0x00000000 0x00000000 
0x00000000 0x00000000" 
        ForceOpState      = 0 
        TimeToStart       = 0 
        TimeToStop        = 0 
        WriteToSyslog     = 0 
        MoveTime          = 0 
        MoveFail          = 0 
        ForceMoveState    = 0 
        ActivePeerDomain  = "db2HADRdomain" 
        NodeNameList      = {"nodeA"} 
        OpState           = 2 
        ConfigChanged     = 0 
        ChangedAttributes = {} 
        MoveState         = [0,{}] 
        OpQuorumState     = 0 
 
This occurs if the value of the database configuration 
parameter HADR_REMOTE_INST is set in upper-case letters. 
For example: 
 
$ db2 get db cfg for HADRDB | grep HADR_REMOTE_INST 
HADR instance name of remote server (HADR_REMOTE_INST) = 
DB2INST1 
 
This will not affect HADR as both HADR pair servers will be in 
peer state. However, the RG will need to be unlocked by 
issuing: "rgreq -o unlock <ResourceGroupName>" 
 
The state of the HADR RG from lssam output will look like this: 
 
Online IBM.ResourceGroup:db2_db2ins1_db2inst1_HADRDB-rg 
Request=Lock Nominal=Online 
        |- Online 
IBM.Application:db2_db2inst1_db2inst1_HADRDB-rs 
Control=SuspendedPropagated 
                |- Online 
IBM.Application:db2_db2inst1_db2inst1_HADRDB-rs:nodeA 
                '- Offline 
IBM.Application:db2_db2inst1_db2inst1_HADRDB-rs:nodeB
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 FP3                              * 
****************************************************************
Local-Fix:
Change the value of the HADR_REMOTE_INST db cfg parameter from 
upper-casing to lower-casing.
verfügbare FixPacks:
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
First fixed in DB2 Version 10.1 FP3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.01.2013
04.11.2013
04.11.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList