Re: Need a lesson in RMAN for RAC

To answer your question (and Randy's query), the restore was from a valid incremental database backup. The perplexing part is that recovering to an hour before my target time has no such problems. Randy, you made a point about open transactions. I had the same thought, but how would an open transaction get "stuck" in an archived log that is over one month old? Something tells me that the stated archived log is a complete red herring, since I can recover to 4:51, but not 5:51. I am trying to find out why that error message popped up at all.

For some extra background, it may be helpful to point out that the aforementioned log is from right after a resetlogs in July (Incarnation 2), and the requested change number is from after another resetlogs in August (Incarnation 3). It almost looks like RMAN is attempting to use an archived log that has a transaction that spans the resetlogs (which is impossible, I know) and somehow thinking that in order to get from Incarnation 2 to Incarnation 3 (ie, Recovery through resetlogs), it wants this archived log.

Just a lame guess, but I mention it so that you experts can use this as a "teachable" moment and enlighten me.

PS - Jared, I just saw that you posted my original email to you. Thanks. Gmail is going really slow on me now.....

On 9/7/07, Jared Still <jkstill_at_gmail.com> wrote:
>
> On 9/7/07, Charles Schultz <sacrophyte_at_gmail.com> wrote:
> >
> > archive log filename=+DATA/lumqa/1_38_629052887.dbf thread=1 sequence=38
> >
> > archive log filename=+DATA/lumqa/2_2_629052887.dbf thread=2 sequence=2
> > ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error
> > below
> > ORA-01152: file 1 was not restored from a sufficiently old backup
> > ORA-01110: data file 1: '+DATA/lumqa/datafile/system.314.629052819'
> >
>
> Was the SYSTEM file actually restored, or is it a file from a pre-existing
> database?
>
> If pre-existing, you may need to apply the online logs, which may or may
> not
> be available to you. If this is a database being restored to a different
> server, you
> may need to get later archive logs and apply them.
>
> That was occasionally required in the hot backup days when someone forget
> to take the tablespaces out of backup mode and archiving the latest log.
>
> Failure to do that step would result in the ORA-1110 error (IIRC).
>
> The fix was to apply the online redo logs if you had them.
>
> The same thing can happen if you restore all but the SYSTEM file and try
> to do a recovery.
>
>
> --
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
>

-- 
Charles Schultz

--
http://www.freelists.org/webpage/oracle-l