|
Problem IC76311
|
Status: Closed |
TSA ON WINDOWS: SCRIPT SUPPORT FOR NON SYNC MODE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Currently the HADR/TSA on Windows sample scripts only work with
HADR Sync mode = Sync.
This is because the hadr_monitor script grep for "Sync" mode
specifically. If the HADR pair is configured using Sync mode
"Nearsync" then the clustered resource will return Unknown
OpState. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* HADR/TSA on Windows solution users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See error description *
****************************************************************
* RECOMMENDATION: *
* Apply DB2 V9.7.0.5 *
**************************************************************** |
| Local Fix: |
In the hadr_monitor.ksh script manually modify this line:
grepFlags='-e'
to
grepFlags='-ie' |
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 |
Apply DB2 V9.7.0.5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.05.2011
08.12.2011
08.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.0.5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
