【12c】12c RMAN新特性之經過網絡遠程恢復數據庫（RESTORE/Recover from Service）

時間  2019-11-06
標籤 12c rman 特性 經過 網絡 遠程 恢復 數據庫 restore recover service 欄目 C&C++ 简体版
原文   原文鏈接

 

【12c】12c RMAN新特性之經過網絡遠程恢復數據庫（RESTORE/Recover from Service）


 



 

經過網絡遠程恢復數據庫（Restore/Recover from Service） 面試

在Oracle 12c中，能夠在主數據庫和備用數據庫之間用一個服務名從新得到或恢復數據文件、控制文件、參數文件（SPFILE）、表空間或整個數據庫。這對於同步主數據庫和備用數據庫極爲有用。 sql

當主數據庫和備用數據庫之間存在至關大的差別時，再也不須要複雜的前滾流程來填補它們之間的差別。RMAN可以經過網絡執行備用恢復以進行增量備份，而且能夠將它們應用到物理備用數據庫。能夠用服務名直接將所需數據文件從備用點拷貝至主站，這是爲了防止主數據庫上數據文件、表空間的丟失，或是沒有真正從備份集恢復數據文件。 數據庫

具體的幾種用法： 微信

數據庫級別：restore database from service <服務別名> 網絡

表空間： restore tablespace from service <服務別名> 併發

控制文件：restore controlfile to '指定的位置' from service <服務別名> oracle

SPFILE: restore spfile from service <服務別名> app

如下命令演示瞭如何用此新功能執行一個前滾來對備用數據庫和主數據庫進行同步。在物理備用數據庫上： ide

rman target "username/password@standby_db_tns as SYSBACKUP" oop

RMAN>RECOVER DATABASE FROM SERVICE primary_db_tns USING COMPRESSED BACKUPSET;

以上案例使用備用數據庫上定義的primary_db_tns鏈接字符串鏈接到主數據庫，而後執行了一個增量備份，再將這些增量備份傳輸至備用目的地，接着將應用這些文件到備用數據庫來進行同步。然而，須要確保已經對primary_db_tns進行了配置，即在備份數據庫端將其指向主數據庫。

在如下命令中，演示了經過從備用數據庫獲取數據文件來恢復主數據庫上丟失的數據文件。在主數據庫上：

rman target "username/password@primary_db_tns as SYSBACKUP"

RMAN>RESTORE DATAFILE '+DG_DISKGROUP/DBANME/DATAFILE/filename' FROM SERVICE standby_db_tns;

 

&說明：

有關RECOVER TABLE的更多內容能夠參考個人BLOG：http://blog.itpub.net/26736162/viewspace-2152712/

有關RECOVER TABLE的更多內容能夠參考個人BLOG：http://blog.itpub.net/26736162/viewspace-2152715/

有關RECOVER TABLE的更多內容能夠參考個人BLOG：http://blog.itpub.net/26736162/viewspace-2152717/

 

 



相信你們在Dataguard環境中遇到過主庫丟失歸檔日誌，而備庫也沒有及時接收，致使備庫出現了GAP的現象。由於日誌的中斷，備庫沒法再去應用以後的日誌，就沒法起到容災的效果。

遇到這種故障，每每主庫若是數據很大的時候，你們都不會去選擇從新搭建來恢復備庫，而會去選擇更輕的增量恢復來解決問題。

即便如此，一旦主庫數據量過大，每日變化量也極多，進行一次增量恢復其實也須要大量的時間以及備份集所須要的空間。甚至，在GAP期間，若是主庫新增了數據文件，那麼也會增長任務量。

在12cR1開始，RMAN提供了一個from service的子句讓備庫能夠經過網絡來執行recover和restore命令。


The FROM SERVICE clause provides the service name of the physical standby database from which the files must be restored. During the restore operation, RMAN creates backup sets, on the physical standby database, of the files that need to be restored and then transfers these backup sets to the target database over the network.


那在哪些狀況下可使用這個新特性呢

  • 當備庫出現GAP，而主庫丟失歸檔須要作增量備份的時候

  • 當備庫丟失數據文件、控制文件以及表空間的須要restore的時候

這個特性其實大大縮減了備庫在一些丟失歸檔須要作增量備份的狀況下的工做量，將須要在主備庫來回切換的操做簡化爲只須要在備庫進行操做就能夠完成。

關於如何運用這一特性，用些簡單的例子來試驗下。

備庫增量恢復演示

模擬一個擁有GAP的備庫的環境： 



SQL> select * from v$archive_gap;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#     CON_ID
---------- ------------- -------------- ----------
 1      1231       1234      1
 2       762        765      1
SQL> show parameter fal
NAME                     TYPE           VALUE
------------------------------------ ---------------------- ------------------------------
fal_client               string         slave_db
fal_server               string         primary_db



