Re: RMAN Error

From: John Schaeffer <amerar_at_iwc.net>
Date: Wed, 25 Mar 2009 09:34:22 -0700 (PDT)
Message-ID: <3a9c48b5-ccd1-49f7-9a0f-a238460861a3_at_f19g2000yqh.googlegroups.com>

On Mar 25, 11:05 am, johnbhur..._at_sbcglobal.net wrote:
> On Mar 25, 11:41 am, John Schaeffer <ame..._at_iwc.net> wrote:
>
> snip
>
>
>
> > > Do you have appropriate cross checking in place before the deletes?
>
> > Hmm....maybe not?
>
> > run {
> > allocate channel d1 type disk;
> > backup validate database archivelog all;
> > backup incremental level 1 cumulative database
> > format '/backup/oracle/daily/ora_%M%D%Y_NI00_%p%s'
> > tag daily_backup
> > plus archivelog format '/backup/oracle/daily/archive/arc_%M%D%Y_NI00_%p
> > %s' delete input;
> > restore database validate;
> > delete noprompt obsolete;
> > delete noprompt expired backup;
>
> > }
>
> I am not a big fan myself of mixing backup related stuff with the
> delete processing ... not convinced this is involved in your problem
> but symptom seems to be from a delete?  ... so not unconvinced either.
>
> You might want to consider pulling the delete logic out of this script
> and front ending the script that will do the delete's with some cross
> checks before it.
>
> run {
> allocate channel d1 type disk;
> crosscheck copy;
> crosscheck backup of database;
> crosscheck backup of controlfile;
> crosscheck archivelog all;
>
> /* maybe some delete's in here now ... */
>
> release channel d1;
>
> }
>
> Personally I like to separate out delete expired functionality from
> delete obsolete also ... ( in separate runs ).

Not sure I quite understand the crosschecks before any backup commands, but I can try your suggestion. Received on Wed Mar 25 2009 - 11:34:22 CDT