|
Problem IT04695
|
Status: Closed |
A LOG FILE ON STANDBY NEVER GETS UPDATED/RESIZED WHEN NEW LOG FILE SIZE INTRODUCES IN ITS PREVIOUS EXTENT. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
During log file size change, when we run deactivate P(or
db2stop) twice on P, A log file on Standby never gets
updated/resized when new log file size introduces in its
previous extent. that's because, If there's an empty extent with
incorrect log file size in the standby active log path, Standby
doesn't check the log file size, so it blindly thinks the log
file is good. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* First Fixed in DB2 9.5 Fix Pack 11 *
**************************************************************** |
| Local Fix: |
|
| Solution |
First Fixed in DB2 9.5 Fix Pack 11 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.10.2014
09.05.2017
09.05.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP11
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.11
|
 |