查詢可知主庫tnsname鏈接串名爲primary_db

step 1 
查詢備庫當前SCN

 


RMAN> select current_scn from v$database;
CURRENT_SCN
-----------
37537287


這裏提一下，12c 開始，RMAN能夠直接執行不少命令，而不須要去使用sql 'sql'的句式去執行。

而後起至nomount狀態

 


RMAN> startup force nomount
Oracle instance started
Total System Global Area    2147483648 bytes
Fixed Size                     8794848 bytes
Variable Size                486542624 bytes
Database Buffers            1644167168 bytes
Redo Buffers                   7979008 bytes

step 2

備庫經過from service子句進行增量恢復

 



RMAN> restore standby controlfile from service primary_db;
Starting restore at 2018-06-01 12:26:40
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=21 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: using network backup set from service primary_db
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
output file name=/data/data1/control01.ctl
Finished restore at 2018-06-01 12:26:43
RMAN> alter database mount;


爲防止在GAP期間有新增的數據文件 

能夠在主庫查詢斷檔以後主庫新增的數據文件 



SQL> select file# from v$datafile where creation_change# > =37537287;
 FILE#
----------
    47




經過from service恢復命令將新增的數據文件經過網絡在備庫恢復。 

RMAN>run
{
SET NEWNAME FOR DATABASE TO '/data/data1/AXTEST/datafile/%f_%U';
RESTORE DATAFILE 47 FROM SERVICE primary_db;
}
executing command: SET NEWNAME
Starting restore at 2018-06-01 12:35:12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=785 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: using network backup set from service primary_db
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00047 to /data/data1/AXTEST/datafile/47_data_D-ZZ_TS-TEST1_FNO-47
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
Finished restore at 2018-06-01 12:35:28

由於主備庫數據文件路徑不一致，須要使用catalog與copy將數據名更新一致。

 



RMAN> catalog start with '/data/data1';

RMAN> switch database to copy;


step 3 
至此，能夠進行增量恢復了 
在from service句式中仍是可使用常規備份時候使用的參數

  • SECTION SIZE （在傳輸時使用併發備份集傳輸）

  • USING COMPRESSED BACKUPSET （在傳輸時使用壓縮，減輕網絡壓力）

 


RMAN> recover database from service primary_db noredo SECTION SIZE 1G USING COMPRESSED BACKUPSET;
....
destination for restore of datafile 00037: /data/data1/AXTEST/688A86E561085C8CE053BB3C0A0A7969/datafile/o1_mf_undo_2_88t4ahp9_.dbf
channel ORA_DISK_1: restoring section 1 of 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
Finished recover at 2018-06-01 13:45:00
#接下來就是正常的起庫開啓實時日誌恢復了


經過這種方式能夠很快的去解決一些備庫須要作增量恢復或者數據文件丟失的故障。

固然，須要使用from service句式時有些必要的條件：

  • 兩個數據庫之間tns必須保持能夠鏈接的狀態

  • 兩個數據庫密碼文件必須保持一致

  • 兩個數據庫的 COMPATIBLE參數必須爲12.0




12c RMAN新特性restore/recover from service遠程恢復


12c中提供了基於網絡的RMAN Restore和recover功能：

 

RMAN restores database files, over the network, from a physical standby database by using the  FROM SERVICE  clause of the  RESTORE command. The  FROM SERVICE  clause provides the service name of the physical standby database from which the files must be restored. During the restore operation, RMAN creates backup sets, on the physical standby database, of the files that need to be restored and then transfers these backup sets to the target database over the network.

To transfer files from the physical standby database as compressed backup sets, use the USING COMPRESSED BACKUPSET clause in the RESTOREcommand. By default, RMAN compresses backup sets using the algorithm that is set in the RMAN configuration. You can override the default and set a different algorithm by using the SET COMPRESSION ALGORITHM command before the RESTORE statement.

RMAN can perform recovery by fetching an incremental backup, over the network, from a primary database and then applying this incremental backup to the physical standby database. RMAN is connected as  TARGET  to the physical standby database. The recovery process is optimized by restoring only the used data blocks in a data file. Use the  FROM SERVICE  clause to specify the service name of the primary database from which the incremental backup must be fetched.

To compress backup sets that are used to recover files over the network, use the USING COMPRESSED BACKUPSET. RMAN compresses backup sets when it creates them on the primary database and then transfers these backup sets to the target

 

restore from service

 

能夠經過restore .. from service指定的對象類型：

  • database

  • datafile

  • tablespace

  • 控制文件

  • SPFILE

 

restore datafile from service

當在主庫Primary丟失/或損壞FILE#=6的user01.dbf數據文件時，能夠直接使用restore datafile from service來從standby(其實並不要求必定是DataGuard,只須要是合適的備用庫便可)上得到數據文件，例如：

  

