Guenadi N Jilevski's Oracle BLOG

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

Using Logical Standby (SQL Apply) for near zero downtime upgrade of two node Oracle RAC database from 10.2.0.5 to 11.2.0.3 -Download

In the article you will have a look at an example of using a logical standby database, also known as SQL Apply, to perform a near zero downtime upgrade of a two node Oracle RAC database from version 10.2.0.5 to version 11.2.0.3. The two node cluster configuration is described here in detail. For the testing both primary and standby databases share the same Oracle GI cluster. Earlier I have upgraded the cluster to 11.2.0.3 and installed Oracle RDBMS 11.2.0.3 binaries on each node. In the article a physical standby database will be build and converted to a logical database that will be used for the upgrade. Each node has a separate non-shared $OH for the GI and RDBMS versions installed. The table below summarizes some environment details used in the article.

Download the article  Using Logical Standby (SQL Apply) database for near zero downtime while upgrading 2 node RAC database from 10.2.0.5 to 11.2.0.3_1 or read online from here

June 26, 2012 Posted by | oracle | 3 Comments

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

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

In the article you will have a look at an example of using a logical standby database, also known as SQL Apply, to perform a near zero downtime upgrade of a two node Oracle RAC database from version 10.2.0.5 to version 11.2.0.3. The two node cluster configuration is described here in detail. For the testing both primary and standby databases share the same Oracle GI cluster. Earlier I have upgraded the cluster to 11.2.0.3 and installed Oracle RDBMS 11.2.0.3 binaries on each node. In the article a physical standby database will be build and converted to a logical database that will be used for the upgrade. Each node has a separate non-shared $OH for the GI and RDBMS versions installed. The table below summarizes some environment details used in the article.

Continue reading

June 26, 2012 Posted by | oracle | 1 Comment