Oracle 11gR2 RAC Cluster service startup and shutdown summary

Introduction: This article was written because one of my students recently set up a RAC cluster in the company, but the sequence and principle of its start-up and shutdown is not particularly clear, I also found in teaching work a lot of students know very little about RAC knowledge, So I am here to the RAC involved in the most commonly used starting and closing sequence and commands listed, because the RAC background resources are many, so the number of commands involved, and finally attached to help manual for temporary use in the work can also be quickly found, If this article can help everyone is I continue to work hard to write the impetus, thank you for my article browsing more valuable comments.

Shutdown process (CRS cluster shutdown, close database)
1. Close the database:
Execute srvctl command with ORACL user
Syntax: srvctl stop database-d dbname [-o immediate]
Function: All instances of dbname can be closed at once
[[email protected] ~]$ srvctl stop database-d racdb-Stop An instance on all nodes
Then check the status:
[Email protected] ~]$ srvctl status database-d racdb
Instance Rac1 is not running on node Rac1
Instance Rac2 is not running on node race
2. Stop have (high availability Services), must be operated as root user
[Email protected] oracle]# Cd/u01/grid/11.2.0/grid/bin
[Email protected] bin]#./crsctl Stop Has-f
[Email protected] bin]#./crsctl Stop Crs-f
This command only shuts down the CRS service for the current node, so it needs to be executed on all nodes of the RAC, as well as boot. has is equivalent to CRS
3. To stop the node Cluster service, you must be the root user:
[Email protected] oracle]# Cd/u01/grid/11.2.0/grid/bin
[[email protected] bin]#./crsctl Stop cluster----Stopping this node Cluster service
[[email protected] bin]#./CRSCTL Stop Cluster-all---Stopping all node services
You can also control which nodes are stopped as follows:
[[email protected] bin]# crsctl stop cluster-n Rac1 RAC2
Crs-2677:stop of ' ora.cssd ' on ' Rac1 ' succeeded
Crs-2677:stop of ' ora.cssd ' on ' Rac2 ' succeeded
。。。。。。。。。。。 Omit log output ..... .....
You can use the above command if you want a command to stop all processes. If the parameter is not specified, it is valid for the current node, if the parameter is specified, it is valid for the related parameter node.
4. Check the cluster process status
[Email protected] bin]# crsctl Check cluster
Verbose output
[Email protected] bin]# Crs_stat-t-V
Check the cluster status of this node only
[[email protected] bin]# CRSCTL Check CRS

