Oracle RAC Specific Settings

Owned by Anton Els (Deactivated)
Last updated: Jan 22, 2014
2 min read

The section below is listing settings that should only be configured when implementing Dbvisit Standby on an Oracle RAC environment.

Variables are sorted alphabetically in the table below

Variable Name

Meaning

RAC

Determines whether Dbvisit Standby is part of an Oracle RAC (Oracle Real Application Cluster) configuration or not. 

This parameter will be set based on your information supplied during the creation of a new DDC file (using dbvisit_setup menu option 1a, or using the new setup configuration under the SETUP menu in the GUI)

Possible Values:

  • Yes
    Dbvisit Standby is part of a RAC configuration over several instances and nodes.

  • No (default value)
    Dbvisit Standby is configured for a single instance database.

In a RAC environment there will be a DDC file (dbv_instance_name.env) for every primary instance in the Oracle RAC.

Example:

    RAC = Yes

 

RAC_TAKEOVER

Determines if Dbvisit Standby processing on this RAC instance takes over Dbvisit Standby processing for another RAC instance (or node), if that instance or node is not available.

All archive log files must be available to all nodes (be located on shared disk). In most cases this will be ASM storage.

The variable RAC_TAKEOVER_SID (discussed below) determines which RAC instance that will be taken over.

If RAC_TAKEOVER is not enabled (set to "No"), the standby database may not be kept up to date if an instance is not available and Dbvisit Standby processing is not taken over by another instance.

Possible Values:

  • Yes 
    Dbvisit Standby (on this server) will take over from another instance (thread) when that instance is unavailable.

  • No 
    Dbvisit Standby (on this server) will NOT take over sending archive logs from another instance (thread) when that instance is unavailable.

If you are not sure, set to Yes.

Example:

    RAC_TAKEOVER = Yes

 

RAC_TAKEOVER_FORCE

Determines if Dbvisit Standby processing on this RAC instance, takes over Dbvisit Standby processing permanently for another RAC instance (thread).

Dbvisit Standby processing on this RAC instance will take over Dbvisit Standby processing on another RAC instance regardless of whether that node is available or not.

All archives must be available to all nodes using shared storage. In most cases this will be ASM.

The variable RAC_TAKEOVER_SID determines which RAC instance will be taken over.

Possible Values:

  • Yes
    Dbvisit Standby (on this instance) will always take over from another instance. 

  • No
    Dbvisit Standby (on this instance) will NOT take over from another instance unless the instance is not available and RAC_TAKEOVER = Yes.

If you are not sure, set to No.

Example (default) value:

    RAC_TAKEOVER_FORCE = No

 

RAC_TAKEOVER_SID

Specify the instance name that Dbvisit Standby processing should take over if that instance (thread) is unavailable.

The instance name must be different to the current instance name.

Example:

If you are running a two node RAC environment with node 1 running instance PROD1 and node 2 running instance PROD2, then you should configure the RAC_TAKEOVER_SID as follow:

    • On Node 1: set the value to match the instance number of Node 2.

RAC_TAKEOVER_SID = PROD2

    • On Node 2: set the value to match the instance number of Node 1.

RAC_TAKEOVER_SID = PROD1

Â