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)

[edsanimate_start entry_animation_type= “pulse” entry_delay= “0.5” entry_duration= “0.5” entry_timing= “linear” exit_animation_type= “” exit_delay= “” exit_duration= “” exit_timing= “” animation_repeat= “1” keep= “yes” animate_on= “load” scroll_offset= “” custom_css_class= “”]Note: If you dont want to Enable JWS or is Already enabled, Skip this Section.[edsanimate_end]

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

 ##################################################################################

 ## Checking Apptier Java 7 for CPU 2024.07 on Platform Linux_x64 – need 1.7.0_431

 ## 2024-09-24 16:04:34 CDT  on  apps.example.com

 ##################################################################################

  2024.04        action  Your Version    bitness Java Location

  ————   ——  ————    ——- —————

  1.7.0_421      UPDATE  1.7.0_411       32-bit  /u01/install/APPS/fs1/EBSapps/10.1.2/jdk/bin/java

  1.7.0_421      UPDATE  1.7.0_411       32-bit  /u01/install/APPS/fs1/EBSapps/comn/util/jdk32/bin/java

  1.7.0_421      UPDATE  1.7.0_411       64-bit  /u01/install/APPS/fs1/EBSapps/comn/util/jdk64/bin/java

  1.7.0_421      UPDATE  1.7.0_411       64-bit  /u01/install/APPS/fs1/FMW_Home/webtier/jdk/bin/java

 ##################################################################################

 ## Checking DB tier Java for CPU 2024.07 on Platform Linux_x64

 ## 2024-09-25 14:53:33 CDT  on  apps.example.com

 ##################################################################################

  ## Check Database Version

 ##################################################################################

 Your database version is 19.21.0.0.0

         ORACLE_HOME     /u01/install/APPS/19.0.0

         ORACLE_SID      EBSCDB

         ORACLE_UNQNAME 

 ## Check Java Version of OJVM, Database JDK and EBS’s appsutil JRE

 ##################################################################################

 Latest Version  action  Your Version  bitness Java Location

 ————– ——– ————  ——- —————

 1.8.0_421         o)    1.8.0_391      64-bit OJVM In database

 1.8.0_421         j)    1.8.0_391      64-bit /u01/install/APPS/19.0.0/jdk/bin/java

 1.8.0_421         u)    1.8.0_391      64-bit /u01/install/APPS/19.0.0/appsutil/jre/bin/java

Copy the Downloaded Patch on Application Tier and Database Tier on any directory

we have copied on /home/oracle/ejcpuc
 

[oracle@ebs12214 ~]$ mkdir -p ejcpuc
[oracle@ebs12214 ~]$ mv p37171025_R12_GENERIC.zip ejcpuc/

[oracle@ebs12214 ~]$ cd ejcpuc/

[oracle@ebs12214 ejcpuc]$ unzip p37171025_R12_GENERIC.zip
Archive:  p37171025_R12_GENERIC.zip
  inflating: ejcpuc.cmd             
  inflating: ejcpuc.sh              
  inflating: Readme.txt             
[oracle@ebs12214 ejcpuc]$

[oracle@ebs12214 ~]$ . ./EBSapps.env run

[oracle@ebs12214 ~]$ cd ejcpuc/
[oracle@ebs12214 ejcpuc]$ sh ejcpuc.sh

##################################################################################
## Checking Apptier Java 7 for CPU 2024.10 on Platform Linux_x64 – need 1.7.0_441
## 2024-11-28 01:39:10 PKT on ebs12214.com
##################################################################################
2024.10 action Your Version bitness Java Location
———— —— ———— ——- —————
1.7.0_441 UPDATE 1.7.0_85 32-bit /u01/oracle/PROD/fs1/EBSapps/10.1.2/jdk/bin/java
1.7.0_441 UPDATE 1.7.0_85 32-bit /u01/oracle/PROD/fs1/EBSapps/comn/util/jdk32/bin/java
1.7.0_441 UPDATE 1.7.0_85 64-bit /u01/oracle/PROD/fs1/EBSapps/comn/util/jdk64/bin/java
1.7.0_441 UPDATE 1.7.0_80 64-bit /u01/oracle/PROD/fs1/FMW_Home/webtier/jdk/bin/java

Follow 1530033.1 to update the JDK(s). Your application tier JDK 7 is lower than the

1.7.0_441 update released in CPU 2024.10.

