1Z0-058 · Question #115
Examine the following output: [oracle@gr5153~]$srvctl add service -d RACDB -s erp -g pool1 -c uniform -y manual [oracle0gr5153~]$srvctl start service -d RACDB -s ERP [oracle@gr5153~]$crsctl stat res…
The correct answer is A. It will shut down all the instances of the RACDB database. D. It will stop the ERP service related to the RACDB database on all the nodes. Shut down all Oracle RAC instances on all nodes. To shut down all Oracle RAC instances for a database, enter the following command, where db_name is the name of the database: srvctl stop database -d db_name Stops a database, its instances, and its services. When the database…
Question
Examine the following output:
[oracle@gr5153~]$srvctl add service -d RACDB -s erp -g pool1 -c uniform -y manual [oracle0gr5153~]$srvctl start service -d RACDB -s ERP [oracle@gr5153~]$crsctl stat res ora.racdb.erp.svc NAME=ora.racdb.erp.svc TYPE=ora.service.type TARGET=ONLINE, ONLINE, ONLINE STATE=ONLINE on gr5118, ONLINE on gr5152, ONLINE on gr5153 [oracle@gr5153~]$ srvctl config database -d RACDB Database unique name: RACDB Database name: RACDB Oracle home:/u01/app/oracle/product/11.2.0/dbhome_1 Oracle user:oracle Spfile:+DATA/RACDB/spfileRACDB.ora Domain:
Start options:open Stop options:immediate Database role:PRIMARY Management policy:AUTOMATIC Server pools:POOL 1 Database instances:
Disk Groups:DATA, FRA Services:ERP Database is policy managed $srvctl stop database -d RACDB -o immediate Which two statements are true regarding the srvctl stop command?
Options
- AIt will shut down all the instances of the RACDB database.
- BIt will shut down only the RACDB instance and the ERP service on the node on which the
- CIt will shut down only the database instance on the node on which the command is executed.
- DIt will stop the ERP service related to the RACDB database on all the nodes.
How the community answered
(30 responses)- A83% (25)
- B10% (3)
- C7% (2)
Explanation
Shut down all Oracle RAC instances on all nodes. To shut down all Oracle RAC instances for a database, enter the following command, where db_name is the name of the database: srvctl stop database -d db_name Stops a database, its instances, and its services. When the database later restarts, services with AUTOMATIC management start automatically but services with MANUAL management policy must be started manually. Oracle Real Application Clusters Administration and Deployment Guide
Topics
Community Discussion
4
Ola B.Apr 19, 2026The correct answers are A and D, and the key thing to understand here is that srvctl operates at the cluster level, not the local node level. When you run srvctl stop database -d RACDB, it sends the stop signal to every instance registered under that database name across all nodes, so all three instances go down, which confirms A. Because the ERP service is policy managed and tied to RACDB, stopping the database also triggers the service stop on every node where it was running, which is what D is telling you. B and C are classic traps that try to get you thinking about how sqlplus shutdown immediate works, but srvctl is a cluster-aware tool and does not care which node you are sitting on when you run the command. Spin up a two-node RAC in a lab and run this yourself, then watch crsctl stat res -t before and after, because seeing all those targets flip from ONLINE to OFFLINE at once will lock this concept in your memory better than any flashcard.
Nina C.Apr 22, 2026Good call on the lab tip, and I would add that the exam also likes to flip that scenario by swapping "database" for "instance" in the srvctl command, because srvctl stop instance only targets one node while srvctl stop database hits them all, so drilling that single-word difference is worth your time before test day.
Nina C.May 9, 2026A and D, srvctl stop database is cluster-wide, so services drop on every node.
Viktor S.Apr 24, 2026I went straight to C first because the command runs from gr5153 and my brain said local node, local action, but that is exactly the trap Oracle sets here. The whole point of srvctl is that it talks to the cluster, not just the box you are sitting on, so "stop database" means stop the database everywhere, which gives you A. And since the ERP service lives on top of RACDB, killing the database on every node kills the service on every node too, that is D. B and C are there to catch people who have memorized "srvctl" as a synonym for "do stuff on my node," which is a dangerous misunderstanding when you are actually managing a production RAC environment.