Oracle® Clusterware Installation Guide 11g Release 1 (11.1) for Microsoft Windows Part Number B28250-03 |
|
|
View PDF |
This appendix provides troubleshooting information for installing Oracle Clusterware. The topics in this appendix are:
Oracle Clusterware Install Actions Log Errors and Causes
See Also:
Oracle Real Application Clusters Administration and Deployment Guide for additional information about Oracle Clusterware and Oracle RAC configuration and deployment.The following is a list of examples of types of errors that can occur during installation:
Run the command ipconfig /all
. Compare the output of this command with the contents of the C:\WINNT\system32\drivers\etc\hosts file to ensure that the node IP is listed.
Run the command nslookup
to see if the host is reachable.
time stamp 2005-04-04 14:49:49 is 106 s in the future
The following is a list of potential errors in the installActions.log:
PRIF-10: failed to initialize the cluster registry
Configuration assistant "Oracle Private Interconnect Configuration Assistant" failed
Step 4: Starting up Oracle Clusterware stack on all nodes
node1 service OracleCSService in improper STOPPED state, err(997)
node2 service OracleCSService in improper STOPPED state, err(997)
Step 4: Starting up Oracle Clusterware stack on all nodes
node1 service OracleCSService in improper STOPPED state, err(0)
node2 service OracleCSService in improper STOPPED state, err(997)
Step 4: Starting up Oracle Clusterware stack on all nodes
oracletest1 failed to startup service OracleEVMService, err(1053)
Step 1: checking status of Oracle Clusterware cluster
Step 2: configuring OCR repository
ignoring upgrade failure of ocr(-1073740972)
failed to configure Oracle Cluster Registry with CLSCFG, ret -1073740972
Each of these error messages can be caused by one of the following issues:
If you are using OCFS for your OCR and Voting disk partitions, then:
Leave the OUI window in place.
Restart the second node, and any additional nodes.
Retry the assistants
If you think the cause may be a timing issue, then:
Leave the OUI window in place.
Start the OracleCSService manually on all nodes. You may also need to start the OracleObjectService manually.
Retry the assistants
If this is true, then:
For Oracle RAC on Windows 2003, you must issue the following commands on all nodes:
diskpart automount enable
If you are already failing at the configuration assistants and this has not yet been run on all nodes in the cluster, you will need to clean up your Oracle Clusterware install, issue this command on all nodes, reboot all nodes, and start the Oracle Clusterware install again.
Periods (".") are not permitted in node names. Instead, use an underscore character ("_") or a hyphen. ("-").
To resolve a failed installation, remove traces of the Oracle installation, and reinstall with a permitted node name.