Compaq Parallel Database Cluster Model PDC/O2000 for Oracle8i and Windows 2000 Administrator Guide

7-6 Compaq Parallel Database Cluster Model PDC/02000 for Oracle8i and Windows 2000 Administrator Guide
Compaq Confidential – Need to Know Required
Writer: John Blackburn Project: Compaq Parallel Database Cluster Model PDC/02000 for Oracle8i and Windows 2000 Administrator Guide Comments:
Part Number: 225082-002 File Name: h-ch7 Troubleshooting.doc Last Saved On: 6/13/01 3:59 PM
■
Determine whether or not you need to deinstall a partial OSD
installation. An incomplete installation can result in a partial installation
of the OSDs on the cluster. If this occurs, you must clean up after the
partial installation (by removing it) before you can successfully run the
OUI again. An incomplete OSD installation could result for various
reasons, for example:
G A cable is no longer seated tightly into its connector
G The node from which you are running the OUI cannot communicate
with all other nodes in the cluster
G The user running the OUI does not have administrator privileges on
all cluster nodes
Refer to “Deinstalling a Partial OSD Installation” in Chapter 6, “Cluster
Management,” for information about how to remove a partial OSD
installation.
Unable to Start OracleCMService
■ Verify that the cluster interconnect is properly configured.
■ Make sure the OSDs have been properly installed on the nodes by
running the OUI on the cluster’s primary node. Click Installed
Products and verify that an entry for the OSDs exists.
■ Verify that the OracleCMService has properly started by checking its
error log. The default location for the error log is
C:\compaq\ops\cmsvr.log. If not found in the default location, look in
the same directory in which the OSD modules were installed.
■ Verify that the Node Manager Service, OracleNMService, is running. If
not, see the error logs in C:\compaq\ops\nm.log. If OracleNMService is
running, check the CM Server logs in C:\compaq\ops\cmsrvr.log.
Attempt to start the OracleCMService again.
■ Check the event logs for errors. Be sure to check both the System and
Application logs.