oracle 18c dataguard 从库scn 不更新BUG
编程语言
2023-09-18 18:01:44
阅读次数: 0
| Bug 29056767 - STANDBY: Datafiles Checkpoint not Updated at Standby Database when Media Recover is running (Doc ID 29056767.8) |
正在上传…重新上传取消To Bottom |
|
Bug 29056767 STANDBY: Datafiles Checkpoint not Updated at Standby Database when Media Recover is running This note gives a brief overview of bug 29056767.
The content was last updated on: 19-APR-2022
Click here for details of each of the sections below. Affects:
| Product (Component) |
Oracle Server (Rdbms) |
| Range of versions believed to be affected |
(Not specified) |
| Versions confirmed as being affected |
|
| Platforms affected |
Generic (all / most platforms affected) |
Fixed:
| The fix for 29056767 is first included in |
|
Interim patches may be available for earlier versions - click here to check.
Description
On a Physical Standby database, media recovery not regularly updating the checkpoint scn and time stored in each datafile header.
This problem only happens in oracle version 18.1 onwards.
Standby media recovery is running, and it's applying successive log seq#'s,
but the checkpoint scn and time stored each datafile header doesn't change.
NOTE: the checkpoint in the datafile headers can be monitored by:
select to_char(sysdate,'HH24:MI:SS'), file#, checkpoint_change#,
to_char(checkpoint_time,'HH24:MI:SS') from v$datafile_header;
A level 1 incremental backup on the standby may skip all the datafiles.
Another impact of this bug is that if media recovery suddenly aborts for some other reason (eg due to a "shutdown abort" of the instance)
then the next media recovery session may try to start scanning redo from much further back in time than necessary, and if that redo is
unavailable, V$MANAGED_STANDBY would show MRP0 status is WAIT_FOR_GAP, alert log file will show 'FAL: Failed to request gap sequence'
Workaround
On the standby,
set: alter system set "_time_based_rcv_ckpt_target"=0;
NOTE: restart media recovery for it to pick up the new parameter value.
NOTE: this parameter can also be proactively set on the primary, so it
is ready in case it becomes the standby in the future
| Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support. |
References
Bug:29056767 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article
|
转载自blog.csdn.net/royjj/article/details/130368570