[oracle@ebs12214 ~]$ . ./env_prodCDB.env
[oracle@ebs12214 ~]$ cd ejcpuc/

[oracle@ebs12214 ejcpuc]$ sh ejcpuc.sh

##################################################################################
## Checking DB tier Java for CPU 2024.10 on Platform Linux_x64
## 2024-11-28 02:03:54 PKT on ebs12214.com
##################################################################################
## Check Database Version
##################################################################################
Your database version is 19.25.0.0.0
ORACLE_HOME /u01/oracle/PROD/19.0.0
ORACLE_SID prodcdb
ORACLE_UNQNAME
## Check Java Version of OJVM, Database JDK and EBS’s appsutil JRE, need 1.8.0_421
##################################################################################
Latest Version action Your Version bitness Java Location
————– ——– ———— ——- —————
1.8.0_431 1.8.0_431 64-bit OJVM In database
1.8.0_421 1.8.0_421 64-bit /u01/oracle/PROD/19.0.0/jdk/bin/java
1.8.0_421 u) 1.8.0_361 64-bit /u01/oracle/PROD/19.0.0/appsutil/jre/bin/java

u) When the DB JDK version is updated to the latest – then follow section 3 of 1530033.1 to update this JRE

USEFUL TIPS Related to EBS Critical Patch Update Checker (ECPUC)

Here are some useful tips for utilizing EBS Critical Patch Update Checker (ECPUC) effectively:

1.Thoroughly Read the README: Take the time to carefully read the README accompanying the patch. It contains various usage scenarios and helpful examples.

2. Stay Updated: Always make sure you are using the latest version of ECPUC. Older versions may not check for the newest EBS CPU patches and fixes.

3. Before Applying EBS CPU Patches and Fixes: As part of your quarterly CPU patching activity, follow these steps:

a) Run ECPUC before applying any EBS CPU patches and fixes. This step helps identify the specific patches and bug fixes required for your environment.

b) Apply all recommended patches promptly. If ECPUC suggests any patches or fixes, apply them to your environment as soon as possible.

4. After Applying EBS CPU Patches and Fixes: After applying the patches and performing cutover, perform the following action:

5. Run ECPUC again to confirm that all recommended patches and fixes were applied successfully.

6. Review and Report on EBS CPU Level: In certain cases, you may need to review and report on the EBS CPU level of your environment. To do this: 

Run ECPUC and review the ECPUC.lst report, which will provide information on your EBS CPU level and identify any recommended patches. 

[oracle@ebs12214 ~]$ mkdir -p ecpuc
[oracle@ebs12214 ~]$ mv p35583866_R12_GENERIC.zip ecpuc/

[oracle@ebs12214 ~]$ cd ecpuc/

[oracle@ebs12214 ecpuc]$ unzip p35583866_R12_GENERIC.zip
Archive: p35583866_R12_GENERIC.zip
inflating: ECPUC.sql
inflating: Readme.txt
[oracle@ebs12214 ecpuc]$

Open a new terminal and Source Application Tier Environment file

