You must complete the following steps in order to upgrade from Oracle E Business Suite (EBS) 12.1.1 to 12.1.3.

1. Download Patch 9239030. Unzip patch in a directory - say /u01/patches. Now make sure you give execute permissions on this directory. To be on safe side I simply use the following command:

chmod 777 -R /u01/patches

2. Now open a new terminal window. Setup Application Tier environment. (for more info see How to setup environment for Application Tier at linux terminal?)

3. Shutdown all application services under Application Tier (for more info see How to stop Application Tier in Oracle E Business Suite?)

4. Bring instance in Maintenance mode using adadmin utility (for more info see How to use adadmin utility for enabling maintenance mode?)

5. As a prerequisitie of Patch 9239030, you must first download and apply Patch R12.AD.B.DELTA.3

6. Now open a new terminal window. Setup Application Tier environment. (for more info see How to setup environment for Application Tier at linux terminal?)

7. Using 'adpatch' utility apply patch 9239030. This is a mega patch and can take up anywhere from 12-24 hours (depending upon the number of CPU's your server have). (for more info see How to use adpatch utility to apply a patch?)

8. In my case, there were several errors thrown by adpatch. These are described below section 'Errors thrown while applying patch'.

9. After fixing the errors, you must restart the failed worker through 'adctrl' utility. (for more info see How to use adctrl utility to restart failed worker in patch application?)

10. After applying the patch, change the disable the instance 'maintenance mode' using 'adadmin' utility. (for more info see How to use adadmin utility for enabling maintenance mode?)

11. Since there are no post-patch application steps for Financials, Procurement or SCM (with the exception of HRMS related patches), start your Application Tier.(for more info see How to start Application Tier?)

12. Login into Oracle Applications. You will now see several new changes, notably the OA page after login is more user friendly (with the option of expanding or collapsing menu items).

13. Test your patch application.

14. I did not face any issues in terms of login or navigating into Oracle Applications or opening the Oracle Application Developer Forms.

15. I did face an issue in opening a OA Form and decided to upgrade to the latest RUP patch 13984450.

 

Important: Retrieving Error Files for 'adpatch' errors and Failed Worker error files (see here for more info Where to find Patch Error and Failed Worker error files?)

 

Errors Faced while applying patch 9239030

ERROR-1. Error while linking FEMCCE module.

An error occurred while relinking application programs.

make: *** [/u01/apps/EBS12/apps/apps_st/appl/fem/12.0.0/bin/FEMCCE] Error 1
Done with link of fem executable 'FEMCCE' on Fri Aug 31 01:24:33 NZST 2012
 
Relink of module "FEMCCE" failed.

SOLUTION - The solution is best described under Oracle Support Note [ID 1303269.1]

 

ERROR-2. Error while executing file for 

 ACTIVITY 'POWFPOAG/BUILD_EXPENSE_DEST_CHARGE_ACC' iwferr:
  - 1602: Could not save.
  - 1400: Could not save to database. MODE=UPGRADE EFFDATE=<null>
  - 1404: Please first load this entity or check protect and custom level of ACTIVITY 'POWFPOAG/IS_EAM_JOB'.

/u01/apps/EBS12/apps/apps_st/appl/fnd/12.0.0/bin/WFLOAD &ui_apps 0 Y UPGRADE @PO:patch/115/import/US/poxwfpag.wft
Log filename : /u01/apps/EBS12/apps/apps_st/appl/admin/VIS/log/l5811192.req


Report filename : /u01/apps/EBS12/apps/apps_st/appl/admin/VIS/out/o5811192.out
Oracle Workflow Definition Loader 2.6.4.0.

Activity 'FND_FLEX_ABORT_GENERATION-1' has no out transition 

SOLUTION

1. Open the patch Driver file u9239090.drv (it will be lying in the directory where you have unzipped your patch)

2. Change from following text from UPGRADE TO FORCE. Save your changes.

# file-version-parsed po patch/115/import/US poxwfpag.wft 120.1.12010000.10
      exec fnd bin WFLOAD bin &phase=daa+52 checkfile(120.1.12000000.8=120.1.12010000.8):po:patch/115/import/US:poxwfpag.wft &ui_apps 0 Y UPGRADE @PO:patch/115/import/US/poxwfpag.wft

to

# file-version-parsed po patch/115/import/US poxwfpag.wft 120.1.12010000.10
      exec fnd bin WFLOAD bin &phase=daa+52 checkfile(120.1.12000000.8=120.1.12010000.8):po:patch/115/import/US:poxwfpag.wft &ui_apps 0 Y FORCE @PO:patch/115/import/US/poxwfpag.wft

 3. Using adctrl utility restart the worker which had thrown out the error (see here for more info How to use adctrl utility to restart failed worker in patch application?)

 

ERROR-3. This error was thrown when only about 120 files were to be executed until patch completion

ORA-23413: table "MTH"."MTH_ENTITY_PLANNED_USAGE" does not have a materialized view log
java.sql.SQLException: ORA-23413: table "MTH"."MTH_ENTITY_PLANNED_USAGE" does not have a materialized view log

INVESTIGATION
1. Run "select log_owner, master, log_table from dba_mview_logs where master like 'MTH_ENTITY_PLANNED_USAGE';"

2. Above query returns a row. Hence materialized view log exists and its name is MLOG$_MTH_ENTITY_PLANNED_U

SOLUTION
1. Drop the materialized view log and recreate

drop materialized view log on MTH.MTH_ENTITY_PLANNED_USAGE;

CREATE MATERIALIZED VIEW LOG ON MTH.MTH_ENTITY_PLANNED_USAGE
WITH ROWID INCLUDING NEW VALUES;

2. Using adctrl utility restart the worker which had thrown out the error (see here for more info How to use adctrl utility to restart failed worker in patch application?)

 

Assumtions

• Oracle Database is up and running

Environment prior to applying patch

• Oracle EBS Release 12.1.1
• Oracle Enterprise Linux 5.7