oracle的data guard创建完成后，检查v$database的protection_mode和protection_level的值。如protection_mode值是maximum availa
oracle的data guard创建完成后，，检查v$database的protection_mode和protection_level的值。如protection_mode值是maximum availability，那么protection_level值也应该是这个值。如果不是这个值，而是resynchronization。这表示data guard的日志同步是不正常的。
在备库的alert.log中也可以看到这样信息：primary database is in maximum performance mode。表示主库其实是最大性能模式，而不是预先设置的最大可用模式。
oracle的data guard在主库设置为最大可用模式不能实现时，自动降级为最大性能模式。这样的结果使得日志同步不再实时。
检查数据字典视图v$database
sql> r
1* select protection_mode,protection_level from v$database
protection_mode protection_level
-------------------- --------------------
maximum availability resynchronization
检查数据库初始化参数log_archive_dest*
sql> show parameter log_archive_dest
name type value
------------------------------------ ----------- ------------------------------
log_archive_dest_1 string location=+vg2/
log_archive_dest_2 string service=oxdb_standby lgwr asyn
c affirm valid_for=(online_lo
gfiles,primary_role) db_unique
_name=oxdg
分析
oracle的data guard有三种保护模式，分别为最大保护模式、最大可用模式、最大性能模式。
minimum requirements for maximum protection mode
redo archival process lgwr
network transmission mode sync
disk write option affirm
standby redo logs? yes
standby database type physical only
minimum requirements for maximum availability mode
redo archival process lgwr
network transmission mode sync
disk write option affirm
standby redo logs? required for physical standby databases only. standby redo logs are not supported for logical standby databases.
standby database type physical or logical
minimum requirements for maximum performance mode
redo archival process lgwr or arch
network transmission mode async when using lgwr process. not applicable when using the arch process.
disk write option noaffirm
standby redo logs? required for physical standby databases using the lgwr process.
standby database type physical or logical