Startup process (CRS cluster start-up database)
1. Launch has
Single node startup
[Email protected] ~]# Crsctl start has
[[email protected] ~]# Crsctl start CRS
[[email protected] ~]# CRSCTL Check CRS
Crs-4638:oracle High Availability Services is online
Crs-4537:cluster Ready Services are online
Crs-4529:cluster Synchronization Services is online
Crs-4533:event Manager is online
All nodes Start
[Email protected] bin]# crsctl start cluster-n Rac1 rac2
Crs-4123:oracle High Availability Services have been started.
[Email protected] bin]# crsctl start Cluster-all
[Email protected] ~]# crsctl Check cluster
Crs-4537:cluster Ready Services are online
Crs-4529:cluster Synchronization Services is online
Crs-4533:event Manager is online
This command launches all RAC CRS-related processes in the background
[Email protected] ~]# Crs_stat-t-V
Crs-0184:cannot communicate with the CRS daemon.
Because start has started the CRS process is more slow to start, my machine waited for 5 minutes, before the full boot success will report the above error, need to wait patiently for a period of time after the execution of the following command to see that all CRS-related process services have been started.
[Email protected] ~]# Crs_stat-t-V
Name Type r/ra f/ft Target State Host
----------------------------------------------------------------------
Ora. DATA.DG ora....up.type 0/5 0/online ONLINE Rac1
Ora .... Er.lsnr ora....er.type 0/5 0/online ONLINE Rac1
Ora .... N1.lsnr ora....er.type 0/5 0/0 Online online Rac2
Ora .... N2.lsnr ora....er.type 0/5 0/0 Online online Rac1
Ora .... N3.lsnr ora....er.type 0/5 0/0 Online online Rac1
Ora.asm ora.asm.type 0/5 0/online ONLINE Rac1
ORA.CVU ora.cvu.type 0/5 0/0 Online online Rac1
ORA.GSD ora.gsd.type 0/5 0/offline OFFLINE
Ora....network ora....rk.type 0/5 0/online ONLINE Rac1
ora.oc4j ora.oc4j.type 0/1 0/2 Online online Rac1
Ora.ons ora.ons.type 0/3 0/online ONLINE Rac1
Ora .... SM1.ASM application 0/5 0/0 online online Rac1
Ora .... C1.lsnr application 0/5 0/0 online online Rac1
ORA.RAC1.GSD application 0/5 0/0 OFFLINE OFFLINE
Ora.rac1.ons application 0/3 0/0 online online Rac1
ORA.RAC1.VIP ora....t1.type 0/0 0/0 Online online Rac1
Ora .... SM2.ASM application 0/5 0/0 online online Rac2
Ora .... C2.lsnr application 0/5 0/0 online online Rac2
ORA.RAC2.GSD application 0/5 0/0 OFFLINE OFFLINE
Ora.rac2.ons application 0/3 0/0 online online Rac2
ORA.RAC2.VIP ora....t1.type 0/0 0/0 Online online Rac2
Ora....ry.acfs ora....fs.type 0/5 0/online ONLINE Rac1
ORA.SCAN1.VIP ora....ip.type 0/0 0/0 Online online Rac2
ORA.SCAN2.VIP ora....ip.type 0/0 0/0 Online online Rac1
ORA.SCAN3.VIP ora....ip.type 0/0 0/0 Online online Rac1
Description
English explanation
ORA.GSD is OFFLINE by default ifthere are no 9i database in the cluster.
Ora.oc4j is OFFLINE in 11.2.0.1 as Databaseworkload Management (DBWLM) is unavailable. These can be ignored IN11GR2 RAC.
Chinese explanation
ORA.GSD is a process used in the Cluster service to communicate with a 9i database, which is saved in the current version for backward compatibility, and the status of offline does not affect the normal operation and performance of CRS, we can ignore
ORA.OC4J is a service process that is in effect in 11.2.0.2 or later, and is used for DBWLM resource management, so the following versions of 11.2.0.1 are not used
2. Start the database:
Oracl User Execution Srvctl command:
Syntax: Srvctl start|stop|status database-d dbname [-o immediate]
Function: All instances of dbname can be started at once
[[email protected] ~]$ srvctl start database-d racdb-Start an instance on all nodes
Then check the status:
[Email protected] ~]$ srvctl status database-d racdb
3. Verbose output resource full name and check status
Crsctl Status Resource-t
Crsctl Status Resource
4. Common SRVCTL Commands
Specify an instance on dbname
Srvctl start|stop|status instance-d-I <instance_name>
5. Display all instance configuration and status under RAC
Srvctl Status|config database-d
6. Show app service for all nodes (Vip,gsd,listener,ons)
Srvctl Start|stop|status nodeapps-n<node_name>
7.ASM Process Service Management
Srvctl Start|stop|status|config asm-n [-i <asm_inst_name>] [-o<oracle_home>]
Srvctl Config asm-a
Srvctl Status Asm-a
6. All environmental information can be obtained:
Srvctl getenv database-d [-i<instance_name>]
7. Set the global environment and variables:
Srvctl setenv database-d-T lang=en
8. Delete existing database information in OCR
Srvctl Remove database-d
9. Add an instance of a database to OCR:
Srvctl Add instance-d-i<instance_name>-N
Srvctl Add instance-d-i<instance_name>-N
10. Check the status of the listener
SRVCTL Status Listener
Srvctl Config listener-a
Scan configuration information
Srvctl Config Scan
SCAN Listener status information
Srvctl Status Scan


