This content has been marked as final. Show 3 replies
Go to the Primary database and then create "CONTROLFILE FOR STANDBY" and transfer it to the 2nd standby database.
Check this MOS note :
1343515.1 RMAN ACTIVE DUPLICATE WHEN CONNECTED TO STANDBY AS TARGET
Understanding ORA-01671 error during controlfile creation / backup [ID 461121.1]
Thanks for the response.
I did that ("backup current control file for standby") from prim and ftp to standby.
In which case, the duplicate doesn't see the backup that was taken in the primary.
The Primary does not know about the backup triggered from the Local-standby.
Tried "catalog resync from DB_UNIQUE_NAME all" and still, when i run the duplicate command, it tries to find the backup that was triggred from the Primary node.
For folks who may stumble on this thread.
2 hosts - 1 - primary, 2 - local stby
3rd host was being added in the mix.
So, we want to build standby number 3 - DR stby
Aim was to create the DR stby from a backup taken from local stby, W/O affecting primary.
Create backup pieces from local stby (to be made available in DR stby) using "backup device type disk format '/u01/backups' database plus archivelog;"
As mseberg pointed out, take a "backup current controlfile for standby" from primary & make it available in DR stby
startup nomount the DR stby
restore controlfile in DR from step2
catalog the backup taken in step 1
Run the duplicate command from DR as usual, connecting to the primary as target and the DR as auxiliary