Oracle eBusiness 12.1.3 to 12.2.

5 upgrade –
Part 1 (Finalizing Path and DB Upgrade)
We have to first be on 12.2 to move to any version ahead of it.

The supported paths till the time I did the upgrade were as below.
Direct upgrade for 11.5.10.2 to 12.2
Direct upgrade for 12.0 or 12.1 to 12.2.

The database supported were 11.2.0.4 or 12c.

The first step has been the database upgrade. The upgrade is simple database upgrade with
DBUA so I am listing just the major steps to be taken care with EBS.
Please go through Interoperability notes for exact steps for your environments.

1. Install the Database Binaries.

2. Update to latest OPatch

3. Follow the interoperability notes to apply additional DB patches. This will save time later.

4. Shutdown application.

5. Drop SYS.ENABLED$INDEXES

SQL> drop table sys.enabled$indexes;

6. Remove the MGDSYS schema

$ sqlplus "/ as sysdba" @?/md/admin/catnomgdidcode.sql

7. Execute Dictionary stats.

SQL> EXECUTE dbms_stats.gather_dictionary_stats;

8. In case of RAC, Run Cluster Verify.

$ cd $ORACLE_HOME/bin
$ cluvfy stage -pre dbinst -upgrade
-src_dbhome <11gHOME>
-dest_dbhome <12cHOME>
-dest_version 12.1.0.2.0

9. Run pre upgrade Script.

$ sqlplus / sysdba
SQL> @preupgrd.sql;
Fix if there are any issue.

10. Upgrade DST in new home.

Check existing DST and default DST that comes with new Orale 12c home.
SQL> SELECT * FROM v$timezone_file;
FILENAME VERSION
-------------------- ----------
timezlrg_23.dat 23
Apply DST patch in new home,
Applying the DSTv23 update for the Oracle Database (Doc ID 1907093.1)
Sec. 2) Oracle RDBMS 12cR1 : Applying the RDBMS DSTv23 patch 19396455 on Oracle
RDBMS 12cR1 ( 12.1.0.1 and 12.1.0.2) .

11. Purge Audit records

SQL> truncate table sys.aud$;

SQL> truncate table sys.fga_log$;

12. Enterprise Manager Database Control

SQL> rdbms/admin/emremove.sql;

13. Copy the old tns_admin to new tns_admin, if you do not want to change anything in
ports.

14. Make sure application has been shutdown.

15. Start the upgrade.

16. Run datapatch as post step of patches applied.

$ORACLE_HOME/OPatch/datapatch

17. Change init parameters following the interoperability notes.

18. Modify listeners to move to new Oracle Home.

srvctl stop listener -l <ListenerName>
srvctl modify listener -l <ListenerName> -o <12cHome>
srvctl start listener -l <ListenerName>

19. Copy script from $APPL_TOP/admin/adgrants.sql and run as sysdba

20. CTXSYS procedure

copy $AD_TOP/patch/115/sql/adctxprv.sql to database server.

Run following from the database server where the file is placed.
$ sqlplus apps/$appspass @adctxprv.sql $SYSTEM_PASS CTXSYS

Then connect as sysdba and run following.

SQL> exec ctxsys.ctx_adm.set_parameter('file_access_role', 'public');
21. Workflow Rule set Validation.Run $FND_TOP/patch/115/sql/wfaqupfix.sql from application
server.

$ sqlplus [APPS user]/[APPS password] @wfaqupfix.sql [APPLSYS user] [APPS user]

22. Run adstats

$ sqlplus "/ as sysdba"

SQL> alter system enable restricted session;
SQL> @adstats.sql
$ sqlplus "/ as sysdba"
SQL> alter system disable restricted session;
SQL> exit;

23. Implement and Run autoconfig.

Create appsutil.zip using perl $AD_TOP/bin/admkappsutil.pl

Unzip that on Database Oracle Home.

24. Copy orai18n.jar

