When performing duplication using RMAN I recieved the following message and duplication came out with errors.
On researching found that the values for parameters 'db_file_name_convert' and 'log_file_name_convert' was not set correctly.
The reasons being last time when duplication was performed the DBA used a different Database as source and the values for 'db_file_name_convert' and 'log_file_name_convert' were still pointing to the previous source database mount points.
So this time without checking or modifying the values the DBA started the duplication and received the above error message.
To fix it
Stop the database,change the values for 'db_file_name_convert' and 'log_file_name_convert' to the correct source Database values and then restart the duplication.
Showing posts with label rman. Show all posts
Showing posts with label rman. Show all posts
Thursday, August 12, 2010
Tuesday, June 29, 2010
RMAN Duplication - UNTIL scn (.......) is ahead of last scn in archived logs (........)
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.
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:
Posts (Atom)