Verify the RAC Cluster & Database Configuration

Verify the RAC Cluster & Database Configuration Status of all instances and services

$ srvctl status database -d prod Instance prod1 is running on node rac1 Instance prod2 is running on node rac2

Status of a single instance

$ srvctl status instance -d prod -i prod1 Instance prod1 is running on node rac1

Status of node applications on a particular node

$ srvctl status nodeapps -n rac1 VIP is running on node: rac1 GSD is running on node: rac1 Listener is running on node: rac1 ONS daemon is running on node: rac1

Status of an ASM instance

$ srvctl status asm -n rac1 ASM instance +ASM1 is running on node rac1

List all configured databases

$ srvctl config database

Display configuration for RAC database

$ srvctl config database -d prod rac1 prod1 /u01/app/oracle/product/10.2.0/db_1 rac2 prod2 /u01/app/oracle/product/10.2.0/db_1

Display all services for the specified cluster database

$ srvctl config service -d prod orcltest PREF: prod2 prod1 AVAIL:

Display the configuration for node applications - (VIP, GSD, ONS, Listener)

$ srvctl config nodeapps -n rac1 -a -g -s -l

VIP exists.: /rac1-vip/192.168.1.200/255.255.255.0/eth0:eth1 GSD exists.ONS daemon exists. Listener exists.

Display the configuration for the ASM instance(s)

$ srvctl config asm -n rac1 +ASM1 /u01/app/oracle/product/10.2.0/db_1

Check the status of application resources.

rac1-> crs_stat -t

Check the status of Oracle Clusterware.

rac1-> crsctl check crs CSS appears healthy CRS appears healthy EVM appears healthy

rac2-> crsctl check crs CSS appears healthy CRS appears healthy EVM appears healthy Execute crsctl on the command line to check out all the available options.

List the RAC instances.

SQL> select instance_name, host_name, archiver, thread#, status from gv$instance;

Check connectivity.

Verify that you are able to connect to the instances and service on each node.

sqlplus system@devdb1 sqlplus system@devdb2 sqlplus system@devdb

Start and Stop Oracle 10g RAC application Resources

Stop application resources First Stop Enterprise Manager Database console ->Stop the Oracle Instance -> Down the ASM Instance -> Down the node application (Virtual IP, GSD, TNS Listener, and ONS).

$ emctl stop dbconsole$ srvctl stop instance -d prod -i prod1 $ srvctl stop instance d prod i prod2 $ srvctl stop asm -n rac1 $ srvctl stop asm n rac2 $ srvctl stop nodeapps -n rac1 $srvctl stop nodeapps n rac2

Start application resources First start the node applications (Virtual IP, GSD, TNS Listener, and ONS) -> Start ASM instance >Start the Oracle instance (and related services) -> Start Enterprise Manager Database console.

$ srvctl start nodeapps -n rac1 $ srvctl start nodeapps -n rac2 $ srvctl start asm -n rac1 $ srvctl start asm -n rac2 $ srvctl start instance -d prod -i prod1

$ srvctl start instance -d prod -i prod2 $ emctl start dbconsole

Start and Stop CRS

TWO MAIN WAYS Option #1: /etc/init.d/init.crs # Supported options: # init.crs start manual startup of the CRS stack # init.crs stop shuts down the CRS stack # init.crs disable prevents CRS stack from starting at boot time # init.crs enable allows CRS stack to start at boot time init q Tells the init command to re-examine the /etc/inittab file Contents of /etc/inittab: h1:2:respawn:/etc/init.evmd run >/dev/null 2>&1 </dev/null h2:2:respawn:/etc/init.cssd fatal >/dev/null 2>&1 </dev/null h3:2:respawn:/etc/init.crsd run >/dev/null 2>&1 </dev/null Option #2: $ORA_CRS_HOME/bin/crsctl stop crs crsctl enable crs enables startup for all CRS daemons crsctl disable crs disables startup for all CRS daemons crsctl start crs starts all CRS daemons. crsctl stop crs stops all CRS daemons. Stops CRS resources in case of cluster. crs_start and crs_stop New feature introduced in 10g R2 The crs_start and crs_stop command can be used to start and stop CRS managed resources $ crs_start resource-name -all (all resource) $ crs_stop resource-name -all (all resource)

crs_relocate change where resource is active $ORA_CRS_HOME/bin/crsctl stop crs crsctl enable crs enables startup for all CRS daemons crsctl disable crs disables startup for all CRS daemons crsctl start crs starts all CRS daemons. crsctl stop crs stops all CRS daemons. Stops CRS resources in case of cluster.

The disabling works! dont forget the change the autostart back when problem gets resolved. repeat steps 2)-4) Adds-on: if you want to stop the autostart for css daemon either, then do this: /etc/init.d/init.cssd stop If you want to stop it from autostarting after bootup; [root@vanpgprodb06 rc3.d]# /etc/init.d/init.crs disable Automatic startup disabled for system boot. As Root Can you stop/start crs on this node? # cd $CRS_HOME/bin # ./crsctl stop crs # ./crsctl start crs