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.
Automatic Block Repair in Active Data Guard per Pluggable Databases
Active Data Guard per Pluggable Database automatically repairs corrupt data blocks at the pluggable database (PDB) level by using the good copy from the standby pluggable database, in the same way Active Data Guard does for the whole Container Database (CDB). When corruption is detected in a PDB, the database replaces bad blocks in real time, without user intervention or raising errors to the application.
This feature keeps the applications and users working, even when block corruption strikes. By fixing data block corruption instantly and transparently, this feature cuts downtime and minimizes data loss risk.
Automatic Standby Pluggable Database Instantiation and Standby Redo Log Creation
When adding a pluggable database in Data Guard per Pluggable Database environments, the broker automatically copies datafiles to the standby container database and creates standby redo logs with the proper number and size.
These enhancements streamline Data Guard per Pluggable Database environments and reduce the number of manual operations, minimizing risk of configuration errors.
Configuration and Member Tagging for Oracle Data Guard
Oracle Data Guard Broker lets you assign user-defined key-value tags to configuration members. Tags make it easy to logically group members using details like location, life cycle status, organization, or compliance needs. Choose any naming scheme to match your business processes.
Tagging enables teams to organize configuration members according to business needs. It improves monitoring and management, supports compliance tracking, and helps classify members while reducing operational errors. As a result, teams gain better control over the Data Guard environment.
DML Redirection for Data Guard per Pluggable Database
Data manipulation statement (DML) redirection now also operates at the pluggable database level in Active Data Guard per Pluggable Database environments. This enhancement directs write operations transparently from the standby to the primary pluggable database.
DML redirection transforms the standby pluggable database from a passive replica into an active, high-value asset. Applications can run mixed read and write workloads directly from the standby PDB. As a result, the standby database delivers greater return on investment by offloading more application activity and increasing the flexibility of disaster recovery environments.
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.
TLS Authentication for Redo Transport
Oracle Data Guard enables use of TLS authentication for redo transport connections. Strong external authentication can be used instead of the password file method, removing the need for password file transfers and centralizing management across multiple databases.
Centralized and strong authentication for the redo transport reduces operational risk and strengthens security controls. Organizations gain efficient key management and increased flexibility, especially in complex data replication scenarios, such as GoldenGate downstream capture, by eliminating shared password dependencies. This enhancement fosters stronger security governance and easier compliance.