Guenadi N Jilevski's Oracle BLOG

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

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