> They are going to get an even more unpleasant surprise if you have
> You could implement your own nice shutdown using events without too
> much trouble.

Sure that's what we have done but any other app from another vendor
that uses the same db and haven't registered those events, the same
problem will reoccur. And even only when 1 app is only used you still
have to check the Db's active connections to check if the active
users have really disconnected and that can only be done when you are
are using SuperServer. And while you are waiting some 'other' owner
or SYSDBA user can reconnect and u can start all over.

> Even so, I would restore to a different location, then copy it in
> place once the restore has been verified as successful.

I think a copy is even more unsafe then trying to rename first. What
will state of the DB be in if its still locked and you copy the newly
created DB from restore over the old one.

> I can not see a good reason for anyone to be connected to a

database > you are about to destroy.

Users are getting paid for doing data entry on the db, one user might
have done something wrong deleting/updating data that should not be
updated/deleted, requests a DB restore to correct what he did ...
Don't think its that rare.

Greetings,
Filip Moons