srvctlSD.txt
2005-03-26 Bikle
-----------------

The file contains a simple screen dump of some srvctl commands.


oracle@v490rep5 $ bash
bash-2.05$ srvctl -h
Usage: srvctl [-V]
Usage: srvctl add database -d <name> -o <oracle_home> [-m <domain_name>] [-p <spfile>] [-A <name|ip>/netmask] [-r {PRIMARY | PHYSICAL_STANDBY | LOGICAL_STANDBY}] [-s <start_options>] [-n <db_name>]
Usage: srvctl add instance -d <name> -i <inst_name> -n <node_name>
Usage: srvctl add service -d <name> -s <service_name> -r "<preferred_list>" [-a "<available_list>"] [-P <TAF_policy>]
Usage: srvctl add service -d <name> -s <service_name> -u {-r "<new_pref_inst>" | -a "<new_avail_inst>"}
Usage: srvctl add nodeapps -n <node_name> -o <oracle_home> -A <name|ip>/netmask[/if1[|if2|...]]
Usage: srvctl add asm -n <node_name> -i <asm_inst_name> -o <oracle_home> [-p <spfile>]
Usage: srvctl config database
Usage: srvctl config database -d <name> [-a] [-t]
Usage: srvctl config service -d <name> [-s <service_name>] [-a] [-S <level>]
Usage: srvctl config nodeapps -n <node_name> [-a] [-g] [-o] [-s] [-l]
Usage: srvctl config asm -n <node_name>
Usage: srvctl disable database -d <name>
Usage: srvctl disable instance -d <name> -i "<inst_name_list>"
Usage: srvctl disable service -d <name> -s "<service_name_list>" [-i <inst_name>]
Usage: srvctl disable asm -n <node_name> [-i <inst_name>]
Usage: srvctl enable database -d <name>
Usage: srvctl enable instance -d <name> -i "<inst_name_list>"
Usage: srvctl enable service -d <name> -s "<service_name_list>" [-i <inst_name>]
Usage: srvctl enable asm -n <node_name> [-i <inst_name>]
Usage: srvctl getenv database -d <name> [-t "<name_list>"]
Usage: srvctl getenv instance -d <name> -i <inst_name> [-t "<name_list>"]
Usage: srvctl getenv service -d <name> -s <service_name> [-t "<name_list>"]
Usage: srvctl getenv nodeapps -n <node_name> [-t "<name_list>"]
Usage: srvctl modify database -d <name> [-n <db_name] [-o <ohome>] [-m <domain>] [-p <spfile>]  [-r {PRIMARY | PHYSICAL_STANDBY | LOGICAL_STANDBY}] [-s <start_options>]
Usage: srvctl modify instance -d <name> -i <inst_name> -n <node_name>
Usage: srvctl modify instance -d <name> -i <inst_name> {-s <asm_inst_name> | -r}
Usage: srvctl modify service -d <db_name> -s <service_name> -i <old_inst_name> -t <new_inst_name> [-f]
Usage: srvctl modify service -d <db_name> -s <service_name> -i <avail_inst_name> -r [-f]
Usage: srvctl modify asm -n <node_name> -i <asm_inst_name> -p <spfile>
Usage: srvctl relocate service -d <name> -s <service_name> -i <old_inst_name> -t <new_inst_name> [-f]
Usage: srvctl remove database -d <name> [-f]
Usage: srvctl remove instance -d <name> -i <inst_name> [-f]
Usage: srvctl remove service -d <name> -s <service_name> [-i <inst_name>] [-f]
Usage: srvctl remove nodeapps -n "<node_name_list>" [-f]
Usage: srvctl remove asm -n <node_name> [-i <asm_inst_name>] [-f]
Usage: srvctl setenv database -d <name> {-t <name>=<val>[,<name>=<val>,...] | -T <name>=<val>}
Usage: srvctl setenv instance -d <name> [-i <inst_name>] {-t "<name>=<val>[,<name>=<val>,...]" | -T "<name>=<val>"}
Usage: srvctl setenv service -d <name> [-s <service_name>] {-t "<name>=<val>[,<name>=<val>,...]" | -T "<name>=<val>"}
Usage: srvctl setenv nodeapps -n <node_name> {-t "<name>=<val>[,<name>=<val>,...]" | -T "<name>=<val>"}
Usage: srvctl start database -d <name> [-o <start_options>] [-c <connect_str> | -q]
Usage: srvctl start instance -d <name> -i "<inst_name_list>" [-o <start_options>] [-c <connect_str> | -q]
Usage: srvctl start service -d <name> [-s "<service_name_list>" [-i <inst_name>]] [-o <start_options>] [-c <connect_str> | -q]
Usage: srvctl start nodeapps -n <node_name>
Usage: srvctl start asm -n <node_name> [-i <asm_inst_name>] [-o <start_options>]
Usage: srvctl status database -d <name> [-f] [-v] [-S <level>]
Usage: srvctl status instance -d <name> -i "<inst_name_list>" [-f] [-v] [-S <level>]
Usage: srvctl status service -d <name> -s "<service_name_list>" [-f] [-v] [-S <level>]
Usage: srvctl status nodeapps -n <node_name>
Usage: srvctl status asm -n <node_name>
Usage: srvctl stop database -d <name> [-o <stop_options>] [-c <connect_str> | -q]
Usage: srvctl stop instance -d <name> -i "<inst_name_list>" [-o <stop_options>] [-c <connect_str> | -q]
Usage: srvctl stop service -d <name> [-s "<service_name_list>" [-i <inst_name>]] [-c <connect_str> | -q] [-f]
Usage: srvctl stop nodeapps -n <node_name>
Usage: srvctl stop asm -n <node_name> [-i <asm_inst_name>] [-o <start_options>]
Usage: srvctl unsetenv database -d <name> -t "<name_list>"
Usage: srvctl unsetenv instance -d <name> [-i <inst_name>] -t "<name_list>"
Usage: srvctl unsetenv service -d <name> [-s <service_name>] -t "<name_list>"
Usage: srvctl unsetenv nodeapps -n <node_name> -t "<name_list>"
bash-2.05$



When I first saw the above syntax, I asked, "Why do I need to specify
the name of the database with the -d option?"

Answer: A cluster may house more than one RAC database; srvctl is an
interface to the cluster.

More screen dumps:

bash-2.05$ srvctl status database -d prov
Instance prov1 is running on node v490rep5
Instance prov2 is running on node v490rep6
Instance prov3 is running on node v490rep7
bash-2.05$               

Notice that it is context sensitive; below I try to specify
an instance when I'm trying to check the status of the db:

bash-2.05$ srvctl status database -d prov -i prov2
PRKO-2002 : Invalid command line option: -i

If I want to check the status of an instance,
I need to specify which db it is in:

bash-2.05$ srvctl status instance -d prov -i prov2
Instance prov2 is running on node v490rep6
bash-2.05$ 


Demo of bouncing an instance.  Notice I can
do it from any node in the cluster:

bash-2.05$ hostname
v490rep5
bash-2.05$ srvctl stop instance -d prov -i prov2
bash-2.05$ ssh v490rep7
Last login: Sat Mar 26 15:22:43 2005 from v490rep5
Sun Microsystems Inc.   SunOS 5.9       Generic May 2002 (autopatch)
oracle@v490rep7 $ 
oracle@v490rep7 $ srvctl start instance -d prov -i prov2
oracle@v490rep7 $ srvctl status database -d prov
Instance prov1 is running on node v490rep5
Instance prov2 is running on node v490rep6
Instance prov3 is running on node v490rep7
oracle@v490rep7 $ 

If I want to query the status of a service,
I need to know the name of the service.
I cannot use srvctl to obtain a list of services:


oracle@v490rep7 $ srvctl status service -d prov
PRKO-2001 : Invalid command line syntax
oracle@v490rep7 $ srvctl status service -d prov -s oltp
Service oltp is running on instance(s) prov1, prov3
oracle@v490rep7 $