在另外一臺伺服器上利用備份恢復RAC資料庫的過程。

這一篇描述恢復前的準備工作。

由於當前沒有現成的RAC環境，只能在一臺伺服器上透過單例項恢復這個RAC資料庫。

由於本地磁碟沒有足夠的空間來存放備份檔案，因此資料庫的備份和需要的歸檔備份檔案都已經透過ftp到方式放到ASM磁碟組中。

雖然這個資料庫是單例項資料庫，但是恢復出來的資料檔案和日誌檔案也會存放到ASM磁碟組中。

下面是恢復前的準備工作，首先設定當前的ORACLE_SID，然後從備份集中恢復初始化引數檔案和控制檔案：

bash-3.00$ export ORACLE_SID=tradedb1
bash-3.00$ rman target /

恢復管理器: Release 10.2.0.3.0 - Production on 星期四 8月 6 17:40:28 2009

已連線到目標資料庫 (未啟動)

RMAN> startup nomount

啟動失敗: ORA-01078: failure in processing system parameters
LRM-00109: ???????????????? '/data/oracle/product/10.2/dbs/inittradedb1.ora'

在沒有引數檔案的情況下啟動 Oracle 例項以檢索 spfile
Oracle 例項已啟動

系統全域性區域總計 159383552 位元組

Fixed Size                     2126864 位元組
Variable Size                 77433840 位元組
Database Buffers              75497472 位元組
Redo Buffers                   4325376 位元組

RMAN> restore spfile to '+DATA/tradedb/spfiletradedb1.ora' from '+DATA/tradedb/9iklkq9n_1_1';

啟動 restore 於 06-8月 -09
使用目標資料庫控制檔案替代恢復目錄分配的通道: ORA_DISK_1
通道 ORA_DISK_1: sid=23 devtype=DISK

通道 ORA_DISK_1: 已找到的自動備份: +DATA/tradedb/9iklkq9n_1_1
MAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: restore 命令 (在 08/06/2009 17:41:51 上) 失敗
ORA-19687: 在備份集內找不到 SPFILE

RMAN> restore spfile to '+DATA/tradedb/spfiletradedb1.ora' from '+DATA/tradedb/9jklkq9n_1_1';

啟動 restore 於 06-8月 -09
使用通道 ORA_DISK_1

通道 ORA_DISK_1: 已找到的自動備份: +DATA/tradedb/9jklkq9n_1_1
通道 ORA_DISK_1: 從自動備份復原 SPFILE 已完成
完成 restore 於 06-8月 -09

RMAN> restore controlfile to '+DATA/tradedb/control01.ctl' from '+DATA/tradedb/9jklkq9n_1_1';

啟動 restore 於 06-8月 -09
使用通道 ORA_DISK_1

通道 ORA_DISK_1: 正在復原控制檔案
通道 ORA_DISK_1: 恢復完成, 用時: 00:00:04
完成 restore 於 06-8月 -09

RMAN> shutdown

Oracle 例項已關閉

RMAN> exit

恢復管理器完成。

由於不瞭解控制檔案和SPFILE初始化引數檔案到底存放在哪個備份級中，因此只能透過嘗試的辦法進行恢復。不過要是原資料庫存在的話，可以透過rman獲得這個資訊，另外備份時的日誌也包含了這個資訊。

由於原始資料庫的RAC環境，且主機記憶體空間比較大，而當前只是普通的單例項環境，且主機上執行了多個資料庫，因此需要對初始化引數進行調整。去掉所有RAC相關的引數設定，去掉例項2和例項1設定的例項級的引數，僅保留資料庫級的引數設定，並根據現有主主機的記憶體，調整SGA和PGA引數。

調整後的初始化引數如下：

*.audit_file_dest='/data/oracle/admin/tradedb/adump'
*.background_dump_dest='/data/oracle/admin/tradedb/bdump'
*.cluster_database=false
*.cluster_database_instances=1
*.compatible='10.2.0.1.0'
*.control_files='+DATA/tradedb/control01.ctl'
*.core_dump_dest='/data/oracle/admin/tradedb/cdump'
*.db_block_size=16384
*.db_domain='us.oracle.com'
*.db_file_multiblock_read_count=16
*.db_name='tradedb'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=tradedbXDB)'
*.global_names=TRUE
*.job_queue_processes=50
*.log_archive_dest_1='LOCATION=+DATA/tradedb/'
*.log_archive_format='%t_%s_%r.dbf'
*.log_archive_local_first=FALSE
*.nls_language='AMERICAN'
*.nls_territory='AMERICA'
*.open_cursors=5000
*.pga_aggregate_target=1098907648
*.processes=300
*.remote_login_passwordfile='EXCLUSIVE'
*.session_max_open_files=20
*.sessions=335
*.sga_target=4395630592
*.streams_pool_size=50331648
*.undo_management='AUTO'
*.undo_retention=10800
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/data/oracle/admin/tradedb/udump'

