| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: shutdown -- big transaction
Pat Minnis wrote:
>
> 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?
See the other post for some other options...
but to answer your question, since 7.3 (I think) the recovery of data once you restart after shutdown abort will be delayed until required.
That is, in the ol' days (pre 7.3) when you restarted an aborted database, the recovery was done for all the blocks needing it, and then the database says "opened". Now the database says open and then as the blocks that need recovery are encountered, they are clean up then.
Cheers
--
"Some days you're the pigeon, and some days you're the statue." Received on Fri Sep 24 1999 - 04:37:12 CDT
 |
 |