Step 1: Upgrade Oracle Database

• As part of upgrading your Oracle E-Business Suite to Oracle Database 19c, your database will undergo a conversion to a multitenant architecture. This means it will consist of a Container Database (CDB) with a single Pluggable Database. Please note that only multitenant architecture databases are supported for Oracle E-Business Suite when using Oracle Database 19c.
• During the upgrade process, you will also need to migrate directories that are defined for PL/SQL File I/O to database directory objects. This requirement arises from the de support of the UTL_FILE_DIR database initialization parameter in Oracle Database 19c.
• Oracle Database Release Update 19.3, as well as Release Updates 19.5 and later, have been certified for compatibility.
• If the products you have implemented do not support 19c, it is advised not to proceed with the database upgrade.

Database Upgrade Part 1 Link:   Oracle EBS Database Upgrade from 12c to 19c Part-1

Database Upgrade Part 2 Link:  Oracle EBS Database Upgrade from 12c to 19c Part-2

Step 2: Apply Latest AD and TXK Delta Release Update Packs

Step 3 Apply Oracle E-Business Suite 12.2.14 Release Update Pack

Having applied the latest available AD and TXK RUPs and having also performed the necessary pre-update steps mentioned in the above sections, you can now proceed withapplying the Oracle E-Business Suite 12.2.14 Release Update Pack

a)  Source the run edition applications environment.

b) Unzip and Staging the Patch 36026788

[oracle@ebs12214 ~]$ cd /u01/Patches/12214_upgrade [oracle@ebs12214 12214_upgrade]$ unzip -o ‘*.zip’ [oracle@ebs12214 12214_upgrade]$ cp -pr 36026788 $PATCH_TOP

c) Start an Online Patching Cycle

d)  Apply Oracle E-Business Suite Release 12.2.14 Patch 36026788.

e) Complete the Patching Cycle (Finalize, Cutover, FSclone)

i) Run Finalize

[oracle@ebs12214 ~]$ adop phase=finalize Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Initializing. Run Edition context : /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch edition context: /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch file system free space: 120.50 GB Validating system setup. Node registry is valid. Checking for existing adop sessions. Continuing with existing session [Session ID: 15]. Session Id : 15 Prepare phase status : COMPLETED Apply phase status : ATLEAST ONE PATCH IS ALREADY APPLIED Cutover phase status : NOT COMPLETED Abort phase status : NOT COMPLETED Session status : FAILED =========================================================================== ADOP (C.Delta.16) Session ID: 15 Node: ebs12214 Phase: finalize Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241210_033617/adop.log =========================================================================== Verifying data dictionary. Running finalize phase database actions. Log: @ADZDSHOWLOG.sql “2024/12/10 03:36:57” Generating log report. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241210_033617/finalize/ebs12214/adzdshowlog.out The finalize phase completed successfully. adop exiting with status = 0 (Success) [oracle@ebs12214 ~]$

ii) Run Cutover

[oracle@ebs12214 ~]$ adop phase=cutover Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Initializing. Run Edition context : /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch edition context: /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch file system free space: 120.47 GB Validating system setup. Node registry is valid. Checking for existing adop sessions. Continuing with existing session [Session ID: 15]. =========================================================================== ADOP (C.Delta.16) Session ID: 15 Node: ebs12214 Phase: cutover Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241210_034304/adop.log =========================================================================== Validating configuration on node: [ebs12214]. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241210_034304/cutover/validate/ebs12214 Checking if finalize required. Finalize phase is not required Submitting request for Internal Concurrent Manager shutdown. You are running adcmctl.sh version 120.19.12020000.7 Shutting down concurrent managers for PROD … ORACLE Password: Submitted request 512325 for CONCURRENT FND SHUTDOWN adcmctl.sh: exiting with status 0 ============================== ************************* ============================================= Calling /u01/oracle/PROD/fs1/EBSapps/comn/util/jdk32/jre/bin/java … Flipping snapshots in run and patch editions. Performing file system cutover. Checking if file system cutover completed. Starting run edition Admin Server. Starting application tier services. Waiting for middle tier services to start on all available nodes. Generating post-cutover reports. Generating log report. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/15/20241210_034304/cutover/ebs12214/adzdshowlog.out The cutover phase completed successfully. adop exiting with status = 0 (Success)

