Setting up administrator-managed databases and policy-managed Oracle RAC databases in an SF Oracle RAC cluster

Article:HOWTO73184  |  Created: 2012-02-28  |  Updated: 2012-04-17  |  Article URL http://www.symantec.com/docs/HOWTO73184
Article Type
How To

Product(s)

Environment

Subject


Setting up administrator-managed databases and policy-managed Oracle RAC databases in an SF Oracle RAC cluster

Customer scenario

You want to set up an environment wherein some nodes host policy-managed databases while some nodes host administrator-managed databases. Sometimes, when you upgrade SF Oracle RAC on all nodes in the cluster, you may want to upgrade the Oracle database to Oracle RAC 11g Release 2 on only some nodes in the cluster. The remaining nodes may continue to run Oracle RAC 10g Release 2 or Oracle RAC 11g Release 1 databases.

Configuration overview

Coexistence of policy and administrator-managed databases requires that Oracle Clusterware be upgraded to use Oracle Grid Infrastructure on all nodes in the cluster. All nodes must belong to the same SF Oracle RAC cluster and Oracle Grid Infrastructure. Both policy-managed and administrator-managed databases can not coexist on the same node. Servers designated for administrator-managed databases are functionally exclusive of policy-managed database servers. The policy decisions that govern failures in the cluster apply only to the specific type of database servers (admin-managed or policy-managed) on which the failures occur. For example, if an admin-managed database resource faults, the policy decisions that effect fault recovery are applied only on the admin-managed database servers. These changes will not impact the servers that host policy-managed databases. This means that nodes hosting administrator-managed databases can not be failover candidates for policy-managed databases even if the administrator-managed database is offline on that node. If an administrator-managed database exists on nodes that are candidates for policy-managed databases, you must remove the administrator-managed databases from the nodes before using them to host policy-based databases. VCS works in tandem with the policy decisions taken by Oracle Grid Infrastructure.

The following figure illustrates a scenario where some nodes host policy-managed databases while some nodes host administrator-managed databases.

Supported configuration

  • SF Oracle RAC: 6.0

  • Oracle clusterware: Oracle Grid Infrastructure on all nodes in the cluster

  • Oracle RAC: Oracle RAC 10g Release 2, Oracle RAC 11g Release 1, Oracle RAC 11g Release 2

Solution

See “To configure policy-managed databases and administrator-managed databases in an SF Oracle RACcluster”.

To configure policy-managed databases and administrator-managed databases in an SF Oracle RACcluster

  1. Install and configure SF Oracle RAC on the nodes.

  2. Install Oracle RAC 11g Release 2 Grid Infrastructure on the nodes.

  3. Install Oracle database binaries on the nodes.

    For administrator-managed databases, install the database binaries on the nodes that will host administrator-managed databases.

    For policy-managed databases, install the database binaries of Oracle RAC 11g Release 2 on the nodes that will host policy-managed databases.

  4. Relink the Oracle database binaries with the Veritas libraries as described in the Oracle post-installation chapter of the installation guide.

    • For Oracle RAC 10g Release 2 databases:

      Using the SF Oracle RAC installer, relink the database binaries for each of the ORACLE_HOME locations.

      Unlink the Veritas ODM library for the databases that reside on ASM.

      $ ln -sf $ORACLE_HOME/lib/libodmd.so $ORACLE_HOME/lib/libodm10.so
    • For Oracle RAC 11g Release 1/Oracle RAC 11g Release 2 databases:

      Using the SF Oracle RAC installer, relink the database binaries in the ORACLE_HOME directory of databases that reside on CFS.

      Note:

      You need not link the database binaries with the Veritas libraries for the databases that reside on ASM.

  5. Create policy-managed databases on the designated nodes.

    For instructions, see the Oracle documentation.

  6. Create administrator-managed databases on the designated nodes.

    Ensure that you pin the nodes designated to host the administrator-managed databases and apply the Oracle Patch as described in the Oracle Metalink document: 948456.1

  7. Configure the VCS service groups for Oracle RAC as described in the Oracle post-installation chapter of the installation guide.

For instructions, see Veritas Storage Foundation for Oracle RAC Installation and Configuration Guide (6.0).

See Deploying Oracle RAC databases on Veritas CFS and Oracle ASM


Legacy ID



uxrt-60_v71546398_v72386815


Article URL http://www.symantec.com/docs/HOWTO73184


Terms of use for this information are found in Legal Notices