Starting the primary companion as a monitored resource

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

NoteBefore monitoring begins on the primary companion, make sure that there is no need to shut down the primary server for maintenance or any other purpose. Once monitoring begins, the primary companion must be moved 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 restart the server using the steps described here.

To start the primary companion as a resource monitored for fail over:

  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_<servername>.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 start the secondary companion.