Re: SHUTDOWN

In article <436qt2$ag1_at_bcrkh13.bnr.ca>, Loren Budd <Loren_Budd_at_nt.com> writes:
|> A shutdown immediate will not log off any current users, but it will
|> prevent new connections from being established. You will still have to
|> wait until current transactions are completed before the shutdown will
|> complete successfully. When you say that the shutdown was hanging, it
|> was probably waiting for all active sessions to complete. We experience
|> the same problem on our production database due to batch processes that
|> run into our backup window (We're currently doing cold backups). If you
|> are performing the shutdown for backup purposes, I recommend coordinating
|> with your application group to ensure their processes are finished before
|> a defined window.
|> In our experience, doing a shutdown abort is very dangerous due to the
|> inconsistency in which you leave the database and even doing a shutdown
|> immediate is not recommended. Try for the shutdown normal. Just my 2 cents
|> worth.
|>
|> Loren
|>
That does not seem to be what the Oracle7 Server admin guide says.
(Oracle 7.0.15 on Solaris 2)

SHUTDOWN IMMEDIATE

• Current Client SQL statements are terminated immediately.
• Any uncomitted transactions are rolled back
• ORACLE does not wait for users currently connected to the database to disconnect. ORACLE implicitly rolls back active transactions and disconnects all connected users.
• the next startup might require instance recovery
• long-running queries, might not get fully rolled back.

Perhaps the documentation is just wrong.

Nick Received on Wed Sep 13 1995 - 00:00:00 CEST