| RMAN DUPLICATE error [message #176267] |
Wed, 07 June 2006 10:04  |
sinistral
Messages: 7
Registered: November 2005
|
Junior Member |
|
|
Oracle 10gR2 (base)
Dataguard, no RAC
no ASM
Performing backups on the physical standby via RMAN. We need to restore our test database, and right now it is equivalent to the production. The DUPLICATE command seemed the best bet. We have controlfile and SPFile both on Auto-backup, and the RMAN on a six day retention with weekly 0 level backups and nightly level 1 cumulative backups.
However, when I run the DUPLICATE it chokes being unable to find a current controlfile nor one in backup, even though we have six days worth of supposedly good (validated) backups. We are not using a catalog, rather the DB controlfile.
The solution to this error is reopen the database and try again. however, the physical standby cannot be opened. It is the standby. Suggestions? What if we move the last backup to the primary database, "register" it there, and try this DUPLICATE?
I have seen nothing on this in my searches, and the Oracle documentation does not address this, though it recommends backup from the Physical Standby.
RMAN-05513 is the error code.
Thanks
|
|
|
|
|
|
|
|
|
|
| Re: RMAN DUPLICATE error [message #176318 is a reply to message #176314] |
Wed, 07 June 2006 19:16  |
sinistral
Messages: 7
Registered: November 2005
|
Junior Member |
|
|
Because I am backing up ON the standby, we are not using a catalog to register databases, and I would prefer not to kill my production database's I/O for 2 plus hours while I create a backup on my production database in order to run this DUPLICATE. I cannot do it from standby without OPENING the standby. The DUPLICATE needs the controlfile, the CURRENT controlfile, and the standby does not have a current.
Can I open a physical standby read only and without ruining it or not?
Will a read only DB have a CURRENT controlfile?
thanks
|
|
|
|
|
|
|
|
| Re: RMAN DUPLICATE error [message #342569 is a reply to message #342561] |
Fri, 22 August 2008 16:59 |
sinistral
Messages: 7
Registered: November 2005
|
Junior Member |
|
|
What I ended up doing was creating a catalog. We run our backups from the physical standby database machine, then run a second backup of just the controlfile (via the same machine) of the open primary machine. That controlfile backup is on the primary box but is still in the catalog as belonging to the database (to the catalog they physcial standby and the primary BD are the same - same ID)
So, cron job does two backups (full/incremental of standby and then controlfile only of primary) and then copies (scp) the controlfile backup to the standby machine from the primary.
Without a catalog, I assume the same could work if you restore the controlfile backup of the primary in the backup machine.
a quickie PL/SQL example:
declare
adev varchar2(500);
aend boolean;
begin
adev := dbms_backup_restore.deviceallocate(NULL);
dbms_backup_restore.restoresetdatafile;
dbms_backup_restore.restorespfileto('outputdirectory/ctl.ctl');
dbms_backup_restore.restorebackuppiece('controlfilebackup_name',
DONE =>aend);
end;
/
Hope this helps someone.
|
|
|
|
| Re: RMAN DUPLICATE error [message #378262 is a reply to message #342569] |
Mon, 29 December 2008 09:37 |
libra.dba@gmail.com
Messages: 1
Registered: December 2008
|
Junior Member |
|
|
how does that work?
i have the backups from the standby. when using RMAN, i connect to the standby database as the target and to the auxiliary instance (not mounted) and issue a duplicate target, it asks for the current controlfile.
Do we have to create a catalog database or we can do it without a catalog also?
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
