Database Software

Hi all,

I have set our primary and standby archive destination states to defer due to network issues.

We are running over a lower bandwidth back up link so shipping is impacting normal users.

The network capacity means it is not possible to set transport services off in DataGuard manager so I deferred the shipping at the database level which usually works.

For some reason this time though the database/Dataguard has sensed this and started to use the standby_archive_dest parameter for its new location and is continuing to ship and resolve the gaps even though the primary is set to defer for the service to our standby.

Any thoughts on why the standby_archive_dest is now being used and how I can shut that shipping off other than shutting down the standby database which we do not want to do?

Cheers

Steve