Data Guard
Oracle Data Guard Redo Decryption for Hybrid Disaster Recovery Configurations
Oracle Data Guard now provides the capability to decrypt redo operations in hybrid cloud disaster recovery configurations where the cloud database is encrypted with Transparent Data Encryption (TDE) and the on-premises database is not.
Hybrid disaster recovery (DR) with Data Guard is now more flexible and easy to configure. Hybrid disaster recovery for the Oracle AI Database allows you to expand outage and data protection to take advantage of the automation and resources of Oracle Cloud Infrastructure (OCI). By enabling the ability to quickly configure disaster recovery in OCI, even in cases where on-premises databases might not already be encrypted with Transparent Data Encryption (TDE), the steps required to configure hybrid disaster recovery environments and prepare on-premises databases for a DR configuration with cloud databases in OCI have been greatly reduced.
JSON Output for the Data Guard Command-Line
The Data Guard command-line (DGMGRL) now presents output in JSON format. Users can choose this structured format to make data straightforward to process and reuse, moving beyond plain-text output.
JSON-formatted output enables easy integration with automation tools and scripting environments. Customers can parse results programmatically, connect workflows, and boost productivity by eliminating manual handling of plain-text results.
Per-PDB Data Guard Integration Enhancements
The new Oracle Data Guard per Pluggable Database architecture provides more granular control over pluggable databases, which can now switch and fail over independently. The enhancements to the Oracle Data Guard per Pluggable Database include simplified setup and validation, automatic addition of temporary files, improved management and housekeeping, and target pluggable databases open for query off-loading (Real-Time Query feature at the pluggable database level).
You can rely on Data Guard protection while keeping the flexibility and high consolidation rates that the multitenant architecture offers, reducing operational costs.
Restrict Switchover and Failover to a List of Databases
The Oracle Data Guard broker property PrimaryDatabaseCandidates lists which databases can become primary during switchover or failover. This property enforces finer control over role transitions, helping customers prevent the activation of undesired databases. An optional override mode lets you perform an emergency failover without changing the policy.
This feature increases control and predictability in managed database environments. Organizations can enforce business, regulatory, or operational rules about which databases may act as the primary, reducing risk from operational errors. The override command ensures critical failover remains possible during emergencies, while surfacing appropriate warnings.