select * from v$version;
BANNER                                                                                         CON_ID
------------------------------------------------------------------------------------------ ----------
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production                        0
PL/SQL Release 12.1.0.2.0 - Production                                                              0
CORE    12.1.0.2.0      Production                                                                          0
TNS for Linux: Version 12.1.0.2.0 - Production                                                      0
NLSRTL Version 12.1.0.2.0 - Production                                                           askmaclean.com
RMAN> select name from v$datafile where file#=6;
NAME                                                                            
--------------------------------------------------------------------------------
/s01/oradata/PDPROD/datafile/o1_mf_users_b2wgb20l_.dbf
 
RMAN> alter database datafile 6 offline;
Statement processed
RMAN> restore datafile 6 from service pdstby;
Starting restore at 04-OCT-14
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=51 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: using network backup set from service pdstby
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00006 to /s01/oradata/PDPROD/datafile/o1_mf_users_b2wgb20l_.dbf
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
Finished restore at 04-OCT-14
RMAN> recover datafile 6 from service pdstby;
Starting recover at 04-OCT-14
using channel ORA_DISK_1
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using network backup set from service pdstby
destination for restore of datafile 00006: /s01/oradata/PDPROD/datafile/o1_mf_users_b2wgb20l_.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/04/2014 02:57:09
ORA-19845: error in backupDatafile while communicating with remote database server
ORA-17628: Oracle error 19648 returned by remote Oracle server
ORA-19648: datafile : incremental-start SCN equals checkpoint SCN
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 6 could not be verified
ORA-19845: error in backupDatafile while communicating with remote database server
ORA-17628: Oracle error 19648 returned by remote Oracle server
ORA-19648: datafile : incremental-start SCN equals checkpoint SCN




以後recover 並online datafile 6便可


 

具體的幾種用法：

 

  • 數據庫級別：　restore database from service <服務別名>

  • 表空間： restore tablespace from service <服務別名>

  • 控制文件： restore controlfile to ‘指定的位置’ from service <服務別名>

  • SPFILE: restore spfile from service <服務別名>

 

 

經過recover .. from service命令能夠經過網絡將service指定的數據庫的增量備份拉過來在本地作recover從而讓本地數據庫跟上遠程數據庫的SCN。

CONNECT TARGET 「sys/<password>@standby as sysdba」 RECOVER DATABASE FROM SERVICE primary;

recover database from service

 

 

此外上述增量備份還能夠是基於壓縮備份的：

 

SET COMPRESSION ALGORITHM ‘BASIC’;

SET COMPRESSION ALGORITHM ‘LOW’;

SET COMPRESSION ALGORITHM ‘MEDIUM’;

SET COMPRESSION ALGORITHM ‘HIGH’;

 

CONNECT TARGET 「sys/<password>@standby as sysdba」

SET COMPRESSION ALGORITHM ‘BASIC’;

RECOVER DATABASE FROM SERVICE primary

USING COMPRESSED BACKUPSET;

 

Rolling Forward a Physical Standby Using Recover From Service Command in 12c (文檔 ID 1987763.1)

In this Document

  Goal
  Solution
  References


APPLIES TO:

Oracle Database - Enterprise Edition - Version 12.1.0.1 and later
Information in this document applies to any platform.

GOAL

 Rolling Forward a Physical Standby Database Using the RECOVER FROM SERVICE Command

A standby database is a transactionally-consistent copy of the production database. It enables production Oracle database to survive disasters and data corruption. If the production database becomes unavailable because of a planned or an unplanned outage, Data Guard can switch a standby database to the production role, minimizing the downtime associated with the outage. Moreover, performance of production database can be improved by offloading resource-intensive backup and reporting operations to standby systems. As you can see, it’s always desirable to have standby database synchronized with the primary database.

Prior to 12c, in order to roll forward the standby database using incremental backups you would need to:

  • Create a control file for the standby database on the primary database.

  • Take an incremental backup on the primary starting from the SCN# of the standby database.

  • Copy the incremental backup to the standby host and catalog it with RMAN.

  • Mount the standby database with newly created standby control file.

  • Cancel managed recovery of the standby database and apply incremental backup to the standby database.

  • Start managed recovery of standby database.

In 12c, this procedure has been dramatically simplified. Now you can use the RECOVER … FROM SERVICE command to synchronize the physical standby database with the primary database.  This command does the following:

  • Creates an incremental backup containing the changes to the primary database. All changes to data files on the primary database, beginning with the SCN in the standby data file header, are included in the incremental backup.

  • Transfers the incremental backup over the network to the physical standby database.

  • Applies the incremental backup to the physical standby database.

