Activate Standby Database
This page describes the CLI interface for Activating Standby Database for Dbvisit Standby v11.
Needs to be run only on standby server. Is executed by running dbvagentmanager binary located in $DBVISIT_BASE/standbymp/bin
activate
This command must be run on standby server only
Purpose:
Activate standby database similar to “dbvctl -d <DDC> -o activate” command
Parameters:
--configuration-name [DDC configuration name]
Successful command run:
$ ./dbvagentmanager --configuration-name SOLO activate
Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvagentmanager_activate_445354.trace.log'.
Will activate configuration SOLO (Oracle) between dbvisit-vip2178 and czlin0212
Current Standby State: SCN: 38645595, Time: 2022-05-09:13:47:40
? Are you sure you want to activate the standby database for configuration SOLO (Oracle) between dbvisit-vip2178 and czlin0212? Yes
Mon, 09 May 2022 13:50:43 +0200 Running pre-checks please wait...
Mon, 09 May 2022 13:50:43 +0200 done
Mon, 09 May 2022 13:50:43 +0200 Next required SCN 38645595 generated at 2022-05-09:13:47:40 +02:00
Mon, 09 May 2022 13:50:43 +0200 Applying available logs...
Mon, 09 May 2022 13:50:44 +0200 Applying Log file(s) from dbvisit-vip2178 to SOLO on czlin0212:
Mon, 09 May 2022 13:50:45 +0200 No new logs to apply.
Mon, 09 May 2022 13:50:45 +0200 Last applied log(s):
Mon, 09 May 2022 13:50:45 +0200 thread 1 sequence 4023
Mon, 09 May 2022 13:50:45 +0200 Next SCN required for recovery 38645595 generated at 2022-05-09:13:47:40 +02:00.
Mon, 09 May 2022 13:50:45 +0200 Next required log thread 1 sequence 4024
Mon, 09 May 2022 13:50:45 +0200 Logs applied
Mon, 09 May 2022 13:50:45 +0200 Activating now...
Mon, 09 May 2022 13:51:08 +0200 Activation complete. Please ensure a backup of this Database is made
Mon, 09 May 2022 13:51:08 +0200 Old archives from before the activation should be removed to avoid mix-up between new and old archive logs
Mon, 09 May 2022 13:51:08 +0200 Process complete
Action completed.