Re: shutdown -- big transaction

Pat Minnis <pminnis_at_indianaonline.net> wrote in message news:cUKG3.113$Rn3.14678_at_news.goodnet.com...
> Has anyone run across this problem?
>
> An 8 hour job runs into the night.
> It is still running when a shutdown immediate is done.
> The automatic shutdown job detects 10 minutes later that the database has
> not been shutdown, so it does a shutdown abort which doesn't do anything
> either.
> 5 hours later, the database goes ahead and shuts down without any apparent
> cause.
>
> Our theory is:
> The 8 hour job generates 8 hours of rollback.
> The shutdown immediate rolls back this transaction -- which takes 5 hours!
> The database shuts down when finished rolling back.
>
> Our question is:
> What can be done about it?
> If a shutdown abort is done instead of immediate, won't startup do 5 hours
> of recovery?

Clearly there is a reason for doing the 8 hour job. Why not detect when its finished and then shutdown. Alternatively, if you're shutting down to do a backup - why not use hot backups ??

Alex Received on Fri Sep 24 1999 - 08:42:26 CDT