iii) Open New Terminal And Source Environment

iv) Run FS Clone to Synchronized File System

Step 4 Post Upgrade Steps

i) Apply Oracle E-Business Suite Release 12.2.14 Online Help

Using adop hotpatch mode on the run file system, apply Oracle E-Business Suite Release 12.2.14 Online Help Patch 36026775.

ii) Apply Oracle Application Framework Patch

After you have installed the Oracle E-Business Suite 12.2.14 Release Update Pack, Oracle recommends that you apply the following critical patch as mentioned in Oracle E-Business Suite Release 12.2 Upgrade Considerations for OAF-based Applications and Oracle CRM Technology Foundation (Doc ID 1927975.1) OAF: Patch 36470037:R12.FWK.C Oracle Application Framework (FWK) Release Post-12.2.14 Consolidated Patch

iii) Implement Java Runtime Environtment (Optional)

Note: If you dont want to Enable JWS or is Already enabled, Skip this Section.

What is Java Web Start?

• Java Web Start (JWS) is a technology that allows for the deployment of Java-based applications to the client desktop, independent of the user’s browser.
•  Users can launch a Java application by simply clicking a link on a web page, which leads to a Java Network Launch Protocol (JNLP) file.
•  The JNLP file instructs the Java Web Start software to download, cache, and run the application, eliminating the need for additional installation procedures.
•  Java Web Start is included as part of the Java Runtime Environment (JRE) software, so users don’t need to install it separately or perform any additional tasks.
•  There is an architectural comparison between Java Plug-in and Java Web Start, which can be understood through the following diagrams showcasing the differences in the client (desktop) tier.

If you wish to enable JWS, you can refer to the provided document titled ‘Using Java Web Start with Oracle E-Business Suite (Doc ID 2188898.1)’.  However, please note that if your environment is on version 12.2.10 or below, the steps outlined in the document are applicable. In our specific case, as we have already upgraded our application to version 12.2.14, all the necessary patches to enable JWS have been included in the upgrade patch. Therefore, we only need to follow the subsequent process described in this section to enable JWS.

Update Context File to Enable JWS

Open the Application Context file in VI Editor as shown below As you Can see out forms launch method is set to browser, we need to change it to jws [oracle@ebs12214 ~]$ echo $CONTEXT_FILE /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml   [oracle@ebs12214 ~]$ grep s_forms_launch_method $CONTEXT_FILE          <config_option type=”techstack” oa_var=”s_forms_launch_method”>browser</config_option> [oracle@ebs12214 ~]$ vi $CONTEXT_FILE After Changing the Parameter of s_forms_launch_method Parameter to jws , Save and Close the Context File [oracle@ebs12214 ~]$ grep s_forms_launch_method $CONTEXT_FILE          <config_option type=”techstack” oa_var=”s_forms_launch_method”>jws</config_option>

Run Autoconfig on Application Tier

[oracle@ebs12214 ~]$ sh $ADMIN_SCRIPTS_HOME/adautocfg.sh

Regenerate JAR Files through ADADMIN Utility

[oracle@ebs12214 ~]$ adadmin

iv) Run ECPUC for Applying Critical Update Patches

For detail EBS Critical Patch Update Checker (ECPUC) application follow the Link below Step by Step Guide to apply EBS Latest CPU OCT-2024 through EBS Critical Patch Update Checker (ECPUC) Oracle E-Business Suite Release 12.2 Critical Patch Update Availability Document (October 2024) (Doc ID 3037725.1)

Source Run Environment

