< Previous  | TOC | Index | Next  >

Creating service groups using the configuration wizard

 To create service groups using the configuration wizard

1. Log on to one of your VCS systems as root. The configuration wizard for Oracle9i RAC is started at the command line.
2. Start the configuration wizard.

# /opt/VRTSvcs/bin/hawizard rac

3. In the Welcome screen that displays, the prerequisites for configuration and the information you will need to complete the configuration is displayed.
   • If your configuration does not meet the configuration requirements, you can stop the wizard by pressing Cancel. Take the necessary steps to meet the requirements and start the wizard again. See step 1
   • If you are ready to configure Oracle service group, press Next on the Welcome screen.

     The wizard begins discovering the current Oracle RAC information before proceeding with the next screen.

     If the wizard does not find all databases and listeners running on all systems in the cluster, it halts with an error, indicating the problem. Press Cancel, and start the wizard again after you correct the problem.

4. In the Wizard Options dialog box, Create RAC service group option.
5. Enter a name for the RAC service group in the Service group name box and click Next.
6. In the Database Selection dialog box, select a database and click Next.
7. In the Instance Configuration dialog box, specify the basic database instance information for the databases you selected.

Click the thumbnail above to view full-sized image.

• For each database instance discovered, basic configuration information is displayed. If necessary, double click in a field to select and edit its contents.
  • Instance name: Each instance is listed in the left hand column.
  • Oracle Parameter File (Pfile): The file that is used to start Oracle. The default location for a given instance is listed. Edit the information if necessary.
  • Start Options: the default is STARTUP_FORCE.
  • Stop Options: Accept the displayed IMMEDIATE option, or select an option from the drop-down menu.
• Select Configure detail monitoring to enable monitoring in detail. If you check enable detail monitoring, be sure you have previously set up the database table, user, and password for the agent to use during monitoring. See step 8. If you are not set up for detail monitoring, do not select it.
• Select Specify Advanced options to define monitoring options such as environment variables, Encoding, and an AutoEndBkup parameter. See step 8.
• Click Next.
8. If you choose to monitor the database in detail, The Detail Monitoring dialog box displays.

Click the thumbnail above to view full-sized image.

For each database instance identified by its Sid, this screen displays fields for defining the attributes that enable detail monitoring of the Oracle database resource. You do not have to enable detail monitoring on all instances, but for each instance for which you check Select, all fields are required:

• User: Oracle user, which the Oracle agent uses to log on to monitor the health of the database.
• Password: Password for the Oracle user. The wizard takes care of encrypting passwords.
• Table: Name of the database table to be used by the Oracle agent monitor.

9. The Oracle Advanced Configuration dialog box is displayed if you have checked Specify Advance options at the bottom of the Instance Configuration Screen.

Click the thumbnail above to view full-sized image.

For each database instance identified by its Sid, this dialog box displays fields for configuring the advanced attributes of the Oracle service group. You may select which database instance you want to configure advance attributes for, and which attributes you want to define, and click Next when you are done.

Advanced attributes include:

• Oracle EnvFile: the source file used by the agent entry point scripts.
• Oracle Encoding: the operating system encoding that corresponds to Oracle encoding for the displayed Oracle output; the encoding value must match the encoding value used by the Netlsnr configuration.
• AutoEndBkup: specifies that datafiles in the database are taken out of the backup mode when instance is brought online.

See the Veritas™ High Availability Agent for Oracle Installation and Configuration Guide for a complete description of the EnvFile, Encoding, and AutoEndBkup attributes.

10. In the Monitor Option Configuration dialog box, for each database instance you can specify whether to use the Process check (the default) or Health check option for monitoring method. Click Next to continue.
11. In the Database Configuration dialog box, the wizard discovers the Mount Point of the database if it installed on a cluster file system and displays it on the Database Configuration screen. If the database exists on raw volumes, the wizard discovers the volumes.

    Confirm or modify the Mount Options displayed and click Next.

Click the thumbnail above to view full-sized image.

12. The Listener Configuration dialog box displays the Sid and name of the Listener corresponding to each database instance, as well as the IP Address and Device name used by each listener. Typically, you cannot change this information, only verify it.

Click the thumbnail above to view full-sized image.

1. You can choose to configure detail monitoring for the Netlsnr agent by clicking the Enable detail monitoring checkbox. The wizard uses the monitor script /opt/VRTSvcs/bin/Netlsnr/LsnrTest.pl to monitor the listeners in detail.
2. You can choose Specify Advanced options to set up an EnvFile (to define environment variables), specify Encoding and the LsnrPwd parameters. See step 13.
3. Click Next.
13. The Listener Advanced Configuration dialog box displays if you have checked Specify Advanced options at the bottom of the Listener Configuration dialog box. If you have set up the listener to use the base, or host, IP address, the wizard displays a warning message when you press Next on the Listener Configuration dialog box. You must click Yes to proceed.

Click the thumbnail above to view full-sized image.

For each Listener identified by name, this screen displays fields for defining the advanced attributes of the Netlsnr resource.

• Netlsnr EnvFile: the name of the source file used by the agent entry point scripts; this file must exist.
• Netlsnr Encoding: the operating system encoding that corresponds to Oracle encoding for the displayed Oracle output; the encoding value must match the encoding value used by the Oracle configuration.
• Listener Password: the password used for Netlsnr; must specify the password as it appears in the listener.ora file. The wizard takes care of encrypting passwords.

Click Next.

14. In the Service Group Summary dialog box, the wizard displays the configuration after you have configured the database and listener resources.

    

    Click the thumbnail above to view full-sized image.

    Click a resource within the service group to display its attributes and their values. For example, if you click the name of the Oracle resource, Ora-racj1, the wizard displays details of the Oracle resource.

    Attributes for the CFSMount resource show dependencies. The NetLsnr resource is configured as part of the CVM service group. The CVM service group also contains other resources, which may not be displayed by the wizard because the wizard does not control them.

    Change names of resources, if desired; the wizard assigns unique names to resources based on their respective name rules. To edit a resource name, select the resource name and click on it, and press Enter after editing each attribute.

15. Review the configuration and Click Finish.

    The wizard implements the configuration changes. The wizard creates the Oracle service group, and adds the Netlsnr resource to the CVM configuration.