Summary: The CRSCTL command is a cluster-level command that enables unified start, stop, and other administrative operations on all cluster resources
The SRVCTL command is a service-level command that enables unified start, stop, and other administrative operations on a single service resource


Attached: srvctl command start and stop for more help
[Email protected] ~]# Srvctl start-h


The SRVCTL start command starts, Oracle Clusterware enabled, non-running objects.


Usage:srvctl start database-d <db_unique_name>[-o <start_options>] [-N]
Usage:srvctl start instance-d <db_unique_name>{-n <node_name>[-i <inst_name>] |-I <inst_name_ List>} [-O <start_options>]
Usage:srvctl start service-d <db_unique_name>[-s "<service_name_list>" [-N <node_name>|-i <inst_ Name>] [-O <start_options>]
Usage:srvctl start Nodeapps [-n <node_name>] [-G] [-V]
Usage:srvctl start VIP {-N <node_name>|-i <vip_name>} [-V]
Usage:srvctl start ASM [-n <node_name>] [-O <start_options>]
Usage:srvctl start listener [-l &LT;LSNR_NAME&GT;] [-N <node_name>]
Usage:srvctl start scan [-I <ordinal_number>] [-N <node_name>]
Usage:srvctl start Scan_listener [-n <node_name>] [-I <ordinal_number>]
Usage:srvctl start oc4j [-v]
Usage:srvctl start Home-o <oracle_home>-s <state_file>-n <node_name>
Usage:srvctl start filesystem-d <volume_device>[-n <node_name>]
Usage:srvctl start diskgroup-g <dg_name>[-n "<node_list>"]
Usage:srvctl start GNS [-L &LT;LOG_LEVEL&GT;] [-N <node_name>] [-v]
Usage:srvctl start CVU [-N <node_name>]
For detailed help on the command and object and its options use:
Srvctl-h


[Email protected] ~]# Srvctl stop-h


The SRVCTL Stop command stops, Oracle Clusterware enabled, starting or running objects.


Usage:srvctl stop database-d <db_unique_name>[-o <stop_options>] [-F]
Usage:srvctl Stop instance-d <db_unique_name>{-n <node_name>|-i <inst_name_list>} [-O <stop_opti Ons>] [-F]
Usage:srvctl stop service-d <db_unique_name>[-s "<service_name_list>" [-N <node_name>|-i <inst_ Name>] [F]
Usage:srvctl Stop Nodeapps [-n <node_name>] [-G] [-f] [-r] [-V]
Usage:srvctl Stop VIP {-N <node_name> |-i <vip_name>} [-F] [-r] [-V]
Usage:srvctl stop ASM [-n <node_name>] [-O <stop_options>] [-F]
Usage:srvctl Stop listener [-l &LT;LSNR_NAME&GT;] [-N <node_name>] [-F]
Usage:srvctl Stop Scan [-I <ordinal_number>] [-F]
Usage:srvctl Stop Scan_listener [-I <ordinal_number>] [-F]
Usage:srvctl Stop oc4j [-f] [-V]
Usage:srvctl Stop Home-o <oracle_home>-s <state_file>-n <node_name>[-t <stop_options>] [-F]
Usage:srvctl stop filesystem-d <volume_device>[-n <node_name>] [-F]
Usage:srvctl stop diskgroup-g <dg_name>[-n "<node_list>" [-f]
Usage:srvctl stop GNS [-n <node_name>] [-f] [-V]
Usage:srvctl Stop CVU [-f]
For detailed help on the command and object and its options use:
Srvctl-h

Ext.: http://blog.itpub.net/26686207/viewspace-1604807/

Oracle 11gR2 RAC Cluster service startup and shutdown summary