This content has been marked as final. Show 3 replies
I cannot see any issues with turning on force_logging on the Primary except if you wait too long you might have a sync issue. I would do it ASAP.
Force Logging Feature in Oracle Database [ID 174951.1]
So turning force_logging ON now would not impact the setup of standby database using hotbackup from pre force_loging ON period?
Would the archive logs handle all the changes taken place in between?
Thanks for the help.
No it won't because the hot backup is a copy period. So do it ASAP and the Archive will handle the rest.
So your hot backup is the Standby copy ( exact copy ). Just make sure forced logging is on and the archive with keep the data in sync.
If you delay then you are up the creek without a paddle as NOLOGGING actions are bound to occur and then the Standby data will not match the Primary.
If you have doubts your best option is to roll the standby forward using RMAN Incremental Backups :