|
Problem IC66908
|
Status: Closed |
AFTER MULTIPLE IMMEDIATE TAKEOVERS (IN A WHILE LOOP) THE SUBSEQU ENT TAKEOVER GETS AN ERROR SQL1035N (DATABASE CURRENTLY IN USE.) |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| 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".
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 Summary: |
****************************************************************
* 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: |
|
| available fix packs: |
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
|
| Solution |
With DB2 v98fp3, takeover will behave normally instead of
getting back error message "SQL1776N" |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.03.2010
28.12.2010
28.12.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.3
|
 |
