Implementing failover using Oracle RAC

Use this procedure to enable console failover when using Oracle RAC

Before you begin

Basic database setup for Oracle RAC is the same as setup for other Oracle databases. Install the console using those settings. After the console is installed, use these procedures to implement failover.

About this task

To enable Oracle RAC failover to work with Build Forge, there is additional configuration required. There are two methods available:
  • SCAN method: modify buildforge.conf. SCAN (single client access name) is a facility in Oracle 11g. When it is used, all nodes in the cluster are made eligible for failover. At least three nodes should be available and set up to fail over on a round-robin basis.
  • Explicit Connection strings method: modify the tnsnames.ora file for Oracle Instant Client and modify buildforge.conf. In this method you specify the service which represents the cluster and each desired cluster node. At least three nodes should be available and set up to fail over on a round-robin basis. The LOAD_BALANCE and FAILOVER parameters must be set.

    You may need the Oracle DBA to provide the name of the service and the list of nodes to use. You configure the tnsnames.ora file for Oracle Instant Client and set the JDBC connection string in buildforge.conf.

Both methods require that you specify SERVICE_NAME, which represents the cluster as a whole. This is different than non-RAC configurations, where SERVICE_NAME is typically the same as the SID.

Procedure


Feedback