DB2 FOR LUW / DB2FORLUW / 970 - DB2

When stopping HADR on an active primary database  with command 
"stop hadr on db dbname", the database is expected to become a 
standard  database and continue to function normally. 
However, in some situation, the  database could be brought 
offline after the same  command. 
 
Messages similar to the following might  appear in the 
db2diag.log: 
 
2011-10-07-17.20.57.326550-240 I63744A399         LEVEL: Error 
PID     : 10158182             TID  : 20625       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 20625                EDUNAME: db2hadrp (HADRDB) 0 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrBindAndListen, probe:20320 
RETCODE : ZRC=0x810F001B=-2129723365=SQLO_ADDR_IN_USE "Address 
already in use" 
...... 
2011-10-07-17.20.57.326961-240 I64883A376         LEVEL: Severe 
PID     : 10158182             TID  : 20625       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 20625                EDUNAME: db2hadrp (HADRDB) 0 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrEduEntry, probe:21100 
MESSAGE : HADR marking logs bad; database should shut down. 
...... 
2011-10-07-17.20.57.328665-240 I66131A459         LEVEL: Error 
PID     : 10158182             TID  : 14457       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : HADRDB 
EDUID   : 14457                EDUNAME: db2loggr (HADRDB) 0 
FUNCTION: DB2 UDB, data protection services, sqlpgsck, probe:430 
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File 
cannot be used" 
          DIA8414C Logging can not continue due to an error.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using HADR                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A stop hadr command in active primary HADR database can      * 
* result into a  database down situation marking a transaction * 
* log file temporarily bad.                                    * 
* A restart database command will bring the database on-line   * 
* again.                                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 6 or higher to avoid     * 
* experiencing this issue.                                     * 
****************************************************************

Once this problem is experienced issue restart  database to 
bring the database online again.  If the standby side HADR was 
stopped already it needs to be restarted before issuing restart 
database in the primary side.

DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 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
 

First fixed in DB2 Version 9.7 Fix Pack 6

keiner bekannt / siehe Local-Fix

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

03.11.2011
18.06.2012
18.06.2012

9.7.FP6