This page describes the CLI interface for sending and applying archivelogs for Dbvisit Standby v11.
All commands needs to be run only on specific server (primary or standby) and are executed by running dbvagentmanager binary located in $DBVISIT_BASE/standbymp/bin
send-logs
This command must be run on primary server only
...
| Code Block |
|---|
$ ./dbvagentmanager --configuration-name SOLO send-logs Trace log will be written to '/dbvisit/app/standbymp/log/trace/dbvagentmanager_send-logs_3021006.trace.log'. Will send logs for configuration SOLO (Oracle) between dbvisit-vip2178 and czlin0212 Mon, 09 May 2022 13:37:15 +0200 Obtaining information from standby database (RUN_INSPECT=Y)... Mon, 09 May 2022 13:37:17 +0200 done Mon, 09 May 2022 13:37:17 +0200 Thread: 1 Archive log gap: 0. Transfer log gap: 0 Mon, 09 May 2022 13:37:17 +0200 Note FORCE_LOGGING is disabled in the primary database. Mon, 09 May 2022 13:37:17 +0200 Performing a log switch... Mon, 09 May 2022 13:37:23 +0200 done Mon, 09 May 2022 13:37:23 +0200 Transferring Log file(s) from SOLO on dbvisit-vip2178 to czlin0212: Mon, 09 May 2022 13:37:24 +0200 thread 1 sequence 4021 (thread_1_seq_4021.1802.1104241041)... Mon, 09 May 2022 13:37:24 +0200 done Action completed. |
apply-logs
This command must be run on standby server only
...