[20161008]修改dg模式.txt
[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/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 【DG】DG的3種保護模式模式
- [20170324]dg相關程式.txt
- DG的保護模式模式
- 【DG】之 Snapshot standby模式模式
- 【DG】三大模式切換模式
- DG_三大模式切換模式
- DG三種模式 圖表解析模式
- Windows修改新建.txt檔名Windows
- Oracle DG管理模式和只讀模式相互切換Oracle模式
- dg 配置,建議關閉shared 模式。模式
- DG -- READ ONLY模式開啟物理Standby模式
- DG學習筆記(7)_保護模式筆記模式
- DG_rman配置修改後不會同步到備庫
- [20170315]簡單探究dg的mrp程式.txt
- [20170203]dg磁碟空間不足的處理.txt
- [20170803]如何檢視dg的redo應用率.txt
- ORACLE10G DG中資料保護模式Oracle模式
- Oracle 修改歸檔模式Oracle模式
- oracle之受限模式修改Oracle模式
- [20160405]bbed修改檔案頭.txt
- [20190225]測試如何使用dg快速主庫.txt
- [20170303]dg環境下線上日誌損壞8.txt
- RAC(ASM)歸檔模式修改ASM模式
- DG中3種保護模式之間的切換模式
- 【DG】DG概念原理詳解
- [20180927]修改sql prompt提示.txtSQL
- [20220329]批量修改檔名.txt
- [20160418]修改oracle監聽埠.txtOracle
- [20190107]12c以上版本配置dg注意.txt
- [20180718]拷貝資料檔案從dg庫.txt
- [20221128]dg資料庫最佳化問題.txt資料庫
- [20170307]dg環境下線上日誌損壞12.txt
- [20170309]dg環境下線上日誌損壞13.txt
- [20170310]dg環境下線上日誌損壞14.txt
- [20170301]dg環境下線上日誌損壞5.txt
- DG保護模式與備用聯機日誌檔案模式
- Ftp - 主被動模式說明及修改模式命令FTP模式
- zabbix agent(Active)模式 /克隆修改模板模式