$ cp $ORACLE_HOME/jlib/orai18n.jar $ORACLE_HOME/jdk/jre/lib/ext/

After creating the XML context file, ensure the variable s_jretop points to
$ORACLE_HOME/jdk/jre and is not altered to any other value.

25. Create MGDSYS schema.

$ sqlplus "/ as sysdba" @?/rdbms/admin/catmgd.sql

25. Start Application and Validate.

The DB upgrade completes here, there may be some patches for 12c and for pre 12.2 need to
be applied on same application here.
Also follow relevant documents for database, OS, Platform/Storage and eBusiness versions
for exact patches to be applied on DB.
Part 2 (Upgrade to 12.2 - A)
Using 12.2 startCD 51 which has been latest by the time of upgrade.

Note:- There can be a lots of variation in terms of steps specific to your own environment. Please go
through the Upgrade guide, release notes and relevant Oracle Support Notes before finalizing your upgrade
steps.

Pre 12.2 Tasks

1. SubTypes Data Corruption Caused by csitxnst.ldt (Doc ID: 1681308.1)

Run scripts pre app upgrade.

- run dbmsxdbschmig.sql, prvtxdbschmig.sql, utlrp.sql scripts:

sqlplus / as sysdba
SQL> alter session set current_schema=SYS;
SQL> @?/rdbms/admin/dbmsxdbschmig.sql
SQL> @?/rdbms/admin/prvtxdbschmig.plb
SQL> @?/rdbms/admin/utlrp.sql
- run adgrants.sql:
sqlplus / as sysdba
SQL> @?/rdbms/admin/adgrants.sql [APPS schema name]

2. Backup the environment

3. Backup CUSTOM.pll

4. Check Guest account for user_id. Should be 6.

SQL> select user_name , user_id from fnd_user where user_name like 'GUEST';

5. Drop Custom Event Triggers.

Run alrdtrig.sql for every custom schema and verify and drop triggers after taking backup.

6. Check for module specific tasks from upgrade guide.

Financial and procurement Tasks, Sub Ledger Accounting, SCM Task, Order Management etc.

Install JRE on database tier.

7. Add SQLNET.ALLOWED_LOGON_VERSION_SERVER to sqlnet.ora Ifile on both the nodes, decide value for
conditions given in upgrade guide.

Install 12.2 File-system

Start rapidwiz, go for upgrade and select for create upgrade file system.
Here you will be asked for many details related to ports, servers, paths and passwords.
Enter those and after initial validation it will come to following screen.

Proceeding with next will install the file system for 12.2 in the given path.
Once the installation is successful, following screen will ask to validate and next button will
show details.

12.2 Upgrade

1. Shutdown application if anything is running.

2. Set FAILED_LOGIN_ATTEMPTS to UNLIMITED for all eBusiness related schemas.

3. Enable Maintenance Mode

4. Apply AD Patch 10117518

Check for Patch readme and follow instructions for pre tasks, merge and post tasks.Follow
Doc: Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID 1320300.1)
Section 3.

5. Download and merge preinstall patches.

Follow Doc: R12.1 and 12.2 Oracle E-Business Suite Preinstall Patches Report [Video] (Doc
ID 1448102.2) for downloading patches.

6. Apply Following the Doc 1320300.1, exactly step by step. This will include preinstall,
merge and apply steps of merged 12.2 Driver.

7 Disable Maintenance Mode.

Part 3 (Upgrade to 12.2 - B) Finishing 12.2 Upgrade

1. Back up the binaries and database.

2. Cleanup Nodes info (Optional).

SQL>exec fnd_conc_clone.setup_clean ;

3. Verify env variables on DB

LD_LIBRARY_PATH = $ORACLE_HOME/lib:$ORACLE_HOME/ctx/lib
ORACLE_SID = <instance name for current database node>
TNS_ADMIN=$ORACLE_HOME/network/admin/<CONTEXT_NAME>
PATH=$ORACLE_HOME/bin:$ORACLE_HOME/appsutil/jre/bin:$PATH
PERL5LIB=$ORACLE_HOME/perl/lib/5.14.1:$ORACLE_HOME/perl/lib/site_perl/5.14.1:$OR
ACLE_HOME/appsutil/perl

