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

AFTER MULTIPLE IMMEDIATE TAKEOVERS (IN A WHILE LOOP) THE SUBSEQU ENT
TAKEOVER GETS AN ERROR SQL1035N (DATABASE CURRENTLY IN USE.)

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problembeschreibung:
With an HADR pair set up, If multiple takeover are issued in a 
tight loop on both primary and standby, db is then put into "db 
is in use" state and subsequent deactivate or takeover requests 
get back an error SQL1035. 
 
This issue appears right after the takeover gets back an error 
SQL1776N  The command cannot be issued on an HADR standby 
database. Reason code = "2". 
 
 
A snapshot output of the while loop run -- 
 
DB20000I  The TAKEOVER HADR ON DATABASE command completed 
successfully. 
SQL1770N  Takeover HADR cannot complete. Reason code = "4". 
SQL1770N  Takeover HADR cannot complete. Reason code = "4". 
SQL1770N  Takeover HADR cannot complete. Reason code = "4". 
SQL1776N  The command cannot be issued on an HADR standby 
database. Reason 
code = "2". 
SQL1035N  The database is currently in use.  SQLSTATE=57019 
SQL1035N  The database is currently in use.  SQLSTATE=57019 
SQL1035N  The database is currently in use.  SQLSTATE=57019 
SQL1035N  The database is currently in use.  SQLSTATE=57019 
SQL1035N  The database is currently in use.  SQLSTATE=57019
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Customer using DB2 HADR                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* With an HADR pair set up, If multiple takeover are issued in * 
* a                                                            * 
* tight loop on both primary and standby, db is then put into  * 
* "db                                                          * 
* is in use" state and subsequent deactivate or takeover       * 
* requests                                                     * 
* get back an error SQL1035.                                   * 
*                                                              * 
*                                                              * 
*                                                              * 
* This issue appears right after the takeover gets back an     * 
* error                                                        * 
* SQL1776N  The command cannot be issued on an HADR standby    * 
*                                                              * 
* database. Reason code = "2".                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v98fp3                                        * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Lösung
With DB2 v98fp3, takeover will behave normally instead of 
getting back error message "SQL1776N"
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.03.2010
28.12.2010
28.12.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.8.FP3
Problem behoben lt. FixList in der Version
9.8.0.3 FixList