Upgrading the Oracle Application Server 10g (10.1.2|10.1.4) Seeded Database from 10.1 to 10.2

Hi Everyone,

Today I have come across the requirement where one of my client wants to upgrade Oracle Application Server seeded database from 10.1 to 10.2. Main reason for doing the activity was not to use de-supported version of oracle product. We really appreciate the clients concerns.

After doing surfing on Google and oracle Metalink. finally i have found one document which is so much useful for making this activity successful.

For upgrading Oracle Infra database from R1 to R2 check metalink ID : 376689.1 

Below are the steps which we have to follow for oracle Application server seeded Database from R1 to R2.


STEP 1. We have to Install Oracle Database Server 10g Release 2 (10.2.0.1) Database Software Only on the same host as the current Oracle Database Server 10g Release 1 (10.1) which contains the Metadata Repository (MR)

STEP 2. Using the Oracle Database Server 10g Release 2 (10.2) Companion CD, install Ultrasearch in the same ORACLE_HOME just created for the 10.2 RDBMS Software.

NOTE:

·         When prompted for "Select a Product to Install", select middle option "Oracle Database 10g Products 10.2.0.1.0"

·         Install in the same ORACLE_HOME where RDBMS 10g 10.2.0.1 was installed

STEP 3. Run the Database Upgrade Assistant (DBUA) from new 10.2 ORACLE_HOME to upgrade the 10.1 Metadata Repository Database to the new 10.2 version.

NOTE:

• The DBUA will find all available database available to upgrade
  
  Be sure to select the one associated with your MR Database
• You may receive a warning saying that the instance version does not match the dictionary version. It will ask to run the 10.1 ORACLE_HOME/rdbms/admin/catpatch.sql to resolve conflict. For this, shutdown the database and open in upgrade mode.
  
  SQL> STARTUP UPGRADE
  SQL>@$ORACLE_HOME/rdbms/admin/catpatch.sql
  
  After completion of the above, check for Invalid Objects and recompile
  
  SQL>$ORACLE_HOME/rdbms/admin/utlrp.sql
  
  Shutdown the DB 10.1 and restart as normal
  
  SQL> SHUTDOWN
  SQL> STARTUP
  
  

STEP 4. Run netca from new 10.2 ORACLE_HOME/bin and configure a new TNS Listener.

NOTE:

• Can keep the default name, or rename to what is desired.
• Recommend using the same port that was in use by old listener

STEP 5. Copy the tnsnames.ora, sqlnet.ora from source ORACLE_HOME/network/admin
to the destination $ORACLE_HOME/network/admin

STEP 6. Edit the source 10.1 ORACLE_HOME/config/ias.properties and change the Install Type from "Infrastructure" to "Infrastructure_ID".

NOTE: If the source Database is in a non-collocated (MR Only) ORACLE_HOME, then no change is necessary to the ias.properties.

STEP 7. Run the following select statement to verify that no INVALID objects are
within the database.

SQL> select object_name, object_type, owner from dba_objects where status='INVALID';

There should be no invalid objects. If there are, run $ORACLE_HOME/rdbms/admin/utlrp.sql

STEP 8. At this point, the new Oracle Database 10.2 and Listener should be running and may be administered and maintained as normal. The Application Server Infrastructure components can be started using opmnctl startall to check for functionality.

We have to check all the services which are given below:

• From original Infrastructure:
    opmnctl startall
• $ORACLE_HOME/bin/ldapbind -p 389 --> Bind Successful
• Start AS Console from Infrastructure
    emctl start iasconsole
• Start AS Console from any middle-tier
    emctl start iasconsole
• Use AS Console to start all remaining components and test

STEP 9. The following are instructions to apply the 10.2.0.2 Patchset, which was performed during the testing of this upgrade process to ensure proper functionality going forward. Any newer Oracle Database Patchset may be applied.

Do the following

- Stop listener
- Shutdown database
- Stop DBConsole
- Backed up DB
- Unzipped the p4547817_10202_LINUX.zip
   -- Substitute for your platform
- cd to uncompressed Disk1 location and execute runInstaller
- After Patch is applied, startup DB using SQL> STARTUP UPGRADE
- Run $ORACLE_HOME/rdbms/admin/catupgrd.sql
- Check log that was spooled for errors
- Check for invalids and run utlrp.sql
- SQL> SHUTDOWN
- SQL> STARTUP

STEP 10. Restart Infrastructure and Midtier Components

STEP 11. When finished, the datafiles, controlfiles, and dump destination directories and files may still be in the source ORACLE_HOME unless this was moved before to a central location.

It solve clients requirement and concerns, I hope will help you while upgrading oracle application server seeded database from R1 to R2.

I hope it will help you …

Enjoyy working with Middleware.

Regards,

Ajinkya Vichare

ajinkya-vichare.blogspot.com