Send and Apply Archivelogs

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

Purpose:

Will send an archivelog from primary server similar to running “dbvctl -d <DDC>” command

Parameters:

--configuration-name [DDC configuration name]

Successful command run:

$ ./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

Purpose:

Will apply an archivelog on standby server similar to running “dbvctl -d <DDC>” command

Parameters:

--configuration-name [DDC configuration name]

Successful command run:

$ ./dbvagentmanager --configuration-name SOLO apply-logs
Trace log will be written to '/usr/dbvisit/standbymp/log/trace/dbvagentmanager_apply-logs_444641.trace.log'.
Will apply logs for configuration SOLO (Oracle) between dbvisit-vip2178 and czlin0212
Mon, 09 May 2022 13:35:34 +0200 Applying Log file(s) from dbvisit-vip2178 to SOLO on czlin0212:
Mon, 09 May 2022 13:35:36 +0200 No new logs to apply.
Mon, 09 May 2022 13:35:36 +0200 Last applied log(s):
Mon, 09 May 2022 13:35:36 +0200 thread 1 sequence 4018
Mon, 09 May 2022 13:35:36 +0200 Next SCN required for recovery 38644880 generated at 2022-05-09:13:35:17 +02:00.
Mon, 09 May 2022 13:35:36 +0200 Next required log thread 1 sequence 4019
Action completed.