Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

Month: December 2024

December 10, 2024 Oracle Database 19c Installation For OID
Oracle Internet Directory

Oracle Database 19c Installation on OEL 8.10

Operating System Setup

1. For Automatic Setup of Operating System Packages and Parameter, Run the following command with Root user

[root@oidserver ~]# dnf install -y oracle-database-preinstall-19c

If you are using RHEL8 or CentOS8, you can pick up the RPM from the OL8 repository and install it. It will pull the dependencies from your normal repositories.

curl -o oracle-database-preinstall-19c-1.0-2.el8.x86_64.rpm https://yum.oracle.com/repo/OracleLinux/OL8/appstream/x86_64/getPackage/oracle-database-preinstall-19c-1.0-2.el8.x86_64.rpm

dnf -y localinstall oracle-database-preinstall-19c-1.0-2.el8.x86_64.rpm

2. Set the password for the “oracle” user.

[root@oidserver ~]# passwd oracle

3. Set secure Linux to permissive by editing the “/etc/selinux/config” file, making sure the SELINUX flag is set as follows.

SELINUX=permissive

4. Once the change is complete, restart the server or run the following command.

[root@oidserver ~]# setenforce Permissive

5. Once the change is complete, restart the server or run the following command.

If you have the Linux firewall enabled, you will need to disable or configure it. To disable it, do the following.

# systemctl stop firewalld
# systemctl disable firewalld

6. Create the directories in which the Oracle software will be installed.

[root@oidserver ~]# mkdir -p /u01/app/oracle/product/19.0.0/dbhome_1
[root@oidserver ~]# chown -R oracle:oinstall /u01/app
[root@oidserver ~]# chmod -R 775 /u01

7. Create an Environment Variable file for the Oracle Database on the Oracle User Home Directory

[oracle@oidserver ~]$ vi setEnv.sh

# Oracle Settings
export TMP=/tmp
export TMPDIR=$TMP

export ORACLE_HOSTNAME=oidserver.com
export ORACLE_UNQNAME=OIDDB
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/19.0.0/dbhome_1
export ORA_INVENTORY=/u01/app/oraInventory
export ORACLE_SID=OIDDB
export DATA_DIR=/u01/oradata

export PATH=/usr/sbin:/usr/local/bin:$PATH
export PATH=$ORACLE_HOME/bin:$PATH

export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
export CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib
[oracle@oidserver ~]$

8. Unzip Software Binaries

Copy the Downloaded Database 19c Zip (V982063-01.zip) file on the /u01/app/oracle/product/19.0.0/dbhome_1 Directory

[oracle@oidserver ~]$ cd /u01/app/oracle/product/19.0.0/dbhome_1
[oracle@oidserver dbhome_1]$ unzip -oq V982063-01.zip

Running Database Installer

[oracle@oidserver dbhome_1]$ export DISPLAY=192.168.1.124:0.0
[oracle@oidserver dbhome_1]$ export CV_ASSUME_DISTID=OEL7.8[oracle@oidserver dbhome_1]$ ./runInstaller
Launching Oracle Database Setup Wizard…The response file for this session can be found at:
 /u01/app/oracle/product/19.0.0/dbhome_1/install/response/db_2024-11-30_10-01-36PM.rsp

You can find the log of this install session at:
 /u01/app/oraInventory/logs/InstallActions2024-11-30_10-01-36PM/installActions2024-11-30_10-01-36PM.log

Select Single Instance Database Installation

Click Next

Select Enterprise Edition

Click Next

Confirm Oracle Base Location

Click Next

Select Database Administration Groups

Click Next

Click Next
Click Install
Installation Started
Run the Script with Root User

[root@oidserver ~]# /u01/app/oracle/product/19.0.0/dbhome_1/root.sh

Click OK

Click Close

Database Creation through DBCA

[oracle@oidserver ~]$ . ./setEnv.sh

[oracle@oidserver ~]$ dbca

Select Advanced Configuration

Click Next

 

Select Oracle Single Instance database

Select Template Name General Purpose or TransactionProcessing

Click Next

Enter Global Database name and SID

Uncheck Option Create as Container database

Click Next

Click Next
Click Next
Click Next
Click Next
Click Next
Click Next
We used the Same Password for all Administrative accounts.

Click Next

Click Next
Verify the settings on the Installation Summary screen.

To change entries, Click BACK to the pertinent screen.

Once satisfied with the settings, click the Finish button to begin the installation.

Database Creation Started
Click Close

Alter Database Parameters

