Re: Using Shutdown Immediate

Here is yet another point of view on this whole topic. And since we're quoting manuals, I'll just quote from another source that seems to have done a bit more research into the whole backup/recovery subject.

In the "Oracle Backup & Recovery Handbook" by Rama Velpuri(pg 30), here's what it says about shutdown normal: "The normal shutdown process stops all user access to the database, waits until all users complete their requests and disconnect from the server, purges data buffer and redo log caches and updates data files and online redo logs, drops file locks, completes ongoing transactions, updates file headers, closes thread, drops the database instance lock, and synchronizes control files and data files."

Fair enough, right?

Here's what it says about shutdown immediate: "If this option is used to shut down the database, the current SQL statements that are being processed by Oracle are terminated immediately, any uncommitted transactions are rolled back, and the database is shut down. The only disadvantage of using this option is that Oracle doesn't wait for the current users to disconnect. However, the database will be consistent and no recovery is required during next startup."

Hmmmmm.

As most of us know, the Oracle manuals can leave things to be either a little bit vague or slanted toward the cautious side. The book quoted above draws upon the knowledge and experience of several people within Oracle itself.

Matt Myers
Symmetry Consulting Corp. Received on Wed Aug 16 1995 - 00:00:00 CEST