This results in rolling forward the standby data files to the same point-in-time as the primary. However, the standby control file still contains old SCN values which are lower than the SCN values in the standby data files. Therefore, to complete the synchronization of the physical standby database, the standby control file needs to be refreshed to update the SCN#.

SOLUTION

Steps to Refresh a Physical Standby Database with Changes Made to the Primary Database

Environment:

Primary Database:
DB_UNIQUE_NAME: prim ( net service name 'PRIM')

Standby Database:
DB_UNIQUE_NAME:clone( net service name 'CLONE')

Use the following steps to refresh the physical standby database with changes made to the primary database:

Prerequisites:

  • Oracle Net connectivity is established between the physical standby database and the primary database.

  • You can do this by adding an entry corresponding to the primary database in the tnsnames.ora file of the physical standby database.

  • The password files on the primary database and the physical standby database are the same.

  • The COMPATIBLE parameter in the initialization parameter file of the primary database and physical standby database is set to 12.0.

  • Start RMAN and connect as target to the physical standby database.

Check the existing size of the Primary database and compare with the standby existing size as we need at-least the difference in size (free space) since standby is behind ,if the datafile on primary has autoextended then standby file would be same in size compared to prod,so when you do the incremental rollforward it would apply the blocks and add any new one to match the size of standby file.

1. Place the physical standby database in MOUNT mode.


    SHUTDOWN IMMEDIATE;
    STARTUP MOUNT;

 2. Stop the managed recovery processes on the physical standby database.

 ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

 

NOTE:  If using broker, you will need to stop MRP through DGMGRL.  I.e.:

DGMGRL> edit database '<Standby db_unique_name>' set STATE='APPLY-OFF' ;

3. Let us identify the datafiles on standby database which are out of sync with respect to primary.


Primary:

SQL> select HXFIL File_num,substr(HXFNM,1,40),fhscn from x$kcvfh;

  FILE_NUM SUBSTR(HXFNM,1,40)                       FHSCN
---------- ---------------------------------------- ----------------
         1 /u01/app/oracle/oradata/prim/system01.db 1984501
         3 /u01/app/oracle/oradata/prim/sysaux01.db 1984501
         4 /u01/app/oracle/oradata/prim/undotbs01.d 1984501
         5 /u01/app/oracle/oradata/prim/pdbseed/sys 1733076
         6 /u01/app/oracle/oradata/prim/users01.dbf 1984501
         7 /u01/app/oracle/oradata/prim/pdbseed/sys 1733076
         8 /u01/app/oracle/oradata/prim/pdb1/system 1984501
         9 /u01/app/oracle/oradata/prim/pdb1/sysaux 1984501
        10 /u01/app/oracle/oradata/prim/pdb1/pdb1_u 1984501
        16 /u01/app/oracle/oradata/prim/pdb3/system 1984501
        17 /u01/app/oracle/oradata/prim/pdb3/sysaux 1984501
        18 /u01/app/oracle/oradata/prim/pdb3/pdb1_u 1984501
        19 /u01/app/oracle/oradata/prim/pdb3/test.d 1984501

13 rows selected.

STANDBy:

SQL>  select HXFIL File_num,substr(HXFNM,1,40),fhscn from x$kcvfh;

  FILE_NUM SUBSTR(HXFNM,1,40)                       FHSCN
---------- ---------------------------------------- ----------------
         1 /u01/app/oracle/oradata/clone/system01.d 1980995
         3 /u01/app/oracle/oradata/clone/sysaux01.d 1980998
         4 /u01/app/oracle/oradata/clone/undotbs01. 1981008
         5 /u01/app/oracle/oradata/clone/pdbseed/sy 1733076
         6 /u01/app/oracle/oradata/clone/users01.db 1981012
         7 /u01/app/oracle/oradata/clone/pdbseed/sy 1733076
         8 /u01/app/oracle/oradata/clone/pdb1/syste 1981015
         9 /u01/app/oracle/oradata/clone/pdb1/sysau 1981021
        10 /u01/app/oracle/oradata/clone/pdb1/pdb1_ 1981028
        16 /u01/app/oracle/oradata/clone/pdb3/syste 1981030
        17 /u01/app/oracle/oradata/clone/pdb3/sysau 1981036
        18 /u01/app/oracle/oradata/clone/pdb3/pdb1_ 1981043
        19 /u01/app/oracle/oradata/clone/pdb3/test. 1981044

13 rows selected. 

On  checking SCN in datafile headers on primary (prim) and standby (clone), we note that whereas SCN

of datafiles 5,7 match on primary and standby, for rest of the  datafiles (1,3,4,6,8,9,10,16,17) standby is lagging behind  primary.

 

4. Note the current SCN of the physical standby database. This is required to determine, in a later step, if new data files were added to the primary database.

Query the V$DATABASE view to obtain the current SCN using the following command:

