RMAN-06457 error when cloning a RAC db to a different box

From: Li Li <litanli_at_gmail.com>
Date: Mon, 1 Feb 2010 17:34:52 -0600
Message-ID: <5f35c2321002011534i681ba464kb494caaa69b8b7cf_at_mail.gmail.com>



Hi, List,

Today when cloning a production RAC DB to a different box, we ran into this RMAN-06457 error. what we did was:

RMAN> run
{
set until sequence 1468 thread 4;
duplicate target database to xxxxx;
}

and it errored out with:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 02/01/2010 16:20:02 RMAN-06457: UNTIL scn (15612469216) is ahead of last scn in archived logs (15576714010)

we have been doing this routinely to refresh our non-production databases with no issue for a long time. One thing to note here is: one of the production RAC server was down (and still is down). SCN 15576714010 appears to be really really old, it doesn't make sense to me. The backup used to clone was from like:

backup device type disk format
'/path/to/backup/location/%d_%I_%Y%M%D_%s_%p' database plus archivelog;

so this basically 1. backup the existing archivelogs, 2. backup the datafiles, 3. backup the new archivelogs that were generated during backing up the datafiles.

sequence 1468 thread 4 was the newly generated archivelogs during backing up the datafiles, I am puzzled how this would lead to the RMAN-06457 error? Can anyone shed some light here?

Thanks in Advance!
-Li

--
http://www.freelists.org/webpage/oracle-l
Received on Mon Feb 01 2010 - 17:34:52 CST

Original text of this message