Hello All,
When performing duplication of database with rman connected to the Source received the following error
upg db009 oracle102 > rman target sys/sys@upg auxiliary /
Recovery Manager: Release 10.2.0.4.0 - Production on Tue Jun 29 17:26:47 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: UPG (DBID=1899709187)
connected to auxiliary database: STAGE (not mounted)
RMAN>
RMAN> run {
SET UNTIL SCN 379298362;
allocate auxiliary channel t1 type disk;
allocate auxiliary channel t2 type disk;
allocate auxiliary channel t3 type disk;
switch datafile all;
duplicate target database to stage;
}2> 3> 4> 5> 6> 7> 8>
executing command: SET until clause
allocated channel: t1
channel t1: sid=1587 devtype=DISK
allocated channel: t2
channel t2: sid=1586 devtype=DISK
allocated channel: t3
channel t3: sid=1585 devtype=DISK
Starting Duplicate Db at 28-JUN-10
released channel: t1
released channel: t2
released channel: t3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/28/2010 14:58:18
RMAN-06457: UNTIL scn (379298362) is ahead of last scn in archived logs (379296482)
RMAN> exit
Issue and Verification
On Checking the Source DB,found that the last scn was older than what I have specified in run block of RMAN.Hence issued checkpoint connected to the source DB.
SQL> select thread#, status, enabled, checkpoint_time, checkpoint_change# from v$thread;
THREAD# STATUS ENABLED CHECKPOINT_TIME CHECKPOINT_CHANGE#
---------- ------ -------- ------------------ ------------------
1 OPEN PUBLIC 28-JUN-10 379296482
SQL> alter system checkpoint;
System altered.
SQL> select thread#, status, enabled, checkpoint_time, checkpoint_change# from v$thread;
THREAD# STATUS ENABLED CHECKPOINT_TIME CHECKPOINT_CHANGE#
---------- ------ -------- ------------------ ------------------
1 OPEN PUBLIC 28-JUN-10 379299681
SQL>
Now re-started the duplication and it completed successfully.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment