I had an Oracle database and asked someone to kill all the users connected to Oracle. They misunderstood and issued the Unix command killall. Well this killed the listener, ASM, DB, and many other things. So the following instructions were what I used to get everything back up and running.
From Burleson Consulting:http://www.dba-oracle.com/t_ora_29701_unable_to_connect_to_cluster.htm
ORA-29701: Unable to connect to Cluster Manager Tips
Oracle Tips by Burleson Consulting
November 5, 2012
Question: What causes
the ORA-29701 error below? Can you
explain how to connect to the cluster manager properly?
ORA-29701: Unable to connect to Cluster Manager.
Answer: The oerr
utility shows this for the ORA-29701 error:
ORA-29701: unable to
connect to Cluster Manager
Cause: Connect to CM failed or timed out.
Action: Verify 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 errors.
Osama Mustafa notes that the ORA-29701 happens when the cssd
daemon is not running and he lists his solution to the ORA-29701 error:
The reason is Oracle cssd daemon process was not running.
As Root User :
Step 1: Go to the /etc folder
Step 2: 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
# ./localconfig delete
Stopping CSSD
Failure in CSS initialization opening OCR.
Shutdown has begun. The daemons should exit soon.
Step 4: Execute the following command
# ./localconfig add
Successfully accumulated necessary OCR keys.
Creating OCR keys for user root, privgrp 'system'
Operation Successful
Configuration for local css has been initialized.
Adding to inittab
Startup will be queued to init within 30 seconds
Checking the status of new oracle init process..
Expecting the CRS daemons to be up within 600 seconds
CSS is active on these nodes
nodelist
CSS is active on all nodes
Oracle CSS service is installed and running under init(1M)
Step 5: Start the ASM instance now.
===========================================================
From Whitehorses by Jos Van Dan Oord: http://blog.whitehorses.nl/2010/02/16/three-ways-to-startup-an-asm-instance-on-a-server/
Three ways to startup an ASM instance
Before 11gR2 there was only one way to startup an ASM
instance [SQLPLUS].
In 11gR2 Oracle has added a startup/shutdown functionality in the ASMCMD line interface
and introduced a new GUI ASMCA.
The GUI willl detect by startup if there is an ASM instance
operational or not. If not then it prompt to start an ASM instance.
The Three methods:
1. SQLPLUS with sysasm attribute
sqlplus / as asmdba
startup
2. ASMCMD
asmcmd> startup
3. ASMCA
=============================================================
Start the listener:
lsnrctl
LSNRCTL> start
No comments:
Post a Comment