Configuring the Agent Using the Agent Configuration Wizard

VCS provides an Agent Configuration wizard that guides you through the process of configuring the agent. The wizard creates and modifies Oracle service groups.

This section describes the steps required to create a new Oracle service group using the wizard. To modify an existing service group, see Modifying the Agent Configuration.

Before configuring the Oracle agent, review the resource type and the attribute definitions of the Oracle and Netlsnr agents, described in Resource Type Definitions. For sample configuration files and resource dependency graphs of the Oracle service group, see Sample Configurations.

Prerequisites

  Make sure that the Oracle instances and listeners to be configured are running. All listeners to be configured must listen to the same virtual IP address.

---

  Note    For the default listener, the configuration wizard requires the listener parameter file, listener.ora, to reside in $ORACLE_HOME/network/admin. No such condition applies for non-default listeners.

---

  The Oracle files (control, data, redo-log, and archive files) must be on shared disks.

  The IP addresses and host names specified in the files listener.ora and tnsnames.ora must be the same.

  If detail monitoring is to be used for a database instance, the table used for detail monitoring must be set up, with user and password assigned.

  Make sure the Oracle type definition is imported to the VCS engine. See Importing the OracleTypes.cf File for instructions.

Importing the OracleTypes.cf File

Before configuring the Oracle agent, you must import the OracleTypes.cf file to the VCS engine.

  To import using the Cluster Manager

1. Start Cluster Manager and log on to the cluster.
2. From the Cluster Explorer's File menu, choose Import Types.
3. In the Import Types dialog box, select the following file.
   /etc/VRTSvcs/conf/OracleTypes.cf
4. Click Import.
5. Save the configuration.

  To import using the command line

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 to include the OracleTypes.cf file:
   include "OracleTypes.cf"