Loading....

As part of the Release 12.1.3 upgrade project, we upgraded the 11.5.10.2 Apps database to 11gR2 (11.2.0.3) from 10.2.0.4.

Best practice is to seperate database upgrade or any platform migration activites from the actual R12 upgrade project. Many are tempted to use the downtime provided by the business for a R12 upgrade to schedule a 10g to 11g database upgrade as well as in some cases a platform migration or 32 bit to 64 bit conversion all in the same downtime.

From the point of view of availability that is great, but by combining all these activities into one task  it is only going to increase the risk as well as complexity of the actual R12 upgrade.

In our case, we were moving from Solaris to Linux platform as well and we performed the platform migration on the 10g database itself.

Read about it here –https://gavinsoorma.com.au/2012/09/migrating-the-11i-e-business-suite-database-to-linux/

We then pointed the Solaris 11.5.10.2 Apps tier to the 10g database on Linux and then performed another task prior to the R12 upgrade which converting to OATM.

After the OATM was completed, we are now upgrading the Linux 10.2.0.4 database to 11.2.0.3.

Download¬†the note on the 11.2.0.3 database upgrade ….

 

 

 

 

Please follow and like us:

Last Update: June 23, 2020  

October 10, 2012 206 Gavin Soorma
Total 0 Votes:
0

Tell us how can we improve this post?

+ = Verify Human or Spambot ?

Add A Knowledge Base Question !

You will receive an email when your question will be answered.

+ = Verify Human or Spambot ?

, , , , ,

Leave a Comment

Your email address will not be published. Required fields are marked *

*
*

Social media & sharing icons powered by UltimatelySocial
Back To Top

Add A Knowledge Base Question !

You will receive an email when your question will be answered.

+ = Verify Human or Spambot ?