|
Problem IC91762
|
Status: Closed |
PRINT ADM12512W WARNING INTO ADMINISTRATION LOG FILE WHENEVER A TABLESPACE IS NO LONGER MAINTAINED BY LOG REPLAY ON HADR STANDBY |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
In an HADR environment, the Standby database might stop
replaying logs for a tablespace due to an unexpected error. A
DBA might not notice the error messages for this tablespace in
the Standby database's db2diag.log. The Standby database will
remain active during this time while replaying logs for other
tablespaces, and 'db2pd -hadr' will still show the HADR Standby
is active. If an hadr failover was executed this particular
tablespace would thus be unavailable.
The purpose of this APAR is to add an ADM12512W warning into the
administration log file (<instance_name>.nfy) whenever a
tablespace is no
longer maintained by log replay on HADR standby. A user can
either scan the administration log for this ADM12512W warning
regularly (or create a cron script to automate this).
Alternately, 'db2pd -tablespaces' can be executed on the Standby
to check the tablespace state. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 for Linux, UNIX, and Windows Fix *
* Pack 3 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 Version 10.1 for Linux, UNIX, and
Windows Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.04.2013
03.10.2013
03.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
