DB2 FOR LUW / DB2FORLUW / A10 - DB2

When TCP connections are made to the HADR standby database by 
software other than HADR database software, the log shipping on 
primary database is stopped. There is a large gap between the 
PRIMARY_LOG_TIME and STANDBY_LOG_TIME values. However, the 
HADR_STATE element is incorrectly reported as being in PEER 
state. A non-forced takeover operation might be allowed and it 
might be successful, but the operation will also experience some 
data loss. 
 
The following is an example of what you might see if this error 
occurs: 
$ db2pd -db sample -hadr 
 
Database Member 0 -- Database SAMPLE -- Active 
 
                HADR_ROLE = PRIMARY 
 
               HADR_STATE = PEER 
 
      HADR_CONNECT_STATUS = CONNECTED 
 HADR_CONNECT_STATUS_TIME = 2013-07-17 15:53:13.671498 
(1374043993) 
 
PRIMARY_LOG_FILE,PAGE,POS = S0001326.LOG, 0, 62379237 
STANDBY_LOG_FILE,PAGE,POS = S0001326.LOG, 0, 62379105 
      HADR_LOG_GAP(bytes) = 13 
 
         PRIMARY_LOG_TIME = 2013-07-17 15:54:55.000000 
(1374044095) 
         STANDBY_LOG_TIME = 2013-07-17 14:57:27.000000 
(1374040647)

**************************************************************** 
* USERS AFFECTED:                                              * 
* All who use HADR                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 FixPack 3                            * 
****************************************************************

Deactivate and activate the standby database in order to ship 
the rest of the logs to the standby database for replay.

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
 

Problem was first fixed in DB2 UDB Version 10.1 FixPack 3

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC94672 IC95669 
Nachfolger : 

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

19.07.2013
27.09.2013
27.09.2013