DB2 FOR LUW / DB2FORLUW / 970 - DB2

DependsOn relationship shouldn't be created for private network 
for HADR setup. 
 
When private network is down, the expected procedure should 
looks like this: 
ifconfig en5 down 
the hadr db resource gets locked (no takeover) 
ifconfig en5 up 
resource gets unlocked 
 
This is because if the private network is down, there will never 
be any HADR synchronization possible. So just keep the primary 
where it is as client apps will still be able to use it, and 
later when the private network problem is resolved, the standby 
will catchup.

Problem Description: 
DEPENDSON RELATIONSHIP SHOULDN'T BE CREATED FOR PRIVATE NETWORK 
Problem Summary: 
DependsOn relationship shouldn't be created for private network 
for HADR setup. 
 
When private network is down, the expected procedure should 
looks like this: 
ifconfig en5 down 
the hadr db resource gets locked (no takeover) 
ifconfig en5 up 
resource gets unlocked 
 
This is because if the private network is down, there will never 
be any HADR synchronization possible. So just keep the primary 
where it is as client apps will still be able to use it, and 
later when the private network problem is resolved, the standby 
will catchup.

For this to happen you need to remove the relationship between 
private network and the instance: 
 
lsrel 
make sure the rg for that relationship is offline 
rmrel -s "Name like '%private%'"

DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows
 

Problem is first fixed in Version 9.7 Fix Pack 1

For this to happen you need to remove the relationship between 
private network and the instance: 
 
lsrel 
make sure the rg for that relationship is offline 
rmrel -s "Name like '%private%'"

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

17.08.2009
21.12.2009
21.12.2009

9.7.FP1