下面建立資料庫啟動所需的目錄：

$ mkdir -p /data/oracle/admin/tradedb
$ cd /data/oracle/admin/tradedb
$ mkdir bdump adump cdump udump

確保ASM例項中對應的目錄已經建立。

下面透過sqlplus啟動資料庫例項：

SQL> startup mount pfile=/export/home/oracle/inittradedb1.ora
ORACLE 例程已經啟動。

Total System Global Area 4395630592 bytes
Fixed Size                  2134096 bytes
Variable Size             882732976 bytes
Database Buffers         3506438144 bytes
Redo Buffers                4325376 bytes
資料庫裝載完畢。
SQL> exit
從 Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options 斷開

下面進入RMAN環境，並清除掉所有的RMAN現有設定：

bash-3.00$ rman target /

恢復管理器: Release 10.2.0.3.0 - Production on 星期五 8月 7 10:22:57 2009

已連線到目標資料庫: TRADEDB (DBID=4181457554, 未開啟)

RMAN> show all;

RMAN 配置引數為:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/data/backup/tradedb/%U';
CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT '*' FORMAT   '/data/backup/tradedb/%U';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT '*' FORMAT   '/data/backup/tradedb/%U';
CONFIGURE CHANNEL 1 DEVICE TYPE 'SBT_TAPE' CONNECT '*';
CONFIGURE CHANNEL 2 DEVICE TYPE 'SBT_TAPE' CONNECT '*';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/data/oracle/product/10.2/dbs/snapcf_tradedb1.f'; # default

RMAN> configure channel device type disk clear;

舊的 RMAN 配置引數:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/data/backup/tradedb/%U';
已成功刪除舊的 RMAN 配置引數

RMAN> configure channel 1 device type sbt clear;

舊的 RMAN 配置引數:
CONFIGURE CHANNEL 1 DEVICE TYPE 'SBT_TAPE' CONNECT '*';
已成功刪除舊的 RMAN 配置引數

RMAN> configure channel 2 device type sbt clear;

舊的 RMAN 配置引數:
CONFIGURE CHANNEL 2 DEVICE TYPE 'SBT_TAPE' CONNECT '*';
已成功刪除舊的 RMAN 配置引數

RMAN> configure channel 1 device type disk clear;

舊的 RMAN 配置引數:
CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT '*' FORMAT '/data/backup/tradedb/%U';
已成功刪除舊的 RMAN 配置引數

RMAN> configure channel 2 device type disk clear;

舊的 RMAN 配置引數:
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT '*' FORMAT '/data/backup/tradedb/%U';
已成功刪除舊的 RMAN 配置引數

RMAN> configure device type disk clear;

舊的 RMAN 配置引數:
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
RMAN 配置引數已成功重置為預設值

RMAN> configure device type sbt clear;

舊的 RMAN 配置引數:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
RMAN 配置引數已成功重置為預設值

由於備份集的存放路徑發生了變化，因此需要透過CATALOG命令，將備份集的新位置加到控制檔案中：

RMAN> catalog backuppiece '+DATA/tradedb/9iklkq9n_1_1';

已列入目錄的備份段
備份段 handle=+DATA/tradedb/9iklkq9n_1_1 recid=2331 stamp=694262033

RMAN> catalog backuppiece '+DATA/tradedb/9jklkq9n_1_1';

已列入目錄的備份段
備份段 handle=+DATA/tradedb/9jklkq9n_1_1 recid=2332 stamp=694262049

RMAN> catalog backuppiece '+DATA/tradedb/9kklkslb_1_1';

已列入目錄的備份段
備份段 handle=+DATA/tradedb/9kklkslb_1_1 recid=2333 stamp=694262061

RMAN> catalog backuppiece '+DATA/tradedb/9lklkslb_1_1';

已列入目錄的備份段
備份段 handle=+DATA/tradedb/9lklkslb_1_1 recid=2334 stamp=694262072

RMAN> catalog backuppiece '+DATA/tradedb/9nklksn0_1_1';

已列入目錄的備份段
備份段 handle=+DATA/tradedb/9nklksn0_1_1 recid=2335 stamp=694262082

RMAN> catalog backuppiece '+DATA/tradedb/9oklkt7p_1_1';

