笔记：物理DG重建又一例

程序员文章站 2022-05-11 22:37:52

...

1、主库生成RMAN备份注意：要运用backupascompressedbackupset，可以节省相当的空间run{allocatechannelc1devicetypedisk;backupascompressedbackupsetformat/u0

1、主库生成RMAN备份

注意：要运用backup as compressed backupset，可以节省相当的空间

run

{

allocate channel c1 device type disk;

backup as compressed backupset format ' /u01/rmanbak/nfs/bk_%U' database;

sql 'alter system archive log current';

release channel c1;

}

2、主库生成从库的控制文件

SQL> alter database create standby controlfile as '/tmp/control01.ctl';

Database altered.

3、主库生成的RMAN备份和控制文件放置到从库制定的位置

因为RMAN备份直接放置到了用从库建立了NFS上，香港服务器租用，所以无需额外的传输，但控制文件需要移动到备库的相应目录

[oracle@dgserver standby]$ mv /u01/rmanbak/nfs/control01.ctl control01.ctl

[oracle@dgserver standby]$ cp control01.ctl control03.ctl

[oracle@dgserver standby]$ cp control01.ctl control02.ctl

4、从库RMAN恢复

[oracle@dgserver standby]$ rman target /

Recovery Manager: Release 10.2.0.5.0 - Production on Sun May 5 09:38:16 2013

connected to target database: PRIMARY (DBID=1656746419, not open)

RMAN> run {

allocate channel c1 device type disk;

allocate channel c2 device type disk;

allocate channel c3 device type disk;

allocate channel c4 device type disk;

restore database;

switch datafile all;

release channel c1;

release channel c2;

release channel c3;

release channel c4;

}

2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12>

using target database control file instead of recovery catalog

allocated channel: c1

channel c1: sid=1479 devtype=DISK

allocated channel: c2

channel c2: sid=1478 devtype=DISK

allocated channel: c3

channel c3: sid=1477 devtype=DISK

allocated channel: c4

channel c4: sid=1476 devtype=DISK

Starting restore at 05-MAY-13

channel c1: starting datafile backupset restore

channel c1: specifying datafile(s) to restore from backup set

restoring datafile 00001 to /u01/oradata/standby/system.262.789583545

restoring datafile 00002 to /u01/oradata/standby/undotbs1.263.789583551

restoring datafile 00003 to /u01/oradata/standby/sysaux.264.789583551

restoring datafile 00004 to /u01/oradata/standby/undotbs2.266.789583557

restoring datafile 00005 to /u01/oradata/standby/users.267.789583559

restoring datafile 00006 to /u01/oradata/standby/inman_index.282.789655375

restoring datafile 00007 to /u01/oradata/standby/in_adcphcled_data.285.789655539

restoring datafile 00008 to /u01/oradata/standby/in_xian_index.286.789655615

restoring datafile 00009 to /u01/oradata/standby/in_xian_data.287.789655707

restoring datafile 00010 to /u01/oradata/standby/tbs_catalog.288.789655837

restoring datafile 00011 to /u01/oradata/standby/eport_index.291.789656023

restoring datafile 00012 to /u01/oradata/standby/in_man_index.292.789656085

restoring datafile 00013 to /u01/oradata/standby/in_suzhou_data.293.789656119

restoring datafile 00014 to /u01/oradata/standby/in_man_data.294.789656245

restoring datafile 00015 to /u01/oradata/standby/in_adcphc_index.295.789656363

restoring datafile 00016 to /u01/oradata/standby/auditadcphc.298.789656683

restoring datafile 00017 to /u01/oradata/standby/in_adcphc_data.299.789656797

restoring datafile 00018 to /u01/oradata/standby/eport_data.302.789657055

restoring datafile 00019 to /u01/oradata/standby/in_suzhou_index.303.789657231

restoring datafile 00020 to /u01/oradata/standby/in_suzhou_data.312.789659221

restoring datafile 00021 to /u01/oradata/standby/users.315.789661229

restoring datafile 00022 to /u01/oradata/standby/users.318.789661589

restoring datafile 00023 to /u01/oradata/standby/users.319.789661839

restoring datafile 00024 to +DATA/in_suzhou_data

restoring datafile 00025 to /u01/oradata/standby/in_suzhou_data

restoring datafile 00026 to /u01/oradata/standby/in_suzhou_data.9154.810742355

restoring datafile 00027 to /u01/oradata/standby/in_adcphc_data.9090.810742665

restoring datafile 00028 to /u01/oradata/standby/system_data

channel c1: reading from backup piece /u01/rmanbak/inc0_PRIMARY_sho8r312_1_1

ORA-19870: error reading backup piece /u01/rmanbak/inc0_PRIMARY_sho8r312_1_1

ORA-19505: failed to identify file "/u01/rmanbak/inc0_PRIMARY_sho8r312_1_1"

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

failover to previous backup