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

HADR GRACEFUL TAKEOVER FAILS ON STANDBY THAT HAS TABLE SPACES/TRANSACTIONS
IN REPAIR STATE.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
In an HADR environment if the primary or standby hits a table 
space I/O error that places a table space into rollforward 
pending or offline/disabled state and then on the standby a 
graceful takeover is issued, the takeover could fail to complete 
with a SQL1042C. 
 
The DB2 diagnostics log would have a message as follows: 
 
FUNCTION: DB2 UDB, recovery manager, sqlprudm, probe:775 
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic 
Error" 
                 DIA8526C A fatal error occurred in data 
protection services. 
DATA #1 : String, 84 bytes 
Unexpected condition!!! HADR graceful takeover should not have 
transactions to undo. 
DATA #2 : db2LogStreamIDType, PD_TYPE_DB2_LOG_STREAM_ID, 2 bytes 
 
0
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* HADR                                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In an HADR environment if the primary or standby hits a      * 
* table space I/O error that places a table space into         * 
* rollforward pending or offline/disabled state and then on    * 
* the standby a graceful takeover is issued, the takeover      * 
* could fail to complete with a SQL1042C.                      * 
*                                                              * 
* The DB2 diagnostics log would have a message as follows:     * 
*                                                              * 
* FUNCTION: DB2 UDB, recovery manager, sqlprudm, probe:775     * 
* MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic  * 
* Error"                                                       * 
*                  DIA8526C A fatal error occurred in data     * 
* protection services.                                         * 
* DATA #1 : String, 84 bytes                                   * 
* Unexpected condition!!! HADR graceful takeover should not    * 
* have                                                         * 
* transactions to undo.                                        * 
* DATA #2 : db2LogStreamIDType, PD_TYPE_DB2_LOG_STREAM_ID, 2   * 
* bytes                                                        * 
* 0                                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* A workaround would be to issue a forced takeover or use      * 
* version 10.5 GA or upgrade to DB2 Cancun Release 10.5.0.4    * 
* (also known as Fix Pack 4) or higher.                        * 
****************************************************************
Local-Fix:
If such an error occurs a workaround would be to issue a forced 
takeover.
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
With the installation of DB2 Version 10.5 Fix Pack 4 a graceful 
takeover with table spaces/transactions requiring repair due to 
an I/O error that can be repaired during the takeover will 
function correctly as pre-v10.5 FP1.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC97848 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
19.09.2013
08.10.2013
25.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList