Data Guard Demonstrations


Data Guard Protection from Lost-Write Corruption
This demonstrates how Data Guard provides unique protection from data corruption caused by lost writes. A data block lost write occurs when an I/O subsystem acknowledges the completion of the block write, while in fact the write did not occur in the persistent storage. When a primary database lost write corruption is detected by a Data Guard physical standby database, Redo Apply (MRP) will stop and the standby will signal an ORA-752 error to explicitly indicate a primary lost write has occurred (preventing corruption from spreading to the standby database). For more information on lost write protection and additional ways that Oracle Data Guard can prevent, detect, or automatically repair data corruption see My Oracle Support Note 1302539.1


Data Guard Broker
This demonstrates capabilities in Oracle Database for easily creating a Data Guard Broker configuration, using the Broker to validate that Data Guard is functioning correctly, and performing basic management tasks using the Data Guard Broker command line interface DGMGRL. Management tasks demonstrated include switchover and automatic restart of database services on the new primary database, failover and automatic restart of database services and publication of FAN events (Fast Application Notification) to inform OCI and JDBC clients that a failover has occurred, and easy reinstatement of the original primary as a synchronized standby of the new primary database. After downloading and starting the demonstration, click on the menu bar at the bottom of the page to manually advance through each of the operations. Click here Data Guard Broker Documentation.


Data Guard Fast-Start Failover - Automatic Database Failover for High Availability in an MAA Configuration
This demonstrates automatic failover between an Oracle RAC primary database and an Oracle RAC standby database in an MAA configuration. Following failover, the original primary is automatically reinstated as a standby database, and automatically resynchronized with the new primary database. High availability and maximum data protection are achieved during a site failure with zero manual intervention required. Click on the demo link to download the demo and run on your desktop, use the control at the bottom of the demo screen to initiate demo. Click here for the accompanying presentation that includes the production experiences of with Data Guard Fast-Start Failover .


Database Rolling Upgrades using Physical Standby Databases - Oracle Database
This demonstration shows how to convert a physical standby to a transient logical standby database and implement a rolling database upgrade with minimal downtime. The standby database will revert to its original state as a physical standby database when the upgrade is complete - through use of the KEEP IDENTITY clause. This benefits physical standby users who wish to execute a rolling database upgrade without investing in redundant storage and effort that would otherwise be needed to create a logical standby database. This process utilizes SQL Apply in a very limited way - as the method to resynchronize the standby database following its upgrade to the new release and to maintain synchronization until it first assumes the primary production role.  The original primary database (now a standby) is then mounted in a new Oracle home and upgraded to the new release via the redo stream using Redo Apply (the physical standby apply process). Click here for MAA best practices and information on a script available on My Oracle Support that further simplifies the transient logical rolling upgrade process.


Extended Datatype Support for SQL Apply
Extended Datatype Support (EDS) enables SQL Apply and Streams to replicate changes to tables that contain datatypes not natively supported from one database to another.  Without EDS, only the tables that contain natively supported datatypes can be replicated. Click here for more details in the accompanying MAA best practices paper.

  demo Online Patching with Oracle Database

This demonstrates a patch being applied online to Oracle Database in order to achieve continuous and uninterrupted database service. The demo automatically runs in your browser when you click on the demo link - use the control's at the bottom of the demo screen if you prefer to manually advance the demo .   Click here for the accompanying presentation of MAA best practices and capabilities included with the Oracle Database to minimize planned downtime during software upgrades.

In-Memory Replay Banner