[20161008]修改dg模式.txt
--dg支持3种模式,最大性能,最大可利用,最大保护.
--一般使用最多的最大性能,测试修改为最大可利用模式.
1.环境:
SYS@test> @ ver1
PORT_STRING VERSION BANNER
------------------------------ -------------- --------------------------------------------------------------------------------
x86_64/Linux 2.4.xx 11.2.0.3.0 Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
DGMGRL> show configuration
Configuration - study
Protection Mode: MaxPerformance
Databases:
test - Primary database
testdg - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
2.修改模式:
DGMGRL> edit configuration set protection mode as maxavailability;
Error: ORA-16627: operation disallowed since no standby databases would remain to support protection mode
Failed.
--//不行,要修改传输模式。
$ oerr ora 16627
16627, 0000, "operation disallowed since no standby databases would remain to support protection mode"
// *Cause: This status was returned because of one of the following:
// - The broker rejected an attempt to change the overall
// configuration protection mode since it could not find any
// enabled standby databases that supported the proposed protection
// mode.
// - The broker rejected an attempt to enable the configuration
// if it determined that there were no enabled standby databases
// that supported the overall protection mode.
// - The broker rejected an attempt to disable or remove a database
// that, if disabled or deleted, would result in no remaining
// standby databases that could support the overall configuration
// protection mode.
// - The broker rejected an attempt to switchover if doing so would
// violate the overall configuration protection mode.
// - Performing automatic health check if the broker determined that
// no standby datbases supported the overall protection mode.
// *Action: - If changing the overall protection mode, confirm that at least
// one standby database satisfies the new protection mode.
// - For enable failures, confirm that at least one standby database
// has a LogXptMode configurable property setting that supports
// the current overall protection mode.
// - For delete and disable failures, confirm that at least one
// other standby database has a LogXptMode configurable property
// setting that supports the overall protection mode.
// - For switchover failures that occur when the configuration
// is operating in maximum protection or maximum availability
// mode, confirm that at least one other standby database has its
// LogXptMode configurable property set to the value "SYNC".
// If the configuration contains a primary database and a single
// standby database and is operating in either maximum protection
// or maximum availability mode, ensure that the LogXptMode
// configurable property of the primary database is set to the
// value "SYNC". Since the old primary database will become the
// standby database after switchover completes, its LogXptMode
// configurable property setting must support the configuration
// protection mode.
// - For health check error, confirm that at least one standby
// database has a LogXptMode configurable property setting
// that supports the current overall protection mode.
DGMGRL> show database testdg 'LogXptMode';
LogXptMode = 'ASYNC'
SYS@test> show parameter log_archive_dest_2
NAME TYPE VALUE
------------------- ------- ----------------------------------------------------------------------------------------------------
log_archive_dest_2 string service="testdg", LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_connect
ions=1 reopen=300 db_unique_name="testdg" net_timeout=30, valid_for=(all_logfiles,primary_role)
DGMGRL> edit database testdg set PROPERTY LogXptMode='SYNC';
Property "logxptmode" updated
DGMGRL> edit configuration set protection mode as maxavailability;
Succeeded.
DGMGRL> show configuration
Configuration - study
Protection Mode: MaxAvailability
Databases:
test - Primary database
testdg - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
SYS@test> show parameter log_archive_dest_2
NAME TYPE VALUE
------------------ ------- ----------------------------------------------------------------------------------------------------
log_archive_dest_2 string service="testdg", LGWR SYNC AFFIRM delay=0 optional compression=disable max_failure=0 max_connection
s=1 reopen=300 db_unique_name="testdg" net_timeout=30, valid_for=(all_logfiles,primary_role)
--//注:改动的参数是test主库的log_archive_dest_2,以前我一致以为是dg的参数,实际上是主库传输到备库的参数。
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/267265/viewspace-2125911/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/267265/viewspace-2125911/

1483

被折叠的 条评论
为什么被折叠?



