|
Problem IT39288
|
Status: Closed |
LOGS DO NOT GET ARCHIVED WHEN CHANGE TO CIRCULAR LOGGING DOES NOT TAKE EFFECT
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
Updating logging to circular does not take effect even after
reactivation when database is in crash recovery pending or any
of tablespaces is not in normal state. In this scenario,
logging should stay the same as what was set as before. However
if it was archiving before, logs will not be archived and stays
in active path. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Issue will be fixed in a future release. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Issue will be fixed in a future release. *
**************************************************************** |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.12.2021
01.12.2021
01.12.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