4. Run autoconfig on database

Make appsutil again from apps using

perl <AD_TOP>/bin/admkappsutil.pl

Unzip on Databzse
unzip -o appsutil.zip

or copy database context file

cd <RDBMS ORACLE_HOME>/appsutil/bin
perl adbldxml.pl

Run Autoconfig
<RDBMS ORACLE_HOME>/appsutil/bin/adconfig.sh contextfile=<context file>

5. Run autoconfig on App.

Drop table ADX_PRE_AUTOCONFIG from APPS schema, will be recreated during autoconfig.
cd <AD_TOP>/patch/115/sql
sqlplus APPS/$APPS_PASS @txkDropAdxPreAutoConfig.sql

Run AutoConfig on all the Application Tier nodes using the following Commands

$ADMIN_SCRIPTS_HOME/adautocfg.sh

6. Start Rapidwiz and run Configuration.

Provide Context File, then in further screens provide inputs as asked.
This will start configuration post confirmation. At the end you will get following screen for
validation.

Here we are done with 12.2 Upgrade. But there is a major step due is ADOP enablement.
ADOP is the new feature introduced with 12.2 making it too much different for earlier
version. It is AD Online Patching, and so it needs specific versions of Database to support
Edition Based Redefinition.

Following are the steps to enable Adop, which is also a part of Upgrade activity.

Enable ADOP

1. Apply E-Business Suite:Online Patching Readiness and GSCC Report patch

22071026:R12.AD.C.

2. Consider Localization if Any.

3. Run Readiness Scripts. (Doc ID 1531121.1)

sqlplus system @$AD_TOP/sql/ADZDPSUM.sql

sqlplus system @$AD_TOP/sql/ADZDPMAN.sql
sqlplus system @$AD_TOP/sql/ADZDPAUT.sql

Resolve all the issues reported by scripts.

4. Fix Data Dictionary or Time Stamp mismatch.

$AD_TOP/patch/115/sql/adzddtsfix.sql (Following the usage instructions provided in it).

Run the $AD_TOP/sql/ADZDDBCC.sql script to identify whether the data dictionary

corruption is still present.

In case yes, follow the doc 1531121.1.

5. Verify the tablespace Freespace.

Set the fs1 env.

Set HOSTNAME env variable without domain name.
Run adzdreport.pl.

Recommended for system to have 25 GB free space and APPS_TS_SEED to have 5 GB

6. Run the Online Patching Enablement - Status Report

sqlplus apps @$AD_TOP/sql/ADZDEXRPT.sql

7. Make sure Application Services are down.

8. Apply ADOP enablement patch. 13543062:R12.AD.C.

adpatch options=hotpatch,forceapply

Monitor the progress using sqlplus apps @$AD_TOP/sql/ADZDSHOWDDLS.sql

9. Check for invalids and compile.

exec sys.utl_recomp.recomp_parallel(n);

10. Re Run the online patching enablement report.

sqlplus <Apps Username> @$AD_TOP/sql/ADZDEXRPT.sql

Re run readiness reports for errors.

sqlplus system @$AD_TOP/sql/ADZDPSUM.sql

sqlplus system @$AD_TOP/sql/ADZDPMAN.sql
sqlplus system @$AD_TOP/sql/ADZDPAUT.sql

Run Compliance Checker again.

sqlplus <Apps Username> @$AD_TOP/sql/ADZDDBCC.sql

11. Resplice Localizations and perform additional activities.

12. Check following DB parameters.

service_names=%s_dbSid%,ebs_patch
recyclebin=off
_SYSTEM_TRIG_ENABLED=true
With this we are done with 12.2 Upgrade. This point onward whatever patches will go to the
system will go using adop utility. So will be the 12.2.5 related patches and upgrade driver.