使用 rman duplicate from active database 搭建dataguard 手记

run {

allocate channel prmy1 type disk;

allocate channel prmy2 type disk;

allocate channel prmy3 type disk;

allocate channel prmy4 type disk;

allocate channel prmy5 type disk;

allocate channel prmy6 type disk;

allocate channel prmy7 type disk;

allocate channel prmy8 type disk;

allocate channel prmy9 type disk;

allocate channel prmy10 type disk;

allocate auxiliary channel stby1 type disk;

allocate auxiliary channel stby2 type disk;

allocate auxiliary channel stby3 type disk;

allocate auxiliary channel stby4 type disk;

allocate auxiliary channel stby5 type disk;

allocate auxiliary channel stby6 type disk;

allocate auxiliary channel stby7 type disk;

allocate auxiliary channel stby8 type disk;

allocate auxiliary channel stby9 type disk;

allocate auxiliary channel stby10 type disk;

duplicate target database for standby from active database dorecover;

}

dorecover:会将备份期间产生的归档日志应用到standby database,但是不会启动日志应用(not  use manual or managed recovery mode.)

Specifies that RMAN should recover the standby database after creating it.

If DORECOVER is
specified, then RMAN also recovers the database. The standby database is left mounted after duplication is complete.

RMAN
leaves the standby database mounted after media recovery is complete, but does not place the standby database in manual or managed recovery mode. After RMAN creates the standby database, you must resolve any gap sequence before placing it in manual or managed
recovery mode, or opening it in read-only mode.

注意点:

在磁盘io不是瓶颈时,一定要考虑下网络带宽;

根据网络带宽,rman 估算综合评估备份时间

版权声明:本文为博主原创文章,未经博主允许不得转载。

时间: 2024-11-08 20:57:45

使用 rman duplicate from active database 搭建dataguard 手记的相关文章

关于 rman duplicate from active database 搭建dataguard

关于 rman duplicate from active database,具体操作实际为backup as copy :会拷贝很多空块:对于那些数据库数据文件超过100G的都不是很建议用:在很大程度上会受到网络带宽的限制,一点出现异常,就要从头再来,非常痛苦: 在做dataguard 能不用duplicate from active database ,还是不要用了,最靠谱的还是用rman 先备份一个吧: 版权声明:本文为博主原创文章,未经博主允许不得转载.

关于 rman duplicate from active database 搭建dataguard--系列一

关于 rman duplicate from active database.详细操作实际为backup as copy .会拷贝非常多空块.对于那些数据库数据文件超过100G的都不是非常建议用:在非常大程度上会受到网络带宽的限制,一旦出现异常,就要从头再来,非常痛苦. 在做dataguard 能不用duplicate from active database ,还是不要用了,最靠谱的还是用rman 先备份一个吧:在做恢复吧

使用RMAN DUPLICATE...FROM ACTIVE DATABASE创建物理standby database

Applies to: Oracle Server - Enterprise Edition - Version 11.1.0.6 to 11.2.0.4 [Release 11.1 to 11.2]Information in this document applies to any platform.GoalStep by step guide on how to create a physical standby database using RMAN DUPLICATE FROM ACT

Creating Physical Standby Using RMAN DUPLICATE...FROM ACTIVE DATABASE执行结果

1> run { 2> allocate channel prmy1 type disk; 3> allocate channel prmy2 type disk; 4> allocate channel prmy3 type disk; 5> allocate auxiliary channel stby type disk; 6> duplicate target database for standby from active database 7> spf

Duplicate From Active Database

RMAN 'Duplicate From Active Database' Feature in 11G (文档 ID 452868.1) 转到底部 APPLIES TO: Oracle Database - Enterprise Edition - Version 11.1.0.6 and laterInformation in this document applies to any platform. PURPOSE The scope of this bulletin is to dis

【翻译自mos文章】在网络流量变大(比如rman duplicat 一个active database)之后,由于脑裂导致节点重启

在网络流量变大(比如rman duplicat 一个active database)之后,由于脑裂导致节点重启 来源于: The node reboots due to split brain during increased network traffic like rman duplicating an active database (文档 ID 985123.1) 适用于: Oracle Server - Enterprise Edition - Version: 11.1.0.7 to

Oracle 11g Data Guard 使用duplicate from active database 创建 standby database

用这种方式来搭建DG ,主库的停机时间很少,只需要重启一下,使参数生效.也可以用这种方法进行DB迁移.DG搭建好,然后把备库激活就可以了. 这样整个迁移中宕机时间也比较短. Oracle 11g的pyhsical standby 支持open read only 下的apply和Real-time query. 因此就有了physical standby 稳定和logical standby 的报表查询功能. Oracle: 11.2.0.1 OS: redhat 5.5 Primary IP:

基于RMAN从活动数据库异机克隆(rman duplicate from active DB)

Oracle 11g RMAN能够实现基于活动数据库进行异机克隆,从而省去需要先备份再ftp到辅助服务器的过程.这一切可以全部交给Oracle来搞定.在克隆期间,Oracle会读取Target DB的所有数据结构,无须人为的干预(不同的磁盘系统,文件路径与文件名要指定转换方式).尽管如此,对于生产环境数据库在整个克隆期间性能会下降,其次在Target Server与Auxiliary Server中会产生较大的网络流量.如果这些可以接受的话,从活动数据库进行异机克隆是一个不错的选择.本文首先描述

RMAN duplicate from active 时遭遇 ORA-17627 ORA-12154

最近在从活动数据库进行异机克隆时碰到了ORA-17629,ORA-17627,ORA-12154的错误,起初以为是一个Bug呢.Oracle Bug着实太多了,已经成了习惯性思维了.汗!错误提示是无法连接到连接到远程数据库,连接字符串无法解析.咦,配置了从auxiliary DB到target DB的tnsnames,且都是连通的阿......   1.故障现象     --下面的操作在auxiliary DB所在的机器上完成     [[email protected] ~]$ export