[oracle@ebs12214 ~]$ . ./EBSapps.env run E-Business Suite Environment Information —————————————- RUN File System : /u01/oracle/PROD/fs1/EBSapps/appl PATCH File System : /u01/oracle/PROD/fs2/EBSapps/appl Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: ebs12214.com Service/SID: PROD Sourcing the RUN File System … Run ecpuc.sql [oracle@ebs12214 ~]$ cd ecpuc/ [oracle@ebs12214 ecpuc]$ sqlplus apps/apps SQL*Plus: Release 10.1.0.5.0 – Production on Tue Dec 10 17:04:43 2024 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production SQL> @ECPUC.sql Start Time: 10-12-2024 17:04:47 **************************************************************************** E-Business Suite Critical Patch Update Checker (ECPUC) ECPUC.sql may be run on any EBS 12.2 environment to identify missing patches that are in the latest EBS CPU. You can download the latest version of ECPUC via Patch 35583866. Refer to the README.txt in Patch 35583866 for instructions for running ECPUC and information regarding the generated ECPUC.lst report. The checker generates the report ECPUC_YYYY-MM-DD_HH24-MI.lst that lists recommended EBS CPU patches and security fixes for your environment per Table 1 ‘CPU Patches for Oracle E-Business Suite’ and Table 2 ‘Additional Patches Required’ documented in the quarterly EBS CPU MOS Note. Each quarterly EBS CPU MOS Note ID is unique. Refer to My Oracle Support (MOS) Knowledge Document 2484000.1, ‘Identifying the Latest Critical Patch Update for Oracle E-Business Suite Release 12′ which includes a link to the current EBS CPU MOS document. ****************************************************************************

Applying Patch 1 of ECPUC Result 37078895

Source Run Environment

[oracle@ebs12214 ~]$ . ./EBSapps.env run E-Business Suite Environment Information —————————————- RUN File System : /u01/oracle/PROD/fs1/EBSapps/appl PATCH File System : /u01/oracle/PROD/fs2/EBSapps/appl Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: ebs12214.com Service/SID: PROD Sourcing the RUN File System …

Unzip Patch

[oracle@ebs12214 ~]$ cd /u01/Patches/12214_upgrade/ [oracle@ebs12214 12214_upgrade]$ unzip -qo p37078895_R12.ATG_PF.C_R12_GENERIC.zip [oracle@ebs12214 12214_upgrade]$ cp -pr 37078895/ $PATCH_TOP

Apply Patch

[oracle@ebs12214 ~]$ adop phase=apply apply_mode=downtime patches=37078895 Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Initializing. Run Edition context : /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch edition context: /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch file system free space: 119.58 GB Validating system setup. Node registry is valid. Checking for existing adop sessions. Application tier services are down. Continuing with the existing session [Session ID: 17]. =========================================================================== ADOP (C.Delta.16) Session ID: 17 Node: ebs12214 Phase: apply Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_180435/adop.log =========================================================================== Applying patch 37078895. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_180435/apply/ebs12214/37078895/log/u37078895.log Running finalize actions for the patches being applied. Log: @ADZDSHOWLOG.sql “2024/12/10 18:05:56” Running cutover actions for the patches being applied. Creating workers to process cutover DDL in parallel Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_180435/apply/ebs12214/log/cutover.log Loading JAR files into database. Loading JAR files into database No JAR files found to load Performing database cutover in Quick mode Generating post apply reports. Generating log report. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_180435/apply/ebs12214/adzdshowlog.out The apply phase completed successfully. adop exiting with status = 0 (Success) [oracle@ebs12214 ~]$

Applying Patch 2 of ECPUC Result 37068559

Source Run Environment

[oracle@ebs12214 ~]$ . ./EBSapps.env run E-Business Suite Environment Information —————————————- RUN File System : /u01/oracle/PROD/fs1/EBSapps/appl PATCH File System : /u01/oracle/PROD/fs2/EBSapps/appl Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: ebs12214.com Service/SID: PROD Sourcing the RUN File System …

