Configuring the Agent Using the Command-line

The VCS enterprise 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.

Follow the instructions below to configure the agent using the sample configuration file:

1. Log in to sysa as root.
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. Copy the Oracle types configuration file into place:
        # cp /etc/VRTSvcs/conf/OracleTypes.cf
        /etc/VRTSvcs/conf/config/OracleTypes.cf
6. Edit the main.cf file. The file /etc/VRTSvcs/conf/sample_oracle/main.cf can be used for reference:
   1. Add an "include" line for the OracleTypes.cf file:
   
                   include "OracleTypes.cf" 
   2. Create the Oracle and Netlsnr resources. You can refer to the examples shown in the file /etc/VRTSvcs/conf/sample_oracle/main.cf.
   3. Edit the default attributes to match the parameters in your configuration. See Resource Type Definitions for more information about the agent attributes.
   4. Assign dependencies to the newly created resources. Refer to the sample file /etc/VRTSvcs/conf/sample_oracle/main.cf. and the sample dependency graphs in Sample Configurations. (See the VERITAS Cluster Server User's Guide for more information on assigning dependencies.)
7. Save and close the file.
8. Verify the syntax of the file /etc/VRTSvcs/conf/config/main.cf:
      # cd /etc/VRTSvcs/conf/config/
     # hacf -verify .
9. Start the VCS engine:
     # hastart
10. Verify that all Oracle service group resources are brought online:
      # hagrp -state
11. Take the service group offline and verify that all resources are stopped:
      # hagrp -offline service_group -sys system_name
      # hagrp -state
12. Bring the service group online again and verify that all resources are available:
      # hagrp -online service_group -sys system_name
      # hagrp -state
13. Start the VCS engine on sysb:
      # hastart
14. Switch the Oracle service group to sysb:
      # hagrp -switch service_group -to sysb
15. Verify that all Oracle service group resources are brought online on sysb:
      # hagrp -state
16. On all the systems, 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