Re: Don't Use Shutdown Immediate for Full Backup

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.

svrmgrl << eod
connect internal
shutdown immediate
startup restrict open
exit
eod

exp ...

svrmgrl << eod
connect internal
alter system disable restricted session; exit
eod

>
>Below is the exact text from the manual.
>
>Oracle 7 Server Administrator's Guide (part no 6694-70-1292) from December 1992
>on page 18-8 says
>
>Preparing to Take a Full Backup:
>
>To guarantee that a database's data files are consistent, always shut down the
>database in normal priority before making a full database backup; never perform
>a full database backup after an instance failure or after the database is
>shutdown with immediate or abort priority (that is using a SHUTDOWN IMMEDIATE
>or SHUTDOWN ABORT statement). In both these cases, the data files are likely
>not to be consistent with respect to a specific point in time.
>
>
>Thank you,
>
>Catherine Cox
>catcox_at_aol.com

-- 
These opinions are my own and not necessarily those of Information Quest
jgarry@eiq.com                           http://www.informationquest.com
http://ourworld.compuserve.com/homepages/joel_garry
"See your DBA?"  I AM the @#%*& DBA!