test

Sun Cluster 3.0 U1 Data Services Installation and Configuration Guide

Verifying the Sun Cluster HA for Oracle Installation

Perform the following verification tests to make sure that you have correctly installed the Sun Cluster HA for Oracle data service.

These sanity checks ensure that all the nodes that run the Sun Cluster HA for Oracle data service can start the Oracle instance and that the other nodes in the configuration can access the Oracle instance. Perform these sanity checks to isolate any problems starting the Oracle software from the Sun Cluster HA for Oracle data service.

How to Verify the Sun Cluster HA for Oracle Installation

  1. Log in as oracle_id to the node that currently masters the Oracle resource group.

  2. Set the environment variables ORACLE_SID and ORACLE_HOME.

  3. Confirm that you can start the Oracle instance from this node.

  4. Confirm that you can connect to the Oracle instance.

    Use the sqlplus command with the tns_service variable defined in the tnsnames.ora file.


    # sqlplus user/passwd@tns_service

  5. Shut down the Oracle instance.

    The Sun Cluster software will restart the Oracle instance because the Oracle instance is under Sun Cluster control.

  6. Switch the resource group that contains the Oracle database resource to another cluster member.

    The following example shows how to complete this step.


    # scswitch -z -g resource-group -h node

  7. Log in as oracle_id to the node that now contains the resource group.

  8. Repeat Step 3 and Step 4 to confirm interactions with the Oracle instance.

Oracle Clients

Clients must always refer to the database by using the logical hostname (an IP address that can move between physical nodes during failover), not the physical hostname (a machine name).

For example, in the tnsnames.ora file, you must specify the logical hostname as the host on which the database instance is running. See "How to Set Up Oracle Database Permissions".

Note -

Oracle client-server connections cannot survive a Sun Cluster HA for Oracle switchover. The client application must be prepared to handle disconnection and reconnection or recovery as appropriate. A transaction monitor might simplify the application. Further, Sun Cluster HA for Oracle node recovery time is application dependent.