增量恢复dg备库.pdf
5墨值下载
2021/8/3
Document 1531031.1
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=u0olkpt9b_52&id=1531031.1
1/5
Copyright (c) 2021, Oracle. All rights reserved. Oracle Confidential.
Steps to perform for Rolling forward a standby database using RMAN incremental backup when datafile is added to primary (Doc ID
1531031.1)
In this Document
Goal
Solution
1) On the standby database, stop the managed recovery process (MRP)
2) On the standby database, find the SCN which will be used for the incremental backup at the primary database:
3) In sqlplus, connect to the primary database and identify datafiles added:
4) Using rman, create backup of missing datafiles and an incremental backup using the SCN derived in the previous step:
5) Transfer all backup sets created on the primary system to the standby system.
6) Restore new controlfile and catalog the backup transfered in step #5:
7) Restore missing datafiles:
8) Rename the datafiles in new standby controlfile
9) Recover the standby database with the cataloged incremental backup:
10) If the standby database needs to be configured for FLASHBACK use the below step to enable.
11) On standby database, clear all standby redo log groups:
12) On the standby database, start the MRP
References
APPLIES TO:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.3 [Release 10.2 to 11.2]
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 11.2.0.4 [Release 11.2]
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
*** Checked for relevance 16-OCT-2016 ***
GOAL
2021/8/3
Document 1531031.1
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=u0olkpt9b_52&id=1531031.1
2/5
The steps in this section can used to resolve problems if a physical standby database has lost or corrupted archived redo data or has an unresolveable archive gap.
SOLUTION
1) On the standby database, stop the managed recovery process (MRP)
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
2) On the standby database, find the SCN which will be used for the incremental backup at the primary database:
SQL> SELECT CURRENT_SCN FROM V$DATABASE;
SQL> select min(checkpoint_change#) from v$datafile_header;
CHECKPOINT_CHANGE#
---------------------
3162298
In ideal situation the above 2 queries will return the almost same SCN. However if there is huge difference its better to take backup using the SCN from second query (lesser SCN),
as one of the datafile may be behind.
3) In sqlplus, connect to the primary database and identify datafiles added:
SQL> SELECT FILE#, NAME FROM V$DATAFILE WHERE CREATION_CHANGE# > <checkpoint_change# from 2>;
4) Using rman, create backup of missing datafiles and an incremental backup using the SCN derived in the previous step:
RMAN> backup datafile <missing file number>, <missing file number>, <missing file number>, <missing file number> format '/tmp/ForStandby_%U'
tag 'FORSTANDBY';
RMAN> backup incremental from SCN 3162298 database format '/tmp/ForStandby_%U' tag 'FORSTANDBY';
RMAN> backup current controlfile for standby format '/tmp/ForStandbyCTRL.bck';
5) Transfer all backup sets created on the primary system to the standby system.
scp /tmp/ForStandby* standby:/tmp
of 5
5墨值下载
【版权声明】本文为墨天轮用户原创内容，转载时必须标注文档的来源（墨天轮），文档链接，文档作者等基本信息，否则作者和墨天轮有权追究责任。如果您发现墨天轮中有涉嫌抄袭或者侵权的内容，欢迎发送邮件至：contact@modb.pro进行举报，并提供相关证据，一经查实，墨天轮将立刻删除相关内容。
下载排行榜
文档被以下合辑收录
评论