SELECT CURRENT_SCN FROM V$DATABASE;

5. The RECOVER … FROM SERVICE command refreshes the standby data files and rolls them forward to the same point-in-time as the primary.

[oracle@localhost ~]$ rman target/

Recovery Manager: Release 12.1.0.1.0 - Production on Mon Mar 9 18:22:52 2015

Copyright (c) 1982, 2013, Oracle and/or its affiliates.  All rights reserved.

connected to target database: PRIM (DBID=4165840403, not open)

RMAN> recover database from service prim noredo using compressed backupset;

  Log:


Starting recover at 09-MAR-15
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=32 device type=DISK
skipping datafile 5; already restored to SCN 1733076
skipping datafile 7; already restored to SCN 1733076
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service prim
destination for restore of datafile 00001: /u01/app/oracle/oradata/clone/system01.dbf
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service prim
destination for restore of datafile 00003: /u01/app/oracle/oradata/clone/sysaux01.dbf
channel ORA_DISK_1: restore complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service prim
destination for restore of datafile 00004: /u01/app/oracle/oradata/clone/undotbs01.dbf
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service prim
destination for restore of datafile 00006: /u01/app/oracle/oradata/clone/users01.dbf
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service prim
destination for restore of datafile 00008: /u01/app/oracle/oradata/clone/pdb1/system01.dbf
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service prim
destination for restore of datafile 00009: /u01/app/oracle/oradata/clone/pdb1/sysaux01.dbf
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service prim
destination for restore of datafile 00010: /u01/app/oracle/oradata/clone/pdb1/pdb1_users01.dbf
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service prim
destination for restore of datafile 00016: /u01/app/oracle/oradata/clone/pdb3/system01.dbf
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service prim
destination for restore of datafile 00017: /u01/app/oracle/oradata/clone/pdb3/sysaux01.dbf
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service prim
destination for restore of datafile 00018: /u01/app/oracle/oradata/clone/pdb3/pdb1_users01.dbf
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service prim
destination for restore of datafile 00019: /u01/app/oracle/oradata/clone/pdb3/test.dbf
channel ORA_DISK_1: restore complete, elapsed time: 00:00:02

Finished recover at 09-MAR-15


6. Lets check the SCNs of the datafiles at primary and standby now.

Primary
--------
SQL> select HXFIL File_num,substr(HXFNM,1,40),fhscn from x$kcvfh;

  FILE_NUM SUBSTR(HXFNM,1,40)                       FHSCN
---------- ---------------------------------------- ----------------
         1 /u01/app/oracle/oradata/prim/system01.db 1985174
         3 /u01/app/oracle/oradata/prim/sysaux01.db 1985183
         4 /u01/app/oracle/oradata/prim/undotbs01.d 1985194
         5 /u01/app/oracle/oradata/prim/pdbseed/sys 1733076
         6 /u01/app/oracle/oradata/prim/users01.dbf 1985203
         7 /u01/app/oracle/oradata/prim/pdbseed/sys 1733076
         8 /u01/app/oracle/oradata/prim/pdb1/system 1985206
         9 /u01/app/oracle/oradata/prim/pdb1/sysaux 1985212
        10 /u01/app/oracle/oradata/prim/pdb1/pdb1_u 1985218
        16 /u01/app/oracle/oradata/prim/pdb3/system 1985221
        17 /u01/app/oracle/oradata/prim/pdb3/sysaux 1985343
        18 /u01/app/oracle/oradata/prim/pdb3/pdb1_u 1985350
        19 /u01/app/oracle/oradata/prim/pdb3/test.d 1985354

Standby
--------
RMAN> select HXFIL File_num,substr(HXFNM,1,40),fhscn from x$kcvfh;

  FILE_NUM SUBSTR(HXFNM,1,40)                       FHSCN
---------- ---------------------------------------- ----------------
         1 /u01/app/oracle/oradata/clone/system01.d 1985174
         3 /u01/app/oracle/oradata/clone/sysaux01.d 1985183
         4 /u01/app/oracle/oradata/clone/undotbs01. 1985194
         5 /u01/app/oracle/oradata/clone/pdbseed/sy 1733076
         6 /u01/app/oracle/oradata/clone/users01.db 1985203
         7 /u01/app/oracle/oradata/clone/pdbseed/sy 1733076
         8 /u01/app/oracle/oradata/clone/pdb1/syste 1985206
         9 /u01/app/oracle/oradata/clone/pdb1/sysau 1985212
        10 /u01/app/oracle/oradata/clone/pdb1/pdb1_ 1985218
        16 /u01/app/oracle/oradata/clone/pdb3/syste 1985221
        17 /u01/app/oracle/oradata/clone/pdb3/sysau 1985343
        18 /u01/app/oracle/oradata/clone/pdb3/pdb1_ 1985350
        19 /u01/app/oracle/oradata/clone/pdb3/test. 1985354

