Re: Shutdown Abort - Not a Good Idea, Right?

You're right, Shutdown Abort is not at all a good idea unless required in emergency.

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.

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

• The database or one of its applications is functioning irregularly and neither of the other types of shutdown work.
• 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.

Hope, will help you.

Thanks,

Vrajesh.

"M. Bhatti" wrote:

> I just recently noticed that, before doing cold backups, our db
> instances (Oracle 7.3.2/8.0.5, Sun Solaris 2.5.1) are shutdown aborted
> than brought up and shutdown normal, so that the cold backup can be
> started immediately after the shutdown normal.
>
> Question is, I thought shutdown abort should not be used except in
> extreme conditions ie when a db instance
> cannot be shutdown normal/immediate.
>
> So, I assume that:
> This is bad idea right (shutdown abort)?
> What can happen to the db?
>
> Thanks for any input.
>
> mkb
Received on Thu Apr 22 1999 - 10:55:17 CDT