|
Problem IC78993
|
Status: Closed |
LONG DATABASE ACTIVATION AFTER HADR RESTART DUE TO A DB2 CRASH. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If an HADR primary database abends for some reason and is
restarted, with an active client application workload against it
(read clients trying to connect to it), the activation of the
database may take a VERY long time to occur
(minutes to hours depending on the number of clients trying to
connect).
The client workload needs to have a timeout configuration such
that if the client is unable to connect within timeout settings,
the client closes the connection to the server and, attempts
(client re-route/ ACR) a connection to the secondary. This
leaves an agent resource on the primary on a "queue" behind the
activation of the database.
When this agent finally gets its turn, it tries to activate the
db and realizes it needs to start the HADR primary. While doing
that, it determines that its client connection has gone away so
it aborts. All agents on the queue go through this processing.
The client workload, once it fails to connect to the secondary
database, re-attempts to connect to the primary where, again, it
eventually times out, adding even MORE agents to the queue and
the cycle continues... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users on DB2 v97 Fp5 and earlier *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v97 FP6 *
**************************************************************** |
| Local Fix: |
As a workaround:
1. Restart db2 server
2. Uncatalog the database
3. Re-catalog the database
4. Activate the database |
| available fix packs: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First Fixed in DB2 v97 FP6 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.09.2011
22.06.2012
22.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
