Question: What causes the ORA-29701 error
below? Can you explain how to connect to the cluster manager
ORA-29701: Unable to connect to Cluster
Answer: The oerr
utility shows this for the ORA-29701 error:
ORA-29701: unable to connect to
Cause: Connect to CM
failed or timed out.
that the CM was started. If the CM was not started, start it
and then retry the database startup. If the CM died or is
not responding, check the Oracle and CM trace files for
As we see, the fix for the ORA-29701 error is to start
the connection manager (CM).
If you have the available downtime, try bouncing the
whole RAC cluster, this will often fix the ORA-29701 error.
The first step is to check the CM logs for errors and
ensure that the CM is running.
cm| grep -i grep|more
44456 1 0 15:29:12 pts/3 0:00 /u01/oracle/product/8.0.5/bin/cmadmin
oracle 46508 1 0 15:29:14 pts/3 0:00 /u01/oracle/product/8.0.5/bin/cmgw
If the CM is not running, start the CM:
$ ./cmctl status
See my notes on
CM starting and testing.
Also see these
notes on troubleshooting the ORA-29701 error:
Also see my notes on
CRS startup issues.
Osama Mustafa notes that the ORA-29701 can also happen when the
cssd daemon is not running and he lists his solution to the
The reason is Oracle cssd daemon process was not running.
As Root User :
Go to the /etc folder
Execute the following command.
# init.cssd start
startup will be queued to init within 30 seconds
Step 3: Wait for 2
minutes and execute the following commands
# cd $ORACLE_HOME/bin
Failure in CSS initialization opening OCR.
Shutdown has begun. The daemons should exit soon.
Execute the following command
# ./localconfig add
Successfully accumulated necessary OCR keys.
keys for user root, privgrp 'system'
Configuration for local css has been initialized.
Startup will be queued to init within 30
Checking the status of new oracle init process..
Expecting the CRS daemons to be up within 600 seconds
is active on these nodes
active on all nodes
Oracle CSS service is installed and
running under init(1M)
Start the ASM instance now.