已列入目錄的備份段
備份段 handle=+DATA/tradedb/9oklkt7p_1_1 recid=2336 stamp=694262091

由於源資料庫的資料檔案存放在veritas管理的共享裸裝置中，而當前目標資料庫使用ASM磁碟組作為共享儲存介質，顯然二者路徑是不一致的，因此需要透過SET NEWNAME FOR DATAFILE語句來設定每個資料檔案的新路徑。

由於資料檔案太多，因此這部分指令碼透過源資料庫中SQL獲得：

SQL> SELECT FILE_ID, FILE_NAME FROM DBA_DATA_FILES;

   FILE_ID FILE_NAME
---------- ------------------------------------------------------------
         1 /dev/vx/rdsk/datadg/tradedb_system_1_4g
         2 /dev/vx/rdsk/datadg/tradedb_undotbs1_1_4g
         3 /dev/vx/rdsk/datadg/tradedb_undotbs1_2_4g
         4 /dev/vx/rdsk/datadg/tradedb_undotbs1_3_4g
         5 /dev/vx/rdsk/datadg/tradedb_undotbs1_4_4g
         6 /dev/vx/rdsk/datadg/tradedb_undotbs1_5_4g
         7 /dev/vx/rdsk/datadg/tradedb_sysaux_1_1g
         8 /dev/vx/rdsk/datadg/tradedb_undotbs2_1_4g
         9 /dev/vx/rdsk/datadg/tradedb_undotbs2_2_4g
        10 /dev/vx/rdsk/datadg/tradedb_undotbs2_3_4g
        11 /dev/vx/rdsk/datadg/tradedb_undotbs2_4_4g
        12 /dev/vx/rdsk/datadg/tradedb_undotbs2_5_4g
        13 /dev/vx/rdsk/datadg/tradedb_users_1_200m
        14 /dev/vx/rdsk/datadg/tradedb_ndmain_1_4g
        15 /dev/vx/rdsk/datadg/tradedb_ndmain_2_4g
        16 /dev/vx/rdsk/datadg/tradedb_ndmain_3_4g
        17 /dev/vx/rdsk/datadg/tradedb_anhui_1
        18 /dev/vx/rdsk/datadg/tradedb_anhui_2
        19 /dev/vx/rdsk/datadg/tradedb_anhui_3
        20 /dev/vx/rdsk/datadg/tradedb_anhui_4
        21 /dev/vx/rdsk/datadg/tradedb_zhejiang_1_4g
        22 /dev/vx/rdsk/datadg/tradedb_zhejiang_2_4g
        23 /dev/vx/rdsk/datadg/tradedb_zhejiang_3_4g
        24 /dev/vx/rdsk/datadg/tradedb_zhejiang_4_4g
        25 /dev/vx/rdsk/datadg/tradedb_zhejiang_5_4g
        26 /dev/vx/rdsk/datadg/tradedb_zhejiang_6_4g
        27 /dev/vx/rdsk/datadg/tradedb_zhejiang_7_4g
        28 /dev/vx/rdsk/datadg/tradedb_zhejiang_8_4g
        29 /dev/vx/rdsk/datadg/tradedb_zhejiang_9_4g
        30 /dev/vx/rdsk/datadg/tradedb_zhejiang_10_4g
        31 /dev/vx/rdsk/datadg/tradedb_zhejiang_11_4g
        32 /dev/vx/rdsk/datadg/tradedb_zhejiang_12_4g
        33 /dev/vx/rdsk/datadg/tradedb_zhejiang_13_4g
        34 /dev/vx/rdsk/datadg/tradedb_zhejiang_14_4g
        35 /dev/vx/rdsk/datadg/tradedb_zhejiang_15_4g
        36 /dev/vx/rdsk/datadg/tradedb_zhejiang_16_4g
        37 /dev/vx/rdsk/datadg/tradedb_zhejiang_17_4g
        38 /dev/vx/rdsk/datadg/tradedb_zhejiang_18_4g
        39 /dev/vx/rdsk/datadg/tradedb_sysaux_2_1g
        40 /dev/vx/rdsk/datadg/tradedb_gpo_1_4g
        41 /dev/vx/rdsk/datadg/tradedb_gpo_2_4g
        42 /dev/vx/rdsk/datadg/tradedb_gpo_3_4g
        43 /dev/vx/rdsk/datadg/tradedb_gpo_4_4g
        44 /dev/vx/rdsk/datadg/tradedb_zhejiang_19_4g
        45 /dev/vx/rdsk/datadg/tradedb_zhejiang_20_4g
        46 /dev/vx/rdsk/datadg/tradedb_beijing_1_4g
        47 /dev/vx/rdsk/datadg/tradedb_beijing_2_4g
        48 /dev/vx/rdsk/datadg/tradedb_beijing_3_4g
        49 /dev/vx/rdsk/datadg/tradedb_beijing_4_4g
        50 /dev/vx/rdsk/datadg/tradedb_beijing_5_4g
        51 /dev/vx/rdsk/datadg/tradedb_beijing_6_4g
        52 /dev/vx/rdsk/datadg/tradedb_beijing_7_4g
        53 /dev/vx/rdsk/datadg/tradedb_beijing_8_4g
        54 /dev/vx/rdsk/datadg/tradedb_beijing_9_4g
        55 /dev/vx/rdsk/datadg/tradedb_beijing_10_4g
        56 /dev/vx/rdsk/datadg/tradedb_beijing_11_4g
        57 /dev/vx/rdsk/datadg/tradedb_beijing_12_4g
        58 /dev/vx/rdsk/datadg/tradedb_beijing_13_4g
        59 /dev/vx/rdsk/datadg/tradedb_beijing_14_4g
        60 /dev/vx/rdsk/datadg/tradedb_beijing_15_4g

