Joords Oracle DBA blog

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.

In Oracle 12.2 there is a new feature added to the  dbca   commando. One of the new feature is creating a standby database [ DBCA Standby Creation ].   At the Standby server install the Oracle Software and start a listener. And start the command " dbca -silent - createDuplicateDB - createAsStandby ". This dbca command will create a standby database , and  nothing more. Get the new standby database operational as a standby database additional steps must be performed. The steps are conform the steps  for building a standby databases . Lets play with the DBCA option for creating a standby database.

Make log shipping to work without copying password file from primary to physical standby when changing sys password on primary? Sometimes in a dataguard configuration the user SYS must be changing because of security policies. This results in a failed redolog shiping problem as describe by Harald van Breederode " Password file maintenance in a Data Guard environment " In this blogpost Harald was also mentioning redo transport authentication by an other Oracle user then SYS. To use an other Oracle user then SYS for redo transport authentication you have to do the following steps: In Oracle 11gR1 Oracle has introduced an new init.ora parameter called REDO_TRANSPORT_USER,  with this parameter Oracle can activate the redo transport authentication to be done by an other user then the default  user SYS.