Guenadi N Jilevski's Oracle BLOG

Oracle RAC, DG, EBS, DR and HA DBA BLOG

Implement classic bi-directional DML and DDL replication between two Oracle RAC databases using OGG 11.2 – Download

Implement classic bi-directional DML and DDL replication between two Oracle RAC databases using OGG 11.2 – Download

In the article you will have a look at an example of how to build a classic bi-directional DML and DDL replication between two Oracle RAC databases. The environment consist of a two node Oracle 11.2.0.3 cluster running a source database RACD (11.2.0.3) and a target database RACDB (11.2.0.3) and is described here and here. Examples are based on OGG classic extract method and the data type limitations exist as described in the official OGG documentation here. Integrated extract method reduces data type limitations but requires Oracle database 11.2.0.3 and a database specific bundle patch for Integrated Extract 11.2.x (Doc ID 1411356.1).
For Exadata 11.2.0.3 databases, the EXADATA_11.2.0.3_BP3 patch (11.2.0.3.3) should be used. The patch is available from the support site referencing patch 13556853. For non-Exadata 11.2.0.3 database, you need to apply patch 13560925 which is available on the support site referencing the patch number.

Read online from here or download Implement bi-directional DML and DDL replication between two Oracle RAC 11.2.0.3 databases using OGG 11.2

July 17, 2012 Posted by | oracle | 3 Comments

Implement classic bi-directional DML and DDL replication between two Oracle RAC databases using OGG 11.2

Implement classic bi-directional DML and DDL replication between two Oracle RAC databases using OGG 11.2

In the article you will have a look at an example of how to build a classic bi-directional DML and DDL replication between two Oracle RAC databases. The environment consist of a two node Oracle 11.2.0.3 cluster running a source database RACD (11.2.0.3) and a target database RACDB (11.2.0.3) and is described here and here. Examples are based on OGG classic extract method and the data type limitations exist as described in the official OGG documentation here. Integrated extract method reduces data type limitations but requires Oracle database 11.2.0.3 and a database specific bundle patch for Integrated Extract 11.2.x (Doc ID 1411356.1).
For Exadata 11.2.0.3 databases, the EXADATA_11.2.0.3_BP3 patch (11.2.0.3.3) should be used. The patch is available from the support site referencing patch 13556853. For non-Exadata 11.2.0.3 database, you need to apply patch 13560925 which is available on the support site referencing the patch number.
Continue reading

July 17, 2012 Posted by | oracle | 7 Comments

Configuring datapump extract in Oracle GoldenGate (OGG) 11.2 –Download

Configuring datapump extract in Oracle GoldenGate (OGG) 11.2 -Download

In the article you will have a look at an example of how to configure an additional datapump extract in OGG. How are OGG installation performed and basic classic CDC extract and replicat configured and verified is described here.

The article will cover the following topics

  • What is a data pump extract
  • Example of setting a data pump extract

Read online from here or download Configuring datapump in Oracle GoldenGate

July 9, 2012 Posted by | oracle | Leave a comment

Configuring datapump extract in Oracle GoldenGate (OGG) 11.2

Configuring datapump extract in Oracle GoldenGate (OGG) 11.2

In the article you will have a look at an example of how to configure an additional datapump extract in OGG. How are OGG installation performed and basic classic CDC extract and replicat configured and verified is described here.
Continue reading

July 9, 2012 Posted by | oracle | 3 Comments

Installing Oracle GoldenGate (OGG) 11.2.1.0.1 in an Oracle cluster 11.2.0.3 (ACFS) and configuring a direct load and classic Change Data Capture (CDC) and Data Apply – Download

Installing Oracle GoldenGate (OGG) 11.2.1.0.1 in an Oracle cluster 11.2.0.3 (ACFS) and configuring a direct load and classic Change Data Capture (CDC) and Data Apply – Download

In the article you will have a look at the OGG 11.2.1.0.1 installation and an example of a classic CDC configuration, initial data load and Data apply. The environment is a two node Oracle RAC cluster running Oracle GI 11.2.0.3 and Oracle RAC RDBMS 11.2.0.3 and Oracle RAC RDBMS 10.2.0.5 described here and here. An ACFS mount point /u02 is created to host the OGG installation directory. The source schema and target schemas are as described in the following table. Both RACD and RACDB are two node databases using ASM. This article applies only to OGG using Oracle database as a target and source. For different databases the same OGG concept applies but setup and parameters are different.

You could read online from here or download Installing Oracle GoldenGate (OGG) 11.2.1.0.1 in a Oracle cluster 11.2.0.3 (ACFS) and configuring a direct load and Change Data Capture (CDC) and Data Apply


