Re: force clean database shutdown

<div class="mail">
<address class="headers">
<span id="from">
<dfn>From</dfn>: Brian Peasland <oracle_dba_at_nospam.peasland.net>
</span>
<span id="date"><dfn>Date</dfn>: Thu, 8 Jun 2006 16:30:15 GMT</span>
<span id="message-id"><dfn>Message-ID</dfn>: <J0Jv6o.J75_at_igsrsparc2&#46;<!--nospam-->er.usgs.gov>
</span>
</address>

<br>

maxim2k wrote:
<br>
<i class="quotelev1">> Hi,</i><br>
<i class="quotelev1">> </i><br>
<i class="quotelev1">> I'm running Oracle Database 10g R2 on Red Hat Enterprise Linux 4.</i><br>
<i class="quotelev1">> </i><br>
<i class="quotelev1">> I've configured the server to use the dbstart/dbshut scripts, provided </i><br>
<i class="quotelev1">> by Oracle, to automatically startup/shutdown the database at when </i><br>
<i class="quotelev1">> starting/shutting down the server.</i><br>
<i class="quotelev1">> </i><br>
<i class="quotelev1">> I've noticed that the dbshut script will sometime take forever to bring </i><br>
<i class="quotelev1">> down the db when shutting down the server, it will just hang there ...</i><br>
<i class="quotelev1">> </i><br>
<i class="quotelev1">> It looks like the database is waiting for its clients to close their </i><br>
<i class="quotelev1">> connections, before going down, or something like that.</i><br>
<i class="quotelev1">> </i><br>
<i class="quotelev1">> How can I force a clean shutdown for the database when the server needs </i><br>
<i class="quotelev1">> to be rebooted (e.g. for a kernel update)?</i><br>
<i class="quotelev1">> </i><br>
<i class="quotelev1">> I have no control over the db clients, I have full control on the server.</i><br>
<i class="quotelev1">> </i><br>
<i class="quotelev1">> Thanks.</i><br>

Does your dbshut script perform a simple SHUTDOWN or SHUTDOWN NORMAL? If   so, then this will wait for all active connections to disconnect. If you do not want to wait this long, you can change your dbshut to use SHUTDOWN IMMEDIATE. The SHUTDOWN IMMEDIATE command will terminate all active session, roll back any work that was in progress, and leave the database in a consistent state at shutdown. Depending on the current transactions, rolling back their work can still take some time to complete. But this is better (IMO) than SHUTDOWN NORMAL.

<strong>HTH,
</strong>
<br>

Brian

-- 
===================================================================

Brian Peasland
oracle_dba_at_nospam&#46;<!--nospam-->peasland.net


<a href="http://www.peasland.net">http://www.peasland.net</a>


Remove the "nospam." from the email address to email me.


"I can give it to you cheap, quick, and good.
Now pick two out of the three" - Unknown


<span id="received"><dfn>Received on</dfn> Thu Jun 08 2006 - 11:30:15 CDT</span>

</div>