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

USING THE DB2HAICU MAINTENANCE MODE OPTION TO MOVE HADR DATABASES MAY CAUSE
THE HADR RESOURCE GROUP TO BE LOCKED

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
If you have a DB2 HADR/TSA setup, and you look to use the 
db2haicu maintenance mode option to move the HADR primary 
database over to the standby node, i.e. option 5 from the below 
db2haicu maintenance mode menu: 
 
$ db2haicu 
(...) 
 
Select an administrative task by number from the list below: 
  1. Add or remove cluster nodes. 
  2. Add or remove a network interface. 
  3. Add or remove HADR databases. 
  4. Add or remove an IP address. 
  5. Move DB2 database partitions and HADR databases for 
scheduled maintenance. 
  6. Create a new quorum device for the domain. 
  7. Destroy the domain. 
  8. Exit. 
 
Then it is possible that the HADR resource group remains locked 
after the move request has successfully completed. The lock 
state of the HADR resource group can be viewed via the lssam 
command output: 
 
Online IBM.ResourceGroup:db2_db2inst1_host03_0-rg Nominal=Online 
        '- Online IBM.Application:db2_db2inst1_host03_0-rs 
                '- Online 
IBM.Application:db2_db2inst1_host03_0-rs:host03 
Online IBM.ResourceGroup:db2_db2inst1_host04_0-rg Nominal=Online 
        '- Online IBM.Application:db2_db2inst1_host04_0-rs 
                '- Online 
IBM.Application:db2_db2inst1_host04_0-rs:host04 
Online IBM.ResourceGroup:db2_db2inst1_db2inst1_DBHADR-rg 
Request=Lock Nominal=Online 
        '- Online 
IBM.Application:db2_db2inst1_db2inst1_DBHADR-rs 
Control=SuspendedPropagated 
                |- Online 
IBM.Application:db2_db2inst1_db2inst1_DBHADR-rs:host03 
                '- Offline 
IBM.Application:db2_db2inst1_db2inst1_DBHADR-rs:host04 
Online IBM.Equivalency:db2_db2inst1_host03_0-rg_group-equ 
        '- Online IBM.PeerNode:host03:host03 
Online IBM.Equivalency:db2_db2inst1_host04_0-rg_group-equ 
        '- Online IBM.PeerNode:host04:host04 
Online IBM.Equivalency:db2_db2inst1_db2inst1_DBHADR-rg_group-equ 
        |- Online IBM.PeerNode:host03:host03 
        '- Online IBM.PeerNode:host04:host04 
Online IBM.Equivalency:db2_public_network_0 
        |- Online IBM.NetworkInterface:eth1:host04 
        '- Online IBM.NetworkInterface:eth0:host03 
 
As seen from the above lssam output, there is a lock request 
placed on the HADR resource group 
"db2_db2inst1_db2inst1_DBHADR-rg". If this is the case, and it 
is determined that the HADR database pair is in primary-standby 
peer state, then this lock has been erroneously placed on the 
HADR resource group and should be removed.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.1 Fixpack 5 or Later.                 * 
****************************************************************
Local-Fix:
Unlock the resource group by issuing the following TSA command 
as root: 
"rgreq -o unlock <Resource Group>"
Lösung
First Fixed in DB2 LUW v10.1 Fixpack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.08.2014
13.07.2015
13.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList