Normally Dbvisit Standby on the primary server does not contact the standby database when transferring log files. This allows complete independent processing.
It is possible for Dbvisit Standby to contact the standby database, obtain the next log sequence number it requires and start transferring this log and subsequent logs until the current log sequence on the primary database.
This option is useful if:
...
| Section |
|---|
| Column |
|---|
| | Panel |
|---|
| bvisitdbvisit -R dbvisitp
======================================================
Dbvisit Standby Database technology
dbvisit started on dbvisit11
======================================================
Performing Oracle Checkpoint.
Waiting for 3 seconds for checkpoint completion...
Resynch option given. Dbvisit installation will be copied to dbvisit12...
Transferring dbv_functions to host dbvisit12:dbv_functions
Transferring dbvisit to host dbvisit12:dbvisit
Transferring dbvisit_setup to host dbvisit12:dbvisit_setup
Transferring dbv_oraStartStop to host dbvisit12:dbv_oraStartStop
Transferring dbv_dbvisitp.env to host dbvisit12:dbv_dbvisitp.env
Transferring dbv_ORACLE_SID.env to host dbvisit12:dbv_ORACLE_SID.env
Contacting Standby Database dbvisitp on dbvisit12...
Last standby sequence obtained (228).
200608292337 - 6 Log transfer(s) for dbvisitp completed.
Last sequence was 234.
======================================================
dbvisit ended on dbvisit11:
====================================================== |
Where dbvisitp is the name of the database |
|
Image ModifiedHome > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Resynchronize from Run Action drop-down menu > Run
Note: The standby database must be available in standby mode or in READ ONLY mode.
This option only needs to be done once to synchronise.