Joords Oracle DBA blog

FASTSYNC is a new DataGuard capability available with Oracle Database 12c. The FASTSYNC configures redo transport services for this configuration member using the SYNC and NOAFFIRM attributes of the LOG_ARCHIVE_DEST_n initialization parameter. The attribute NOAFFIRM specifies that the standby acknowledge receipt of redo without waiting for the write to the standby redo log file to complete. This mode is only available in maximum availability protection mode . Remark: FASTSYNC transport mode uses the NOAFFIRM attribute of the LOG_ARCHIVE_DEST_n parameter, data loss is possible. The following attributes of LOG_ARCHIVE_DEST_N initialization parameter define the redo transport mode that is used by primary database to send redo to the standby database:

Oracle GoldenGate can run on a machine separate from the source and/or target database server. The setup is called GoldenGate remote capturing and delivery . A creation of a GoldenGate Replicate Hub . On Oracle Databases the remote capture can be a remote integrated capture or downstream capture. For remote delivery can be an integrated delivery, a coordinated delivery or classic delivery. Architect overview GoldenGate Replicatie Hub - Remote Capture and Delivery

Using the RedoRoutes Property for Remote Alternate Destinations within a Dataguard environments. The RedoRoutes property can be used to set up a remote alternate destination so that a terminal Standby Database ( Standby DB, Cascade Standby DB, FarSync DB) can still receive redo data even if the Standby Database from which it was receiving the redo data fails. In this example below we have a primary cdb1 who send his redo data to the farsync instance. The farsync cdb1fs send the redo data to the standby database cdb2. See the instructions for building the dataguard environnment " MaxAvailability DataGuard environment : Adding a far sync instance to the environment ". Is it possible to configure a setup, when the primary database, cdb1, send the redo data directly to standby database CDB2 in a case that the farsync csb1fs is not available.  And when the FAR SYNC instance cdb1fs is operational again the configuration is operational again as designed.