Configuring the Application agent to make OHASD highly available

You can configure the Application agent to ensure the OHASD process is made highly available in the VCS cluster.

To configure the Application agent for the Ohasd process to ensure the service is online

  1. Configure the Application agent

                 Application ohasd_res (
                    StartProgram = "<GRID_HOME>/bin/crsctl start has"
                    StopProgram = "<GRID_HOME>/bin/crsctl stop has"
                    PidFiles @node1 = {
                             "<GRID_HOME>/ohasd/init/node1.pid" }
                    PidFiles @node2 = {
                             "<GRID_HOME>/ohasd/init/node2.pid" }
                    )
    
  2. Set up the resource dependency on the Ohasd daemon if the resource is configured:

    • For databases that are running in oracle restart mode

    • For the ASMInst resource

  3. In the following dependency tree, ohasd resource is configured in a failover service group or parallel service group.

    Run the # $GRID_HOME/bin/srvctl disable has command to disable the automatic startup of ohasd on all the nodes in the VCS cluster.

Figure: shows OHASD resource configured in Parallel service group with the ASMInst resource in the Failover service group

shows OHASD resource configured in Parallel service group with the ASMInst resource in the Failover service group

Figure: shows OHASD resource configured in Failover service group with the ASMInst resource.

shows OHASD resource configured in Failover service group with the ASMInst resource.

Figure: shows the dependency tree of databases that are running in oracle restart mode.

shows the dependency tree of databases that are running in oracle restart mode.