Migrating from HP Oracle Database Machine to Sun Oracle Database Machine 11.2 using Data Guard (Doc ID 1055938.1)

Last updated on FEBRUARY 04, 2020

Applies to:

Purpose

 ===================================

This write-up describes two methods that can be used to perform a database upgrade from the HP Oracle Database Machine to the Sun Oracle Database Machine. The method you choose to perform database upgrades can vary depending on the following considerations:

• Downtime required to complete the upgrade
• Setup time and effort required before the downtime
• Temporary additional resources necessary (for example, disk space or CPU)
• Complexity of the steps allowed to complete the upgrade
• Data Type restrictions
• Database release of the source

Case 1: Migration from HP Oracle Database Machine running 11.1 software to Sun Oracle Database Machine 11.2 with less than 5 minutes downtime

Use Data Guard SQL Apply or a transient logical standby database to upgrade a database with minimal downtime. Additional procedures must be considered when using the rolling upgrade procedure described in Oracle Data Guard Concepts and Administration since Oracle Database 11.1 is not compatible with 11.2 Exadata Server software.
The high level steps are:

1. On the 11.1 Database Machine that is running the primary database create a logical standby or transition a physical standby to a logical standby for the upgrade procedure
2. Copy the logical standby database to the Sun Oracle DBM
3. Upgrade the logical standby to 11.2
4. Change database extent sizes according to Exadata best practices as required
5. Redirect primary redo to the newly upgraded logical standby
6. Perform a Data Guard switchover

Case 2: Migrating from HP Oracle Database Machine running 11.1 software to Sun Oracle Database Machine 11.2 with less than 2 hours of downtime

If additional downtime can be tolerated (less than 2 hours),insufficient space on HP Oracle Database Machine for standby database, , or the application uses unsupported data types for logical standby approach, then perform the upgrade by restoring a physical standby to the 11.2 DBM and activating the standby.
The high level steps are:

1. Use RMAN duplicate create a physical standby on the 11.2 DBM
2. Manually copy archive logs to the 11.2 DBM Recover archive logs to bring standby forward When the standby is caught up except for the current logs, shutdown the application, restart the database in exclusive mode, archive log current, copy the remaining the logs and apply. Depending this step, your downtime will vary. Upgrade and recompilation time vary per application.
3. Activate the standby, open the database, and perform the upgrade.

Case 3: Migrating from HP Oracle Database Machine running 11.2 software to Sun Oracle Database Machine 11.2 with less than 5 minutes of downtime

1. Using RMAN duplicate create a physical standby on the 11.2 DBM
2. Setup Data Guard transport and real time apply. Ensure the standby recovery is caught up.
3. Perform a Data Guard switchover and application client failover

Details