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

HADR STANDBY LOSES CONNECTION AND RECONNECTS FOLLOWING A GRACEFUL TAKEOVER
WHEN SUPERASYNC IS USED FOR HADR_SYNCMODE

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Right after a graceful takeover is issued, the new hadr standby 
loses connection and reconnects. This failure is seen when 
superasync mode is used for 
the HADR pair. The problem may not be very common. When the 
problem reproduces, similar to the following diagnostic data 
will be seen in the DB2 db2diag.log 
 
2013-08-29-01.38.40.836081-240 I710579A654          LEVEL: 
Severe 
PID     : 27328552             TID : 10025          KTID : 
46727219 
PROC    : db2sysc 
INSTANCE: tnarayan             NODE : 000           DB   : 
MSDBDR 
HOSTNAME: coralpib65 
EDUID   : 10025                EDUNAME: db2hadrs.0.0 (MSDBDR) 
FUNCTION: DB2 UDB, data protection services, sqlpgWriteToDisk, 
probe:909 
MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File 
cannot be used" 
          DIA8414C Logging can not continue due to an error. 
DATA #1 : <preformatted> 
TailPage 790 does not match pagePso 30942925468 and firstLso 
30939693201. 
lowLso: 30942913241, highLso: 30942917317
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL DB2 LUW HADR users using superasync synchronization mode * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix    * 
* Pack 4) or higher.                                           * 
****************************************************************
Local-Fix:
Please upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix 
Pack 4) or higher. 
If the problem is reproduced before the upgrade is applied, 
restarting HADR will fix the issue. After the restart the pair 
will connect successfully and standby will catchup with primary 
from the correct position.
verfügbare FixPacks:
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

Lösung
Fixed in DB2 Cancun Release 10.5.0.4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
16.09.2013
08.09.2014
14.10.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList