available : enable/disable/start/stop/relocate/status/ add/remove/modify/getenv/setenv/unsetenv/config
avaliable : database/instance/service/nodeapps/vip_range
show help: srvctl -h
2. Examples:
2.1 srvctl config
Available options: database|service|nodeapps|asm
Usage for backward compatibility
srvctl config: Display database name
srvctl config -V : Display the version of srvctl
# display the database info on the specfied node srvctl config -p orcl -n rac1 :
Full usage:
# list all registered instance of the database srvctl config database -d orcl example output:
rac1 orcl1 /orabase/product/10.1.0/db_1 rac2 orcl2 /orabase/product/10.1.0/db_1
# show additional attributes srvctl config database -d orcl -a example output:
DB_NAME: orcl ORACLE_HOME: /orabase/product/10.1.0/db_1 SPFILE: /oradata/orcl/spfileorcl.ora DOMAIN: null DB_ROLE: null START_OPTIONS: null
# show tns entries srvctl config database -d orcl -t
Example client-side TNS entry for service orcltest:
orcltest = (description= (address=(protocol=tcp)(host=db_vip)(port=dedicated_port)) (connect_data= (service_name=orcltest) (failover_mode= (type=select) (method=basic) ) ) )
# Display help srvctl config service -h
# Display service's information srvctl config service -d orcl -s
# display help srvctl config nodeapps -h
# display node's information srvctl config nodeapps -n rac1
example output: rac1 orcl1 /orabase/product/10.1.0/db_1
# display VIP configuration srvctl config nodeapps -n rac1 -a
# display GSD configuration srvctl config nodeapps -n rac1 -g
# display OSD configuration srvctl config nodeapps -n rac1 -s
# display Listener configuration srvctl config nodeapps -n rac1 -l
2.2 srvctl status
Available options: database|instance|service|nodeapps|asm
# Display help for database level srvctl status database -h
# Display instance's running status on each node srvctl status database -d orcl
example output: Instance orcl1 is(not) running on node rac1 Instance orcl2 is(not) running on node rac2
# include disabled applications srvctl status database -d orcl -f
# verbos output srvctl status database -d orcl -v
# Additional information for EM Console srvctl status database -d orcl -S EM_AGENT_DEBUG
# Additional information for EM Console srvctl status database -d orcl -i orcl1 -S EM_AGENT_DEBUG
# Display help for instance level srvctl status instance -h
# display appointed instance's running status srvctl status instance -d orcl -i orcl1
# Display help for node level srvctl status nodeapps -h
# Display all app's status on the node xxx srvctl status nodeapps -n
Not finished, Continue...
2.3 srvctl start
I think maybe it's one of the most frequently used commands as well as 'srvctl stop'.
Available options: database|instance|service|nodeapps|asm
# Start database srvctl start database -d orcl -o nomount srvctl start database -d orcl -o mount srvctl start database -d orcl -o open
# Grammar for start instance srvctl start instance -d [db_name] -i [instance_name] -o [start_option] -c [connect_str] -q
# Start all instances on the all nodes srvctl start instance -d orcl -i orcl1,orcl2,...
# Start ASM instance srvctl start ASM -n [node_name] -i asm1 -o open
# Start all apps in one node srvctl start nodeapps -n [node_name]
2.4 srvctl stop
I think maybe it's also one of the most frequently used commands as well as 'srvctl start'.
Available options: database|instance|service|nodeapps|asm
# Stop database srvctl stop database -d orcl -o normal srvctl stop database -d orcl -o immediate srvctl stop database -d orcl -o abort
# Grammar for stop instance srvctl stop instance -d [db_name] -i [instance_name] -o [start_option] -c [connect_str] -q
# Stop all instances on the all nodes srvctl stop instance -d orcl -i orcl1,orcl2,...
# Stop ASM instance srvctl stop ASM -n [node_name] -i asm1 -o [option]
# Stop all apps in one node srvctl stop nodeapps -n [node_name]
2.5 srvctl add
Available options: database|instance|service|nodeapps|asm
Description:
Add a configuration to your cluster database configuration. "srvctl add service" adds services to a database and assigns them to instances. You can use "srvctl add service" to configure the Transparent Application Failover (TAF) policy for a service.
# Add database
2.6 srvctl remove
Available options: database|instance|service|nodeapps|asm
Description: Removes the named object from the cluster environment.
# Remove database