home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC95669 Status: Closed

TCP CONNECTIONS FROM NON-HADR DATABASE SOFTWARE TO THE STANDBY MIGHT ALTER
THE HADR STATE AND STALL LOG SHIPPING ON THE PRIMARY

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 HADR users                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.3.                             * 
****************************************************************
Local Fix:
Deactivate and activate the standby database in order to ship 
the rest of the logs to the standby database for replay.
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
The problem was first fixed in DB2 version 10.5.0.3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.09.2013
16.10.2014
07.04.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList
10.5.0.4 FixList