Unzip Patch

[oracle@ebs12214 ~]$ cd /u01/Patches/12214_upgrade/ [oracle@ebs12214 12214_upgrade]$ unzip -qo p37068559_R12.GMD.C_R12_GENERIC.zip [oracle@ebs12214 12214_upgrade]$ cp -pr 37068559/ $PATCH_TOP

Apply Patch

[oracle@ebs12214 ~]$ adop phase=apply apply_mode=downtime patches=37068559 Enter the APPS password: Enter the EBS_SYSTEM password: Enter the WLSADMIN password: Validating credentials. Initializing. Run Edition context : /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch edition context: /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml Patch file system free space: 119.58 GB Validating system setup. Node registry is valid. Checking for existing adop sessions. Application tier services are down. Continuing with the existing session [Session ID: 17]. =========================================================================== ADOP (C.Delta.16) Session ID: 17 Node: ebs12214 Phase: apply Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_181022/adop.log =========================================================================== Applying patch 37068559. Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_181022/apply/ebs12214/37068559/log/u37068559.log Running finalize actions for the patches being applied. Log: @ADZDSHOWLOG.sql “2024/12/10 18:12:20” Running cutover actions for the patches being applied. Creating workers to process cutover DDL in parallel Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_181022/apply/ebs12214/log/cutover.log Loading JAR files into database. Loading JAR files into database No JAR files found to load Performing database cutover in Quick mode Generating post apply reports. Generating log report. Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/17/20241210_181022/apply/ebs12214/adzdshowlog.out The apply phase completed successfully. adop exiting with status = 0 (Success) [oracle@ebs12214 ~]$

v) Run ECPUC Again after Applying Critical Update Patches

Source Run Environment

[oracle@ebs12214 ~]$ . ./EBSapps.env run E-Business Suite Environment Information —————————————- RUN File System : /u01/oracle/PROD/fs1/EBSapps/appl PATCH File System : /u01/oracle/PROD/fs2/EBSapps/appl Non-Editioned File System : /u01/oracle/PROD/fs_ne DB Host: ebs12214.com Service/SID: PROD Sourcing the RUN File System … Run ecpuc.sql [oracle@ebs12214 ~]$ cd ecpuc/ [oracle@ebs12214 ecpuc]$ sqlplus apps/apps SQL*Plus: Release 10.1.0.5.0 – Production on Tue Dec 10 17:04:43 2024 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production SQL> @ECPUC.sql Start Time: 10-12-2024 17:04:47 **************************************************************************** E-Business Suite Critical Patch Update Checker (ECPUC) ECPUC.sql may be run on any EBS 12.2 environment to identify missing patches that are in the latest EBS CPU. You can download the latest version of ECPUC via Patch 35583866. Refer to the README.txt in Patch 35583866 for instructions for running ECPUC and information regarding the generated ECPUC.lst report. The checker generates the report ECPUC_YYYY-MM-DD_HH24-MI.lst that lists recommended EBS CPU patches and security fixes for your environment per Table 1 ‘CPU Patches for Oracle E-Business Suite’ and Table 2 ‘Additional Patches Required’ documented in the quarterly EBS CPU MOS Note. Each quarterly EBS CPU MOS Note ID is unique. Refer to My Oracle Support (MOS) Knowledge Document 2484000.1, ‘Identifying the Latest Critical Patch Update for Oracle E-Business Suite Release 12′ which includes a link to the current EBS CPU MOS document. ****************************************************************************

 vi) Run FS Clone to Synchronized File System

Step 5 Starting and Verifying Application 12.2.14

Start Application Services

Verifying Application

Login Console

• Expand System Administrator Responsibility.

•  Click Define Profile Options to Open Forms Interface.

You can See and Verify the Following Application and Database Version

Application Version: 12.2.14