Re: Don't Use Shutdown Immediate for Full Backup

I didn't know about the restricted option at the startup. However, what we do is the following:

shutdown immediate (which kills every sessions), startup
alter system switch logfile
shutdown
then full backup

This way we force the creation of a recent archived redofile and also a recent checkpoint. Then we have a recently checkpointed database on a backup and the most up to date archived redofiles also on a backup.

-- 
Michel Gauthier
qgmi1_at_qbc.clic.net
Produits Forestiers Donohue Inc.
The ideas expressed/language used reflect those of the author,
Not necessarly those of Donohue Inc.



> > In article <19980204003400.TAA11602_at_ladder03.news.aol.com>,

> > Catcox <catcox_at_aol.com> wrote:

> > >The manual says not to do a SHUTDOWN IMMEDIATE if you are going to do

 a full


> > >cold backup of the database.  However  SHUTDOWN NORMAL isn't likely to

 bring


> > >the database down since invariably there are sessions hanging.  Of

 course the


> > >backup is done in the middle of the night, and I won't be around to

 kill any


> > >sessions.   I'm wondering what other people have done.  Should I write

 a script


> > >to kill all sessions before the shutdown script runs or what?

> >

> > That is one way.  The other way is to do the shutdown immediate, bring

 the


> > database back up restricted.