Home » RDBMS Server » Backup & Recovery » DB duplication - RMAN-06025 missing archive logs
DB duplication - RMAN-06025 missing archive logs [message #237637] Tue, 15 May 2007 05:14 Go to next message
n_de_fontenay
Messages: 33
Registered: October 2006
Location: Paris
Member
Hi,

I’ve been digging around the problem and found out that at recovery time, RMAN keep asking me for archive logs which doesn’t exist any more in my repository…

I always get this error message:

I’ve just performed backup moments ago. The oldest archive on my server is 21360… and I moved the backups to the auxiliary server so those old 19XXX should not be a problem. Yet I keep having the following… I've tried many fresh backup.

The error looks like this:

RMAN-03002: failure of Duplicate Db command at 05/15/2007 17:53:52

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 21393 lowscn 13512740 found to restore

RMAN-06025: no backup of log thread 1 seq 21363 lowscn 13402915 found to restore

RMAN-06025: no backup of log thread 1 seq 19343 lowscn 12141344 found to restore

RMAN-06025: no backup of log thread 1 seq 19342 lowscn 12141243 found to restore

As a result of this, no logs will be restored in my archive folder for recovery of the database and the duplication will fail.

Does anybody has an idea of what’s going on?

Thanks in advance,

Nico
Re: DB duplication - RMAN-06025 missing archive logs [message #237946 is a reply to message #237637] Wed, 16 May 2007 03:28 Go to previous messageGo to next message
Frank Naude
Messages: 4502
Registered: April 1998
Senior Member
Were these archlog files backed up?

6025, 1, "no backup of log thread %d seq %d lowscn %s found to restore"
// *Cause:  An archive log restore restore could not proceed
//          because no backup of the indicated archived log was found.
//          It may be the case that a backup of this file exists but
//          does not satisfy the criteria specified in the user's restore
//          operands.
// *Action: None - this is an informational message.  See message 6026 for
//          further details.


6026, 1, "some targets not found - aborting restore"
// *Cause:  Some of the files specified for restore could not be found.
//          Message 6023, 6024, or 6025 is also issued to indicate which
//          files could not be found.  Some common reasons why a file
//          can not be restored are that there is no backup
//          or copy of the file that is known to recovery manager, or
//          there are no backups or copies that fall within the criteria
//          specified on the RESTORE command, or some datafile copies have
//          been made but not cataloged.
// *Action: The Recovery Manager LIST command can be used to display the
//          backups and copies that Recovery Manager
//          knows about.  Select the files to be restored from that list.

Re: DB duplication - RMAN-06025 missing archive logs [message #237953 is a reply to message #237946] Wed, 16 May 2007 03:36 Go to previous message
n_de_fontenay
Messages: 33
Registered: October 2006
Location: Paris
Member
Hi.
Thanks a lot for answering.

They were backed up but since then, they have been deleted.

That's why I did a (lot of) new backup.

To make sure the repository is clean, I've crosschecked the archivelog and the backups and deleted expired ones...

I don't understand why RMAN keeps referencing to them for a recovery which is much newer than those archivelogs could be.

These backups are a couple of days old now.

I've done:

backup database plus archivelog not backed up 1 times this morning

Then I've used until 'sysdate - 0.04' (one hour earlier back in time).

*depressed*
Previous Topic: how to deal with RMAN
Next Topic: Database duplication
Goto Forum:
  


Current Time: Mon Dec 05 11:08:03 CST 2016

Total time taken to generate the page: 0.10710 seconds