|
Problem IC61987
|
Status: Closed |
IN THE HADR MONITOR SCRIPT, THE GCF CALL MAY HANG DUE TO HUNG RSCT CALLS IN TSA 3.1 |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
If the RSCT calls to TSA hangs, the hadr monitor script will
also hang at the gcf stage.
To resolve this, we use db2pd to find out the status of the hadr
resource. Due to LI73951, the db2pd can potentially return
blank; in these cases, we use db2 snapshot to obtain the status. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* TSA 3.1 users with HADR scenarios. *
****************************************************************
* PROBLEM DESCRIPTION: *
* The hadr monitor script may hang. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.5.0.5 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The problem was first fixed in version 9.5 fix pack 5. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC62302
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.07.2009
21.12.2009
21.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.0.5,
9.5.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.5
|
 |
