Re: problem with dbshut/dbstart?

Ken,
You are correct on everything except I am not aware of shutdown abort ever corrupting the database. It will kill all process and not roll anything back on the way down, but on the way up it will handle all the rollback that is required from the aborted transactions on shutdown.

Marty

Ken Mizuta wrote in message <36B54610.23F5BEB1_at_jp.oracle.com>...
>
>Bruce,
>
>Shutdown does not corrput your database. In fact, if you try to shutdown
the
>database without the immediate, it means that it WAITS for all users to log
>off. So, as long as the users do not log off, then the database is still
>running. (If you shutdown the Sequent box in this state, then you might
>corrupt the database, because the database may still be waiting for users
to
>log off and may not have had the chance to shutdown. Shutdown immediate, on
>the other hand, does not wait for users to log off and actually forces the
>users off the database, then does a graceful shutdown of the database.
>Shutdown abort just drops the database (using abort may corrupt the
database).
>
>If you are using dbshut in a script which is automatically run when the
>Sequent box is shutdown, then you should make sure that the database is
truly
>shutdown before it continues.. i.e., don't use "&" to run dbshut in the
>background. Wait for dbshut to return before continuing shutdown of the
>Sequent box.
>
>Ken
>
Received on Mon Feb 01 1999 - 17:10:14 CST