Bring Up Primary Companion as a Monitored Resource

Follow the instructions in this section to start the primary companion as a service that is monitored by the high availability subsystem.

NoteBefore you begin monitoring the primary companion, make sure you no longer need to shut down the primary server for maintenance or other purposes. Once you begin monitoring the primary companion, you must move it to suspended mode to bring it down. If you are unsure, start the primary server using the startserver script in $SYBASE/$SYBASE_ASE/install, finish configuring the companion, then reboot the server using the steps described here.

To start the primary companion as a resource that is monitoring for failover:

  1. Stop the HACMP services on the primary node.

  2. Check /tmp/hacmp.out to make sure the node_down event completed, then restart the HACMP services either by using SMIT or by executing this command as “root” at the command line:

    /usr/sbin/cluster/etc/rc.cluster -boot '-N' '-b'  '-i'
    

    This automatically executes the RUNHA_<server_name>.sh monitor script, which brings up the primary companion and monitors it during crash or hang situations.

    Repeat this process on the secondary node to bring up the secondary companion.