Recovering Resources

If a resource fails to start, do the following to recover it:1. Run the following command to clear the status of the resource and try to start

the resource again: # crm resource cleanup <resource name>

2. Check /var/log/message to find the cause of the failure.3. Check the ping-internal resource. Make sure all the IP addresses configured in

ping-internal can be reached with the ping command.4. Check the ping-external resource. Make sure all the IP addresses configured in

ping-external can be reached with the ping command.

Recovering Volume Group Resources

If vg-oracle or vg-global fails to start, do the following to recover them:

1. Perform the operations described in Section 6.6.3.2. Make sure that raw disk devices, for example, /dev/emcpowera, are still

available.3. Make sure the clvm and dlm resources are normal. If not, restart these

resources.4. Make sure the latest OS patches are installed

6.6.5 Recovering File System Resources

If file system resources such as fs-emadb and fs-backup fail to start, do the following to recover them:

1. Perform the operations described in Section 6.6.3.2. Make sure volume group resources vg-oracle and vg-global are normal. If not,

perform the operations described in Section 6.6.4.3. Make sure the mount points exist.4. Run the following command as the root user to check the file system:

# fsck <device name>

Make sure the file system is normal and clean.

Stopping or Restarting Pacemaker

Do the following to stop or then restart Pacemaker and all the resources it manages:1. Stop Multi Activation AS. For details, see Section 4.1.2. Stop Oracle Data Guard. For details, see Section 6.3.3. Run the following command as the root user to stop Pacemaker:

# rcopenais stop

4. Or run the following command as the root user to restart Pacemaker: # rcopenais restart