Oracle 21c introduces the ability to improve the performance of queries executed on the read-only active Standby Database by enabling the use of the Result Cache feature to store query results for recurring use- so not just enabled on the Primary database, but the Standby database as well. The new Oracle 21c clause RESULT_CACHE (STANDBY […]
A new feature in Oracle 21c is the ability to create a Data Guard Far Sync Instance via Data Guard Broker. The DGMGRL command CREATE FAR_SYNC automates the entire process of creating the Far Sync database instance for a Data Guard Configuration. It internally runs the RMAN DUPLICATE TARGET DATABASE FOR FARSYNC command and creates […]
The Data Guard Broker PREPARE DATABASE FOR DATA GUARD command configures a database to be used as a Primary Database in a Data Guard Broker configuration. It enables and sets a number of database parameters like LOG_BUFFER, DG_BROKER_START, STANDBY_FILE_MANAGEMENT, DB_BLOCK_CHECKSUM etc. It also enables FLASHBACK and ARCHIVELOG for the database and creates the Standby Redo […]
In a previous post we have looked at some of the new features for the Data Guard Broker Observer in 19c like the ability to run the Observer in OBSERVE ONLY mode as well as some other features like multiple Observers and multiple failover target standby databases. In this note we look at how Master […]
One of the new features introduced in Oracle 19c is to run the Data Guard Broker Observer in OBSERVE ONLY MODE. Without impacting the current Data Guard configuration, we can test how various fast start failover scenarios would work in our environment before actually enabling the change to the Observer configuration. The Data Guard Broker […]
One of the new Data Guard Broker features introduced in Oracle 12c Release 2 was the ability to set multiple Fast Start Failover (FSFO) targets with the broker determining which was the ideal Data Guard standby database to perform a failover operation to. This was configured via the property FastStartFailoverTarget. In this example we have […]
This note outlines the steps to create an Oracle 19c Container Database via DBCA and then use the RMAN DUPLICATE command to create an Oracle 19c physical standby Container Database. Download the note ….
This note illustrates the steps required to upgrade an Oracle 12c Data Guard Primary and Standby database configuration to Oracle 19c and the convert the Oracle 19c non-CDB Primary/Standby databases to an Oracle 19c Pluggable Databases hosted in an Oracle 19c Data Guard Container CDB. Download the note ….
Oracle 12c Release 2 introduced the ability to execute a DGMGRL command script via the @ command as well as the ability to call host operating system commands via the HOST command. A number of new Data Guard Broker features have been introduced in Oracle 18c like the DGMGRL commands like VALIDATE DATABASE SPFILE, VALIDATE […]
One of the new features in Oracle 19c is that either when a flashback or point-in-time recovery is performed on the primary database in an Oracle Data Guard configuration, the same operation is also performed on the standby database as well. Following a flashback or PITR operation, the primary database is then opened with the […]
New in Oracle 12c Release 2 is the ability for scripts to be executed through the Data Guard broker DGMGRL command-line interface very similar to like say in SQL*Plus. DGMGRL commands, SQL commands using the DGMGRL SQL command, and OS commands using the new HOST (or !) capability can be bundled into a script file […]
One of the real nice new features in Oracle 12c Release 2 (22.214.171.124) is the ability to create an Oracle Data Guard Standby Database using DBCA (Database Configuration Assistant). This really does simplify the process of creating a standby database as well and automates a number of steps in the creation process which were earlier […]
This note describes the procedure of creating an Oracle 126.96.36.199 Data Guard Physical Standby database with a two-node Real Application Cluster (RAC) Primary and Standby database on an Oracle Exadata X5-2 eight rack. The procedure will use RMAN for the creation of the Physical Standby database and will use the DUPLICATE FROM ACTIVE DATABASE method […]
Some times we need to have an exact replica of the production database data to urgently test an issue encountered in production. If the production database is very large having a clone process running on the production server or taking a fresh full database backup just for the clone is also not desirable as well […]