Oracle DataGuard物理备库的数据模式
在DataGuard中数据保护模式要按照需求来设置 在所有的配置中都是用性能换数据的安全,要么就是用数据的安全级别来换性能。 1.数据
在DataGuard中数据保护模式要按照需求来设置
在所有的配置中都是用性能换数据的安全,要么就是用数据的安全级别来换性能。
1.数据的保护模式
第一种:最大限度保护数据
Maximum availability: This protection mode provides the highest level of data protection that is possible without compromising the availability of a primary database. With Oracle Data Guard, transactions do not commit until all redo data needed to recover those transactions has either been received in memory or written to the standby redo log (depending upon configuration) on at least one synchronized standby database. If the primary database cannot write its redo stream to at least one synchronized standby database, it operates as if it were in maximum performance mode to preserve primary database availability until it is again able to write its redo stream to a synchronized standby database.
This protection mode ensures zero data loss except in the case of certain double faults, such as failure of a primary database after failure of the standby database.
--先将log写入到内存或者一个备库归档,然后执行事务,,除了双方同时故障的意外。
第二种:最大性能
Maximum performance: This is the default protection mode. It provides the highest level of data protection that is possible without affecting the performance of a primary database. This is accomplished by allowing transactions to commit as soon as all redo data generated by those transactions has been written to the online log. Redo data is also written to one or more standby databases, but this is done asynchronously with respect to transaction commitment, so primary database performance is unaffected by delays in writing redo data to the standby database(s).
This protection mode offers slightly less data protection than maximum availability mode and has minimal impact on primary database performance.
--默认的保护方式,先将事务执行,然后记录到log,然后同步到备库,对主库iude影响非常小
第三种:数据0丢失
Maximum protection: This protection mode ensures that no data loss will occur if the primary database fails. To provide this level of protection, the redo data needed to recover a transaction must be written to both the online redo log and to the standby redo log on at least one synchronized standby database before the transaction commits. To ensure that data loss cannot occur, the primary database will shut down, rather than continue processing transactions, if it cannot write its redo stream to at least one synchronized standby database.
--当事务提交后,将log先提交到备库,关闭主库其他的事务,然后执行事务,完毕后执行下一个事务
2.修改方式(数据保护由主库参数操控)
注意:在主库操作
按数据包户程度排序
maximize protection
SQL> select protection_mode,protection_level from v$database;
PROTECTION_MODE PROTECTION_LEVEL
------------------------------------------------------------ ------------------------------------------------------------
MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE
SQL> alter database set standby database to maximize availability;
数据库已更改。
SQL> select protection_mode,protection_level from v$database;
PROTECTION_MODE PROTECTION_LEVEL
------------------------------------------------------------ ------------------------------------------------------------
MAXIMUM AVAILABILITY RESYNCHRONIZATION //没生效
更多详情见请继续阅读下一页的精彩内容:
推荐阅读:
使用RMAN的Duplicate功能创建物理DataGuard
Oracle基础教程之通过RMAN复制数据库
RMAN备份策略制定参考内容
RMAN备份学习笔记
Oracle数据库备份加密 RMAN加密
通过RMAN备份duplicate创建DataGuard
上一篇: Pear DB 新手入门指南教程_PHP
推荐阅读
-
Oracle DataGuard物理备库的数据模式
-
物理备数据库的切换与故障转移
-
Oracle数据库由dataguard备库引起的log file sync等待问题
-
关于Oracle将目标数据库设为归档模式应该注意的问题
-
Oracle 11g DataGuard 物理备库配置及Active DataGuard测试
-
论述层次模型的概念 论述网状模型的概念 论述数据库系统的三级模式结构什么叫数据于程序的物理独立性?什么叫数据与程序的逻辑独立性?为什么数据库系统具有数据于程序的独立性
-
oracle的归档模式 ORACLE数据库归档日志常用命令
-
oracle的归档模式 ORACLE数据库归档日志常用命令
-
Oracle数据库 DGbroker三种保护模式的切换
-
Oracle中的逻辑数据库和物理数据库