10g RAC startup process

Question

Can sombody tell me how the RAC instance will start. I know like CSS is the first process to start and then what happens how everything comes up.
Thanks

Answer 1

Maverick wrote:
thanks for the reply.
The link you have provided is for 11g i think
i Need 10g RAC startup process.
ThanksStopping the Oracle RAC 10g Environment
The first step is to stop the Oracle instance. When the instance (and related services) is down, then bring down the ASM instance. Finally, shut down the node applications (Virtual IP, GSD, TNS Listener, and ONS).
$ export ORACLE_SID=orcl1
$ emctl stop dbconsole
$ srvctl stop instance -d orcl -i orcl1
$ srvctl stop asm -n linux1
$ srvctl stop nodeapps -n linux1
Starting the Oracle RAC 10g Environment
The first step is to start the node applications (Virtual IP, GSD, TNS Listener, and ONS). When the node applications are successfully started, then bring up the ASM instance. Finally, bring up the Oracle instance (and related services) and the Enterprise Manager Database console.
$ export ORACLE_SID=orcl1
$ srvctl start nodeapps -n linux1
$ srvctl start asm -n linux1
$ srvctl start instance -d orcl -i orcl1
$ emctl start dbconsole
Start/Stop All Instances with SRVCTL
Start/stop all the instances and their enabled services. I have included this step just for fun as a way to bring down all instances!
$ srvctl start database -d orcl
$ srvctl stop database -d orcl
reference:http://www.rampant-books.com/art_hunter_rac_start_stop_cluster.htm
refer the links for more informations:
Starting and Stopping Instances and Oracle Real Application Clusters Databases
http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/dbinstmgt.htm#BCEBGHHC
Server Control Utility Reference
http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/srvctladmin.htm
answered by ssolbach
Just a minor comment on the stop nodeapps.
While it is fine to stop the nodeapps on the server, the drawback to this is, that the VIP will not failover if you stop the nodeapps, but will be stopped.
Hence if you only shutdown one server, then you are causing clients to fail to connect to the VIP and having to wait for the TCP/Timeout.
So if you are not going to shut down all the server, but just want to shutdown one node, you should failover the VIP the the other node.
See: Note 749160.1 Vip Does Not Failover When Nodeapps Stopped
So it is sometimes better instead of stopping the nodeapps, to simply shutdown the cluster with crsctl stop crs (which will failover the VIP).
Sebastian
reference:-
Re: RAC Questions