SQL> alter system set open_cursors=800 scope=both;
SQL> alter system set processes=1000 scope=spfile;
SQL> alter system set sessions=1000 scope=spfile;

Hope you found this document informative and gained valuable insights.

December 8, 2024 (EJCPUC)EBS Java Critical Patch Update Checker OCT-2024
APPS DBA

(EJCPUC)EBS Java Critical Patch Update Checker OCT-2024

Introduction

A new utility, Oracle E-Business Suite Java Critical Patch Update Checker (EJCPUC) was released with the October 2024 CPU.

Which Oracle strongly recommend that you run EJCPUC against your EBS environment to Identify the current Java CPU level for the various Java Homes in your EBS environment. Identify required Java CPU patches and security fixes for your environment.

The E-Business Suite Java Critical Patch Update Checker (EJCPUC) is a tool designed to identify available Java CPU patches corresponding to the most recent Oracle E-Business Suite (EBS) Critical Patch Update (CPU).

When executed, EJCPUC displays the versions of the Java Homes on either the Application tier or database tier, depending on where it is run.

 The patch contents for EJCPUC are updated with each CPU cycle to reflect the Java versions applicable for that cycle.

Scenarios for Running EJCPUC

Quarterly CPU Analysis and Patching:

  • Run EJCPUC to check the current Java version in your environment and identify the required updates.
  • Refer to the “Understanding the EJCPUC” section in this README for guidance on interpreting the output.
  • After applying the recommended quarterly patches and completing the cutover, rerun EJCPUC to verify that all Java Homes have been updated.

 

Environment Reporting:

  • Use EJCPUC to review and report on the EBS Java versions in your environment by running the tool.

 

Understanding the EJCPUC Output for Application

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

 ## 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

Follow 1530033.1 to update the JDK(s).

Your application tier JDK 7 is lower than the 1.7.0_421 update released in CPU 2024.07.

The first line in the EJCPUC output above

 – states the CPU it is for, 2024.07 indicates the July CPU of 2024.
 – lists the Java version released as part of this CPU cycle (1.7.0_421)

 
The 4 last lines lists the 4 relevant application tier JDK homes along with

 – the version released for this CPU
 – the action you must perform
 – the version currently installed
 – if it is a 32-bit, 64-bit or hybrid JDK home
 – the location of the checked JDK

 

Understanding the EJCPUC Output for Database

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

 ## 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

 

  • o) Apply the Database Release Update (DBRU) recommended by ETCC which will update the DB OJVM version to the latest
  • j) Apply the Database Release Update (DBRU) recommended by ETCC which will update the DB JDK version to the latest
  • u) When the DB JDK version is updated to the latest – then follow section 3 of 1530033.1 to update this JRE

EJCPUC output above lists the database version (to determine the Java major version for the DB)

Then the output lists the Java version of the 3 relevant Java locations along with

 – the version released for this CPU

 – the action you must perform

 – the version currently installed

 – if it is a 32-bit, 64-bit or hybrid JDK home

 – the location of the checked JDK/JRE

 

 

Downloading EJCPUC Patch

Release Link : EJCPUC Release Link

 

 

Download Link:    EJCPUC Patch 37171025

 

 

Unzip EJCPUC Patch and Run ejpuc.sh

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]$

 

Running EJCPUC.sh on Application Tier

 Open a new terminal and Source Application Tier Environment file

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

 

 

Running EJCPUC.sh on Database Tier

 Open a new terminal and Source Database Tier Environment file

