Re: Media recovery when using an old controlfile

I believe (haven't tried it myself), that since you recovered using a backup controlfile that you would have had to open with RESETLOGS anyway. You were able to recover everything, but the system probably needed RESETLOGS to open. To the system, you still did incomplete recovery even though you got everything. So you now have a new incarnation of the database, and hopefully, you've backed it up by now. Remember, when you open with RESETLOGS, you effectively wipe out what is in the online redo logs so you won't be able to use the same recovery method again.

HTH,
Brian

Jurjen Oskam wrote:
>
> In article <3efaa55b$1_1_at_news.estpak.ee>, Tanel Poder wrote:
>
> > Please let me know the results then.
>
> It works! In the log below, it asks for sequence 49366, but that isn't generated
> yet. Trying to apply the online redo logs worked:
>
> SVRMGR> recover database using backup controlfile until cancel;
> ORA-00279: change 1703294757 generated at 06/26/2003 10:17:08 needed for thread 1
> ORA-00289: suggestion : /oracle/app/oracle/admin/prod1/arch/arch1_49366.rdo
> ORA-00280: change 1703294757 for thread 1 is in sequence #49366
> Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
> /dbentry/prod1/redo1_100_01
> ORA-00310: archived log contains sequence 49362; sequence 49366 required
> ORA-00334: archived log: '/dbentry/prod1/redo1_100_01'
> ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
> ORA-01194: file 1 needs more recovery to be consistent
> ORA-01110: data file 1: '/dbentry/prod1/div1_500_01'
> [snip several other wrong redologs]
> SVRMGR> recover database using backup controlfile until cancel;
> ORA-00279: change 1703294757 generated at 06/26/2003 10:17:08 needed for thread 1
> ORA-00289: suggestion : /oracle/app/oracle/admin/prod1/arch/arch1_49366.rdo
> ORA-00280: change 1703294757 for thread 1 is in sequence #49366
> Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
> /dbentry/prod1/redo2_100_01
> Log applied.
> Media recovery complete.
> SVRMGR> alter database open resetlogs;
> Statement processed.
> SVRMGR>
>
> Unfortunately, I mindlessly opened the database with RESETLOGS. It would
> have been nice to see NORESETLOGS also work, since the database is
> recovered to the most recent condition.
>
> --
> Jurjen Oskam
>
> PGP Key available at http://www.stupendous.org/

-- 
===================================================================

Brian Peasland
oracle_dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"