Oracle Database Oracle Clusterware Installation Guide for HP-UX

Performing Cluster Diagnostics During Oracle Clusterware Installations
Cause: Oracle Clusterware is either not installed, or the Oracle Clusterware
services are not up and running.
Action: Install Oracle Clusterware, or review the status of your Oracle
Clusterware. Consider restarting the nodes, as doing so may resolve the problem.
Node nodename is unreachable
Cause: Unavailable IP host
Action: Attempt the following:
1. Run the shell command ifconfig -a. Compare the output of this command
with the contents of the /etc/hosts file to ensure that the node IP is listed.
2. Run the shell command nslookup to see if the host is reachable.
3. As the oracle user, attempt to connect to the node with ssh or rsh. If you
are prompted for a password, then user equivalence is not set up properly.
Review the section "Configuring SSH or RCP on All Cluster Nodes" on
page 2-20.
PROT-8: Failed to import data from specified file to the cluster registry
Cause: Insufficient space in an existing Oracle Cluster Registry device partition,
which causes a migration failure while running rootupgrade. To confirm, look
for the error "utopen:12:Not enough space in the backing store" in the log file
$ORA_CRS_HOME/log/hostname/client/ocrconfig_pid.log.
Action: Identify a storage device that has 280 MB or more available space. Locate
the existing raw device name from /var/opt/oracle/srvConfig.loc, and
copy the contents of this raw device to the new device using the command dd.
Time stamp is in the future
Cause: One or more nodes has a different clock time than the local node. If this is
the case, then you may see output similar to the following:
time stamp 2005-04-04 14:49:49 is 106 s in the future
Action: Ensure that all member nodes of the cluster have the same clock time.
A.3 Performing Cluster Diagnostics During Oracle Clusterware
Installations
If Oracle Universal Installer (OUI) does not display the Node Selection page, then
perform clusterware diagnostics by running the olsnodes -v command from the
binary directory in your Oracle Clusterware home (CRS_home/bin on Linux and
UNIX-based systems, and CRS_home\BIN on Windows-based systems) and analyzing
its output. Refer to your clusterware documentation if the detailed output indicates
that your clusterware is not running.
In addition, use the following command syntax to check the integrity of the Cluster
Manager:
cluvfy comp clumgr -n node_list -verbose
In the preceding syntax example, the variable node_list is the list of nodes in your
cluster, separated by commas.
Troubleshooting the Oracle Clusterware Installation Process A-3