13 rows selected

 

From above,we can see primary and standby SCNs matching now.


However, the standby control file still contains old SCN values which are lower than the SCN values in the standby data files. 
Therefore, to complete the synchronization of the physical standby database, we must refresh the standby control file to update the SCN#.

7. Use the following commands to shut down the standby database and then start it in NOMOUNT mode.


    SHUTDOWN IMMEDIATE;
    STARTUP NOMOUNT;


8. Restore the standby control file by using the control file on the primary database using service prim.

The following command restores the control file on the physical standby database by using the primary database control file.

RESTORE STANDBY CONTROLFILE FROM SERVICE <primary_tns_service>;

RMAN> restore standby controlfile from service prim;

Starting restore at 09-MAR-15
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: using network backup set from service prim
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output file name=/u01/app/oracle/oradata/clone/control01.ctl
output file name=/u01/app/oracle/fast_recovery_area/clone/control02.ctl
Finished restore at 09-MAR-15

 

After this step, the names of files in the standby control file are the names that were used in the primary database.

NOTE:  Depending on the configuration, the path and/or names of the standby datafiles after the standby controlfile refresh may be correct and thus steps #9 and #10 can be skipped.  

 

Mount the standby database using the following command:

RMAN> alter database mount;

Statement processed
released channel: ORA_DISK_1


RMAN> report schema;

Starting implicit crosscheck backup at 09-MAR-15
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=21 device type=DISK
Crosschecked 9 objects
Finished implicit crosscheck backup at 09-MAR-15

Starting implicit crosscheck copy at 09-MAR-15
using channel ORA_DISK_1
Crosschecked 2 objects
Finished implicit crosscheck copy at 09-MAR-15

searching for all files in the recovery area
cataloging files...
cataloging done

List of Cataloged Files
=======================
File Name: /u01/app/oracle/fast_recovery_area/CLONE/archivelog/2015_03_05/o1_mf_1_17_11q13dm8_.arc
File Name: /u01/app/oracle/fast_recovery_area/CLONE/archivelog/2015_03_05/o1_mf_1_16_10q13dm8_.arc
File Name: /u01/app/oracle/fast_recovery_area/CLONE/archivelog/2015_03_05/o1_mf_1_2_bhk1ctcz_.arc
File Name: /u01/app/oracle/fast_recovery_area/CLONE/archivelog/2015_03_05/o1_mf_1_1_bhk17cw8_.arc

RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
Report of database schema for database with db_unique_name CLONE

List of Permanent Datafiles
===========================
File Size(MB) Tablespace           RB segs Datafile Name
---- -------- -------------------- ------- ------------------------
1    780      SYSTEM               ***     /u01/app/oracle/oradata/prim/system01.dbf
3    730      SYSAUX               ***     /u01/app/oracle/oradata/prim/sysaux01.dbf
4    90       UNDOTBS1             ***     /u01/app/oracle/oradata/prim/undotbs01.dbf
5    250      PDB$SEED:SYSTEM      ***     /u01/app/oracle/oradata/prim/pdbseed/system01.dbf
6    5        USERS                ***     /u01/app/oracle/oradata/prim/users01.dbf
7    590      PDB$SEED:SYSAUX      ***     /u01/app/oracle/oradata/prim/pdbseed/sysaux01.dbf
8    260      PDB1:SYSTEM          ***     /u01/app/oracle/oradata/prim/pdb1/system01.dbf
9    620      PDB1:SYSAUX          ***     /u01/app/oracle/oradata/prim/pdb1/sysaux01.dbf
10   5        PDB1:USERS           ***     /u01/app/oracle/oradata/prim/pdb1/pdb1_users01.dbf
16   260      PDB3:SYSTEM          ***     /u01/app/oracle/oradata/prim/pdb3/system01.dbf
17   620      PDB3:SYSAUX          ***     /u01/app/oracle/oradata/prim/pdb3/sysaux01.dbf
18   5        PDB3:USERS           ***     /u01/app/oracle/oradata/prim/pdb3/pdb1_users01.dbf
19   50       PDB3:TEST            ***     /u01/app/oracle/oradata/prim/pdb3/test.dbf

List of Temporary Files
=======================
File Size(MB) Tablespace           Maxsize(MB) Tempfile Name
---- -------- -------------------- ----------- --------------------
1    60       TEMP                 32767       /u01/app/oracle/oradata/prim/temp01.dbf
2    20       PDB$SEED:TEMP        32767       /u01/app/oracle/oradata/prim/pdbseed/pdbseed_temp01.dbf
3    373      PDB1:TEMP            32767       /u01/app/oracle/oradata/prim/pdb1/temp01.dbf
4    71       PDB3:TEMP            32767       /u01/app/oracle/oradata/prim/pdb3/temp01.dbf


