For better separation of duty, Oracle Database now provides an Oracle Data Guard-specific administration privilege, SYSDG, to handle standard administration duties for Oracle Data Guard. This new privilege is based on the least privilege principle. The SYSDBA privilege continues to work as in previous releases.
Primary database redo can now be cascaded in real time as it is being written to the standby redo log file at a physical standby or a far sync instance. This feature is known as real-time cascading and it requires a license for the Oracle Active Data Guard option.
Far Sync Instance
A new type of remote Oracle Data Guard destination, called a far sync instance, accepts redo from the primary database and then ships that redo to other members of the Oracle Data Guard configuration.
Maximum Availability mode now allows the LOG_ARCHIVE_DEST_n attributes SYNC and NOAFFIRM to be used together. This enables asynchronous standby database to be deployed at a further distance from the primary site without increasing the impact on primary database performance.
Other Notable Changes are
- Online relocation of datafiles for standby/primary database
- Support for GDS in the dataguard broker.
- When you perform a switchover from an Oracle RAC primary database to a physical standby database, it is no longer necessary to shut down all but one primary database instance.
- The USING CURRENT LOGFILE clause is no longer required to start real-time apply.
- You can create a physical standby of a multitenant container database (CDB)