Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Please Help. Database recovery

gsar10Jul 26 2013 — edited Aug 1 2013

Hello,

I have successfully restored all database files from a hot backup and additionally have the archived redo logs.

But the recovery process shows:


RMAN: recover database UNTIL TIME "to_date('2013-07-21:05:00:00', 'yyyy-mm-dd:hh24:mi:ss')";

Starting recover at 27-JUL-13

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=3 device type=DISK

starting media recovery

archived log for thread 1 with sequence 23366 is already on disk as file /mnt/backup/archivelog/2013_06_22/o1_mf_1_23366_8w9wgpq2_.arc

archived log for thread 1 with sequence 23367 is already on disk as file /mnt/backup/archivelog/2013_06_22/o1_mf_1_23367_8w9wtm3n_.arc

archived log for thread 1 with sequence 23368 is already on disk as file /mnt/backup/archivelog/2013_06_22/o1_mf_1_23368_8w9x5tdy_.arc

archived log for thread 1 with sequence 23369 is already on disk as file /mnt/backup/archivelog/2013_06_22/o1_mf_1_23369_8w9z4b22_.arc

...

...

...

archived log for thread 1 with sequence 23637 is already on disk as file /mnt/backup/archivelog/2013_07_21/o1_mf_1_23637_8ypbdlz4_.arc

archived log for thread 1 with sequence 23638 is already on disk as file /mnt/backup/archivelog/2013_07_22/o1_mf_1_23638_8yt3mgjm_.arc

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of recover command at 07/27/2013 00:15:12

RMAN-06053: unable to perform media recovery because of missing log

RMAN-06025: no backup of archived log for thread 1 with sequence 23365 and starting SCN of 9386955859715 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 23364 and starting SCN of 9386954389776 found to restore

RMAN-06025: no backup of archived log for thread 1 with sequence 23363 and starting SCN of 9386953882006 found to restore

RMAN-00567: Recovery Manager could not print some error messages

If i issue

recover database until cancel

I am prompted to use backup control file and then I get:

SQL> recover database until cancel using backup controlfile;

ORA-00279: change 2575661 generated at 09/14/2010 19:35:16 needed for thread 1

ORA-00289: suggestion :

/mnt/backup/archivelog/2013_07_27/o1_mf_1_2430_%u_.arc

ORA-00280: change 2575661 for thread 1 is in sequence #2430

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

Of course thereis no such file , so I supply a file that exists and has redo data for the time after the backup:

/mnt/backup/archivelog/2013_07_21/o1_mf_1_23637_8ypbdlz4_.arc

ORA-00310: archived log contains sequence 23637; sequence 2430 required

ORA-00334: archived log:

'/mnt/backup/archivelog/2013_07_21/o1_mf_1_23637_8ypbdlz4_.arc'

ORA-10879: error signaled in parallel recovery slave

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: '+DATA/isdwh03/datafile/system.256.729342523'

I think oracle wants to go very early in time (3 years ago) to begin recovery. Of course I have not these very old redo logs!!

I have read elsewhere that such problem can occur with datafile 1.

Is there a solution or must I lastly use the _allow_resetlogs_corruption”=true parameter?

Thank you

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 29 2013
Added on Jul 26 2013
13 comments
895 views