9. Update the names of the data files and the temp files in the standby control file.

 

   Use the CATALOG command and the SWITCH command to update all the data file names.

        RMAN> catalog start with '<path where the actual standby datafile existed>';

        In this case

        RMAN> Catalog start with '/u01/app/oracle/oradata/clone/';

searching for all files that match the pattern /u01/app/oracle/oradata/clone

List of Files Unknown to the Database
=====================================
File Name: /u01/app/oracle/oradata/clone/pdb1/pdb1_users01.dbf
File Name: /u01/app/oracle/oradata/clone/pdb1/sysaux01.dbf
File Name: /u01/app/oracle/oradata/clone/pdb1/system01.dbf
File Name: /u01/app/oracle/oradata/clone/pdbseed/sysaux01.dbf
File Name: /u01/app/oracle/oradata/clone/pdbseed/system01.dbf
File Name: /u01/app/oracle/oradata/clone/sysaux01.dbf
File Name: /u01/app/oracle/oradata/clone/system01.dbf
File Name: /u01/app/oracle/oradata/clone/undotbs01.dbf
File Name: /u01/app/oracle/oradata/clone/users01.dbf
File Name: /u01/app/oracle/oradata/clone/pdb3/pdb1_users01.dbf
File Name: /u01/app/oracle/oradata/clone/pdb3/sysaux01.dbf
File Name: /u01/app/oracle/oradata/clone/pdb3/system01.dbf
File Name: /u01/app/oracle/oradata/clone/pdb3/test.dbf

Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done

List of Cataloged Files
=======================
File Name: /u01/app/oracle/oradata/clone/pdb1/pdb1_users01.dbf
File Name: /u01/app/oracle/oradata/clone/pdb1/sysaux01.dbf
File Name: /u01/app/oracle/oradata/clone/pdb1/system01.dbf
File Name: /u01/app/oracle/oradata/clone/pdbseed/sysaux01.dbf
File Name: /u01/app/oracle/oradata/clone/pdbseed/system01.dbf
File Name: /u01/app/oracle/oradata/clone/sysaux01.dbf
File Name: /u01/app/oracle/oradata/clone/system01.dbf
File Name: /u01/app/oracle/oradata/clone/undotbs01.dbf
File Name: /u01/app/oracle/oradata/clone/users01.dbf
File Name: /u01/app/oracle/oradata/clone/pdb3/pdb1_users01.dbf
File Name: /u01/app/oracle/oradata/clone/pdb3/sysaux01.dbf
File Name: /u01/app/oracle/oradata/clone/pdb3/system01.dbf
File Name: /u01/app/oracle/oradata/clone/pdb3/test.dbf

10. Switch to cataloged copy.

RMAN> SWITCH DATABASE TO COPY;

datafile 1 switched to datafile copy "/u01/app/oracle/oradata/clone/system01.dbf"
datafile 3 switched to datafile copy "/u01/app/oracle/oradata/clone/sysaux01.dbf"
datafile 4 switched to datafile copy "/u01/app/oracle/oradata/clone/undotbs01.dbf"
datafile 5 switched to datafile copy "/u01/app/oracle/oradata/clone/pdbseed/system01.dbf"
datafile 6 switched to datafile copy "/u01/app/oracle/oradata/clone/users01.dbf"
datafile 7 switched to datafile copy "/u01/app/oracle/oradata/clone/pdbseed/sysaux01.dbf"
datafile 8 switched to datafile copy "/u01/app/oracle/oradata/clone/pdb1/system01.dbf"
datafile 9 switched to datafile copy "/u01/app/oracle/oradata/clone/pdb1/sysaux01.dbf"
datafile 10 switched to datafile copy "/u01/app/oracle/oradata/clone/pdb1/pdb1_users01.dbf"
datafile 16 switched to datafile copy "/u01/app/oracle/oradata/clone/pdb3/system01.dbf"
datafile 17 switched to datafile copy "/u01/app/oracle/oradata/clone/pdb3/sysaux01.dbf"
datafile 18 switched to datafile copy "/u01/app/oracle/oradata/clone/pdb3/pdb1_users01.dbf"
datafile 19 switched to datafile copy "/u01/app/oracle/oradata/clone/pdb3/test.dbf"


Here, /u01/app/oracle/oradata/clone is the location of the data files on the physical standby database.
All data files must be stored in this location.

11. Use the current SCN returned in Step 4 to determine if new data files were added to the primary database since the standby database was last refreshed. If yes, these data files need to be restored on the standby from the primary database.

The following example assumes that the CURRENT_SCN returned in Step 6 is 1984232 and lists the data files that were created on the primary after the timestamp represented by this SCN:

