Vinay, August 04, 2025 - 6:33 am UTC
Thanks to attend it.
Yeh, it is RAC on both sites, Primary(2 nodes RAC), Standby(2 nodes, RAC).
I want to update same database on Primary and Standby, same table.
I will be hitting queries on Primary site only, but in case when Primary, due to uncertain reasons down, It should be able to update same table automatically without changing any thing at Standby site.
August 05, 2025 - 2:49 am UTC
If your primary is down, then your standby should now be active no?
That is the role of the standby - to *become* the primary if the primary is lost
DB Architect
A reader, August 05, 2025 - 5:16 am UTC
Hi,
I am trying to configure Primary DB as active only, but in case there is some issue, and for some time Primary is not accessible, application should be able to update in Active Dataguard.
Once Primary becomes available again user would start connecting and updating in Primary again and not in Dataguard.
August 06, 2025 - 3:02 am UTC
If your primary is not accessible, there is no way that any ins/upd/del DML against the Active DataGuard node is possible.
ADG
A reader, August 05, 2025 - 6:16 am UTC
Hello,
"Once Primary becomes available again user would start connecting and updating in Primary again and not in Dataguard."
Unless you failover to standby, it is still in RO mode in which case "updating" the data will not work even if the application can connect to it.
Either you have either failover automatically or manually but essentially the standby will have to become the new Primary and allow RW transactions.
That is essentially what Connor is trying to convey.
August 06, 2025 - 3:01 am UTC
yup