Re: RMAN level 0 complains it can't find archivelogs

On Mar 27, 1:56 pm, "Andy Kent" <andykent.bristol1..._at_virgin.net> wrote:
> On Mar 27, 12:26 pm, "sybrandb" <sybra..._at_gmail.com> wrote:
>
>
>
> > On Mar 27, 12:43 pm, "Andy Kent" <andykent.bristol1..._at_virgin.net>
> > wrote:
>
> > > I'm putting together an RMAN strategy on 10g under Linux, temporarily
> > > doing everything to disk while we prove the principles. I want to re-
> > > start a fresh cycle of backups with a brand new full backup (10.2 on
> > > Linux). I scheduled a full backup from EM checking the "Use as the
> > > base of an incremental backup strategy" box and it generated the
> > > following command:
>
> > > backup incremental level 0 cumulative device type disk tag ...
>
> > > The job failed because a week-old archive log is no longer on disk
> > > (we'd had several successful incrementals since then), which surprised
> > > me given the box I'd checked. What do I have to do differently so it
> > > will just start with a clean slate and not try to find archivelogs?
> > > Why does EM generate the keyword "cumulative"? - it seems redundant
> > > in the context of a level 0... ?
>
> > > Thanks
>
> Is there some way that can be circumvented with CROSSCHECK / DELETE
> EXPIRED or similar, or is the reference to the logs outside the scope
> of RMAN? I've implemented a recovery catalog since the missing
> archivelogs were created, don't know if that makes a difference.
>
> To save me doing a lengthy manual trawl (I know, I know, but the first
> hits I got don't say much), can you tell me: is alter database open
> resetlogs part of a more complex procedure or do I simply issue that
> statement?
>
> Thanks
>
> Andy
>
>
>
> > > Andy
>
> > either a cold backup or an alter database open resetlogs, I am afraid.
> > Your current archivelogs are in your controlfile,and if you don't back
> > them up and delete them using RMAN, this error is inevitable. Usually
> > one would add 'skip inaccessible' to a backup archivelog command, but
> > this limits the recoverability of the database.
>
> > --
> > Sybrand Bakker
> > Senior Oracle DBA- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

Alter database open resetlogs is normally issued after the database has been *mounted* only (for backup/recovery purposes or to relocate datafiles etc).
So the typical procedure would be
shutdown immediate
startup mount
alter database open resetlogs

Be aware though this moment will act like 'birth'. You won't be able to recover the database before this moment, so you'd better make a cold backup (and make sure you keep that one forever). A cold backup can be made using RMAN, making sure the database is mounted only. During cold backup RMAN will ignore any archives, as you don't need archives to restore a cold backup.

--
Sybrand Bakker
Senior Oracle DBA