It would seem fairly obvious that
is exactly the opposite of
. In fact, all of the
crs_stop are identical to those of
Please be aware that
are precision tools; that is, they are used to start and stop a single
resource in most cases.
is the better option when starting and stopping resources.
utility can take profiles created with
-p or with
and register a resource with the cluster.
Profiles should be in the
directory. The filename
must be the name of the resource with an extension of .cap.
Example of profile generation:
$ crs_stat -p ora.racnode2.vip >
$ cat $ORA_CRS_HOME/crs/public/ora.racnode2.vip.cap
DESCRIPTION=CRS application for VIP on a node
USR_ORA_CONNECT_STR=/ as sysdba
The simplest invocation of
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.
$ crs_register ora.racnode2.vip -dir
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.
command simply unregisters a resource from the cluster.
It is a good idea to save the profile or a resource before
playing with this command!
To unregister a resource, run
followed by the name of the
resource. For example:
$ crs_unregister ora.racnode2.vip
When it comes to RAC command line management,
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
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:
Usage: srvctl <command> <object> [<options>]
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>"
Unique name for the database
Comma separated instance names
Options to shutdown command (e.g. normal, transactional,
immediate, or abort)
As this example shows,
incorporate a main command, an object, and available options.
This help text has shown that to stop an instance, the
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.