Steps required when planning to upgrade Oracle software using a new $O_H location

The steps in this article apply when you want to upgrade your Oracle software using a new $O_H location. (Example upgrade 11.2.0.3 to 11.2.0.4)

When upgrade recreates Oracle Data Dictionary this article doesn't apply, because object and user IDs are overwritten during the upgrade. Setup Wizard must be re-run in such case.  


Problem Details

Problem Statement

What is the correct process to when upgrading Oracle software using a new $O_H location

Applicable Error Code

N/A

Affected Versions

2.7, 2.8

Affected Platforms

All

 


Description

When planning to upgrade the Oracle software using a new $O_H location, make sure the following are done, eg : 11.2.0.3 to 11.2.0.4

Steps Performed

 

  1. Determine the MINE.ORACLE_HOME value using the console:

dbvrep> show oracle 

  • .ORACLE_HOME = /home/u01/app/11.2.0.3/grid 

MINE.ORACLE_HOME = /home/u01/app/11.2.0.3/grid 

  • .ORACLE_SID = 

dbvrep>

 

Old Home:

ORACLE_HOME /home/u01/app/oracle/product/11.2.0.3/dbhome_1

GRID_HOME /home/u01/app/11.2.0.3/grid

New Home:

ORACLE_HOME /u01/app/oracle/product/11.2.0.4/dbhome_1

GRID_HOME /u01/app/11.2.0.4/grid

 

2. Update -MINE.ddc file

memory_set TNS_ADMIN /u01/app/oracle/product/11.2.0.4/dbhome_1/network/admin
memory_set ORACLE_HOME /u01/app/11.2.0.4/grid

 

3. Restart MINE process

 

NOTE:

If OPEN RESETLOGS is used, replicate will not be able to handle it and will have to reconfigure replication from scratch.