This content has been marked as final. Show 5 replies
If it would have been only few archives that were to be registered, then you could use:
But since you say that the archive size is around 17GB, try to catalog the directory containing the archives that you copied on the standby
alter database register logfile '<archive log path>';
Once you register them manually, you can start the MRP on the standby database.
RMAN>catalog start with '<path of the archives that have been copied to standby>';
Hope this helps http://jarneil.wordpress.com/2008/05/16/registering-archive-logfiles-on-a-standby/
To resolve the huge archive gap, You can go for incremental rollforward, You can use link from my blog http://www.oracle-ckpt.com/rman-incremental-backups-to-roll-forward-a-physical-standby-database-2/
As i read your post, It is issue more with Network rather than anything.
What is the redo log file size do you have? However you are using Real-time apply. Then if you once resolve the GAP between primary and standby later only the current redo has to be transferred from primary to standby.
Apart from that, I would suggest to see network tuning, By adjusting SDU/TDU size in Network parameters, So that you can control the size of the data need to send across the network.
For this, I suggest you to review MAA Network best practices document http://www.oracle.com/technetwork/database/features/availability/maa-wp-10gr2-dataguardnetworkbestpr-134557.pdf
Review it and let me know after you performed above changes.
Edited by: CKPT on Feb 28, 2013 9:58 PM
Set LOG_ARCHIVE_DEST_STATE_2='DEFER' on the primary. That will prevent the two databases from communicating with each other while the Standby recovers from the archivelogs that you have copied over.
Once the Standby has completed the catchup or the lag is a very small number of archivelogs, set LOG_ARCHIVE_DSET_STATE_2='ENABLE' on the primary.
Hemant K Chitale
Set LOG_ARCHIVE_DEST_STATE_2 ='DEFER' on the Primary. That will stop the two databases from communicating with each other. You can then have the Standby RECOVER using the Archivelogs that you have copied over.
Once the gap is very low, you can then set LOG_ARCHIVE_DEST_STATE_2='ENABLE' to re-enable gap resolution.
Hemant K Chitale