July 8, 2012 Posted by | oracle | 5 Comments

Installing Oracle GoldenGate (OGG) 11.2.1.0.1 in an Oracle cluster 11.2.0.3 (ACFS) and configuring a direct load and classic Change Data Capture (CDC) and Data Apply

Installing Oracle GoldenGate (OGG) 11.2.1.0.1 in an Oracle cluster 11.2.0.3 (ACFS) and configuring a direct load and classic Change Data Capture (CDC) and Data Apply

In the article you will have a look at the OGG 11.2.1.0.1 installation and an example of a classic CDC configuration, initial data load and Data apply. The environment is a two node Oracle RAC cluster running Oracle GI 11.2.0.3 and Oracle RAC RDBMS 11.2.0.3 and Oracle RAC RDBMS 10.2.0.5 described here and here. An ACFS mount point /u02 is created to host the OGG installation directory. The source schema and target schemas are as described in the following table. Both RACD and RACDB are two node databases using ASM. This article applies only to OGG using Oracle database as a target and source. For different databases the same OGG concept applies but setup and parameters are different.
Continue reading

July 8, 2012 Posted by | oracle | 3 Comments

Using Physical Standby with transient Logical Standby (SQL Apply) for near zero downtime upgrade of two node Oracle RAC database from 11.2.0.2 to 11.2.0.3 – Download

Using Physical Standby with transient Logical Standby (SQL Apply) for near zero downtime upgrade of two node Oracle RAC database from 11.2.0.2 to 11.2.0.3 – Download

In the article you will have a look at an example of using a physical standby database for a near zero downtime upgrade of a two node Oracle RAC database from Oracle 11.2.0.2 to Oracle 11.2.0.3. The cluster configuration is described here. The approach discussed in the article is available from Oracle 11gR1 onwards only and is similar to using a logical standby database for near zero downtime migration discussed here. However, the approach involving a physical standby database starts from an existing physical database that in turn is transitioned temporarily into a transient logical standby database only for upgrade and at the end you have upgraded primary and physical standby databases. For the testing both the primary and standby databases share the same 11.2.0.3 cluster. Furthermore, My Oracle Support Note 949322.1 provides a script physru that will be used that significantly simplifies the upgrade. Also a transient logical standby approach performs only one database migration on the standby site and on the next switchover synchronizes the newly converted physical database(former primary) with the upgraded primary(former standby) whereas the logical standby database performs two upgrades on the logical standby database. Look at the official Oracle documentation here for the enhanced clauses options added in Oracle 11gR1 to the ALTER DATABASE RECOVER TO LOGICAL STANDBY KEEP IDENTITY; that allows a physical standby database to be used for a rolling upgrade by converting it into a logical standby database that keeps the same DB_NAME and DBID as the primary. Oracle documentation states:

You can read online from here or download Using Physical Standby (with transient SQL Apply) for near zero downtime upgrade of two node Oracle RAC database from 11.2.0.2 to 11.2.0.3

July 3, 2012 Posted by | oracle | 1 Comment

Using Physical Standby with transient Logical Standby (SQL Apply) for near zero downtime upgrade of two node Oracle RAC database from 11.2.0.2 to 11.2.0.3

Using Physical Standby with transient Logical Standby (SQL Apply) for near zero downtime upgrade of two node Oracle RAC database from 11.2.0.2 to 11.2.0.3

In the article you will have a look at an example of using a physical standby database for a near zero downtime upgrade of a two node Oracle RAC database from Oracle 11.2.0.2 to Oracle 11.2.0.3. The cluster configuration is described here. The approach discussed in the article is available from Oracle 11gR1 onwards only and is similar to using a logical standby database for near zero downtime migration discussed here. However, the approach involving a physical standby database starts from an existing physical database that in turn is transitioned temporarily into a transient logical standby database only for upgrade and at the end you have upgraded primary and physical standby databases. For the testing both the primary and standby databases share the same 11.2.0.3 cluster. Furthermore, My Oracle Support Note 949322.1 provides a script physru that will be used that significantly simplifies the upgrade. Also a transient logical standby approach performs only one database migration on the standby site and on the next switchover synchronizes the newly converted physical database(former primary) with the upgraded primary(former standby) whereas the logical standby database performs two upgrades on the logical standby database. Look at the official Oracle documentation here for the enhanced clauses options added in Oracle 11gR1 to the ALTER DATABASE RECOVER TO LOGICAL STANDBY KEEP IDENTITY; that allows a physical standby database to be used for a rolling upgrade by converting it into a logical standby database that keeps the same DB_NAME and DBID as the primary. Oracle documentation states:
Continue reading

July 3, 2012 Posted by | oracle | 2 Comments