已選擇60行。

SQL> SELECT 'SET NEWNAME FOR DATAFILE ' || FILE_ID || ' TO ''+DATA/tradedb/'
2 || SUBSTR(FILE_NAME, 21) || ''';'
3 FROM DBA_DATA_FILES;

'SETNEWNAMEFORDATAFILE'||FILE_ID||'TO''+DATA/TRADEDB/'||SUBSTR(FILE_NAME,21)||''';'
--------------------------------------------------------------------------------------
SET NEWNAME FOR DATAFILE 1 TO '+DATA/tradedb/tradedb_system_1_4g';
SET NEWNAME FOR DATAFILE 2 TO '+DATA/tradedb/tradedb_undotbs1_1_4g';
SET NEWNAME FOR DATAFILE 3 TO '+DATA/tradedb/tradedb_undotbs1_2_4g';
SET NEWNAME FOR DATAFILE 4 TO '+DATA/tradedb/tradedb_undotbs1_3_4g';
SET NEWNAME FOR DATAFILE 5 TO '+DATA/tradedb/tradedb_undotbs1_4_4g';
SET NEWNAME FOR DATAFILE 6 TO '+DATA/tradedb/tradedb_undotbs1_5_4g';
SET NEWNAME FOR DATAFILE 7 TO '+DATA/tradedb/tradedb_sysaux_1_1g';
SET NEWNAME FOR DATAFILE 8 TO '+DATA/tradedb/tradedb_undotbs2_1_4g';
SET NEWNAME FOR DATAFILE 9 TO '+DATA/tradedb/tradedb_undotbs2_2_4g';
SET NEWNAME FOR DATAFILE 10 TO '+DATA/tradedb/tradedb_undotbs2_3_4g';
SET NEWNAME FOR DATAFILE 11 TO '+DATA/tradedb/tradedb_undotbs2_4_4g';
SET NEWNAME FOR DATAFILE 12 TO '+DATA/tradedb/tradedb_undotbs2_5_4g';
SET NEWNAME FOR DATAFILE 13 TO '+DATA/tradedb/tradedb_users_1_200m';
SET NEWNAME FOR DATAFILE 14 TO '+DATA/tradedb/tradedb_ndmain_1_4g';
SET NEWNAME FOR DATAFILE 15 TO '+DATA/tradedb/tradedb_ndmain_2_4g';
SET NEWNAME FOR DATAFILE 16 TO '+DATA/tradedb/tradedb_ndmain_3_4g';
SET NEWNAME FOR DATAFILE 17 TO '+DATA/tradedb/tradedb_anhui_1';
SET NEWNAME FOR DATAFILE 18 TO '+DATA/tradedb/tradedb_anhui_2';
SET NEWNAME FOR DATAFILE 19 TO '+DATA/tradedb/tradedb_anhui_3';
SET NEWNAME FOR DATAFILE 20 TO '+DATA/tradedb/tradedb_anhui_4';
SET NEWNAME FOR DATAFILE 21 TO '+DATA/tradedb/tradedb_zhejiang_1_4g';
SET NEWNAME FOR DATAFILE 22 TO '+DATA/tradedb/tradedb_zhejiang_2_4g';
SET NEWNAME FOR DATAFILE 23 TO '+DATA/tradedb/tradedb_zhejiang_3_4g';
SET NEWNAME FOR DATAFILE 24 TO '+DATA/tradedb/tradedb_zhejiang_4_4g';
SET NEWNAME FOR DATAFILE 25 TO '+DATA/tradedb/tradedb_zhejiang_5_4g';
SET NEWNAME FOR DATAFILE 26 TO '+DATA/tradedb/tradedb_zhejiang_6_4g';
SET NEWNAME FOR DATAFILE 27 TO '+DATA/tradedb/tradedb_zhejiang_7_4g';
SET NEWNAME FOR DATAFILE 28 TO '+DATA/tradedb/tradedb_zhejiang_8_4g';
SET NEWNAME FOR DATAFILE 29 TO '+DATA/tradedb/tradedb_zhejiang_9_4g';
SET NEWNAME FOR DATAFILE 30 TO '+DATA/tradedb/tradedb_zhejiang_10_4g';
SET NEWNAME FOR DATAFILE 31 TO '+DATA/tradedb/tradedb_zhejiang_11_4g';
SET NEWNAME FOR DATAFILE 32 TO '+DATA/tradedb/tradedb_zhejiang_12_4g';
SET NEWNAME FOR DATAFILE 33 TO '+DATA/tradedb/tradedb_zhejiang_13_4g';
SET NEWNAME FOR DATAFILE 34 TO '+DATA/tradedb/tradedb_zhejiang_14_4g';
SET NEWNAME FOR DATAFILE 35 TO '+DATA/tradedb/tradedb_zhejiang_15_4g';
SET NEWNAME FOR DATAFILE 36 TO '+DATA/tradedb/tradedb_zhejiang_16_4g';
SET NEWNAME FOR DATAFILE 37 TO '+DATA/tradedb/tradedb_zhejiang_17_4g';
SET NEWNAME FOR DATAFILE 38 TO '+DATA/tradedb/tradedb_zhejiang_18_4g';
SET NEWNAME FOR DATAFILE 39 TO '+DATA/tradedb/tradedb_sysaux_2_1g';
SET NEWNAME FOR DATAFILE 40 TO '+DATA/tradedb/tradedb_gpo_1_4g';
SET NEWNAME FOR DATAFILE 41 TO '+DATA/tradedb/tradedb_gpo_2_4g';
SET NEWNAME FOR DATAFILE 42 TO '+DATA/tradedb/tradedb_gpo_3_4g';
SET NEWNAME FOR DATAFILE 43 TO '+DATA/tradedb/tradedb_gpo_4_4g';
SET NEWNAME FOR DATAFILE 44 TO '+DATA/tradedb/tradedb_zhejiang_19_4g';
SET NEWNAME FOR DATAFILE 45 TO '+DATA/tradedb/tradedb_zhejiang_20_4g';
SET NEWNAME FOR DATAFILE 46 TO '+DATA/tradedb/tradedb_beijing_1_4g';
SET NEWNAME FOR DATAFILE 47 TO '+DATA/tradedb/tradedb_beijing_2_4g';
SET NEWNAME FOR DATAFILE 48 TO '+DATA/tradedb/tradedb_beijing_3_4g';
SET NEWNAME FOR DATAFILE 49 TO '+DATA/tradedb/tradedb_beijing_4_4g';
SET NEWNAME FOR DATAFILE 50 TO '+DATA/tradedb/tradedb_beijing_5_4g';
SET NEWNAME FOR DATAFILE 51 TO '+DATA/tradedb/tradedb_beijing_6_4g';
SET NEWNAME FOR DATAFILE 52 TO '+DATA/tradedb/tradedb_beijing_7_4g';
SET NEWNAME FOR DATAFILE 53 TO '+DATA/tradedb/tradedb_beijing_8_4g';
SET NEWNAME FOR DATAFILE 54 TO '+DATA/tradedb/tradedb_beijing_9_4g';
SET NEWNAME FOR DATAFILE 55 TO '+DATA/tradedb/tradedb_beijing_10_4g';
SET NEWNAME FOR DATAFILE 56 TO '+DATA/tradedb/tradedb_beijing_11_4g';
SET NEWNAME FOR DATAFILE 57 TO '+DATA/tradedb/tradedb_beijing_12_4g';
SET NEWNAME FOR DATAFILE 58 TO '+DATA/tradedb/tradedb_beijing_13_4g';
SET NEWNAME FOR DATAFILE 59 TO '+DATA/tradedb/tradedb_beijing_14_4g';
SET NEWNAME FOR DATAFILE 60 TO '+DATA/tradedb/tradedb_beijing_15_4g';

已選擇60行。

到目前為止，所有的準備工作已經完成，下面可以開始資料庫的恢復過程了。

單例項環境利用備份恢復RAC資料庫（一）

相關文章