...
| No Format |
|---|
oracle@dbvlin501[/usr/dbvisit/standby]: ./dbvisit proddb
=============================================================
Dbvisit Standby Database Technology (7.0.01.11254) (pid 10632)
dbvisit started on dbvlin501: Thu Aug 22 23:12:11 2013 ()
=============================================================
>>> Obtaining information from standby database (RUN_INSPECT=Y)...
>>> Checking Dbvisit Standby for configurational differences between dbvlin501 and
dbvlin502...
No configurational differences found between dbvlin501 and dbvlin502.
>>> Log file(s) for proddb will be transferred from dbvlin501 to dbvlin502...
> Transferring 'o1_mf_1_5437_91fnr2k9_.arc.gz' to server dbvlin502:7890
Progress: 0%...20%...40%...60%...80%...100% [2725 KB/s] - done.
> Transferring 'o1_mf_1_5438_91fnr2yf_.arc.gz' to server dbvlin502:7890
Progress: 0%...20%...40%...60%...80%...100% [1513 KB/s] - done.
> Transferring 'o1_mf_1_5439_91fnr3bw_.arc.gz' to server dbvlin502:7890
Progress: 0%...20%...40%...60%...80%...100% [1708 KB/s] - done.
3 archive log transfers to dbvlin502 for proddb completed.
Last sequence was 5439.
>>> 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:12:27 2013
============================================================= |
| Note | ||
|---|---|---|
| ||
When running Dbvisit Standby on an Oracle RAC environment, you will need to run the sending of archive logs on each of the primary RAC Nodes. Example, if you have a database called PROD with instance PROD1 on node 1 and PROD2 on node 2 you will end up with a DDC file per node, example:
Node 1: dbv_PROD1.env Node 2: dbv_PROD2.env
When scheduling or running Dbvisit on the RAC nodes, you will run Dbvisit Standby as follow:
On Node 1 execute the command: dbvisit PROD1 On Node 2 execute the command: dbvisit PROD2 It is recommended that when you schedule Dbvisit Standby on the RAC nodes to schedule them at least 1 minute apart and not at the exact same time. |
When Dbvisit Standby is executed to send Archive Logs to the Standby database the process can be summarised as follow:
...
- Archive logs located in the Dbvisit ARCHDEST location will be applied to the standby database
- If the archive logs are compressed (based on the COMPRESS value in the DDC file), they will be automatically uncompressed (based on the UNCOMPRESS value in DDC file) after which they will be applied to the standby database.
- Once all archive logs available in the ARCHDEST location was applied, will Dbvisit Standby execute the Dbvisit Standby Archivelog Management Module (AMM) which will manage the ARCHDEST location on the standby database server.
| Note | ||
|---|---|---|
| ||
When using Oracle RAC as the primary environment, it is important to note that you only have to run Dbvisit Standby on the standby server for ONE of the DDC files and you do not have to run it for both. Example: If you have a 2 node primary RAC environment, with dbv_PROD1.env and dbv_PROD2.env as the DDC files for the RAC database called PROD. You will run Dbvisit Standby on both primary RAC nodes to ship each node's respective archive logs (archive logs for that thread) to the standby. But on the standby server, you only have to run Dbvisit Standby for one of the DDC files. Dbvisit Standby will apply all logs from both threads during recovery. In this case you can run only "dbvisit PROD1" to apply all the logs on the standby. |