Configuring the VCS service group for Oracle using the command-line

The Cluster Server agent for Oracle comes with a sample configuration file that can be used as reference to directly modify your present configuration file. When you use this method, you must stop and restart VCS to implement the configuration.

The Cluster Server agent for Oracle also includes sample configuration files for ASM configurations in a VCS environment.

To configure the service group using the sample configuration file

  1. Log in as superuser on the system where oracle is running.
  2. Ensure that all changes to the existing configuration have been saved and that further changes are prevented while you modify main.cf:
    # haconf -dump  -makero
    
  3. To ensure that VCS is not running while you edit main.cf, issue the following command to stop the VCS engine on all systems and leave the resources available:
    # hastop -all  -force
    
  4. Make a backup copy of the main.cf file:
    # cd /etc/VRTSvcs/conf/config
    # cp main.cf main.cf.orig
    
  5. Edit the main.cf file.

    You can use the file /etc/VRTSagents/ha/conf/Oracle/sample_main.cf for reference.

    Do the following:

    • Create the Oracle and Netlsnr resources.

      For ASM instances and disk groups, create the ASMInst and ASMDG resources.

    • Edit the default attributes to match the parameters in your configuration.

    • Assign dependencies to the newly created resources.

      See the Cluster Server Administrator’s Guide for more information on assigning dependencies.

  6. Save and close the file.
  7. Verify the syntax of the file /etc/VRTSvcs/conf/config/main.cf:
    # cd /etc/VRTSvcs/conf/config/
    # hacf -verify .
    
  8. Start the VCS engine:
    # hastart
    
  9. Verify that all Oracle service group resources are brought online:
    # hagrp -state
    
  10. Take the service group offline and verify that all resources are stopped:
    # hagrp -offline service_group -sys system_name
    # hagrp -state
    
  11. Bring the service group online again and verify that all resources are available:
    # hagrp -online service_group -sys system_name
    # hagrp -state
    
  12. Start the VCS engine on all remaining nodes in the cluster:
    # hastart
    
  13. (Optional) Switch the Oracle service group to to one of the cluster node to verify that it has been configured correctly for failover:
    # hagrp -switch service_group -to any
    

    Verify that all Oracle service group resources are brought online on the system:

    # hagrp -state
    	
  14. On all the nodes, look at the following log files for any errors or status:
    /var/VRTSvcs/log/engine_A.log
    /var/VRTSvcs/log/Oracle_A.log
    /var/VRTSvcs/log/Netlsnr_A.log
    /var/VRTSvcs/log/ASMInst_A.log
    /var/VRTSvcs/log/ASMDG_A.log

More Information

About the sample configurations for Oracle enterprise agent

About the resource type and attribute definitions

About the sample configurations for Oracle enterprise agent