SELECT file# FROM V$DATAFILE WHERE creation_change# >= 1984232;

If no files are returned in Step 11, then go to Step 13. If one or more files are returned in Step 11, then restore these data files from the primary database as in step 12.

12. If you are not connected to a recovery catalog, then use the following commands to restore data files that were added to the primary after the standby was last refreshed ( assuming datafile 21  added to the primary):

RUN
{
SET NEWNAME FOR DATABASE TO '/u01/app/oracle/oradata/clone';
RESTORE DATAFILE 21 FROM SERVICE prim;
}

If you are connected to a recovery catalog, then use the following command to restore data files that were added to the primary after the standby was last refreshed (assuming data file 21 added to the primary):

RESTORE DATAFILE 21 FROM SERVICE prim;



13. Update the names of the online redo logs and standby redo logs in the standby control file using one of the following methods:

 - Use the ALTER DATABASE CLEAR command to clear the log files in all redo log groups of the standby database. RMAN then recreates all the standby redo logs and the online redo log files.

 Note:

Clearing log files is recommended only if the standby database does not have access to the online redo log files and standby redo log
 files of the primary database( for ex: standby and primary at same server or using same ASM disk group). If the standby database has access to the redo log files of the primary database and the redo log file
 names of the primary database are OMF names, then the ALTER DATABASE command will delete log files on the primary database.

 - Use the ALTER DATABASE RENAME FILE command to rename the redo log files.
   Use a separate command to rename each log file.

   To rename log files, the STANDBY_FILE_MANAGEMENT initialization parameter must be set to MANUAL. 
   Renaming log files is recommended when the number of online redo logs files and standby redo log files is the same
   in the primary database and the physical standby database.

   (Oracle Active Data Guard only) Perform the following steps to open the physical standby database:



On the primary database, switch the archived redo log files using the following command:

       

ALTER SYSTEM ARCHIVE LOG CURRENT;

 
On the physical standby database, run the following commands:

        RECOVER DATABASE;
        ALTER DATABASE OPEN READ ONLY;

     Start the managed recovery processes on the physical standby database by using the following command:


     ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;


REFERENCES

NOTE:1646232.1 - ORA-19573 when trying to restore to standby with incremental backup From Primary or During any RMAN restore operation






About Me

........................................................................................................................

● 本文做者：小麥苗，部份內容整理自網絡，如有侵權請聯繫小麥苗刪除

● 本文在itpub（http://blog.itpub.net/26736162）、博客園（http://www.cnblogs.com/lhrbest）和我的微信公衆號（xiaomaimiaolhr）上有同步更新

● 本文itpub地址：http://blog.itpub.net/26736162

● 本文博客園地址：http://www.cnblogs.com/lhrbest

● 本文pdf版、我的簡介及小麥苗雲盤地址：http://blog.itpub.net/26736162/viewspace-1624453/

● 數據庫筆試面試題庫及解答：http://blog.itpub.net/26736162/viewspace-2134706/

● DBA寶典今日頭條號地址：http://www.toutiao.com/c/user/6401772890/#mid=1564638659405826

........................................................................................................................

● QQ羣號：230161599（滿）、618766405

● 微信羣：可加我微信，我拉你們進羣，非誠勿擾

● 聯繫我請加QQ好友（646634621），註明添加原因

● 於 2018-04-01 06:00 ~ 2018-04-31 24:00 在魔都完成

● 最新修改時間：2018-07-01 06:00 ~ 2018-07-31 24:00

● 文章內容來源於小麥苗的學習筆記，部分整理自網絡，如有侵權或不當之處還請諒解

● 版權全部，歡迎分享本文，轉載請保留出處

........................................................................................................................

● 小麥苗的微店：https://weidian.com/s/793741433?wfr=c&ifr=shopdetail

● 小麥苗出版的數據庫類叢書：http://blog.itpub.net/26736162/viewspace-2142121/

● 小麥苗OCP、OCM、高可用網絡班：http://blog.itpub.net/26736162/viewspace-2148098/

● 小麥苗騰訊課堂主頁：https://lhr.ke.qq.com/

........................................................................................................................

使用微信客戶端掃描下面的二維碼來關注小麥苗的微信公衆號（xiaomaimiaolhr）及QQ羣（DBA寶典）、添加小麥苗微信，學習最實用的數據庫技術。

........................................................................................................................

歡迎與我聯繫
相關文章
相關標籤/搜索
每日一句
    每一个你不满意的现在，都有一个你没有努力的曾经。
本站公眾號
   歡迎關注本站公眾號,獲取更多信息
聯繫我們 最近搜索 最新文章 沪ICP备13005482号-10 MyBatis教程 SQL 教程 MySQL教程 Java 教程 Thymeleaf 教程 Hibernate教程 Spring教程 Redis教程