Configuring the agent to monitor Oracle

Perform the following steps to configure monitoring for Oracle on a virtual machine using the Symantec High Availability Configuration wizard.

To configure monitoring for Oracle

  1. Launch the Symantec High Availability Configuration wizard.
  2. Review the information on the Welcome panel and click Next.
  3. On the Application Inputs panel, select Oracle from the Supported Applications list and then click Next.

    You can use the Search box to search for the Oracle application.

  4. To review and modify listener configurations, in the Oracle Listener Details panel, select a listener from the list that the wizard automatically discovers and displays.

    For each listener, you can review the following details:

    • Listener

    • Home

    • Owner

    • Env File

    • TnsAdmin

    • Password

      The wizard automatically populates some of the above fields. Among the displayed fields, only the Home and Owner fields represent mandatory attributes. Apart from Listener, you can edit the values in the above fields.

  5. If you want to add a listener for monitoring, enter the name of the listener in the Listener text box. Click Add and then provide the required details.

    If you want to remove a listener from the displayed list, select the listener and click Remove.

  6. Repeat steps 4 and 5 for other listener instances that you want to monitor, and then click Next.
  7. To review and modify database configurations (including its associated listeners and mount points), on the Database Selection panel, click a database instance from the list of Database SIDs, that the wizard automatically discovers and displays.
  8. For each database instance, you can review the following details:
    • Database SID

    • Oracle Home

    • Database Owner

    • PFILE Path

    • Env File

      Among the displayed fields, only Database SID, Oracle Home, and Database Owner represent mandatory attributes. For each database instance that you select, the wizard also automatically displays the associated listeners and mount points.

  9. For each database, from the Selected Listeners list and Mount Points list, you can select the listeners and mount points that you want to associate with the database instance, and set up dependencies.
  10. Repeat steps 7 to 9 for each database instance that you want to monitor, and then click Next.
  11. On the Configuration Inputs panel, use the Edit icon to specify the user name and password of the systems for VCS cluster operations.

    Cluster systems lists the systems included in the cluster configuration. Application failover targets lists the systems to which the application can fail over. Move the required systems to the Application failover targets list. Use the up and down arrow keys to define the priority order of the failover systems. The local system is selected by default for both, the cluster operations and as a failover target.

  12. Click Next.
  13. Skip this step if you do not want to add more systems to your cluster.

    To add a system to the cluster, click Add System. In the Add System dialog box, specify the following details of the system that you want to add to the VCS cluster and click OK.

    System Name or IP address

    Specify the name or IP address of the system that you want to add to the VCS cluster.

    User name

    Specify the user account for the system.

    Typically, this is the root user. The root user should have the necessary privileges.

    Password

    Specify the password for the user account mentioned.

    Use the specified user account on all systems

    Select to use the specified user account on all the cluster systems that have the same user name and password.

  14. If you are configuring a cluster and if you want to modify the security settings for the cluster, click Advanced Settings. In the Advanced settings dialog box, specify the following details and click OK.

    Use Single Sign-on

    Select to configure single sign-on using VCS Authentication Service for cluster communication.

    This option is enabled by default.

    Use VCS user privileges

    Select to configure a user with administrative privileges to the cluster.

    Specify the username and password and click OK.

    Note:

    The Advanced Settings link is not visible if the cluster is already created.

  15. Skip this step if the cluster is already configured. By default, the links are configured over Ethernet.

    On the Network Details panel, select the type of network protocol to configure the VCS cluster network links and then specify the adapters for network communication.

    The wizard configures the VCS cluster communication links using these adapters. You must select a minimum of two adapters per system.

    Select Use MAC address for cluster communication (LLT over Ethernet) or Use IP address for cluster communication (LLT over UDP), depending on the IP protocol that you want to use and then specify the required details to configure the VCS cluster communication network links. You must specify these details for each cluster system.

    • To configure LLT over Ethernet, select the adapter for each network communication link. You must select a different network adapter for each communication link.

    • To configure LLT over UDP, select the type of IP protocol and then specify the required details for each communication link.

      Depending on the IP protocol, specify the following:

      Network Adapter

      Select a network adapter for the communication links.

      You must select a different network adapter for each communication link.

      IP Address

      Displays the IP address.

      Port

      Specify a unique port number for each link.

      For IPv4 and IPv6, the port range is from 49152 to 65535.

      A specified port for a link is used for all the cluster systems on that link.

      Subnet mask (IPv4)

      Displays the subnet mask details.

      Prefix (IPv6)

      Displays the prefix details.

    By default, one of the links is configured as a low-priority link on a public network interface. The second link is configured as a high-priority link. To change a high-priority link to a low-priority link, click Modify. In the Modify low-priority link dialog box, select the link and click OK.

    Note:

    Symantec recommends that you configure one of the links on a public network interface. You can assign the link on the public network interface as a low-priority link for minimal VCS cluster communication over the link.

  16. Skip this step if the application does not use virtual IP address.

    Note:

    If the application does not use a virtual IP address, you must remove the auto-populated subnet mask entry before proceeding to the next step.

    In the Virtual Network Details panel, specify the IP protocol and virtual IP address for the application.

    Depending on the IP protocol, specify the following:

    Virtual IP address

    Specify a unique virtual IP address.

    Subnet Mask (IPv4)

    Specify the subnet mask details.

    Prefix (IPv6)

    Select the prefix from the drop-down list.

    Network Adapter

    Select the network adapter that will host the virtual IP.

    If you want to add another virtual IP address for your application, click Add virtual IP address.

    If you want to remove a virtual IP address, click the Remove icon.

    If you select multiple instances for the same virtual IP address, those instances are configured in the same service group.

  17. Click Next.
  18. Skip this step if you did not select mount points.

    On the Target ESX Details panel, specify all the ESX hosts to which the virtual machines can fail over. Each ESX host must be able to access the required shared datastores that contain visible disks. Enter the administrative user account details for each ESX host and click Next.

    To specify the ESX hosts, click Add ESX Host and in the Add ESX Host dialog box, specify the following details:

    ESX hostname or IP address

    Specify the target ESX hostname or IP address.

    The virtual machines can fail over on this ESX host during vMotion. All the additional ESX hosts should have access to the datastore on which the disks used by the application reside.

    User name

    Specify a user account for the ESX host. The user account must have administrator privileges on the specified ESX host.

    Password

    Specify the password for the user account provided in the User name text box.

    The wizard validates the user account and the storage details on the specified ESX hosts.

  19. On the Summary panel, review the VCS cluster configuration summary and then click Next to proceed with the configuration.

    If the network contains multiple clusters, the wizard verifies the cluster ID with the IDs assigned to all the accessible clusters in the network. The wizard does not validate the assigned ID with the clusters that are not accessible during the validation. Symantec recommends you to validate the uniqueness of the assigned ID in the existing network. If the assigned ID is not unique or if you want to modify the cluster name or cluster ID, click Edit. In the Edit Cluster Details dialog box, modify the details as necessary and click OK.

  20. On the Implementation panel, the wizard creates the VCS cluster, configures the application for monitoring, and creates cluster communication links.

    The wizard displays the status of each task. After all the tasks are complete, click Next.

    If the configuration task fails, click View Logs to check the details of the failure. Rectify the cause of the failure and run the wizard again to configure application monitoring.

  21. On the Finish panel, click Finish to complete the wizard workflow.

    This completes the application monitoring configuration.

    If the application status shows as not running, click Start to start the configured components on the system.

More Information

Launching the Symantec High Availability Configuration wizard