Re: Best way to handle Oracle shutdowns from Unix script

>
> I wouldn't do it with my database! By killing oracle background processes
> this way you're just asking for trouble. A better way is to:
>
> 1. shutdown abort
> 2. startup in restricted mode
> 3. shutdown immediate or normal
>
> This will kill all active connections, rollback open transactions, and
 put
> the database into a consistent state so it can be backed up cold.
>

1. Shutdown abort DOES NOT rollback open transactions. It just takes the instance down, no questions asked. You need to shutdown immediate to cancel active transactions and rollback. Abort should only be used when all else fails.

2. If you startup restrict, there is no reason to shutdown immediate, normal will work just the same.

Killing background processes (smon, pmon, arch, etc.) isn't a good idea, but killing dedicated server processes is a good idea if you are trying to come down cleanly. In many months running over 120 instances of Oracle I have never experienced any problems using shutdown immediate or killing dedicated server processes. I have seen big problems result when an untrained operator did a shutdown abort with tablespaces in backup. Received on Wed Oct 15 1997 - 00:00:00 CDT