[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 …

Change the Directory to the Unzip Patch Location

[oracle@ebs12214 ~]$ cd ecpuc/
[oracle@ebs12214 ecpuc]$ ls -l
total 40
-rw-r–r–. 1 oracle oinstall 24364 Oct 15 11:31 ECPUC.sql
-rw-r–r–. 1 oracle oinstall 5297 Nov 25 18:04 p35583866_R12_GENERIC.zip
-rw-r–r–. 1 oracle oinstall 5879 Oct 15 11:33 Readme.txt
[oracle@ebs12214 ecpuc]$

Connect to the Database Apps User and run ECPUC.sql

[oracle@ebs12214 ecpuc]$ sqlplus apps

SQL*Plus: Release 10.1.0.5.0 – Production on Mon Nov 25 18:11:59 2024

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Enter password:

Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production

SQL> @ECPUC.sql

Start Time: 27-11-2024 14:08:42
****************************************************************************
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.
****************************************************************************

currently spooling to ECPUC_2024-11-27_14-08.lst
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production

Start Time: 27-11-2024 14:08:42
****************************************************************************
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.
****************************************************************************
============================================================================
SECTION-1 ECPUC Version
============================================================================

EBS CPU Checker Version
———————–
2024.1

============================================================================
SECTION-2 Oracle E-Business Suite (EBS): Instance Information
============================================================================

****************************************************************************
Instance Summary
****************************************************************************

EBS Release EBS CPU Level
———– ————-
12.2.12 2022.07

Instance Name Database Database Version
—————- —————- ——————
prodcdb PROD 19.25.0.0.0

ATG Product  Product Name                             Code Level

———— —————————————- ———-

ad           Applications DBA                         C.16

txk          Oracle Applications Technology Stack     C.16

atg_pf       Oracle Applications Technology Family    C.11

fwk          Oracle Applications Framework            C.11

==============================================================================
SECTION-3 Required EBS CPU and Security Fixes
==============================================================================

******************************************************************************
The following output is a list of required patches and security fixes
that are missing in your environment.

It is strongly recommended that you apply all of the listed patches as soon as possible.

If no patches (no rows) are listed then no additional action is required
at this time as your environment includes all patches for this EBS CPU.
******************************************************************************

The following patches are required for this EBS CPU
————————————————————–
36944346:12.2.0
37078884:R12.ATG_PF.C
37078919:R12.SCM_PF.C
37120495:R12.CC_PF.C
35362524:R12.IGI.C
34979060:R12.MSC.C

6 rows selected.

currently spooling to ECPUC_2024-11-27_14-08.lst

Dowloading Patches in ECPUC List

36944346:12.2.0

37078884:R12.ATG_PF.C

37078919:R12.SCM_PF.C

37120495:R12.CC_PF.C

35362524:R12.IGI.C

34979060:R12.MSC.C

[oracle@ebs12214 ~]$ source /u01/oracle/PROD/EBSapps.env run

E-Business Suite Environment Information
—————————————-
RUN File System : /u01/oracle/PROD/fs2/EBSapps/appl
PATCH File System : /u01/oracle/PROD/fs1/EBSapps/appl
Non-Editioned File System : /u01/oracle/PROD/fs_ne

DB Host: ebs12214.com Service/SID: PROD

Sourcing the RUN File System …

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

[oracle@ebs12214 ~]$ perl $AD_TOP/bin/admkappsutil.pl
Starting the generation of appsutil.zip
Log file located at /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/admin/log/MakeAppsUtil_11271555.log
output located at /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/admin/out/appsutil.zip

MakeAppsUtil completed successfully.

[oracle@ebs12214 ~]$

Copy the appsutil.zip file to <RDBMS ORACLE_HOME>

Open a new terminal and Source Database Tier Environment file

[oracle@ebs12214 ~]$ . ./env_PROD.env
[oracle@ebs12214 ~]$ cd $ORACLE_HOME

Take Backup of Current appsutil Directory

[oracle@ebs12214 19.0.0]$ cp -pr appsutil appsutil_backup

Copy appsutil.zip to Oracle Database Home

[oracle@ebs12214 19.0.0]$ cp /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/admin/out/appsutil.zip /u01/oracle/PROD/19.0.0

Unzip appsutil.zip

[oracle@ebs12214 19.0.0]$ unzip -o appsutil.zip
Archive: appsutil.zip

[oracle@ebs12214 ~]$ source /u01/oracle/PROD/19.0.0/PROD_ebs12214.env

[oracle@ebs12214 ~]$ cd $ORACLE_HOME
[oracle@ebs12214 19.0.0]$ cd appsutil/scripts/PROD_ebs12214/

[oracle@ebs12214 PROD_ebs12214]$ ./adautocfg.sh

—————- *********** ————- *********** ——————————–

Updating rdbms version in Context file to db19
Updating rdbms type in Context file to 64 bits
Configuring templates from ORACLE_HOME …

AutoConfig completed successfully.

[oracle@ebs12214 PROD_ebs12214]$

Open New Terminal for Running Autoconfig on Application

[oracle@ebs12214 ~]$ source /u01/oracle/PROD/EBSapps.env run

E-Business Suite Environment Information
—————————————-
RUN File System : /u01/oracle/PROD/fs2/EBSapps/appl
PATCH File System : /u01/oracle/PROD/fs1/EBSapps/appl
Non-Editioned File System : /u01/oracle/PROD/fs_ne

DB Host: ebs12214.com Service/SID: PROD

Sourcing the RUN File System …

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

—————- *********** ————- *********** ——————————–

AutoConfig completed successfully.

[oracle@ebs12214 scripts]$

[oracle@ebs12214 ~]$ . ./EBSapps.env run

E-Business Suite Environment Information
—————————————-
RUN File System : /u01/oracle/PROD/fs2/EBSapps/appl
PATCH File System : /u01/oracle/PROD/fs1/EBSapps/appl
Non-Editioned File System : /u01/oracle/PROD/fs_ne

DB Host: ebs12214.com Service/SID: PROD

Sourcing the RUN File System …

Unzip the Patches

[oracle@ebs12214 ~]$ cd ecpuc/cpu_patches/
[oracle@ebs12214 cpu_patches]$ unzip -oq p34979060_R12.MSC.C_R12_GENERIC.zip
[oracle@ebs12214 cpu_patches]$ cp -pr 34979060 $PATCH_TOP

[oracle@ebs12214 cpu_patches]$ unzip -oq p35362524_R12.IGI.C_R12_GENERIC.zip
[oracle@ebs12214 cpu_patches]$ cp -pr 35362524 $PATCH_TOP

[oracle@ebs12214 cpu_patches]$ unzip -oq p37078884_R12.ATG_PF.C_R12_GENERIC.zip
[oracle@ebs12214 cpu_patches]$ cp -pr 37078884 $PATCH_TOP

[oracle@ebs12214 cpu_patches]$ unzip -oq p37078919_R12.SCM_PF.C_R12_GENERIC.zip
[oracle@ebs12214 cpu_patches]$ cp -pr 37078919 $PATCH_TOP

[oracle@ebs12214 cpu_patches]$ unzip -oq p37120495_R12.CC_PF.C_R12_GENERIC.zip
[oracle@ebs12214 cpu_patches]$ cp -pr 37120495 $PATCH_TOP

Apply Patches

[oracle@ebs12214 ~]$ adop phase=apply patches=34979060,35362524,37078884,37078919,37120495 merge=yes

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

Validating system setup.
Node registry is valid.

Checking for existing adop sessions.
Continuing with existing session [Session ID: 9].

===========================================================================
ADOP (C.Delta.16)
Session ID: 9
Node: ebs12214
Phase: apply
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_161347/adop.log
===========================================================================

Starting patch merge.
Merging patches where applicable.
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_161347/apply/ebs12214/admrgpch.log

Applying patch ADOP_MRG_20241127_1732706068:u_1360318917.drv.
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_161347/apply/ebs12214/ADOP_MRG_20241127_1732706068/log/u_1360318917.log

Generating post apply reports.

Generating log report.
Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_161347/apply/ebs12214/adzdshowlog.out

The apply phase completed successfully.

adop exiting with status = 0 (Success)
[oracle@ebs12214 ~]$

Complete Patching Cycle

Open a new terminal and Source Application Tier Environment file

[oracle@ebs12214 ~]$ . ./EBSapps.env run

E-Business Suite Environment Information
—————————————-
RUN File System : /u01/oracle/PROD/fs2/EBSapps/appl
PATCH File System : /u01/oracle/PROD/fs1/EBSapps/appl
Non-Editioned File System : /u01/oracle/PROD/fs_ne

DB Host: ebs12214.com Service/SID: PROD

Sourcing the RUN File System …

Run Finalize,cutover,cleanup in same adop session

[oracle@ebs12214 ~]$ adop phase=finalize,cutover,cleanup

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: 137.04 GB

Validating system setup.
Node registry is valid.

Checking for existing adop sessions.
Continuing with existing session [Session ID: 9].

—————- *********** ————- *********** ——————————–

===========================================================================
ADOP (C.Delta.16)
Session ID: 9
Node: ebs12214
Phase: finalize,cutover,cleanup
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_162438/adop.log
===========================================================================

Checking if file system cutover completed.

Broadcast message from oracle@ebs12214.com (somewhere) (Wed Nov 27 16:33:44 202

PROD environment has changed.
All users must re-source the environment.

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/9/20241127_162438/cutover/ebs12214/adzdshowlog.out

Broadcast message from oracle@ebs12214.com (somewhere) (Wed Nov 27 16:44:28 202

PROD environment has changed.
All users must re-source the environment.

Processing cleanup actions in parallel.
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_162438/cleanup/ebs12214/log/cleanup.log

Generating report of queued DDL actions.

Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_162438/cleanup/ebs12214/adzdallddls.out

Running cleanup in STANDARD mode.
Log: @ADZDSHOWLOG.sql “2024/11/27 17:21:49”
[ERROR] [CLEANUP 1:1 ddl_id=26909] ORA-01432: public synonym to be dropped does not exist SQL: drop public synonym WF_ALL_JOBS force

Generating log report.
Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_162438/cleanup/ebs12214/adzdshowlog.out

The finalize phase completed successfully.
The cutover phase completed successfully.
The cleanup phase completed successfully.

adop exiting with status = 0 (Success)
[oracle@ebs12214 ~]$

[oracle@ebs12214 ~]$ source /u01/oracle/PROD/EBSapps.env run

E-Business Suite Environment Information
—————————————-
RUN File System : /u01/oracle/PROD/fs2/EBSapps/appl
PATCH File System : /u01/oracle/PROD/fs1/EBSapps/appl
Non-Editioned File System : /u01/oracle/PROD/fs_ne

DB Host: ebs12214.com Service/SID: PROD

Sourcing the RUN File System …

[oracle@ebs12214 ~]$

Connect to the Database Apps User and run ECPUC.sql

[oracle@ebs12214 ~]$ cd ecpuc/
[oracle@ebs12214 ecpuc]$ sqlplus apps

SQL*Plus: Release 10.1.0.5.0 – Production on Mon Nov 25 18:11:59 2024

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Enter password:

Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production

SQL> @ECPUC.sql

Start Time: 27-11-2024 17:34:29
****************************************************************************
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.
****************************************************************************
============================================================================
SECTION-1 ECPUC Version
============================================================================

EBS CPU Checker Version
———————–
2024.1

============================================================================
SECTION-2 Oracle E-Business Suite (EBS): Instance Information
============================================================================

****************************************************************************
Instance Summary
****************************************************************************

EBS Release EBS CPU Level
———– ————-
12.2.12 2024.10

Instance Name Database Database Version
—————- —————- ——————
prodcdb PROD 19.25.0.0.0

ATG Product  Product Name                             Code Level

———— —————————————- ———-

ad           Applications DBA                         C.16

txk          Oracle Applications Technology Stack     C.16

atg_pf       Oracle Applications Technology Family    C.11

fwk          Oracle Applications Framework            C.11

==============================================================================
SECTION-3 Required EBS CPU and Security Fixes
==============================================================================

******************************************************************************
The following output is a list of required patches and security fixes
that are missing in your environment.

It is strongly recommended that you apply all of the listed patches as soon as possible.

If no patches (no rows) are listed then no additional action is required
at this time as your environment includes all patches for this EBS CPU.
******************************************************************************

no rows selected ===> (As you Can see no more Patches Required by ECPUC)

currently spooling to ECPUC_2024-11-27_17-34.lst
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production

Download AD-TXK Patches

Patch 36303698: ERROR WHILE USING AD_ZD.GRANT_PRIVS AFTER APPLYING AD/TXK 15 PATCH

SQL*Plus: Release 19.0.0.0.0 – Production on Tue Nov 26 23:39:25 2024
Version 19.25.0.0.0

Copyright (c) 1982, 2024, Oracle.  All rights reserved.

Connected to:

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production

Version 19.25.0.0.0

SQL> show parameter _disable_actualization_for_grant

NAME                       TYPE  VALUE
———————————— ———– ——————————
_disable_actualization_for_grant     boolean     TRUE

SQL> select abbreviation, name, codelevel from ad_trackable_entities where abbreviation in( ‘ad’,’txk’,’atg_pf’)  order by abbreviation;

ABBREVIATION  NAME                                    CODELEVEL
———— —————————————- ———-
ad             Applications DBA                         C.14
atg_pf         Oracle Applications Technology Family    C.11
txk            Oracle Applications Technology Stack     C.14

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 …

[oracle@ebs12214 ~]$ adop phase=prepare

Enter the APPS password:
Enter the EBS_SYSTEM password:
Enter the WLSADMIN password:

Validating credentials.

Warning: WebLogic Admin Server is not running.

Trying to start Admin Server.

You are running adadminsrvctl.sh version 120.10.12020000.11

================ Note: It will take time  If fs_clone is not done in Previous Patching Cycle ===================

The prepare phase completed successfully.

adop exiting with status = 0 (Success)
[oracle@ebs12214 ~]$

[oracle@ebs12214 AD_TXK]$ cd 36119925/
[oracle@ebs12214 36119925]$ cd admin/

[oracle@ebs12214 admin]$ ls -ltrh adgrants.sql
-rwxr-xr-x. 1 oracle oinstall 152K Jan 1 2002 adgrants.sql

Copy adgrants.sql to Oracle DataBase Home appsutil/admin folder

[oracle@ebs12214 ~]$ cd /u01/oracle/PROD/19.0.0/appsutil ==== (Database home Directory)
[oracle@ebs12214 appsutil]$ mkdir -p admin === (create admin Directory if not available)

[oracle@ebs12214 ~]$ cd /u01/Patches/AD_TXK/36119925/admin
[oracle@ebs12214 admin]$ cp adgrants.sql /u01/oracle/PROD/19.0.0/appsutil/admin

Copy unzipped patch 36119925, 36303698 to $PATCH_TOP

[oracle@ebs12214 ~]$ cd /u01/Patches/AD_TXK
[oracle@ebs12214 AD_TXK]$ cp -pr 36119925/ $PATCH_TOP
[oracle@ebs12214 AD_TXK]$ cp -pr 36303698 $PATCH_TOP

[oracle@ebs12214 ~]$ . ./env_prodCDB.env
[oracle@ebs12214 admin]$ export ORACLE_PDB_SID=PROD === (Export ORACLE_PDB_SID also)
[oracle@ebs12214 ~]$ cd $ORACLE_HOME/appsutil/admin
[oracle@ebs12214 admin]$ sqlplus / as sysdba @adgrants.sql apps

SQL*Plus: Release 19.0.0.0.0 – Production on Wed Nov 27 00:54:54 2024
Version 19.25.0.0.0

Copyright (c) 1982, 2024, Oracle. All rights reserved.

Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.25.0.0.0

Current user is SYS

—————————————————
— adgrants.sql started at 2024-11-27 00:54:54 —
—————————————————
Removing logs from prior runs of adgrants.sql
–
Start granting from SYS to EBS_SYSTEM
–
End granting from SYS to EBS_SYSTEM

Completed granting and checking privileges

Generating list of ERRORS and WARNINGS to print out

CURRENT_USER
———————————————————————————————————————————————————————————————————————————————————-
SYS user ERRORS and WARNINGS will report at end of script

Creating PL/SQL profiler objects.

—————————————————
— profload.sql started at 2024-11-27 00:54:59 —

In 12.2c and beyond, the Oracle-supplied profload.sql script is a verification script, not an installation script.
Testing for correct installation
SYS.DBMS_PROFILER successfully loaded.

—————————————————–
— profload.sql completed at 2024-11-27 00:55:05 —

————————————————–
— proftab.sql started at 2024-11-27 00:55:05 —

—————————————————–
— profltab.sql completed at 2024-11-27 00:55:06 —

Installing Hierarchical Profiler.
–
Loading Stylesheets if missing

Begin creating the APPS_NE.ADGRANTS_VER_PKG package

End creating the APPS_NE.ADGRANTS_VER_PKG package

Executing PURGE DBA_RECYCLEBIN.

The following ERRORS and WARNINGS have been encountered during this adgrants session:

Grants given by this script have been written to the ad_zd_logs table.
You can run $AD_TOP/sql/ADZDSHOWLOG.sql to produce a report showing these grants.

Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.25.0.0.0

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 …

[oracle@ebs12214 ~]$ adop phase=apply patches=36119925,36303698 merge=yes

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: 140.57 GB

Validating system setup.
Node registry is valid.

Checking for existing adop sessions.
Continuing with existing session [Session ID: 7].

===========================================================================
ADOP (C.Delta.14)
Session ID: 7
Node: ebs12214
Phase: apply
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_010759/adop.log
===========================================================================

Starting patch merge.
Merging patches where applicable.
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_010759/apply/ebs12214/admrgpch.log -console off

Executing the merge of the patch drivers
— Processing patch: /u01/oracle/PROD/fs1/EBSapps/appl/admin/PROD/log/ADOP_MRG_20241127_1732651731/src/36303698
— Processing file: /u01/oracle/PROD/fs1/EBSapps/appl/admin/PROD/log/ADOP_MRG_20241127_1732651731/src/36303698/u36303698.drv
— Done processing file: /u01/oracle/PROD/fs1/EBSapps/appl/admin/PROD/log/ADOP_MRG_20241127_1732651731/src/36303698/u36303698.drv
— Done processing patch: /u01/oracle/PROD/fs1/EBSapps/appl/admin/PROD/log/ADOP_MRG_20241127_1732651731/src/36303698

— Processing patch: /u01/oracle/PROD/fs1/EBSapps/appl/admin/PROD/log/ADOP_MRG_20241127_1732651731/src/36119925
— Processing file: /u01/oracle/PROD/fs1/EBSapps/appl/admin/PROD/log/ADOP_MRG_20241127_1732651731/src/36119925/u36119925.drv
— Done processing file: /u01/oracle/PROD/fs1/EBSapps/appl/admin/PROD/log/ADOP_MRG_20241127_1732651731/src/36119925/u36119925.drv
— Done processing patch: /u01/oracle/PROD/fs1/EBSapps/appl/admin/PROD/log/ADOP_MRG_20241127_1732651731/src/36119925

Copying files…

5% complete. Copied 47 files of 937…
10% complete. Copied 94 files of 937…
15% complete. Copied 141 files of 937…
20% complete. Copied 188 files of 937…
25% complete. Copied 235 files of 937…
30% complete. Copied 282 files of 937…
35% complete. Copied 328 files of 937…
40% complete. Copied 375 files of 937…
45% complete. Copied 422 files of 937…
50% complete. Copied 469 files of 937…
55% complete. Copied 516 files of 937…
60% complete. Copied 563 files of 937…
65% complete. Copied 610 files of 937…
70% complete. Copied 656 files of 937…
75% complete. Copied 703 files of 937…
80% complete. Copied 750 files of 937…
85% complete. Copied 797 files of 937…
90% complete. Copied 844 files of 937…
95% complete. Copied 891 files of 937…
100% complete. Copied 937 files of 937…

Character-set converting files…

2 unified drivers merged.

Patch merge completed successfully
Please check the log file at /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_010759/apply/ebs12214/admrgpch.log.
Applying patch ADOP_MRG_20241127_1732651731:u_ad_3350299135.drv.
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_010759/apply/ebs12214/ADOP_MRG_20241127_1732651731/log/u_ad_3350299135.log

Generating post apply reports.

Generating log report.
Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_010759/apply/ebs12214/adzdshowlog.out

The apply phase completed successfully.

adop exiting with status = 0 (Success)
[oracle@ebs12214 ~]$

Source Application Run Environment

[oracle@ebs12214 AD_TXK]$ source /u01/oracle/PROD/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 …

Apply TXK Patch

[oracle@ebs12214 AD_TXK]$ adop phase=apply patches=36117775

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: 139.25 GB

Validating system setup.
Node registry is valid.

Checking for existing adop sessions.
Continuing with existing session [Session ID: 7].

===========================================================================
ADOP (C.Delta.16)
Session ID: 7
Node: ebs12214
Phase: apply
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_012651/adop.log
===========================================================================

Applying patch 36117775.
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_012651/apply/ebs12214/36117775/log/u36117775.log

Generating post apply reports.

Generating log report.
Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_012651/apply/ebs12214/adzdshowlog.out

The apply phase completed successfully.

adop exiting with status = 0 (Success)
[oracle@ebs12214 AD_TXK]$

[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 Finalize Phae

[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/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: 137.88 GB

Validating system setup.
Node registry is valid.

Checking for existing adop sessions.
Continuing with existing session [Session ID: 7].

===========================================================================
ADOP (C.Delta.16)
Session ID: 7
Node: ebs12214
Phase: finalize
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_024556/adop.log
===========================================================================

Verifying data dictionary.

Running finalize phase database actions.
Log: @ADZDSHOWLOG.sql “2024/11/27 02:46:50”
Compiling invalid objects.

Generating log report.
Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_024556/finalize/ebs12214/adzdshowlog.out

The finalize phase completed successfully.

adop exiting with status = 0 (Success)

Run CutOver Phase

[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/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: 137.88 GB

Validating system setup.
Node registry is valid.

Checking for existing adop sessions.
Continuing with existing session [Session ID: 7].

===========================================================================
ADOP (C.Delta.16)
Session ID: 7
Node: ebs12214
Phase: cutover
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_025204/adop.log
===========================================================================

Validating configuration on node: [ebs12214].
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_025204/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 500248 for CONCURRENT FND SHUTDOWN

adcmctl.sh: exiting with status 0
adcmctl.sh: check the logfile /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/logs/appl/admin/log/adcmctl.txt for more information …

Cancelling ADZDPATCH concurrent request

Waiting for Internal Concurrent Manager to go down.
Stopping patch edition Admin Server.
You are running adadminsrvctl.sh version 120.10.12020000.11

The AdminServer is already shutdown
AdminServer logs are located at /u01/oracle/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain/servers/AdminServer/logs
adadminsrvctl.sh: exiting with status 2
adadminsrvctl.sh: check the logfile /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/logs/appl/admin/log/adadminsrvctl.txt for more information …

Stopping patch edition Node Manager.

You are running adnodemgrctl.sh version 120.11.12020000.12

The Node Manager is already shutdown
NodeManager log is located at /u01/oracle/PROD/fs2/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1
adnodemgrctl.sh: exiting with status 2

adnodemgrctl.sh: check the logfile /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/logs/appl/admin/log/adnodemgrctl.txt for more information …

Stopping the application tier services on current node.
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_025204/cutover/ebs12214

Stopping run edition Admin Server.
You are running adadminsrvctl.sh version 120.10.12020000.11
Stopping WLS Admin Server…
Refer /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/logs/appl/admin/log/adadminsrvctl.txt for details
AdminServer logs are located at /u01/oracle/PROD/fs1/FMW_Home/user_projects/domains/EBS_domain/servers/AdminServer/logs
adadminsrvctl.sh: exiting with status 0
adadminsrvctl.sh: check the logfile /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/logs/appl/admin/log/adadminsrvctl.txt for more information …

Stopping run edition Node Manager.

You are running adnodemgrctl.sh version 120.11.12020000.12

NodeManager log is located at /u01/oracle/PROD/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1
adnodemgrctl.sh: exiting with status 0
adnodemgrctl.sh: check the logfile /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/logs/appl/admin/log/adnodemgrctl.txt for more information …

Running stored cutover DDLs.
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/7/20241127_025204/cutover/ebs12214/log/cutover.log

Loading JAR files into database.
No JAR files found to load

Performing database cutover.
Log: @ADZDSHOWLOG.sql “2024/11/27 02:57:48”

Statement handler reference is invalid.

Session killed.
Note that this is normal in the online patching cutover phase.
DB-Handle Error Code: 28
DB-Handle Error Message: ORA-00028: your session has been killed (DBD ERROR: OCIStmtExecute/Describe)
Reconnecting to the database.sh: which: line 1: syntax error: unexpected end of file

Flipping snapshots in run and patch editions.

Performing file system cutover.

Checking if file system cutover completed.

Broadcast message from oracle@ebs12214.com (somewhere) (Wed Nov 27 02:59:49 202

PROD environment has changed.
All users must re-source the environment.

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/7/20241127_025204/cutover/ebs12214/adzdshowlog.out

Broadcast message from oracle@ebs12214.com (somewhere) (Wed Nov 27 03:10:01 202

PROD environment has changed.
All users must re-source the environment.

The cutover phase completed successfully.

adop exiting with status = 0 (Success)
[oracle@ebs12214 ~]$

[oracle@ebs12214 ~]$ source /u01/oracle/PROD/EBSapps.env run

E-Business Suite Environment Information
—————————————-
RUN File System : /u01/oracle/PROD/fs2/EBSapps/appl
PATCH File System : /u01/oracle/PROD/fs1/EBSapps/appl
Non-Editioned File System : /u01/oracle/PROD/fs_ne

DB Host: ebs12214.com Service/SID: PROD

Sourcing the RUN File System …

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

[oracle@ebs12214 ~]$ perl $AD_TOP/bin/admkappsutil.pl
Starting the generation of appsutil.zip
Log file located at /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/admin/log/MakeAppsUtil_11270317.log
output located at /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/admin/out/appsutil.zip

MakeAppsUtil completed successfully.

[oracle@ebs12214 ~]$ . ./env_PROD.env
[oracle@ebs12214 ~]$ cd $ORACLE_HOME

Take Backup of Current appsutil Directory

[oracle@ebs12214 19.0.0]$ cp -pr appsutil appsutil_backup

Copy appsutil.zip from Application Tier to Oracle Database Home (In our case, we have Application and Database on Same Machine)

[oracle@ebs12214 19.0.0]$ cp /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/admin/out/appsutil.zip /u01/oracle/PROD/19.0.0

Unzip appsutil.zip

[oracle@ebs12214 19.0.0]$ unzip -o appsutil.zip

Archive:  appsutil.zip

SQL*Plus: Release 10.1.0.5.0 – Production on Wed Nov 27 05:02:14 2024

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production

SQL> @$AD_TOP/sql/ADZDDBCC.sql