Troubleshooting Oracle Clusterware common startup failures

郑全

As an Oracle DBA in a non-cluster environment, your responsibilities limited to manage, troubleshoot and diagnose problems that are pertaining to the database technologies. In contrast, you will have an additional responsibility of managing Clusterware and troubleshooting its problems in a cluster environment. The purpose of this article is to help you understanding the basics about Clusterware startup sequence and troubleshoot most common Clusterware startup failures. Additionally, this article also wills focus on some of the useful tools, utilities that are handy identifying the root cause of Clusterware related problems.
In my perspective and personal experience, the following is some of the challenges most DBAs in their cluster environment confront:

• Node eviction
• Cluster becoming unhealthy
• Unable to start cluster and some of the Clusterware components
  

Clusterware startup sequenceIt’s worthwhile understanding how things get started or stopped while managing and troubleshooting a system. In this segment, we will closely look at how an Oracle Clusterware stack components are get started, and in which sequence they come up on a node reboot or manual cluster startup. This understanding will greatly help addressing most cluster stack common start-up failures and gives you a glance where to start the investigation in case any cluster component doesn’t start.
The diagram below depicts Oracle Cluster stack (components) startup sequence at various levels:

登录/注册后可看大图