Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 
 

Oracle RAC Command Line Management

Oracle Database Tips by Donald Burleson

crs_stop

It would seem fairly obvious that crs_stop is exactly the opposite of crs_start .  In fact, all of the options to crs_stop are identical to those of crs_start.

 

Please be aware that crs_start and crs_stop are precision tools; that is, they are used to start and stop a single resource in most cases.  Usually using srvctl is the better option when starting and stopping resources.

crs_register

The crs_register utility can take profiles created with crs_stat -p or with crs_profile and register a resource with the cluster.

 

Profiles should be in the CRS_HOME/crs/public directory.  The filename must be the name of the resource with an extension of .cap.  For example, ora.racnode2.vip would be:  CRS_HOME/crs/public/ora.racnode2.vip.cap.

 

Example of profile generation:

 

$ crs_stat -p ora.racnode2.vip >

    $ORA_CRS_HOME/crs/public/ora.racnode2.vip.cap

$ cat $ORA_CRS_HOME/crs/public/ora.racnode2.vip.cap

NAME=ora.racnode2.vip

TYPE=application

ACTION_SCRIPT=/u01/app/oracle/product/11.1.0/crs/bin/racgwrap

ACTIVE_PLACEMENT=1

AUTO_START=1

CHECK_INTERVAL=15

DESCRIPTION=CRS application for VIP on a node

FAILOVER_DELAY=0

FAILURE_INTERVAL=0

FAILURE_THRESHOLD=0

HOSTING_MEMBERS=racnode2

OPTIONAL_RESOURCES=

PLACEMENT=favored

REQUIRED_RESOURCES=

RESTART_ATTEMPTS=0

SCRIPT_TIMEOUT=60

START_TIMEOUT=0

STOP_TIMEOUT=0

UPTIME_THRESHOLD=7d

USR_ORA_ALERT_NAME=

USR_ORA_CHECK_TIMEOUT=0

USR_ORA_CONNECT_STR=/ as sysdba

USR_ORA_DEBUG=0

USR_ORA_DISCONNECT=false

USR_ORA_FLAGS=

USR_ORA_IF=eth0

USR_ORA_INST_NOT_SHUTDOWN=

USR_ORA_LANG=

USR_ORA_NETMASK=255.255.255.0

USR_ORA_OPEN_MODE=

USR_ORA_OPI=false

USR_ORA_PFILE=

USR_ORA_PRECONNECT=none

USR_ORA_SRV=

USR_ORA_START_TIMEOUT=0

USR_ORA_STOP_MODE=immediate

USR_ORA_STOP_TIMEOUT=0

USR_ORA_VIP=192.168.1.125

 

The simplest invocation of crs_register basically involves providing the resource name.  Optionally, a directory can be provided where the .cap files will reside if they are not in the default location.  For example:

 

$ crs_register ora.racnode2.vip -dir /u01/app/oracle/caps

 

A default registration would look like this:

 

$ crs_register ora.racnode2.vip

 

As long as a .cap file is present for that resource in the public location, it will become registered.

crs_unregister

The crs_unregister command simply unregisters a resource from the cluster.

 

Tip:  It is a good idea to save the profile or a resource before playing with this command!

 

To unregister a resource, run crs_unregister  followed by the name of the resource.  For example:

 

$ crs_unregister ora.racnode2.vip

srvctl

When it comes to RAC command line management, srvctls the main attraction.  This tool allows reconfiguration, addition, deletion, starting, stopping, and anything else involving management of RAC resources registered (or not registered) with the cluster.

 

Using this tool, it is possible to disable a database, or cause the system not to come online automatically, start and stop ASM, listeners, nodeapps, instances, and more.

 

To make all of this possible, there are a huge array of commands and options associated with srvctl.  Thankfully, there is also help at every turn, with the -h option being available with every command or subcommand to show proper syntax.  For instance, if someone is curious about commands to stop an Oracle instance:

 

$ srvctl

Usage: srvctl <command> <object> [<options>]

    command: enable|disable|start|stop|relocate|status|add|remove|modify|getenv|setenv|unsetenv|config

    objects: database|instance|service|nodeapps|asm|listener

 

For detailed help on each command and object and its options use:

 

    srvctl <command> <object> -h

 

$ srvctl stop instance -h

Usage: srvctl stop instance -d <name> -i "<inst_name_list>" [-o <stop_options>]

    -d <name>           Unique name for the database

    -i "<inst,...>"     Comma separated instance names

    -o <stop_options>   Options to shutdown command (e.g. normal, transactional, immediate, or abort)

    -h                  Print usage

 

As this example shows, srvctl commands incorporate a main command, an object, and available options.  This help text has shown that to stop an instance, the stop command, instance object, and -d and -i options will do the work:

 

$ srvctl stop instance -d racdb -i racdb1

 

Oracle uses the information registered within clusterware to know which node to use for the specified command.

 
   
Oracle Grid and Real Application Clusters

See working examples of Oracle Grid and RAC in the book Oracle Grid and Real Application Clusters.

Order directly from Rampant and save 30%. 
 


 

 

��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational