This section will cover additional notes and information specific to using Dbvisit Standby in an Oracle RAC environment.
Introduction
Dbvisit Standby will be installed on all the servers in an Oracle RAC configuration. For example if you are using a four node cluster, you need to install Dbvisit Standby on all four nodes as well as on the Standby server(s).
...
| Note | ||
|---|---|---|
| ||
DDC files should be created on the primary nodes - this is where the master copy of the DDC files are located and maintained. A copy of the DDC file will be transferred and maintained on the standby server by Dbvisit Standby. You should not manually create or modify the DDC file on the standby server. All DDC creation and changes should be made from the primary servers. |
Sending Archive Logs to the Standby
Executing (run) the default Dbvisit Standby commands from the command line can be done by running the following:
...
| Note | ||
|---|---|---|
| ||
All Archive logs generated on RAC database must be shipped (copied) to the standby database server (archive logs from all threads are needed for recovery). Dbvisit Standby is making use of a directory referred to as the ARCHDEST. This location is specific to Dbvisit Standby and is not - and should not, be seen as the same as the Oracle Database Archive destinations. When using Oracle RAC environments and Dbvisit Standby, you need to make sure you create the Dbvisit ARCHDEST directory on ALL the nodes as well as the standby server. This directory should be exactly the same on all nodes. ARCHDEST is the directory for (archive) log files on standby server, where it is not used to storage archive logs on the primary server, but it is used as a "temporary" location to move archive logs to while they are copied out of the ASM storage. For more detail please see ARCHDEST and ARCHTMP in the section discussing the Dbvisit Standby DDC configuration variables. It is important that Dbvisit Standby be executed from all the primary RAC nodes to ensure all archive logs from all the threads are copied to the standby server. |
Applying Archive Logs for RAC Environment on the Standby
When running/executing Dbvisit Standby on the standby server to apply the logs, the command used is the same as what you will be using to ship the logs to the standby (when running Dbvisit Standby on the primary nodes). One key difference on the apply side is that you only have to execute the Dbvisit Standby command for one of the DDC files. It will start the recovery process and it will take all the archive logs from all the threads into account (taking all logs shipped from all primary nodes into account).
...