Errors on Duplicate for stanby

From: <ewertonsalles_at_gmail.com>
Date: Fri, 22 May 2009 23:44:01 -0700 (PDT)
Message-ID: <1dc45e5e-7999-47f7-b527-dacf6ea8cbd0_at_c9g2000yqm.googlegroups.com>



Hi All,
I'm having some trouble to duplicate a database (standby) to other node.
I understood by this error messages that the archivelogs being asked were not backup by rman on the primary node, so I'm doing this and sending to stanby node.
They were already in the stanby server but rman was not using them to recover.
If someone can confirm or explain this behavior.

Thank you



backup on the primary was:

backup device type disk format '/rman01/...' database plus archivelog;
backup device type disk format '/rman01/....' current controlfile for standby;


Errors on the standby after duplicate:

{

allocate auxiliary channel disk device type disk format ' / rman01/ ...' ;
duplicate target database for standby dorecover; }
....
....
contents of Memory Script:
{

   set until scn 8632227162;
   recover
   standby
   clone database
    delete archivelog
   ;
}
executing Memory Script

executing command: SET until clause

Starting recover at 22-MAY-09

starting media recovery

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: '/u01/oradata/EPSPDG1/epsp_system01.dbf'

released channel: disk1
released channel: disk2
RMAN-00571:



RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS

RMAN-00571:
RMAN-03002: failure of Duplicate Db command at 05/22/2009 13:29:02
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 3 seq 18629 lowscn 8631733788
found to restore
RMAN-06025: no backup of log thread 2 seq 21785 lowscn 8630576830 found to restore
RMAN-06025: no backup of log thread 2 seq 21784 lowscn 8629360241 found to restore
RMAN-06025: no backup of log thread 2 seq 21781 lowscn 8626784076 found to restore
RMAN-06025: no backup of log thread 2 seq 21780 lowscn 8625765588 found to restore
RMAN-06025: no backup of log thread 1 seq 27414 lowscn 8630576788 found to restore
RMAN-06025: no backup of log thread 1 seq 27413 lowscn 8629360012 found to restore
RMAN-06025: no backup of log thread 1 seq 27412 lowscn 8629349808 found to restore
RMAN-06025: no backup of log thread 1 seq 27411 lowscn 8628927237 found to restore
RMAN-06025: no backup of log thread 1 seq 27410 lowscn 8627295971 found to restore
RMAN-06025: no backup of log thread 1 seq 27409 lowscn 8625765846 found to restore
RMAN-06102: no channel to restore a backup or copy of log thread 3 seq 18628 lowscn 8631120934
RMAN-06102: no channel to restore a backup or copy of log thread 3 seq 18627 lowscn 8630576690
RMAN-06102: no channel to restore a backup or copy of log thread 3 seq 18626 lowscn 8629887408
RMAN-06102: no channel to restore a backup or copy of log thread 3 seq 18625 lowscn 8629360265
RMAN-06102: no channel to restore a backup or copy of log thread 3 seq 18624 lowscn 8629349987 Received on Sat May 23 2009 - 01:44:01 CDT

Original text of this message