Skip to Main Content

Database Software

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!

RMAN duplication failed due to missing archive logs

240948Sep 14 2006 — edited Sep 15 2006

I'm just having no love from RMAN.

I tried to perform a PITR duplication from PROD to DEV2 last night up to 2006/09/09 04:30:00 (roughly 5 days ago). It failed with this message:

Oracle Error:
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: '/oracle/dev2/u08/oradata/dev2/system01.dbf'

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/14/2006 11:11:42
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 157898 lowscn 517153382 found to restore
RMAN-06025: no backup of log thread 1 seq 157897 lowscn 517151682 found to restore
RMAN-06025: no backup of log thread 1 seq 157896 lowscn 517148600 found to restore

I connect to the PROD RMAN instance and do a 'report need backup' and it didn't list any files needed to satisfy the 7 day recovery window. Nor does it list those archive log sequences as backed up, but it does list log sequences before and after.

I'm somewhat fortunate that this is "only" for a development instance, but it pretty much shakes my confidence in the ability of RMAN to perform a disaster recovery.

I launch RMAN with this command:

$ORACLE_HOME/bin/rman target sys/pass@prodinst nocatalog auxiliary sys/pass@dev2 log=dupe.log append

I run my duplication with this command:

DUPLICATE TARGET DATABASE TO DEV2 UNTIL TIME '2006/09/09:04:30:00';

(Yes I've set my $NLS_DATE_FORMAT env var). It basically runs fine until that error.

RMAN is the only thing that removes archive logs from disk, and should only do so after they are backed up. So the obvious questions are:

1. What happened to these logs? (Obviously I'm sure no one can answer)

More importantly:

2. Why does RMAN say everything is peachy via 'report need backup' but still fail at duplication?

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Oct 13 2006
Added on Sep 14 2006
14 comments
3,593 views