Re: shutdown -- big transaction

A "shutdown abort" does not flush the db buffer and redo log caches. It does not update file headers. It does not synchronize control files and db files. It's not a good way to bring down the database. While most times you can get away with doing an abort, you are taking a big risk with your data. An operating system and application software can always be re-installed and re-configured. But how are you going to re-create your data? (Hope you have backups.) There is a difference between normal shutdowns and aborts. That's why you should startup and bring down right after an abort. If you are impatient, try "shutdown immediate".

HTH,
Brian

Greg Stark wrote:
>
> So what exactly is the consequence of shutdown abort? We're always impatient
> to shut down the database as quickly as possible and often give up and
> shutdown abort. If what you're saying is true there's little consequence, why
> doesn't shutdown always do the equivalent of abort?
>
> I've also been told that after an abort i should start the database up and do
> a clean shutdown and then start it up again before going live again. Is that
> just superstition?
>
> Connor McDonald <connor_mcdonald_at_yahoo.com> writes:
>
> > 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
> > --
> > ===========================================
> > Connor McDonald
> > "These views mine, no-one elses etc etc"
> > connor_mcdonald_at_yahoo.com
> >
> > "Some days you're the pigeon, and some days you're the statue."
>
> --
> greg
Received on Tue Oct 05 1999 - 16:55:44 CDT