Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.tools -> Re: Shutdown Normal time

Re: Shutdown Normal time

From: Myron Wintonyk <Myron.Wintonyk_at_UAlberta.CA>
Date: Thu, 01 Mar 2001 11:24:35 +1000
Message-ID: <3A9DA4D3.37064D60@UAlberta.CA>

Here's the text from the oracle manual. Note that oracle WAITS for all users to log off BEFORE
it shuts down the database.

Shutting Down with the NORMAL Option
Normal database shutdown proceeds with the following conditions:

No new connections are allowed after the statement is issued.

Before the database is shut down, Oracle waits for all currently connected users to disconnect from the database.

The next startup of the database will not require any instance recovery procedures.

To shut down a database in normal situations, use the SHUTDOWN command with the NORMAL option:

 SHUTDOWN NORMAL; Shutting Down with the IMMEDIATE Option
Use immediate database shutdown only in the following situations:

A power shutdown is going to occur soon.

The database or one of its applications is functioning irregularly.

Immediate database shutdown proceeds with the following conditions:

Any uncommitted transactions are rolled back. (If long uncommitted transactions exist, this method of shutdown might not complete quickly, despite its name.)

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 of the database will not require any instance recovery procedures.

To shut down a database immediately, use the SHUTDOWN command with the IMMEDIATE option

SHUTDOWN IMMEDIATE;


Note:
The SHUTDOWN IMMEDIATE statement disconnects all existing idle connections and shuts down the database. If, however, you have submitted processes (for example, inserts, selects or updates) that are awaiting results, the SHUTDOWN TRANSACTIONAL statement allows the process to complete before disconnecting.


Shutting Down with the TRANSACTIONAL Option When you wish to perform a planned shutdown of an instance while allowing active transactions to complete first, use the SHUTDOWN command with the TRANSACTIONAL option:

SHUTDOWN TRANSACTIONAL; After submitting this statement, no client can start a new transaction on this instance. If clients attempt to start a new transaction, they are disconnected. After all transactions have completed, any client still connected to the instance is disconnected. At this point, the instance shuts down just as it would when a SHUTDOWN IMMEDIATE statement is submitted. The next startup of the database will not require any instance recovery procedures.

A transactional shutdown prevents clients from losing work, and at the same time, does not require all users to log off.

Shutting Down with the ABORT Option
You can shut down a database instantaneously by aborting the database's instance. If possible, perform this type of shutdown only in the following situations:

The database or one of its applications is functioning irregularly and neither of the other types of shutdown works.

You need to shut down the database instantaneously (for example, if you know a power shutdown is going to occur in one minute).

You experience problems when starting a database instance.

Aborting an instance shuts down a database and yields the following results:

Current client SQL statements being processed by Oracle are immediately terminated.

Uncommitted transactions are not rolled back.

Oracle does not wait for users currently connected to the database to disconnect; Oracle implicitly disconnects all connected users.

The next startup of the database will require instance recovery procedures.

If both the normal and immediate shutdown options do not work, abort the current database instance immediately by issuing the SHUTDOWN command with the ABORT option:

SHUTDOWN ABORT; Peter Johnson wrote:

> How long does it take to shutdown an Oracle 8i DB when using shutdown
> normal ?
>
> Cause it is just sitting there atm and doesn't appear to be responding
> to that command at all.
>
> Any help would be appreciated.
>
> Thanks in advance.
>
> Peter Johnson
Received on Wed Feb 28 2001 - 19:24:35 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US