[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

 

 

 

 

 

 

 

 

December 6, 2024 (ECPUC) EBS Critical Patch Update Checker-OCT-2024
APPS DBA

Step by Step Guide to apply EBS Latest CPU OCT-2024 through EBS Critical Patch Update Checker (ECPUC)

The EBS Critical Patch Update Checker (ECPUC) is a diagnostic tool developed by Oracle to help users of Oracle E-Business Suite (EBS) determine whether they have applied the latest Critical Patch Updates (CPUs) for their environment. Critical Patch Updates are Oracle’s mechanism for providing security fixes and updates across its products.

 

Key Features of ECPUC:

  1. Security Validation:

    • ECPUC checks whether your EBS environment has implemented the patches required by the most recent CPU.
    • It verifies security measures and configuration settings to ensure compliance with Oracle’s recommendations.
  1. Automated Assessment:

  • The tool scans the environment and cross-references the applied patches against Oracle’s repository of critical patch updates.
  • It identifies missing patches or misconfigured systems.
  1. Comprehensive Reporting:

  • Generates detailed reports highlighting compliance with Oracle’s security patch requirements.
  • Flags missing patches or other vulnerabilities that could pose risks to the environment.
  1. Simplification of Patch Management:

  • Reduces the complexity of ensuring that the EBS environment remains secure.
  • Provides actionable insights to help administrators prioritize patching efforts.

Benefits of Using ECPUC:

  • Enhanced Security: Keeps your EBS environment protected against known vulnerabilities.
  • Time Efficiency: Automates a manual and often tedious validation process.
  • Proactive Risk Management: Helps organizations stay ahead of potential threats by maintaining up-to-date patching.
  • Regulatory Compliance: Ensures your environment adheres to compliance standards that require regular patch updates.

 

Oracle regularly updates ECPUC to reflect the latest CPU releases, ensuring that organizations have a reliable way to verify their patch compliance.

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. 

Dowloading ECPUC Patch

  

Download Link:     https://updates.oracle.com/download/35583866.html

Notes:

  • It is important to always download the latest ECPUC.
  • If you run ECPUC against an environment at a later EBS CPU level than the ECPUC, you will receive the following error message: “Environment EBS CPU level xxx is later than the EBS  CPU checker version xxxx. Please download Patch 35583866 for the latest version of the ECPUC”.

Unzip ECPUC Patch and Run ECPUC.sql

Copy the downloaded Patch on Linux Oracle User home directory /home/oracle

[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

Checking  ECPUC report

[oracle@ebs12214 ecpuc]$ cat ECPUC_2024-11-27_14-08.lst

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

As per the Above Report, we need to Download 6 Patches as shown Below

Dowloading Patches in ECPUC List

Patch 1

36944346:12.2.0

Patch 2

37078884:R12.ATG_PF.C

Patch 3

37078919:R12.SCM_PF.C

Patch 4

37120495:R12.CC_PF.C

Patch 5

35362524:R12.IGI.C

 

Patch 6 

34979060:R12.MSC.C

 

Copy the downloaded Patches on /home/oracle/ecpuc/cpu_patches

Unzip and Apply CPU Patch for OCT 2024

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 …
Unzip the Patch file
[oracle@ebs12214 cpu_patches]$ cd /home/oracle/ecpuc/cpu_patches/
[oracle@ebs12214 cpu_patches]$ unzip -qo  p36944346_12.2.0_R12_LINUX.zip 
[oracle@ebs12214 cpu_patches]$ cp -pR 36944346/ $PATCH_TOP
Start Prepare Phase
[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
Starting WLS Admin Server…
Refer /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/logs/appl/admin/log/adadminsrvctl.txt for details
AdminServer logs are located at /u01/oracle/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain/servers/AdminServer/logs
adadminsrvctl.sh: exiting with status 0
adadminsrvctl.sh: check the logfile /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/logs/appl/admin/log/adadminsrvctl.txt for more information …  
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.43 GB
Validating system setup.
    Node registry is valid.
Checking for existing adop sessions.
    No pending session exists.
    Starting new adop session.
===========================================================================
ADOP (C.Delta.16)
Session ID: 9
Node: ebs12214
Phase: prepare
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_141509/adop.log
===========================================================================
Validating configuration on node: [ebs12214].
    Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_141509/prepare/validate/ebs12214
[WARNING]: There could be issues while validating the ports used for E-Business Suite instance
against ports used in /etc/services. Refer the log file for more details.
Verifying data dictionary.
Validating system is ready to prepare.
    Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_141509/prepare/ebs12214
Detecting configuration changes.
    Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_141509/prepare/ebs12214/adConfigChanges.log
The log file is /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_141509/prepare/ebs12214/adConfigChanges.log
    No file system configuration changes were detected.
Checking AD-TXK codelevel.
    AD-TXK codelevel has changed.
    Checking for CLONE record existence for ebs12214
    CLONE record already exist for ebs12214
Checking for pending cleanup actions.
    No pending cleanup actions found.
Validating database is ready to prepare.
Starting Apps listener.
adalnctl.sh version 120.3.12020000.4
Checking for FNDFS executable.
Starting listener process APPS_PROD.
adalnctl.sh: exiting with status 0
adalnctl.sh: check the logfile /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/logs/appl/admin/log/adalnctl.txt for more information …  
Submitting ADZDPATCH concurrent program.
Saving database logs from previous session.
    Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_141509/prepare/ebs12214/adzdshowlog_cleanup.out
Creating database patch edition.
    Log: @ADZDSHOWLOG.sql “2024/11/27 14:21:04”
preparing the seed tables needed for autoconfig execution.
Running AutoConfig on patch edition file system.
The log file for this session is located at: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_141509/prepare/ebs12214/adconfig.log
wlsDomainName: EBS_domain
WLS Domain Name is VALID.
AutoConfig is configuring the Applications environment…
AutoConfig will consider the custom templates if present.
Using CONFIG_HOME location     : /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214
Classpath                   : /u01/oracle/PROD/fs1/FMW_Home/Oracle_EBS-app1/shared-libs
/ebs-appsborg/WEB-INF/lib/ebsAppsborgManifest.jar:/u01/oracle/PROD/fs1/EBSapps/comn/java/classes
Using Context file          : /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml
Context Value Management will now update the Context file
Updating Context file…COMPLETED
Attempting upload of Context file and templates to database…COMPLETED
Configuring templates from all of the product tops…
Configuring AD_TOP……..COMPLETED
Configuring FND_TOP…….COMPLETED
Configuring ICX_TOP…….COMPLETED
Configuring MSC_TOP…….COMPLETED
Configuring IEO_TOP…….COMPLETED
Configuring BIS_TOP…….COMPLETED
Configuring CZ_TOP……..COMPLETED
Configuring SHT_TOP…….COMPLETED
Configuring AMS_TOP…….COMPLETED
Configuring CCT_TOP…….COMPLETED
Configuring WSH_TOP…….COMPLETED
Configuring CLN_TOP…….COMPLETED
Configuring OKE_TOP…….COMPLETED
Configuring OKL_TOP…….COMPLETED
Configuring OKS_TOP…….COMPLETED
Configuring CSF_TOP…….COMPLETED
Configuring IBY_TOP…….COMPLETED
Configuring JTF_TOP…….COMPLETED
Configuring MWA_TOP…….COMPLETED
Configuring CN_TOP……..COMPLETED
Configuring CSI_TOP…….COMPLETED
Configuring WIP_TOP…….COMPLETED
Configuring CSE_TOP…….COMPLETED
Configuring EAM_TOP…….COMPLETED
Configuring GMF_TOP…….COMPLETED
Configuring PON_TOP…….COMPLETED
Configuring FTE_TOP…….COMPLETED
Configuring ONT_TOP…….COMPLETED
Configuring AR_TOP……..COMPLETED
Configuring AHL_TOP…….COMPLETED
Configuring IES_TOP…….COMPLETED
Configuring OZF_TOP…….COMPLETED
Configuring CSD_TOP…….COMPLETED
Configuring IGC_TOP…….COMPLETED
AutoConfig completed successfully.
Synchronizing patch filesystem with run filesystem.
    Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_141509/prepare/ebs12214
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_141509/prepare/ebs12214
Synchronizing snapshots.
Generating editions report.
    Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_141509/prepare/ebs12214/adzdshowed.out
Generating log report.
    Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_141509/prepare/ebs12214/adzdshowlog.out
Stopping services on patch file system.
    Stopping 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/fs1/FMW_Home/user_projects/domains/EBS_domain/servers/AdminServer/logs
adadminsrvctl.sh: exiting with status 2
adadminsrvctl.sh: check the logfile /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/logs/appl/admin/log/adadminsrvctl.txt for more information …  
    Stopping 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/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1
adnodemgrctl.sh: exiting with status 2
adnodemgrctl.sh: check the logfile /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/logs/appl/admin/log/adnodemgrctl.txt for more information …  
The prepare phase completed successfully.
adop exiting with status = 0 (Success)

Apply Patch once Prepare Phase Finishes

[oracle@ebs12214 ~]$ adop phase=apply patches=36944346

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.42 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: apply
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_143436/adop.log
===========================================================================

Applying patch 36944346.
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/9/20241127_143436/apply/ebs12214/36944346/log/u36944346.log

Generating post apply reports.

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

The apply phase completed successfully.

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

Update Database Tier to Latest Autoconfig Code

Create the New appsutil.zip

Update all database tier nodes with the latest AutoConfig code, by performing the following steps on the application and database tiers

Open a new terminal and Source Application Tier Environment file

[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

Autoconfig on DB and APPS

Open New Terminal for Running Autoconfig on Database

[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]$

Unzip Apply Other Patches in ECPUC LIST

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 …

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 ~]$

Run ECPUC.sql again and Check the Report

Open a new terminal and Source Application Tier Environment file

[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

Hope you found this document informative and gained valuable insights.

December 3, 2024 Apply EBS AD-TXK Release 16 Update
APPS DBA

Step By Step Guide to Apply Oracle E-Business Suite R12.2 ADTXK Update 16

Oracle Applications DBA (AD) and Oracle E-Business Suite Technology Stack (TXK) Release Update Packs are periodic updates provided by Oracle to enhance and maintain the technology stack components of Oracle E-Business Suite (EBS). These packs include fixes, optimizations, and new features to ensure stability, performance, and compatibility with the latest Oracle technologies.

Key Components:

  1. AD (Applications DBA):
    • Contains utilities, scripts, and tools for managing and maintaining Oracle EBS applications.
    • Covers tasks like patching, cloning, and upgrading EBS environments.
  2. TXK (Technology Stack):
    • Provides updates to the underlying technology stack of Oracle EBS, such as Oracle WebLogic Server, Oracle Fusion Middleware, and configuration files.
    • Ensures compatibility with the latest EBS versions and database releases.

Purpose of Release Update Packs:

  • Bug Fixes: Resolve known issues in AD and TXK components.
  • Feature Enhancements: Introduce improvements and new functionality to streamline administration tasks.
  • Compatibility Updates: Ensure integration with newer database versions (e.g., Oracle Database 19c) and middleware components.
  • Security Updates: Address vulnerabilities and enhance security configurations.

Benefits of AD and TXK Update Packs:

  1. Improved system stability and performance.
  2. Support for newer hardware and software configurations.
  3. Enhanced automation for routine tasks like patching and cloning.
  4. Simplified compliance with Oracle’s recommended best practices.

Where to Download:

  • AD and TXK Release Update Packs can be downloaded from My Oracle Support (MOS).
  • Refer to the following documents for guidance: 
    • Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)
    • Oracle E-Business Suite Release 12.2: Consolidated List of Oracle Database Patches and Bug Fixes (Doc ID 1594274.1)

When to Apply:

  • During routine maintenance to keep your environment up-to-date.
  • Before upgrading your Oracle EBS or migrating to a new database version.
  • To resolve specific issues or enhance system performance.

These updates are essential for maintaining a robust and secure Oracle EBS environment, ensuring seamless operations and compatibility with Oracle’s evolving technology stack.

Pre-Requisites of AD-TXK

(ETCC) EBS Technology Codelevel Checker

Use the Below given file to Download the latest ETCC Patch and Identifying and applying the required Database and Middleware Technology Patches

Link 🔗Apply ETCC(OCT-2024) Patches

Download AD-TXK Patches

Patch R12.AD.C.delta.16: R12.AD.C.DELTA.16
Patch R12.TXK.C.delta.16: R12.TXK.C.DELTA.16
Ad critical patch

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

Check Database Parameter and adtxk code level

[oracle@ebs12214 ~]$ sqlplus / as sysdba

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

Apply AD-TXK Patches

Prepare for Applying AD-TXK Patch

Source Apps Env and Run Prepare Phase

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

[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 ~]$

Unzip AD Patches 36119925 and 36303698

[oracle@ebs12214 ~]$ cd /u01/Patches/AD_TXK
[oracle@ebs12214 AD_TXK]$ unzip -qo p36119925_R12.AD.C_R12_LINUX.zip
[oracle@ebs12214 AD_TXK]$ unzip -qo p36303698_R12.AD.C_R12_GENERIC.zip

[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

Running ADgrants.sql

Source Database Environment File and Then Run ADgrants.sql

[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

Apply AD Patch 36119925 and 36303698

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

[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 ~]$

Unzip and Apply TXK Patch 36117775

[oracle@ebs12214 ~]$ cd /u01/Patches/AD_TXK/
[oracle@ebs12214 AD_TXK]$ unzip -qo p36117775_R12.TXK.C_R12_GENERIC_1of3.zip
[oracle@ebs12214 AD_TXK]$ unzip -qo p36117775_R12.TXK.C_R12_GENERIC_2of3.zip
[oracle@ebs12214 AD_TXK]$ unzip -qo p36117775_R12.TXK.C_R12_GENERIC_3of3.zip
[oracle@ebs12214 AD_TXK]$ cp -pR 36117775/ $PATCH_TOP

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]$

Complete Online Patching Cycle

Source Apps ENV in new Terminal

[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 ~]$

Post AD-TXK Patch Configuration

Update Database Tier to Latest Autoconfig Code

Create the appsutil.zip

Update all database tier nodes with the latest AutoConfig code, by performing the following steps on the application and database tiers

Source Application Run Environment

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

Copy the appsutil.zip file to <RDBMS ORACLE_HOME> and Unzip

Open New Terminal Source Database Environment

[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

Autoconfig on DataBase and APPS Tier

Open New Terminal for Running Autoconfig on Database and Source DB Environment
[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/
Run Autoconfig On DB
[oracle@ebs12214 PROD_ebs12214]$ ./adautocfg.sh 
Enter the APPS user password:
The log file for this session is located at:
/u01/oracle/PROD/19.0.0/appsutil/log/PROD_ebs12214/11270323/adconfig.log
AutoConfig is configuring the Database environment…
AutoConfig will consider the custom templates if present.
Using ORACLE_HOME location : /u01/oracle/PROD/19.0.0
Value of s_dbcset is US7ASCII
Character set is present in the allowed list. No need to add orai18n.jar to the CLASSPATH.
Value of s_dbcset is US7ASCII
Character set is present in the allowed list. No need to add orai18n.jar to the CLASSPATH.
Classpath                   : :/u01/oracle/PROD/19.0.0/jdbc/lib/ojdbc8.jar:
/u01/oracle/PROD/19.0.0/appsutil/java/xmlparserv2.jar:
/u01/oracle/PROD/19.0.0/appsutil/java:/u01/oracle/PROD/19.0.0/jlib/netcfg.jar:
/u01/oracle/PROD/19.0.0/jlib/ldapjclnt19.jar
Using Context file          : /u01/oracle/PROD/19.0.0/appsutil/PROD_ebs12214.xml
Context Value Management will now update the Context file
Updating Context file…COMPLETED
Attempting upload of Context file and templates to database…COMPLETED
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 Tier
Source Application Environment file
[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 Autoconfig on AppsTier
[oracle@ebs12214 ~]$ cd $ADMIN_SCRIPTS_HOME
[oracle@ebs12214 scripts]$ ./adautocfg.sh 
Enter the APPS user password:
The log file for this session is located at:
/u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/admin/log/11270325/adconfig.log
wlsDomainName: EBS_domain
WLS Domain Name is VALID.
AutoConfig is configuring the Applications environment…
AutoConfig will consider the custom templates if present.
Using CONFIG_HOME location     : /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214
Classpath                   : /u01/oracle/PROD/fs2/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-INF/lib/ebsAppsborgManifest.jar:/u01/oracle/PROD/fs2/EBSapps/comn/java/classes
Using Context file          : /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml
Context Value Management will now update the Context file
Updating Context file…COMPLETED
Attempting upload of Context file and templates to database…COMPLETED
Configuring templates from all of the product tops…
Configuring AD_TOP……..COMPLETED
Configuring FND_TOP…….COMPLETED
Configuring ICX_TOP…….COMPLETED
Configuring MSC_TOP…….COMPLETED
Configuring IEO_TOP…….COMPLETED
Configuring BIS_TOP…….COMPLETED
Configuring CZ_TOP……..COMPLETED
Configuring SHT_TOP…….COMPLETED
Configuring AMS_TOP…….COMPLETED
Configuring CCT_TOP…….COMPLETED
Configuring WSH_TOP…….COMPLETED
Configuring CLN_TOP…….COMPLETED
Configuring OKE_TOP…….COMPLETED
Configuring OKL_TOP…….COMPLETED
Configuring OKS_TOP…….COMPLETED
Configuring CSF_TOP…….COMPLETED
Configuring IBY_TOP…….COMPLETED
Configuring JTF_TOP…….COMPLETED
Configuring MWA_TOP…….COMPLETED
Configuring CN_TOP……..COMPLETED
Configuring CSI_TOP…….COMPLETED
Configuring WIP_TOP…….COMPLETED
Configuring CSE_TOP…….COMPLETED
Configuring EAM_TOP…….COMPLETED
Configuring GMF_TOP…….COMPLETED
Configuring PON_TOP…….COMPLETED
Configuring FTE_TOP…….COMPLETED
Configuring ONT_TOP…….COMPLETED
Configuring AR_TOP……..COMPLETED
Configuring AHL_TOP…….COMPLETED
Configuring IES_TOP…….COMPLETED
Configuring OZF_TOP…….COMPLETED
Configuring CSD_TOP…….COMPLETED
Configuring IGC_TOP…….COMPLETED
AutoConfig completed successfully.
[oracle@ebs12214 scripts]$

Synchronize the File Systems

  • This action copies the new run edition code and configuration to the other file system.

  • After you apply AD-TXK Delta 16, you should run fs_clone to synchronize the run and patch file systems with the configuration changes that the new codelevel introduces.

  • If you do not run fs_clone, it will run automatically in the next prepare phase, which will consequently take more time.

Open New Terminal for Running fs_clone
Source Application Environment file
[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]$ adop phase=fs_clone
Enter the APPS password:
Enter the EBS_SYSTEM password:
Enter the WLSADMIN password:
Validating credentials.
Validating credentials.
Warning: WebLogic Admin Server is not running.
Trying to start Admin Server.
You are running adadminsrvctl.sh version 120.10.12020000.11
Starting WLS Admin Server…
Refer /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/logs/appl/admin/log/adadminsrvctl.txt for details
AdminServer logs are located at
/u01/oracle/PROD/fs2/FMW_Home/user_projects/domains/EBS_domain/servers/AdminServer/logs
adadminsrvctl.sh: exiting with status 0
adadminsrvctl.sh: check the logfile
/u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/logs/appl/admin/log/adadminsrvctl.txt for more information …  
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.18 GB
Validating system setup.
    Node registry is valid.
Checking for existing adop sessions.
    No pending session exists.
    Starting new adop session.
===========================================================================
ADOP (C.Delta.16)
Session ID: 8
Node: ebs12214
Phase: fs_clone
Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/8/20241127_033418/adop.log
===========================================================================
Validating configuration on node: [ebs12214].
    Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/8/20241127_033418/fs_clone/validate/ebs12214
[WARNING]: There could be issues while validating the ports used for E-Business Suite instance against ports
used in /etc/services. Refer the log file for more details.
Checking for pending cleanup actions.
    Running cleanup as it was not run in previous patching cycle.
Processing cleanup actions in parallel.
    Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/8/20241127_033418/fs_clone/ebs12214/log/cleanup.log
Generating report of queued DDL actions.
    Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/8/20241127_033418/fs_clone/ebs12214/adzdallddls.out
Running cleanup in STANDARD mode.
    Log: @ADZDSHOWLOG.sql “2024/11/27 03:39:50”
    [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
Blocking managed server ports.
    Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/8/20241127_033418/fs_clone/ebs12214/txkCloneAcquirePort.log
Performing CLONE steps.
    Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/8/20241127_033418/fs_clone/ebs12214
Beginning application tier FSCloneStage – Wed Nov 27 03:41:07 2024
/u01/oracle/PROD/fs2/EBSapps/comn/util/jdk32/bin/java -Xmx600M -Doracle.jdbc.autoCommitSpecCompliant=false
-Doracle.jdbc.DateZeroTime=true -Doracle.jdbc.DateZeroTimeExtra=true -DCONTEXT_VALIDATED=false -Doracle.installer.oui_loc=/oui -classpath
/u01/oracle/PROD/fs2/FMW_Home/webtier/lib/xmlparserv2.jar:/u01/oracle/PROD/fs2/FMW_Home/oracle_common/modules/
oracle.jdbc_11.1.1/ojdbc6dms.jar:/u01/oracle/PROD/fs2/FMW_Home/oracle_common/modules/oracle.odl_11.1.1/ojdl.jar:
/u01/oracle/PROD/fs2/FMW_Home/oracle_common/modules/oracle.dms_11.1.1/dms.jar::/u01/oracle/PROD/fs2/EBSapps/comn/java/classes:
/u01/oracle/PROD/fs2/FMW_Home/webtier/oui/jlib/OraInstaller.jar:/u01/oracle/PROD/fs2/FMW_Home/webtier/oui/jlib/ewt3.jar:/
u01/oracle/PROD/fs2/FMW_Home/webtier/oui/jlib/share.jar:/u01/oracle/PROD/fs2/FMW_Home/webtier/../Oracle_EBS-app1/oui/jlib/srvm.jar:
/u01/oracle/PROD/fs2/FMW_Home/webtier/jlib/ojmisc.jar:/u01/oracle/PROD/fs2/FMW_Home/
wlserver_10.3/server/lib/weblogic.jar:/u01/oracle/PROD/fs2/FMW_Home/oracle_common/jlib/obfuscatepassword.jar 
oracle.apps.ad.clone.FSCloneStageAppsTier -e /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml -targ
/u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml -stage /u01/oracle/PROD/fs2/EBSapps/comn/adopclone_ebs12214
-tmp /tmp -component appsTier -nopromptmsg 
Log file located at /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/admin/log/clone/FSCloneStageAppsTier_11270341.log
Completed FSCloneStage…
Wed Nov 27 03:57:34 2024
Beginning application tier FSCloneApply – Wed Nov 27 04:02:13 2024
/u01/oracle/PROD/fs2/EBSapps/comn/adopclone_ebs12214/FMW/t2pjdk/bin/java -Xmx600M -Doracle.jdbc.autoCommitSpecCompliant=false
-Doracle.jdbc.DateZeroTime=true -Doracle.jdbc.DateZeroTimeExtra=true -DCONTEXT_VALIDATED=false -Doracle.installer.oui_loc=/oui -classpath
/u01/oracle/PROD/fs2/EBSapps/comn/adopclone_ebs12214/jlib/xmlparserv2.jar:/u01/oracle/PROD/fs2/FMW_Home/oracle_common/modules/
oracle.jdbc_11.1.1/ojdbc6dms.jar:/u01/oracle/PROD/fs2/FMW_Home/oracle_common/modules/oracle.odl_11.1.1/ojdl.jar:
/u01/oracle/PROD/fs2/FMW_Home/oracle_common/modules/oracle.dms_11.1.1/dms.jar::
u01/oracle/PROD/fs2/EBSapps/comn/adopclone_ebs12214/jlib/java:
/u01/oracle/PROD/fs2/EBSapps/comn/adopclone_ebs12214/jlib/oui/OraInstaller.jar:/u01/oracle/PROD/fs2/EBSapps/comn
/adopclone_ebs12214/jlib/oui/ewt3.jar:/u01/oracle/PROD/fs2/EBSapps/comn/adopclone_ebs12214/jlib/oui/share.jar:
/u01/oracle/PROD/fs2/FMW_Home/webtier/../Oracle_EBS-app1/oui/jlib/srvm.jar:/u01/oracle/PROD/fs2/EBSapps/comn/adopclone_ebs12214/jlib/ojmisc.jar:/u01/oracle/PROD/fs2/FMW_Home/
wlserver_10.3/server/lib/weblogic.jar:/u01/oracle/PROD/fs2/EBSapps/comn/adopclone_ebs12214/jlib/obfuscatepassword.jar 
oracle.apps.ad.clone.FSCloneApplyAppsTier -e /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml -targ
/u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml -stage /u01/oracle/PROD/fs2/EBSapps/comn/adopclone_ebs12214 -tmp /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/appltmp -nodbac -component appsTier -nopromptmsg 
Log file located at /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/admin/log/clone/FSCloneApplyAppsTier_11270402.log
Log file located at /u01/oracle/PROD/fs2/inst/apps/PROD_ebs12214/admin/log/clone/FSCloneApplyAppsTier_11270402.log
Target System Fusion Middleware Home set to /u01/oracle/PROD/fs1/FMW_Home
Target System Web Oracle Home set to /u01/oracle/PROD/fs1/FMW_Home/webtier
Target System Appl TOP set to /u01/oracle/PROD/fs1/EBSapps/appl
Target System COMMON TOP set to /u01/oracle/PROD/fs1/EBSapps/comn
Target System Instance Top set to /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214
Report file located at /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/temp/portpool.lst
The new APPL_TOP context file has been created :
  /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml
contextfile=/u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/appl/admin/PROD_ebs12214.xml
Completed FSCloneApply…
Wed Nov 27 04:55:42 2024
Resetting FARM name…
runDomainName: EBS_domain
patchDomainName: EBS_domain
targets_xml_loc: /u01/oracle/PROD/fs1/FMW_Home/user_projects/domains/EBS_domain/sysman/state/targets.xml
Patch domain is not updated, no need to reset FARM name.
Releasing managed server ports.
    Log: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/8/20241127_033418/fs_clone/ebs12214/txkCloneAcquirePort.log
Synchronizing snapshots.
Stopping services on patch file system.
    Stopping 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 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/fs1/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1
adnodemgrctl.sh: exiting with status 2
adnodemgrctl.sh: check the logfile /u01/oracle/PROD/fs1/inst/apps/PROD_ebs12214/logs/appl/admin/log/adnodemgrctl.txt for more information …  
Generating log report.
    Output: /u01/oracle/PROD/fs_ne/EBSapps/log/adop/8/20241127_033418/fs_clone/ebs12214/adzdshowlog.out
The fs_clone phase completed successfully.
adop exiting with status = 0 (Success)
[oracle@ebs12214 scripts]$

Online Patching DB Compliance Checker

Run the Online Patching Database Compliance Checker report to check for online patching database objects standards violations:

[oracle@ebs12214 scripts]$ sqlplus apps/apps

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

This utility reports any violations of the Online Patching Development Standards. All Oracle E-Business Suite violations are fixed by the Release 12.2 upgrade.  You must fix any object listed in this report that is part of your custom code.

Verify AD TXK Version Applied

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.16
atg_pf         Oracle Applications Technology Family       C.11
txk            Oracle Applications Technology Stack        C.16

Hope you found this document informative and gained valuable insights.