Cluster Server 7.4 Agent for Oracle Installation and Configuration Guide - Linux

Last Published:
Product(s): InfoScale & Storage Foundation (7.4)
Platform: Linux
  1. Introducing the Cluster Server agent for Oracle
    1. About the Cluster Server agent for Oracle
      1.  
        About the agent for Oracle ASM
    2.  
      Supported software for VCS agent for Oracle
    3.  
      Changes introduced in the 7.4 release
    4. How the agent makes Oracle highly available
      1.  
        How the Oracle and Netlsnr agents support intelligent resource monitoring
      2.  
        How the agent makes Oracle ASM instance highly available
      3.  
        How the agent supports container database (CDB) and pluggable database (PDB) in Oracle 12C
    5. About Cluster Server agent functions for Oracle
      1. Oracle agent functions
        1.  
          Startup and shutdown options for the Oracle agent
        2.  
          Startup and shutdown options for the pluggable database (PDB)
        3.  
          Recommended startup modes for pluggable database (PDB) based on container database (CDB) startup modes
        4.  
          Monitor options for the Oracle agent in traditional database and container database
        5.  
          Monitor for the pluggable database
        6.  
          How the agent handles Oracle error codes during detail monitoring
        7.  
          Info entry point for Cluster Server agent for Oracle
        8.  
          Action entry point for Cluster Server agent for Oracle
        9. How the Oracle agent supports health check monitoring
          1.  
            Generating the executable required for Oracle health check monitoring
          2.  
            Considerations to run the build_oraapi.sh script
          3.  
            Building the Oracle agent executable using the build_oraapi.sh script
      2.  
        Netlsnr agent functions
      3. ASMInst agent functions
        1.  
          ASMInst agent Startup options
        2.  
          ASMInst agent Shutdown options
        3.  
          Monitor options for the ASMInst agent
      4.  
        ASMDG agent functions
    6.  
      Typical Oracle configuration in a VCS cluster
    7.  
      About setting up Oracle in a VCS cluster
  2. Installing and configuring Oracle
    1.  
      About installing Oracle in a VCS environment
    2.  
      Before you install Oracle in a VCS environment
    3. About VCS requirements for installing Oracle
      1.  
        Location of the $ORACLE_HOME
      2.  
        Failing over Oracle after a VCS node failure during hot backup
    4. About Oracle installation tasks for VCS
      1.  
        Installation tasks for $ORACLE_HOME on shared disks
      2.  
        Installation tasks for $ORACLE_HOME on local disks
      3.  
        Installation tasks for Oracle using ASM
    5. Installing ASM binaries for Oracle 11gR2 or 12c in a VCS environment
      1.  
        Configuring VCS to support Oracle Restart function
    6. Configuring Oracle ASM on the first node of the cluster
      1.  
        Enabling the clustering daemon for ASM-managed database
      2.  
        Enabling Oracle Cluster Synchronization Service daemon to start automatically
    7.  
      Configuring and starting up ASM on remaining nodes for 11gR2 or 12c
    8. Installing Oracle binaries on the first node of the cluster
      1.  
        Disabling the clustering daemon for Oracle 10g or later
    9.  
      Configuring the Oracle database
    10.  
      Copying the $ORACLE_BASE/admin/SID directory
    11.  
      Copying the Oracle ASM initialization parameter file
    12.  
      Verifying access to the Oracle database
  3. Installing and removing the agent for Oracle
    1.  
      Before you install or upgrade the agent for Oracle
    2.  
      Installing the VCS agent for Oracle software
    3. Upgrading the VCS agent for Oracle
      1.  
        Upgrading VCS agent for Oracle to use with VCS 7.4
    4.  
      Disabling the Cluster Server agent for Oracle
    5.  
      Removing the Cluster Server agent for Oracle
  4. Configuring VCS service groups for Oracle
    1.  
      About configuring a service group for Oracle
    2. Configuring Oracle instances in VCS
      1.  
        Configuring a single Oracle instance in VCS
      2.  
        Configuring multiple Oracle instances (single listener) in VCS
      3.  
        Configuring multiple Oracle instances (multiple listeners) in VCS
      4.  
        Configuring an Oracle instance with shared server support in VCS
    3. Before you configure the VCS service group for Oracle
      1.  
        Importing the type definition files for Cluster Server agent for Oracle
    4. Configuring the VCS service group for Oracle
      1.  
        Configuring the VCS service group for Oracle using Cluster Manager (Java console)
      2. Configuring the VCS service group for Oracle using the command-line
        1.  
          Encrypting Oracle database user and listener passwords
    5. Setting up detail monitoring for VCS agents for Oracle
      1. Setting up detail monitoring for Oracle
        1.  
          Enabling and disabling detail monitoring for Oracle resource
      2.  
        Setting up detail monitoring for Netlsnr
    6. Enabling and disabling intelligent resource monitoring for agents manually
      1.  
        Administering the AMF kernel driver
  5. Configuring VCS service groups for Oracle using the Veritas High Availability Configuration wizard
    1.  
      Typical VCS cluster configuration in a virtual environment
    2.  
      About configuring application monitoring using the High Availability solution for VMware
    3.  
      Getting ready to configure VCS service groups using the wizard
    4.  
      Before configuring application monitoring
    5.  
      Launching the High Availability Configuration wizard
    6.  
      Configuring the agent to monitor Oracle
    7. Understanding service group configurations
      1.  
        Resource dependency
      2.  
        Service group dependency
      3.  
        Infrastructure service groups
    8. Understanding configuration scenarios
      1.  
        Configuring a single instance/multiple instances in VCS
      2.  
        Configuring multiple Oracle instances in VCS using multiple runs of the wizard
      3.  
        Configuring multiple applications
    9.  
      High Availability Configuration wizard limitations
    10. Troubleshooting
      1.  
        High Availability Configuration wizard displays blank panels
      2.  
        The High Availability Configuration wizard displays the 'hadiscover is not recognized as an internal or external command' error
      3.  
        Running the 'hastop - all' command detaches virtual disks
      4.  
        Log files
    11. Sample configurations
      1.  
        Sample VCS configuration file for single Oracle instance (VxVM)
      2.  
        Sample VCS configuration file for single Oracle instance (LVM)
  6. Administering VCS service groups for Oracle
    1.  
      About administering VCS service groups
    2.  
      Bringing the service group online
    3.  
      Taking the service group offline
    4.  
      Switching the service group
    5.  
      Modifying the service group configuration
  7. Pluggable database (PDB) migration
    1.  
      Migrating Pluggable Databases (PDB) between Container Databases (CDB)
  8. Troubleshooting Cluster Server agent for Oracle
    1.  
      About troubleshooting Cluster Server agent for Oracle
    2.  
      Error messages common to the Oracle and Netlsnr agents
    3.  
      Error messages specific to the Oracle agent
    4.  
      Error messages specific to the Netlsnr agent
    5.  
      Error messages specific to the ASMInst agent
    6.  
      Error messages specific to the ASMDG agent
    7.  
      Troubleshooting issues specific to Oracle in a VCS environment
    8. Verifying the Oracle health check binaries and intentional offline for an instance of Oracle
      1.  
        Verifying the intentional offline behavior of the VCS Oracle agent
    9.  
      Disabling IMF for a PDB resource
  9. Appendix A. Resource type definitions
    1.  
      About the resource type and attribute definitions
    2. Resource type definition for the Oracle agent
      1.  
        Resource Type Definition for systemD Support
      2.  
        Attribute definition for the Oracle agent
      3.  
        About the Sid attribute in a policy managed database
      4. Using systemD attributes for Oracle application service
        1.  
          Adding key-value pairs to SystemDAttrList attribute
        2.  
          Customizing the Oracle service unit file with systemD attributes
      5.  
        Configuring HugePages for Oracle on Linux
    3. Resource type definition for the Netlsnr agent
      1.  
        Attribute definition for the Netlsnr agent
    4. Resource type definition for the ASMInst agent
      1.  
        Resource type definition for the ASMInst agent to support systemD
      2.  
        Attribute definition for the ASMInst agent
    5. Resource type definition for the ASMDG agent
      1.  
        Attribute definition for the ASMDG agent
  10. Appendix B. Sample configurations
    1.  
      About the sample configurations for Oracle enterprise agent
    2. Sample single Oracle instance configuration
      1.  
        Sample VCS configuration file for single Oracle instance
    3. Sample multiple Oracle instances (single listener) configuration
      1.  
        Sample VCS configuration file for multiple Oracle instances (single listener)
    4. Sample multiple instance (multiple listeners) configuration
      1.  
        Sample VCS configuration file for multiple Oracle instances (multiple listeners)
    5. Sample Oracle configuration with shared server support
      1.  
        Sample VCS configuration file for Oracle instance configured with shared server support
    6. Sample Oracle ASM configurations
      1. Sample configuration for ASM disks as raw disks
        1.  
          Sample VCS configuration file for ASM-managed Oracle instance
      2. Sample configuration for ASM disks as VxVM volumes
        1.  
          Sample VCS configuration file for ASM disks as VxVM disks
      3. Sample configuration for ASM disks as CVM volumes
        1.  
          Sample VCS configuration file for ASM that uses CVM volumes
    7.  
      Sample configuration of Oracle pluggable database (PDB) resource in main.cf
    8.  
      Sample configuration of migratable Oracle pluggable database (PDB) resource in main.cf
    9.  
      Sample Configuration of Oracle supported by systemD
    10.  
      Sample configuration of ASMInst supported by systemD
  11. Appendix C. Best practices
    1.  
      Best practices for multiple Oracle instance configurations in a VCS environment
  12. Appendix D. Using the SPFILE in a VCS cluster for Oracle
    1.  
      About the Oracle initialization parameter files
    2.  
      Starting an Oracle instance
    3.  
      Using the SPFILE in a VCS cluster
  13. Appendix E. OHASD in a single instance database environment
    1.  
      About OHASD in a single instance database environment
    2.  
      Configuring the Application agent to make OHASD highly available

Configuring the agent to monitor Oracle

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

To configure monitoring for Oracle

  1. Launch the 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:

    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 Storage HA Inputs panel, specify all the ESX/ESXi hosts to which the virtual machines can fail over. Each ESX/ESXi host must be able to access the required shared datastores that contain visible disks. Enter the administrative user account details for each ESX/ESXi host and click Next.

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

    ESX/ESXi hostname or IP address

    Specify the target ESX/ESXi hostname or IP address.

    The virtual machines can fail over on this ESX/ESXi host during vMotion. All the additional ESX/ESXi 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/ESXi host. The user account must have administrator privileges on the specified ESX/ESXi 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/ESXi 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. 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 Diagnostic information 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.