Re: [Oracle8i]Immediate shutdown

szalas <gszalach_at_hotmail.com> schreef in berichtnieuws bg3h3l$dpm$1_at_julia.coi.pw.edu.pl...
| Hi,
|
| I performed immediate shutdown on my database.
| It didn't shutdown immediately but it is still in progress.
| Is there any possibility to see what it's currently doing and possibly
kill
| process which delayed my shutdown??
| I suppose that one session with distributed transaction cause this
problem.
| I had tried to kill this session but it wasn't killed immediately and only
| marked as killed.
| So am I supposed to wait for shutdown or do I have some other choices????
|
| Thank you very much for any solutions
| Szalas

When shutdown immediate is taking a long time there are 2 possibilities: a. transactions are being rolled back. This can take just as long as the transaction was running.
b. there is a problem with a system call that does not finish. Shutdown immediate ends all sessions but must wait on certain internal calls to finish. They normally run very very short, but I experienced it does not sometimes, in all versions.

To speed up things I would start another session as sys and a. shutdown abort. This should stop the database immediately b. startup restrict. This starts the db but does only allows users with "restricted session privilige" to log on, that should exclude "normal" sessions
c. shutdown immediate. Now you have a clean shutdown database that does not need recovery, no fuzzy files.

In fact: this is our normal way of bringing a database down because we regulary experienced symptoms you describe. In my experience the rollback of the transactions goes much much faster like this than when done in a shutdown immediate. But when I write this down, this can become a long thread again, because I know others here does not see the need for such an approach and even strongly advice against it. One had the experience the db could not be started after shutdown abort because it got corrupted. I never have seen that. Received on Mon Jul 28 2003 - 12:48:10 CDT