Data Guard Broker中改属性是否须要两侧分别执行?
Data Guard Broker有一些属性,能够经过 show configuration 看到。
我有时会想,这些个属性,是不是分别属于primary 和 standby,若是
想要修改,是否须要分别登录到primary 和 standby ,来分别修改呢?
这也是不少客户常常有的疑问。故此我进行了以下的实验。
先看看primary 端的 属性值:bash
-bash-4.1$ dgmgrl /
DGMGRL for Linux: Version 12.1.0.2.0 - 64bit Production
Copyright (c) 2000, 2013, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
Connected as SYSDG.
DGMGRL> show configuration verbose;
Configuration - DRSolution
Protection Mode: MaxPerformance
Members:
orcl12102 - Primary database
orcl12102_stby - Physical standby database
Properties:
FastStartFailoverThreshold = '30'
OperationTimeout = '30'
TraceLevel = 'USER'
FastStartFailoverLagLimit = '30'
CommunicationTimeout = '180'
ObserverReconnect = '0'
FastStartFailoverAutoReinstate = 'TRUE'
FastStartFailoverPmyShutdown = 'TRUE'
BystandersFollowRoleChange = 'ALL'
ObserverOverride = 'FALSE'
ExternalDestination1 = ''
ExternalDestination2 = ''
PrimaryLostWriteAction = 'CONTINUE'
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL>
再看Standby 端的属性:ide
-bash-4.1$ dgmgrl /
DGMGRL for Linux: Version 12.1.0.2.0 - 64bit Production
Copyright (c) 2000, 2013, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
Connected as SYSDG.
DGMGRL> show configuration verbose;
Configuration - DRSolution
Protection Mode: MaxPerformance
Members:
orcl12102 - Primary database
orcl12102_stby - Physical standby database
Properties:
FastStartFailoverThreshold = '30'
OperationTimeout = '30'
TraceLevel = 'USER'
FastStartFailoverLagLimit = '30'
CommunicationTimeout = '180'
ObserverReconnect = '0'
FastStartFailoverAutoReinstate = 'TRUE'
FastStartFailoverPmyShutdown = 'TRUE'
BystandersFollowRoleChange = 'ALL'
ObserverOverride = 'FALSE'
ExternalDestination1 = ''
ExternalDestination2 = ''
PrimaryLostWriteAction = 'CONTINUE'
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL>
从 primary 和 standby 两边看到的属性值都是同样的。因此我有一个猜想,这些属性值是共通的。
下面经过修改 CommunicationTimeout 的值来进行验证:
在primary 端修改:code
DGMGRL> EDIT CONFIGURATION SET PROPERTY CommunicationTimeout=120;
Property "communicationtimeout" updated
改完后验证一下:orm
DGMGRL> show configuration verbose;
Configuration - DRSolution
Protection Mode: MaxPerformance
Members:
orcl12102 - Primary database
orcl12102_stby - Physical standby database
Properties:
FastStartFailoverThreshold = '30'
OperationTimeout = '30'
TraceLevel = 'USER'
FastStartFailoverLagLimit = '30'
CommunicationTimeout = '120' ******
ObserverReconnect = '0'
FastStartFailoverAutoReinstate = 'TRUE'
FastStartFailoverPmyShutdown = 'TRUE'
BystandersFollowRoleChange = 'ALL'
ObserverOverride = 'FALSE'
ExternalDestination1 = ''
ExternalDestination2 = ''
PrimaryLostWriteAction = 'CONTINUE'
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL>
那么,在 standby 端,会看到怎样的结果呢?server
DGMGRL> show configuration verbose;
Configuration - DRSolution
Protection Mode: MaxPerformance
Members:
orcl12102 - Primary database
orcl12102_stby - Physical standby database
Properties:
FastStartFailoverThreshold = '30'
OperationTimeout = '30'
TraceLevel = 'USER'
FastStartFailoverLagLimit = '30'
CommunicationTimeout = '120' <<<<<<<<<<<<< 从 standby 端,也能够看到这个值,确实被改变了。
ObserverReconnect = '0'
FastStartFailoverAutoReinstate = 'TRUE'
FastStartFailoverPmyShutdown = 'TRUE'
BystandersFollowRoleChange = 'ALL'
ObserverOverride = 'FALSE'
ExternalDestination1 = ''
ExternalDestination2 = ''
PrimaryLostWriteAction = 'CONTINUE'
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
DGMGRL>
事实上,从 standby 端来更改其余的属性值,也是能够的,咱们也能够从primary 端,链接到 data guard broker,看到一样的改变。
因此说,Data Guard Broker 搭建完毕后,若是想更改其属性值,不管是从primary 端,仍是从standby 端,登录链接到broker 后,
在哪一端修改都是能够的。blog