Oracle 11G配置单实例DataGuard(二)
4.用spfile将standby启动到nomount状态：
SQL> create spfile from pfile;
SQL> startup nomount
5.Primary开始duplicate
[oracle@rhel5 admin]$ rman target / auxiliary sys/oracle@standby
Recovery Manager: Release 11.2.0.1.0 - Production on Sun Oct 20 12:10:19 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1333198576)
connected to auxiliary database: ORCL (not mounted)
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby1 type disk;
duplicate target database for standby from active database;
}
（2） 在执行duplicate的时候，如果源库和目标库目录相同，那么在duplicate 时，需要加上nofilenamecheck，如下：
RMAN> duplicate target database for standby from active database nofilenamecheck;
三、后续工作
1.主库已经使用了spfile，但是备库用的还是之前的pfile：
2.只要备库的监听不重启，重启备库后，主库还是能识别的。如果备库的监听重启了。那么主库也就需要重启。
3.复制结束后的Standby只启动到mount standby的状态。 并没有启动MRP的应用归档程序。所以这个时候查询主备库，归档是不同步的。需要手动的启动MRP进程。
Primary:
SQL> alter system archive log current;
Sun Oct 20 13:42:29 2013
Archived Log entry 4 added for thread 1 sequence 63 ID 0x50dddec2 dest 1:
Sun Oct 20 13:42:29 2013
RFS[4]: Selected log 4 for thread 1 sequence 64 dbid 1333198576 branch 808520212
Standby 非 Real-Time Apply：:
SQL> alter database recover managed standby database disconnect from session;
Attempt to start background Managed Standby Recovery process (orcl)
Sun Oct 20 14:20:08 2013
MRP0 started with pid=26, OS id=8307
MRP0: Background Managed Standby Recovery process started (orcl)
Serial Media Recovery started
Managed Standby Recovery not using Real Time Apply
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Log /oradata/orcl/standby/arch/1_63_808520212.dbf
Media Recovery Log /oradata/orcl/standby/arch/1_64_808520212.dbf
Media Recovery Waiting for thread 1 sequence 65 (in transit)
Completed: alter database recover managed standby database disconnect from session
4.备库Real-Time Apply：
在duplicate结束后，备库没有添加standby redo log file。但是主库采用的是：lgwr async传送的日志。当备库的RFS 进程接收到日志后，发现备库没有standby redo log的时候，备库会自动用ARCH将其写入归档文件。
在备库添加standby redo log：
--在备库添加standby redo log需要先停MRP，可以在duplicate 之前在主库加standby redo log，这样在duplicate 后会在备库中自动增加standby redo。
ALTER DATABASE ADD STANDBY LOGFILE ('/oradata/orcl/standby/standbyredo11.dbf','/oradata/orcl/standby/standbyredo12.dbf') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE ('/oradata/orcl/standby/standbyredo21.dbf','/oradata/orcl/standby/standbyredo22.dbf') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE ('/oradata/orcl/standby/standbyredo31.dbf','/oradata/orcl/standby/standbyredo32.dbf') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE ('/oradata/orcl/standby/standbyredo41.dbf','/oradata/orcl/standby/standbyredo42.dbf') SIZE 50M;
在主库也添加一下standby redo log，也是为了方便switchover
ALTER DATABASE ADD STANDBY LOGFILE ('/oradata/orcl/standbyredo11.dbf','/oradata/orcl/standbyredo12.dbf') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE ('/oradata/orcl/standbyredo21.dbf','/oradata/orcl/standbyredo22.dbf') SIZE 50M;
ALTER DATABASE ADD