From Dbvisit Standby version 11.4, the automatic standby update can be managed using CLI. This is done by using either the dbvagentmanager or dbvcontrol binary. The options are very simple and straightforward.
Auto-Update using dbvagentmanager
Below is the option for setting up and managing automatic standby updates from dbvagentmanager. These options must be run only from the Primary database server.
The dbvagentmanager CLI commands for auto-update must be run only from the primary database server.
The auto-update has two options.
Modify: This option helps you to manage the automatic standby update for one or multiple configurations.
Status: This option provides the status of a single or multiple configurations
Let's look at the individual options and various functions of these.
Status Option:
[oracle@dbvel71 bin]$ ./dbvagentmanager auto-update status -h
Show the status of Automated Standby Update for one or more configurations
This command operates on one or more configurations whose primary host is the current host.
If the flags specified match more than one configuration, the user is prompted to choose which they wish to operate on, unless the --noprompt flag is specified, in which case all matching configurations are operated on.
Usage:
dbvagentmanager auto-update status [flags]
Examples:
To show the status of Automated Standby Update for a named configuration:
dbvagentmanager auto-update status --configuration-name DEV
To show the status of Automated Standby Update for selected configurations:
dbvagentmanager auto-update status
To show the status of Automated Standby Update for all configurations with primary on the current host:
dbvagentmanager auto-update status --noprompt
Flags:
-g, --logToStderr send logs to STDERR instead of writing to log files
-d, --configuration-name string name of the configuration to operate on
-t, --configuration-type string type of the configuration to operate on
--instance-name string instance name of the configuration to operate on (SQL Server configurations only)
--noprompt update all matching configurations without prompting the user to select
-h, --help help for status
[oracle@dbvel71 bin]$
Examples:
If there is only one configuration between the agents and the control center, no other options other than status need to be provided.
[oracle@dbvel71 bin]$ ./dbvagentmanager auto-update status Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvagentmanager_auto-update_status_7084.trace.log'. orcl21c (Oracle) between dbvel71 and dbvel72: ENABLED with an interval of 600 seconds (daemon running with pid 6461) [oracle@dbvel71 bin]$
For SQLServer, you can choose the options to view the status of specific configurations. An option is provided to choose the specific configuration using the keyboard.
The output would look like this.
AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com: ENABLED with an interval of 120 seconds TEAM (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com: ENABLED with an interval of 120 seconds NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com: ENABLED with an interval of 120 seconds LINE (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com: ENABLED with an interval of 300 seconds
If there are multiple configurations on the setup, then the -d option can be provided to get the status of a specific configuration using the configuration name.
Oracle:
[oracle@dbvel71 bin]$ ./dbvagentmanager auto-update status -d orcl21c Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvagentmanager_auto-update_status_8876.trace.log'. orcl21c (Oracle) between dbvel71 and dbvel72: ENABLED with an interval of 600 seconds (daemon running with pid 6461) [oracle@dbvel71 bin]$
SQL Server:
C:\Program Files\Dbvisit\standbymp\bin>dbvagentmanager.exe auto-update status -d NEW Trace log will be written to 'C:\Program Files\Dbvisit\standbymp\log\trace\dbvagentmanager_auto-update_status_2976.trace.log'. NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com: ENABLED with an interval of 120 seconds
Status with -t option
This option lets us choose to view the status of either Oracle or SqlServer.
[oracle@dbvel71 bin]$ ./dbvagentmanager auto-update status -t oracle Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvagentmanager_auto-update_status_8923.trace.log'. orcl21c (Oracle) between dbvel71 and dbvel72: ENABLED with an interval of 600 seconds (daemon running with pid 6461) [oracle@dbvel71 bin]$
C:\Program Files\Dbvisit\standbymp\bin>dbvagentmanager.exe auto-update status -d AdWorks -t sqlServer Trace log will be written to 'C:\Program Files\Dbvisit\standbymp\log\trace\dbvagentmanager_auto-update_status_1888.trace.log'. AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com: ENABLED with an interval of 120 seconds
C:\Program Files\Dbvisit\standbymp\bin>dbvagentmanager.exe auto-update status -t sqlServer Trace log will be written to 'C:\Program Files\Dbvisit\standbymp\log\trace\dbvagentmanager_auto-update_status_1568.trace.log'. ? Please choose the configurations to operate on AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds), TEAM (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds), NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds), KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds), LINE (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 300 seconds) AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com: ENABLED with an interval of 120 seconds TEAM (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com: ENABLED with an interval of 120 seconds NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com: ENABLED with an interval of 120 seconds KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com: ENABLED with an interval of 120 seconds LINE (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com: ENABLED with an interval of 300 seconds
The -g option provides you with standard log output of the status on the screen rather than in the log file. This is useful for troubleshooting in case the auto-update is not working as expected.
[oracle@dbvel71 bin]$ ./dbvagentmanager auto-update status -g
2023-05-29T10:31:33.150+12:00 | INFO | d92b71778ef96334 | Starting CLI command: ./dbvagentmanager auto-update status -g [args=["./dbvagentmanager","auto-update","status","-g"] service="dbvagentmanager auto-update status" loc=internal/cli/command.go:138 function=internal/cli.(*baseCommand).wrapRun.func1]
2023-05-29T10:31:33.150+12:00 | DEBUG | d92b71778ef96334 | Finding configurations [params={"ConfigurationType":"","ConfigurationName":"","HostName":"dbvel71","InstanceName":""} service="dbvagentmanager auto-update status" loc=internal/cli/configurationselection.go:186 function=internal/cli.(*ConfigurationSelection).ResolveAll]
2023-05-29T10:31:33.150+12:00 | DEBUG | d92b71778ef96334 | Invoking dbvnet API [messageKey="find_configurations" params={"ConfigurationType":"","ConfigurationName":"","HostName":"dbvel71","InstanceName":""} service="dbvagentmanager auto-update status" loc=cmd/dbvagentmanager/internal/dbvnetclient/dbvnetclient.go:110 function=cmd/dbvagentmanager/internal/dbvnetclient.dbvnetClient.invokeAPI]
2023-05-29T10:31:33.152+12:00 | DEBUG | d92b71778ef96334 | Loaded client certificate [dir="certificates" service="dbvagentmanager auto-update status" loc=internal/natscert/real.go:63 function=internal/natscert.RealCertificateManager.LoadClientCertificates]
2023-05-29T10:31:33.157+12:00 | DEBUG | d92b71778ef96334 | Got response from dbvnet API [response="{\"Status\":200,\"Result\":{\"Configurations\":[{\"ConfigurationId\":1,\"ConfigurationType\":\"Oracle\",\"ConfigurationName\":\"orcl21c\",\"PrimaryAgentManagerId\":\"11fldq8lszwvc\",\"PrimaryAgent\":{\"AgentManagerConfig\":{\"NatsAddress\":\"192.168.56.10\",\"NatsPort\":5533,\"HostAddress\":\"dbvel71\",\"OS\":\"linux\",\"DefaultBackupDir\":\"/usr/dbvisit/standbymp/backup\",\"Partition\":\"/\",\"IPAddresses\":[\"[::1]\",\"10.0.2.9\",\"[fe80::dd6a:8688:d95a:4bc]\",\"192.168.56.9\",\"[fe80::410e:323c:3b6e:c01c]\"],\"ServiceUser\":\"oracle\",\"AgentManagerId\":\"11fldq8lszwvc\",\"FileTransferListenAddress\":\"dbvel71\",\"FileTransferListenPort\":7890},\"UserScript\":\"\",\"SpecificData\":{}},\"StandbyAgentManagerId\":\"1h2hxuqv0bxqi\",\"StandbyAgent\":{\"AgentManagerConfig\":{\"NatsAddress\":\"192.168.56.10\",\"NatsPort\":5533,\"HostAddress\":\"dbvel72\",\"OS\":\"linux\",\"DefaultBackupDir\":\"/usr/dbvisit/standbymp/backup\",\"Partition\":\"/\",\"IPAddresses\":[\"[::1]\",\"10.0.2.10\",\"[fe80::c2b9:a1bc:fd1:2545]\",\"192.168.56.10\",\"[fe80::7872:f3ef:5603:83c6]\"],\"ServiceUser\":\"oracle\",\"AgentManagerId\":\"1h2hxuqv0bxqi\",\"FileTransferListenAddress\":\"dbvel72\",\"FileTransferListenPort\":7890},\"UserScript\":\"\",\"SpecificData\":{}},\"Settings\":{\"ApplicationDelayMinutes\":0,\"StandbyMode\":{\"UndoFilePath\":\"\",\"Enabled\":false},\"AutomatedStandbyUpdate\":{\"Enabled\":true,\"IntervalSeconds\":600,\"BackupType\":\"\"},\"Notifications\":{\"To\":null},\"Observer\":{\"Enabled\":false,\"NotificationOnly\":true,\"CheckIntervalSeconds\":60,\"MaxFailCount\":3,\"SendEmail\":true,\"SendSlack\":true,\"HeartbeatEnabled\":false,\"HeartbeatHour\":7,\"HeartbeatMinute\":0,\"TimeGap\":false,\"TimeGapSeconds\":0,\"DiskSpace\":false,\"DiskSpaceCheckingPath\":null,\"DiskSpaceGb\":0,\"Rule\":\"D\"},\"ArchiveManagement\":{\"Primary\":{\"MaxFileNumber\":0,\"MaxDays\":0,\"MaxSizeInGB\":0,\"Enabled\":false},\"Standby\":{\"MaxFileNumber\":0,\"MaxDays\":0,\"MaxSizeInGB\":0,\"Enabled\":false}},\"UserScriptList\":null},\"HasFailedOver\":false,\"AutoCreated\":false,\"Disabled\":false,\"LicenseKey\":\"\"}]}}" service="dbvagentmanager auto-update status" loc=cmd/dbvagentmanager/internal/dbvnetclient/dbvnetclient.go:119 function=cmd/dbvagentmanager/internal/dbvnetclient.dbvnetClient.invokeAPI]
2023-05-29T10:31:33.158+12:00 | DEBUG | d92b71778ef96334 | Found configurations [configurations=[{"ConfigurationId":1,"ConfigurationType":"Oracle","ConfigurationName":"orcl21c","PrimaryAgentManagerId":"11fldq8lszwvc","PrimaryAgent":{"AgentManagerConfig":{"NatsAddress":"192.168.56.10","NatsPort":5533,"HostAddress":"dbvel71","OS":"linux","DefaultBackupDir":"/usr/dbvisit/standbymp/backup","Partition":"/","IPAddresses":["[::1]","10.0.2.9","[fe80::dd6a:8688:d95a:4bc]","192.168.56.9","[fe80::410e:323c:3b6e:c01c]"],"ServiceUser":"oracle","AgentManagerId":"11fldq8lszwvc","FileTransferListenAddress":"dbvel71","FileTransferListenPort":7890},"UserScript":"","SpecificData":{}},"StandbyAgentManagerId":"1h2hxuqv0bxqi","StandbyAgent":{"AgentManagerConfig":{"NatsAddress":"192.168.56.10","NatsPort":5533,"HostAddress":"dbvel72","OS":"linux","DefaultBackupDir":"/usr/dbvisit/standbymp/backup","Partition":"/","IPAddresses":["[::1]","10.0.2.10","[fe80::c2b9:a1bc:fd1:2545]","192.168.56.10","[fe80::7872:f3ef:5603:83c6]"],"ServiceUser":"oracle","AgentManagerId":"1h2hxuqv0bxqi","FileTransferListenAddress":"dbvel72","FileTransferListenPort":7890},"UserScript":"","SpecificData":{}},"Settings":{"ApplicationDelayMinutes":0,"StandbyMode":{"UndoFilePath":"","Enabled":false},"AutomatedStandbyUpdate":{"Enabled":true,"IntervalSeconds":600,"BackupType":""},"Notifications":{"To":null},"Observer":{"Enabled":false,"NotificationOnly":true,"CheckIntervalSeconds":60,"MaxFailCount":3,"SendEmail":true,"SendSlack":true,"HeartbeatEnabled":false,"HeartbeatHour":7,"HeartbeatMinute":0,"TimeGap":false,"TimeGapSeconds":0,"DiskSpace":false,"DiskSpaceCheckingPath":null,"DiskSpaceGb":0,"Rule":"D"},"ArchiveManagement":{"Primary":{"MaxFileNumber":0,"MaxDays":0,"MaxSizeInGB":0,"Enabled":false},"Standby":{"MaxFileNumber":0,"MaxDays":0,"MaxSizeInGB":0,"Enabled":false}},"UserScriptList":null},"HasFailedOver":false,"AutoCreated":false,"Disabled":false,"LicenseKey":""}] service="dbvagentmanager auto-update status" loc=internal/cli/configurationselection.go:191 function=internal/cli.(*ConfigurationSelection).ResolveAll]
2023-05-29T10:31:33.158+12:00 | DEBUG | d92b71778ef96334 | Describing configuration [configurationId="1" service="dbvagentmanager auto-update status" loc=internal/cli/configurationselection.go:195 function=internal/cli.(*ConfigurationSelection).ResolveAll]
2023-05-29T10:31:33.158+12:00 | DEBUG | d92b71778ef96334 | Described configuration [configurationId="1" description="orcl21c (Oracle) between dbvel71 and dbvel72" service="dbvagentmanager auto-update status" loc=internal/cli/configurationselection.go:202 function=internal/cli.(*ConfigurationSelection).ResolveAll]
2023-05-29T10:31:33.158+12:00 | DEBUG | d92b71778ef96334 | Invoking dbvnet API [messageKey="get_auto_update_status" params={"ConfigurationId":1} service="dbvagentmanager auto-update status" loc=cmd/dbvagentmanager/internal/dbvnetclient/dbvnetclient.go:110 function=cmd/dbvagentmanager/internal/dbvnetclient.dbvnetClient.invokeAPI]
2023-05-29T10:31:33.158+12:00 | DEBUG | d92b71778ef96334 | Loaded client certificate [dir="certificates" service="dbvagentmanager auto-update status" loc=internal/natscert/real.go:63 function=internal/natscert.RealCertificateManager.LoadClientCertificates]
2023-05-29T10:31:33.163+12:00 | DEBUG | d92b71778ef96334 | Got response from dbvnet API [response="{\"Status\":200,\"Result\":{\"Settings\":{\"Enabled\":true,\"IntervalSeconds\":600,\"BackupType\":\"\"},\"OracleDaemonStatus\":{\"Status\":\"running\",\"Pid\":6461}}}" service="dbvagentmanager auto-update status" loc=cmd/dbvagentmanager/internal/dbvnetclient/dbvnetclient.go:119 function=cmd/dbvagentmanager/internal/dbvnetclient.dbvnetClient.invokeAPI]
orcl21c (Oracle) between dbvel71 and dbvel72: ENABLED with an interval of 600 seconds (daemon running with pid 6461)
Modify Option:
This option has flags to disable, enable, set time intervals between standby and primary, and various other options.
[oracle@dbvel71 bin]$ ./dbvagentmanager auto-update modify -h
Modify the local Automated Standby Update settings for one or more configurations
This command operates on one or more configurations whose primary host is the current host.
If the flags specified match more than one configuration, the user is prompted to choose which they wish to operate on, unless the --noprompt flag is specified, in which case all matching configurations
are operated on.
The specified modifications are applied to the Automated Standby Update settings of each of the selected configurations.
The user is prompted for confirmation before any updates are performed, unless the --noconfirm flag is specified.
If the Agent Manager on this host is not connected to the Control Center, the changes will take effect locally but will not show up in the Control Center until the connection is reestablished.
Usage:
dbvagentmanager auto-update modify [flags]
Examples:
To disable Automated Standby Update for a named configuration:
dbvagentmanager auto-update modify --configuration-name DEV --disable
To enable Automated Standby Update for selected configurations:
dbvagentmanager auto-update modify --enable
To disable Automated Standby Update for all configurations with primary on the current host:
dbvagentmanager auto-update modify --noprompt --disable
To enable Automated Standby Update for all configurations with primary on the current host without confirmation:
dbvagentmanager auto-update modify --noprompt --enable --noconfirm
Flags:
-g, --logToStderr send logs to STDERR instead of writing to log files
-d, --configuration-name string name of the configuration to operate on
-t, --configuration-type string type of the configuration to operate on
--instance-name string instance name of the configuration to operate on (SQL Server configurations only)
--noprompt update all matching configurations without prompting the user to select
--enable enable Automated Standby Update
--disable disable Automated Standby Update
--set-enabled enabled set whether Automated Standby Update is enabled (true or false) (default (unset))
--set-interval-seconds interval set the Automated Standby Update interval in seconds (default (unset))
--noconfirm skip the confirmation prompt and proceed immediately
-h, --help help for modify
Disable/Enable Automatic Standby Update:
[oracle@dbvel71 bin]$ ./dbvagentmanager auto-update modify --disable Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvagentmanager_auto-update_modify_13422.trace.log'. Will update configuration orcl21c (Oracle) between dbvel71 and dbvel72 (currently DISABLED with an interval of 600 seconds) to be DISABLED with an interval of 600 seconds ? Update 1 configuration(s) - are you sure? Yes Successfully updated configuration orcl21c (Oracle) between dbvel71 and dbvel72
[oracle@dbvel71 bin]$ ./dbvagentmanager auto-update modify --enable Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvagentmanager_auto-update_modify_17456.trace.log'. Will update configuration orcl21c (Oracle) between dbvel71 and dbvel72 (currently DISABLED with an interval of 600 seconds) to be ENABLED with an interval of 600 seconds ? Update 1 configuration(s) - are you sure? Yes Successfully updated configuration orcl21c (Oracle) between dbvel71 and dbvel72 [oracle@dbvel71 bin]$
disable/enable with noconfirm: This option does not ask for confirmation but disables your automated standby update
[oracle@dbvel71 bin]$ ./dbvagentmanager auto-update modify --disable --noconfirm Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvagentmanager_auto-update_modify_12303.trace.log'. Will update configuration orcl21c (Oracle) between dbvel71 and dbvel72 (currently ENABLED with an interval of 600 seconds) to be DISABLED with an interval of 600 seconds Successfully updated configuration orcl21c (Oracle) between dbvel71 and dbvel72 [oracle@dbvel71 bin]$
[oracle@dbvel71 bin]$ ./dbvagentmanager auto-update modify --enable --noconfirm Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvagentmanager_auto-update_modify_18106.trace.log'. Will update configuration orcl21c (Oracle) between dbvel71 and dbvel72 (currently DISABLED with an interval of 600 seconds) to be ENABLED with an interval of 600 seconds Successfully updated configuration orcl21c (Oracle) between dbvel71 and dbvel72 [oracle@dbvel71 bin]$
Disable/enable with noprompt: This option would disable all the active configurations without letting the user choose what configuration to disable. This is valid only when you have multiple configurations. But confirmation is required to disable/enable.
C:\Program Files\Dbvisit\standbymp\bin>dbvagentmanager.exe auto-update modify --enable --noprompt Trace log will be written to 'C:\Program Files\Dbvisit\standbymp\log\trace\dbvagentmanager_auto-update_modify_4444.trace.log'. Will update configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently DISABLED with an interval of 120 seconds) to be ENABLED with an interval of 120 seconds Will update configuration TEAM (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently DISABLED with an interval of 120 seconds) to be ENABLED with an interval of 120 seconds Will update configuration NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently DISABLED with an interval of 120 seconds) to be ENABLED with an interval of 120 seconds Will update configuration KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently DISABLED with an interval of 120 seconds) to be ENABLED with an interval of 120 seconds Will update configuration LINE (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently DISABLED with an interval of 300 seconds) to be ENABLED with an interval of 300 seconds ? Update 5 configuration(s) - are you sure? Yes Successfully updated configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration TEAM (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration LINE (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com
noprompt with noconfirm. This would disable all active configurations and not ask for confirmation or let you choose any configuration.
C:\Program Files\Dbvisit\standbymp\bin>dbvagentmanager.exe auto-update modify --enable --noprompt --noconfirm Trace log will be written to 'C:\Program Files\Dbvisit\standbymp\log\trace\dbvagentmanager_auto-update_modify_4776.trace.log'. Will update configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds) to be ENABLED with an interval of 120 seconds Will update configuration TEAM (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds) to be ENABLED with an interval of 120 seconds Will update configuration NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds) to be ENABLED with an interval of 120 seconds Will update configuration KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds) to be ENABLED with an interval of 120 seconds Will update configuration LINE (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 300 seconds) to be ENABLED with an interval of 300 seconds Successfully updated configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration TEAM (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration LINE (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com
disabling and enabling specific configurations: To use this option -d is used to choose the configuration for which the options can be enabled or disabled
[oracle@dbvel71 bin]$ ./dbvagentmanager auto-update modify -d orcl21c --disable Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvagentmanager_auto-update_modify_13790.trace.log'. Will update configuration orcl21c (Oracle) between dbvel71 and dbvel72 (currently ENABLED with an interval of 600 seconds) to be DISABLED with an interval of 600 seconds ? Update 1 configuration(s) - are you sure? Yes Successfully updated configuration orcl21c (Oracle) between dbvel71 and dbvel72
C:\Program Files\Dbvisit\standbymp\bin>dbvagentmanager.exe auto-update modify -d AdWorks --disable Trace log will be written to 'C:\Program Files\Dbvisit\standbymp\log\trace\dbvagentmanager_auto-update_modify_900.trace.log'. Will update configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds) to be DISABLED with an interval of 120 seconds ? Update 1 configuration(s) - are you sure? Yes Successfully updated configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com
[oracle@dbvel71 bin]$ ./dbvagentmanager auto-update modify -d orcl21c --enable Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvagentmanager_auto-update_modify_18812.trace.log'. Will update configuration orcl21c (Oracle) between dbvel71 and dbvel72 (currently DISABLED with an interval of 600 seconds) to be ENABLED with an interval of 600 seconds ? Update 1 configuration(s) - are you sure? Yes Successfully updated configuration orcl21c (Oracle) between dbvel71 and dbvel72 [oracle@dbvel71 bin]$
C:\Program Files\Dbvisit\standbymp\bin>dbvagentmanager.exe auto-update modify -d AdWorks --enable Trace log will be written to 'C:\Program Files\Dbvisit\standbymp\log\trace\dbvagentmanager_auto-update_modify_956.trace.log'. Will update configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently DISABLED with an interval of 120 seconds) to be ENABLED with an interval of 120 seconds ? Update 1 configuration(s) - are you sure? Yes Successfully updated configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com
Change Automatic Standby Interval
The option --set-interval-seconds is used to change the automated standby interval time. The -d option is used to specify the configuration for which the interval is changed. The option of noprompt and noconfirm is used in the same way as above. If -d is not used, all the configuration’s interval is changed to the provided value. The -t option is used to change for specific database types (Oracle, SQLServer).
[oracle@dbvel71 bin]$ ./dbvagentmanager auto-update modify -d orcl21c --set-interval-seconds 300 Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvagentmanager_auto-update_modify_23600.trace.log'. Will update configuration orcl21c (Oracle) between dbvel71 and dbvel72 (currently ENABLED with an interval of 600 seconds) to be ENABLED with an interval of 300 seconds ? Update 1 configuration(s) - are you sure? Yes Successfully updated configuration orcl21c (Oracle) between dbvel71 and dbvel72 [oracle@dbvel71 bin]$
C:\Program Files\Dbvisit\standbymp\bin>dbvagentmanager.exe auto-update modify --set-interval-seconds 75 Trace log will be written to 'C:\Program Files\Dbvisit\standbymp\log\trace\dbvagentmanager_auto-update_modify_1764.trace.log'. ? Please choose the configurations to operate on AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds), TEAM (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds), NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds), KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds), LINE (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 300 seconds) Will update configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds) to be ENABLED with an interval of 75 seconds Will update configuration TEAM (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds) to be ENABLED with an interval of 75 seconds Will update configuration NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds) to be ENABLED with an interval of 75 seconds Will update configuration KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 120 seconds) to be ENABLED with an interval of 75 seconds Will update configuration LINE (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 300 seconds) to be ENABLED with an interval of 75 seconds ? Update 5 configuration(s) - are you sure? Yes Successfully updated configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration TEAM (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration LINE (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com
C:\Program Files\Dbvisit\standbymp\bin>dbvagentmanager.exe auto-update modify -d KEY --set-interval-seconds 90 --noconfirm Trace log will be written to 'C:\Program Files\Dbvisit\standbymp\log\trace\dbvagentmanager_auto-update_modify_4836.trace.log'. Will update configuration KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 75 seconds) to be ENABLED with an interval of 90 seconds Successfully updated configuration KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com
Auto-Update using dbvcontrol
The above operations from the agentmanager can also be directly done from the dbvcontrol executable. The key advantage is all the options can be done from the single control center server using the dbvcontrol executable.
[oracle@dbvel72 bin]$ ./dbvcontrol auto-update -h
Modify the Automated Standby Update settings for one or more configurations
This command operates on one or more configurations, applying the specified modification to the Automated Standby Update settings of each of them.
If the flags specified match more than one configuration, the user is prompted to choose which they wish to operate on, unless the --noprompt flag is specified, in which case all matching configurations
are operated on.
The user is prompted for confirmation before any updates are performed, unless the --noconfirm flag is specified.
Credentials for a Control Center user are required. Set the DBVUSERNAME environment variable or specify the --username flag to set the user name to use. If neither the flag or the environment variable
are set then you will be prompted for the user name.
Set the DBVPASSWORD environment variable to provide the password. It is possible, but not recommended, to specify the password using the --password flag; doing so will cause the password to be visible
to other processes on the system and to be recorded in log files. If neither the flag or the environment variable are set then you will be prompted for the password.
Usage:
dbvcontrol auto-update [flags]
Examples:
To disable Automated Standby Update for a named configuration:
dbvcontrol auto-update --configuration-name DEV --disable
To disable Automated Standby Update for configurations involving a particular host:
dbvcontrol auto-update --host-name host1 --noprompt --disable
To enable Automated Standby Update for selected configurations:
dbvcontrol auto-update --enable
To enable Automated Standby Update for all configurations:
dbvcontrol auto-update --noprompt --enable
To enable Automated Standby Update for all configurations without confirmation:
dbvcontrol auto-update --noprompt --enable --noconfirm
Flags:
-g, --logToStderr send logs to STDERR instead of writing to log files
-U, --username string username to log into the Control Center with (you can also use the DBVUSERNAME environment variable)
-P, --password string password to log into the Control Center with (NOT RECOMMENDED - use the DBVPASSWORD environment variable instead!)
-d, --configuration-name string name of the configuration to operate on
-t, --configuration-type string type of the configuration to operate on
--host-name string host name of the configuration to operate on
--instance-name string instance name of the configuration to operate on (SQL Server configurations only)
--enable enable Automated Standby Update
--disable disable Automated Standby Update
--set-enabled enabled set whether Automated Standby Update is enabled (true or false) (default (unset))
--set-interval-seconds interval set the Automated Standby Update interval in seconds (default (unset))
--noprompt update all matching configurations without prompting the user to select
--noconfirm skip the confirmation prompt and proceed immediately
-h, --help help for auto-update
To run any of the options for auto-update using dbvcontrol. The -U and -P must be used (-U username for the control center -P password for the control center). If no option is used the username and password is prompted for the user to enter.
[oracle@dbvel72 bin]$ ./dbvcontrol auto-update --disable Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvcontrol_auto-update_25047.trace.log'. Please enter credentials for the StandbyMP Control Center. ? Username: admin ? Password: ***** Will update configuration orcl21c (Oracle) between dbvel71 and dbvel72 (currently DISABLED with an interval of 300 seconds) to be DISABLED with an interval of 300 seconds ? Update 1 configuration(s) - are you sure? Yes Successfully updated configuration orcl21c (Oracle) between dbvel71 and dbvel72 [oracle@dbvel72 bin]$
[oracle@dbvel72 bin]$ ./dbvcontrol auto-update -U admin -P admin --enable Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvcontrol_auto-update_25123.trace.log'. Will update configuration orcl21c (Oracle) between dbvel71 and dbvel72 (currently DISABLED with an interval of 300 seconds) to be ENABLED with an interval of 300 seconds ? Update 1 configuration(s) - are you sure? Yes Successfully updated configuration orcl21c (Oracle) between dbvel71 and dbvel72
C:\Program Files\Dbvisit\standbymp\bin>dbvcontrol.exe auto-update -U admin -P admin -d AdWorks --disable Trace log will be written to 'C:\Program Files\Dbvisit\standbymp\log\trace\dbvcontrol_auto-update_2428.trace.log'. Will update configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 75 seconds) to be DISABLED with an interval of 75 seconds ? Update 1 configuration(s) - are you sure? Yes Successfully updated configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com
The --noconfirm and --noprompt options work exactly the same as the dbvagentmanager auto-update option.
C:\Program Files\Dbvisit\standbymp\bin>dbvcontrol.exe auto-update -U admin -P admin -d AdWorks --enable --noconfirm Trace log will be written to 'C:\Program Files\Dbvisit\standbymp\log\trace\dbvcontrol_auto-update_344.trace.log'. Will update configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently DISABLED with an interval of 75 seconds) to be ENABLED with an interval of 75 seconds Successfully updated configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com
The -d option is used for choosing the specific configuration name, and the -t option is used for choosing either Oracle or SqlServer.
C:\Program Files\Dbvisit\standbymp\bin>dbvcontrol.exe auto-update -U admin -P admin -t sqlserver --disable --noconfirm Trace log will be written to 'C:\Program Files\Dbvisit\standbymp\log\trace\dbvcontrol_auto-update_3640.trace.log'. ? Please choose the configurations to operate on AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 75 seconds), TEAM (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 75 seconds), NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 75 seconds), KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 90 seconds), LINE (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 75 seconds) Will update configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 75 seconds) to be DISABLED with an interval of 75 seconds Will update configuration TEAM (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 75 seconds) to be DISABLED with an interval of 75 seconds Will update configuration NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 75 seconds) to be DISABLED with an interval of 75 seconds Will update configuration KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 90 seconds) to be DISABLED with an interval of 90 seconds Will update configuration LINE (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com (currently ENABLED with an interval of 75 seconds) to be DISABLED with an interval of 75 seconds Successfully updated configuration AdWorks (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration TEAM (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration NEW (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration KEY (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com Successfully updated configuration LINE (SQL Server) between MSSQLSERVER on toru.MP-webinar.envbuilder.cubicle-labs.com and MSSQLSERVER on wha.MP-webinar.envbuilder.cubicle-labs.com
The other option is to use --host-name is used for changing the auto-update setting specific to primary host. This can be done to update the setting if configurations have different primary and standby hosts. and --instance-name is used for SQL Server instance names.