duplicate database for standby fails [message #266713] |
Tue, 11 September 2007 08:23 |
vdoshi007
Messages: 2 Registered: July 2007 Location: USA
|
Junior Member |
|
|
All,
I have a RAC standby database that exists but is very far behind the RAC primary and am trying to recreate the standby database.
I did a backup of the primary database and created a standby control file using
RMAN>backup device type disk format 'dir' current controlfile for standby;
I shutdown the existing standby database, created a new spfile without the controlfile names in it and did a nomount of the standby database.
Ran the duplicate target database command
RMAN> duplicate target database for standby;
Starting Duplicate Db at 11-SEP-07
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=312 instance=dgaglk1 devtype=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: sid=311 instance=dgaglk1 devtype=DISK
allocated channel: ORA_AUX_DISK_3
channel ORA_AUX_DISK_3: sid=310 instance=dgaglk1 devtype=DISK
allocated channel: ORA_AUX_DISK_4
channel ORA_AUX_DISK_4: sid=309 instance=dgaglk1 devtype=DISK
contents of Memory Script:
{
restore clone standby controlfile;
sql clone 'alter database mount standby database';
}
executing Memory Script
Starting restore at 11-SEP-07
using channel ORA_AUX_DISK_1
using channel ORA_AUX_DISK_2
using channel ORA_AUX_DISK_3
using channel ORA_AUX_DISK_4
channel ORA_AUX_DISK_1: restoring control file
ORA-19625: error identifying file /u001/app/oracle/product/10.2/db/dbs/standby_dgaglk.ctl
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-19600: input file is control file (/u001/app/oracle/product/10.2/db/dbs/standby_dgaglk.ctl)
ORA-19601: output file is control file (+FRA)
failover to previous backup
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /u002/oracle/dataguard/agilink/h7io555v_1_1
ORA-19870: error reading backup piece /u002/oracle/dataguard/agilink/h7io555v_1_1
ORA-19505: failed to identify file "/u002/oracle/dataguard/agilink/h7io555v_1_1"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
failover to previous backup
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /u002/oracle/dataguard/agilink/h3io4ugf_1_1
ORA-19870: error reading backup piece /u002/oracle/dataguard/agilink/h3io4ugf_1_1
ORA-19505: failed to identify file "/u002/oracle/dataguard/agilink/h3io4ugf_1_1"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
failover to previous backup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/11/2007 12:43:32
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
It seems that RMAN is looking for another standby controlfile that I had created before and not the most recent standby controlfile...
Can anyone help me why is that and how do I get around this error?
Thanks
|
|
|
|
|
|
|
|
Re: duplicate database for standby fails [message #352189 is a reply to message #266713] |
Mon, 06 October 2008 09:49 |
Checkpoint
Messages: 6 Registered: October 2008
|
Junior Member |
|
|
Hey folks,
I know the thread's a bit old, but it matches my current condition. I created one standby controlfile -- then a few days later created a newer one.
Trying to run the duplication process, but it keeps trying to look for the older version of the standby controlfile (which I've deleted). I've checked paths and permissions; I've placed a copy of the new file on both primary and standby servers and duplicated the exact structure -- what am I missing here?
I'd post the exact error message, but rather than take up the space you can see the original thread -- it's identical to that log when it blows up.
Any suggestions?
Many thanks in advance!
|
|
|
|
|
|
|