Following the deprecation of the Data Guard Association resource model for Exadata Database Services in Oracle AI Database 26ai and Oracle Database 19c, Oracle E-Business Suite (EBS) Business Continuity procedures have been updated to support the newer Data Guard Group resource model and APIs for standby database creation and role transitions.

For additional details, refer to the announcement “Deprecated Data Guard Association APIs” (February 5, 2026) in the Announcements section of the OCI Console. You can also consult MOSFS Article KB171317, Deprecated Data Guard Association APIs (February 2026).

Note: EBS currently supports one standby database per environment. Support for multiple standbys is being considered for a future release—stay tuned for updates.

Updated Documentation

Our EBS Business Continuity documentation has been updated to reference OCI guidance for provisioning standby databases using the Data Guard Group model. The appropriate procedure depends on your database release and cloud service.

Oracle AI Database 26ai

Oracle Database 19c

Existing Data Guard Association Configurations

If you have already implemented EBS Disaster Recovery using the Data Guard Association model, you should plan to transition to the Data Guard Group model.

See Appendix D: Switch to Data Guard Group Resource Model in MOSFS articles KA1258, KA1259, KA1263, and KA1252 for detailed instructions.

Note: The Data Guard resource model conversion is a simple, non-disruptive metadata change. However, we strongly recommend validating your configuration by performing failover and failback testing after the switch.

References

Related Articles