R12.1.1 to R12.1.3 Upgrade.

In this post i am going to list out the steps to upgrade R12.1.1 to R12.1.3

NOTE: Please make a note that i have not included pre and post patch steps while applying patches. Please go-through the patch README’s carefully while applying patches…….

Step1: 

Upgrade Database from 11.1.0.7 to 11gr2. I have upgraded from 11.1.0.7 to 11.2.0.2. 

Please follow below URL for Database upgrade for R12.1.1 EBS

https://balaoracledba.com/2013/11/13/upgrade-11-1-0-7-to-11-2-0-2-on-r12-1-1/

Step2:

Put the application under maintainence using adadmin 

Step3. 

Apply below patch

8919491.B                  Oracle Applications Technology 12.1.3 Product Family Release Update Pack

Step4

Apply Below Patch

17884289 R12.AD.B.Delta.4

Step5:

Apply Below Patch

9239090              R12                    ORACLE E-BUSINESS SUITE 12.1.3 RELEASE UPDATE PACK


Step6:

Apply Below Patch

9239095.                      R12Oracle E-Business Suite Online Help for 12.1.3 Release Update Pack


Step7:

Apply Below Patch

9817770.BPOST-R12.ATG_PF.B.DELTA.3 CONSOLIDATED PATCH

Step8: 

Apply Below patch

9966055.B1OFF:12.1.3:TRANSLATED VERSION OF FNDSCSGN NOT LAUNCHED

Step9:  

Run AutoConfig on the APPL_TOP.

Step10:

Run the admkappsutil.pl utility to create the file appsutil.zip in the <INST_TOP>/admin/out directory.Step9:

Run AutoConfig on the APPL_TOP.

perl <AD_TOP>/bin/admkappsutil.pl

Step11:

Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>.

Step12:

Uncompress appsutil.zip under the <RDBMS ORACLE_HOME>.

Step13:

unzip the appsutil.zip  as below

unzip -o appsutil.zip

Step14: 

Run AutoConfig on the <RDBMS ORACLE_HOME>.

Step15:

Re-run adpreclone.pl on the database tier and the application tier. Since updates included in Oracle E-Business 
Suite Release 12.1.3 were applied to the system, adpreclone must be run again to apply the updates 
to the clone directory structures that were used during cloning.

perl adpreclone.pl dbTier

perl adpreclone.pl appsTier

This finishes the Application upgrade.

Start the Application Tier Services.

NOTE:After finishing the application upgrade. we need to apply product family patches.

(IN THIS UPGRADE I DIDNT APPLIED BELOW PRODUCT SPECIFIC PATCHES)

Patch	Product Family	Product Family Readme Documents
Oracle Applications Technology Release 12.1.3 (R12.ATG_PF.B.DELTA.3) Patch 8919491	Applications Technology (ATG_PF)	Document 1066312.1
Oracle Customer Releationship Management Release 12.1.3 (R12.CC_PF.B.DELTA.3) Patch 9249345	Customer Relationship Management (CC_PF)	Document 1081433.1
Oracle Financials Release 12.1.3 (R12.FIN_PF.B.DELTA.3) Patch 9147733	Financials (FIN_PF)	Document 1081425.1
Oracle Human Resource Management System Release 12.1.3 (R12.HR_PF.B.DELTA.3)Patch 9114911	Human Resources (HR_PF)	Document 1081427.1
Oracle E-Business Suite Diagnostics Release 12.1.3 (R12.IZU.B.DELTA.3) Patch 9239092	E-Business Suite Diagnostics (IZU)	Document 1081428.1
Oracle Procurement Release 12.1.3  (R12.PRC_PF.B.DELTA.3) Patch 9249354	Procurement (PRC_PF)	Document 1081431.1
Oracle Projects Release12.1.3 (R12.PJ_PF.B.DELTA.3) Patch 9147711	Projects (PJ_PF)	Document 1081434.1
Oracle Supply Chain Management Release 12.1.3 (R12.SCM_PF.B.DELTA.3) Patch 9245674	Supply Chain Management (SCM_PF)	Document 1081459.1
Oracle Value Chain Planning Release 12.1.3 (R12.SCP_PF.B.DELTA.3) Patch 9245525	Oracle Value Chain Planning (SCP_PF)	Document 1081461.1

Posted May 7, 2014 by balaoracledba.com in 11i/R12, OracleAppsR12, Upgrade

ORA-01408 such column list already indexed 11.2.0.2 to 11.2.0.4 Upgrade error   Leave a comment

During the Upgrade from 11.2.0.2 to 11.2.0.4 on OEL5.5 64-bit for EBS R12.1.3 I faced below issue

Solution:

Ora-01408 Error Upgrading to 11g using Dbua (and manual upgrade) (Doc ID 737400.1)

1. Remove the offending index:

drop index system.REPCAT$_AUDIT_COLUMN_IDX1;

2.

2.1 -If the upgrade has finished without any other error, create the following index:

create index system.repcat$_audit_column_f2_idx
on system.repcat$_audit_column
(base_sname,base_oname,base_conflict_type_id, base_reference_name);

2.2.- If the upgrade was cancelled or more errors were reported, retry the upgrade manually (see Note 429825.1) :

$ cd $ORACLE_HOME/rdbms/admin
$ sqlplus “/ as sysdba”
SQL> startup UPGRADE
SQL> set echo on
SQL> SPOOL upgrade.log
SQL> @catupgrd.sql
SQL> spool off