upgrade Oracle EBS R12.1.1 to 12.1.3

How to upgrade Oracle EBS R12.1.1 to 12.1.3

Here are the complete guidelines to upgrade Oracle Ebusiness Suite to 12.1.3 from 12.1.1. Before upgrade our database version was 11.1.0.7.

Although we have followed the doc Oracle E-Business Suite Release 12.1.3
Readme [ID 1080973.1], we have done some changes in the steps for successful upgrade.

Oracle Apps 12.1.3 upgrade is only possible if your system is in 12.1.1 or upper version. If you have not upgraded your EBS to 12.1.1 version you can follow the following article to do so.

how-to-upgrade-oracle-ebs-r1206-to-1211

Prerequisite Steps

Step 1

At first make some changes in the database parameters for upgrade. You need to set the following parameters using initialization file.

recyclebin=false

_pga_max_size=104857600

_disable_fast_validate = TRUE

Use the following kind of comand to changes the mentioned three parameters.

alter system set "_disable_fast_validate"=FALSE SCOPE=BOTH;

[If you don't change the _pga_max_size to greater than 104857600. You may get the following error during upgrade.

ORA-04030: out of process memory when trying to allocate 822904 bytes

(pga heap,kco buffer)

ORA-07445: exception encountered: core dump [dbgtfdFileWrite()+48]

[SIGSEGV] [ADDR:0xFFFFFFFF7FFC1C88] [PC:0x1063BD2D0] [Address not mapped

to object] []]

For additional information check the Document 761570.1

Step 2

Apply the specific database patches as applicable for your database by following Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade [ID 761570.1] .

[Our oracle inventory was corrupted, so, I have created a local inventory for opatch application and applied the patches. For opatch issues you can check the following articles.

some-common-opatch-application-issue

oracle-inventory-configuration-during

Additionally you can apply the opatch with no_inventory option in this situation.

opatch apply no_inventory]

Step 3

If you are already upgraded to 12.1.1 version, you have already upgraded form tier and web tier. So, no action is required for form and web tier upgrade. But, you can always check the latest doc for form and web tier latest patches.

Main Upgrade Patch Application

Step 4

Download the following two patches from metalink 9239089, 9239090.

Using autopatch utility first apply R12.AD.B.DELTA.3 Patch 9239089. Then apply the main upgrade patch 9239090.

The main patch application has taken more than three days to complete in our environment. Our system is 8 CPU solaris box with 16 GB RAM. The main patch failed two times with error. We have fixed the errors using adctrl utility and resumed the patch application.

Post upgrade steps

Step 5

Apply the following two patches immediately after upgrade 9817770, 9966055.

Step 6

Source the application env file. Then run autoconfig in apps tier.

$ $ADMIN_SCRIPTS_HOME/adautocfg.sh

Now generate the appsutil.zip file.

$ perl /bin/admkappsutil.pl

Copy appsutil.zip file in DB_HOME. Unzip the appsutil.zip file.

After sourcing the database env file run autoconfig in database tier.

Step 7

Now run preclone in db tier first, then in apps tier.

perl adpreclone.pl dbTier

perl adpreclone.pl appsTier

Step 8

Apply the language patch of the main patch 9239090 if applicable in your environment. In our case French was the additional language that is installed in our system. So, we have applied the french version of 9239090 in this step.

Step 9

Do the step 6 and step 7 again after applying language pack. Then, restrat the whole apps tier and database tier.

This step is not mentioned in the upgrade doc. But, if you don't do it your application login page will not open.

Step 10

Login to the Oracle EBS and check the version. Now, start testing individual product.

Reference document

Oracle E-Business Suite Release 12.1.3 Readme [ID 1080973.1]

Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade [ID 761570.1]

Database Initialization Parameters for Oracle Applications Release 12 [ID 396009.1]

Oracle® E-Business Suite Upgrade Guide

-----------------------------------

Issue faced 1

ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column

Check the following url for solution.

http://forums.oracle.com/forums/thread.jspa?threadID=415560&tstart=15