It might happen that you would like to resend all the archivelogs still required by the standby for recovery.
It might also be possible that you have recovered the standby database outside Dbvisit Standby. If this was done it is also recommended to resync the archive logs which will update the internal Dbvisit Repository as well.
This can be done by running the command:
All logs that still need to be applied to the standby database will be resent from the primary to the standby. In addition to this, the DDC file will also be resent from the primary to the standby server.
oracle@dbvlin501[/usr/dbvisit/standby]: ./dbvisit -R proddb
Dbvisit Standby Database Technology (7.0.01.11254) (pid 10854)
dbvisit started on dbvlin501: Thu Aug 22 23:20:49 2013 ()
Waiting 3 seconds for log switch completion...
Resynch option given. Dbvisit Standby configuration will be copied to dbvlin502...
> Transferring 'dbv_proddb.env' to server dbvlin502:7890
Progress: 0%...20%...40%...60%...80%...100% [17625 KB/s] - done.
Contacting Standby Database proddb on dbvlin502...
Next standby sequence required for recovery (5440).
>>> Log file(s) for proddb will be transferred from dbvlin501 to dbvlin502...
> Transferring 'o1_mf_1_5440_91fo8qww_.arc.gz' to server dbvlin502:7890
Progress: 0%...20%...40%...60%...80%...100% [6645 KB/s] - done.
1 archive log transfer to dbvlin502 for proddb completed.
Last sequence was 5440.
>>> Dbvisit Archive Management Module (AMM)
Config: number of archives to keep = 0
Config: number of days to keep archives = 7
Config: archive backup count = 0
Config: diskspace full threshold = 80%
Current disk percent full (/u01/app/oracle/flash_recovery_area) = 24%
Current disk percent full (FRA) = 76%
Number of archive logs deleted = 0
dbvisit ended on dbvlin501: Thu Aug 22 23:21:09 2013