|
Problem IC71685
|
Status: Closed |
"ROLLFORWARD LAST COMMITTED TIMESTAMP" VALUE IS NOT SHOWN IN A DATABASE SNAPSHOT ISSUED AGAINST A HADR STANDBY DATABASE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In versions prior to V9.7 when running a "get database
snapshot for <db>" command on a hadr standby database, the
output would include the
"Rollforward last committed timestamp" value.
This value was incorrectly removed in V9.7, causing difficulties
in monitoring the progress of a HADR standby database |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* HADR users *
****************************************************************
* PROBLEM DESCRIPTION: *
* On Standby, a database snapshot does not show the *
* rollforward position *
****************************************************************
* RECOMMENDATION: *
* Upgrade the db2 server to V9.7 Fixpak 4 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 |
This problem has first been fixed in V9.7 Fixpak 4 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC72943
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.10.2010
24.05.2011
24.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
