<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Oracle Instance Management on Oracle Scripts</title><link>https://www.oraclescripts.com/tags/oracle-instance-management/</link><description>Recent content in Oracle Instance Management on Oracle Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>OracleScripts.com</copyright><lastBuildDate>Fri, 26 Jan 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://www.oraclescripts.com/tags/oracle-instance-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Starting and Stopping Oracle Database Instances with SRVCTL</title><link>https://www.oraclescripts.com/post/start-stop-oracle-database-instances-with-srvctl/</link><pubDate>Fri, 26 Jan 2024 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/start-stop-oracle-database-instances-with-srvctl/</guid><description>
&lt;h2 id="starting-and-stopping-oracle-database-instances-with-srvctl"&gt;Starting and Stopping Oracle Database Instances with SRVCTL&lt;/h2&gt;
&lt;h2 id="purpose"&gt;Purpose&lt;/h2&gt;
&lt;p&gt;Planned work on one node of an Oracle RAC database begins with a small task. You stop the instance on that node, do the work, and start the instance again. The Server Control utility, &lt;code&gt;srvctl&lt;/code&gt;, does this task from the command line. It starts or stops one named instance and leaves the other instances in the cluster as they are.&lt;/p&gt;
&lt;p&gt;SRVCTL does more than send a shutdown command. It starts and stops instances by configuring and managing Oracle Clusterware resources. Those resources define agents that run the database startup and shutdown. This is the reason to prefer SRVCTL over a manual SQL*Plus session on a cluster node.&lt;/p&gt;</description></item></channel></rss>