Mahir M. Quluzade | Oracle Blog

Oracle Database 11g  Release 1 onward new package - DBMS_DG. Package contains a procedure  INITIATE_FS_FAILOVER, yet. This procedure for using  to specify a condition string that, when encountered by an application, allows the application to request the primary database to immediately invoke a fast-start failover. Syntax DBMS_DG.INITIATE_FS_FAILOVER (condstr IN VARCHAR2) RETURN BINARY_INTEGER; condstr - parameter Specifies the condition string for which a fast-start failover should be requested. If no condition string argument is supplied, the default string of "Application Failover Requested" will be logged in the broker log file and in the database alert log of the primary database. There are conditions detectable by applications running outside of the Oracle database that may warrant the Oracle Data Guard broker to perform a fast-start failover. Because the range of possible conditions is virtually unlimited, it is left to the applications to determine whi

When you need safely remove broker-managed Data Guard Configuration then, oracle recommend following steps… You know dg_broker_start parameter is TRUE and data guard configuration information contains in broker configuration files dg_broker_config_file1, dg_broker_config_file2 with broker-managed Data Guard Configuration. Following steps I use on my test machines witch is running on Oracle Virtual Box. I captures video on this machines, too. Primary and Standby Database running on Oracle Linux Server 6.2 and installed Oracle Database 11g Release 2 (11.2.0.3). DG – is my breoker-managed Data Guard configuration. admdb is primary database, stldb – is standby database. DGMGRL> show configuration Configuration - dg Protection Mode: MaxPerformance Databases: admdb - Primary database stldb - Physical standby database Fast-Start Failover: DISABLED Configuration Status: SUCCESS Archive log destinations like as SQL> show parameter log_archive_dest_ NAME

I’ll be speaking at Azerbaijan Oracle User Group II Meeting on July 28th at Qafqaz University.  As expected, I’ll talk about   " Different   operating systems  in same Data Guard configuration" Here’s the speakers and subjects: Different operating systems in same Data Guard configuration -  Mahir M. Quluzade Oracle Database Resource Management  –  Javid Hasanov New Features Oracle 11g PL/SQL -    Ramin Orujov More info (In Azerbaijani) :  http://www.azeroug.org/?p=40   Waiting you to Azerbaijan Oracle User Group II  Meeting

Note: To use the Oracle Data Guard cascading redo transport destination feature described in this video, you should be using Oracle Database 11g Release 2 (11.2.0.2). Releases prior to 11.2.0.2 have several limitations for this feature that are not present in release 11.2.0.2. *** We are know usually in data guard configurations standby databases receives primary database generated redo indirectly from  primary. A cascaded redo transport destination receives primary database redo indirectly from a standby database rather than directly from a primary database. A standby database that cascades primary database redo to one or more cascaded destinations is known as a cascading standby database. Cascading offloads the overhead associated with performing redo transport from a primary database to a cascading standby database. A cascading standby database can cascade primary database redo to up to 30 cascaded destinations, each of which can be a physical, logical, or snapshot