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:

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.

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.

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.

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

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.

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.

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

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

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

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.

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

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.

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

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

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.

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.

Oracle Solutions We believe in delivering tangible results for our customers in a cost-effective manner

(ECPUC) EBS Critical Patch Update Checker-OCT-2024

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

Key Features of ECPUC:

Security Validation:

Automated Assessment:

Comprehensive Reporting:

Simplification of Patch Management:

Benefits of Using ECPUC:

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

Dowloading ECPUC Patch

Unzip ECPUC Patch and Run ECPUC.sql

Checking ECPUC report

Dowloading Patches in ECPUC List

Unzip and Apply CPU Patch for OCT 2024

Update Database Tier to Latest Autoconfig Code

Create the New appsutil.zip

Autoconfig on DB and APPS

Unzip Apply Other Patches in ECPUC LIST

Run ECPUC.sql again and Check the Report

Hope you found this document informative and gained valuable insights.

About Syed Saad

Related Articles

Check Also

Proudly in the Top 100 Oracle Blogs on the Web

One comment

Leave a Reply Cancel reply

(ECPUC) EBS Critical Patch Update Checker-OCT-2024

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

Key Features of ECPUC:

Security Validation:

Automated Assessment:

Comprehensive Reporting:

Simplification of Patch Management:

Benefits of Using ECPUC:

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

Dowloading ECPUC Patch

Unzip ECPUC Patch and Run ECPUC.sql

Checking ECPUC report

Dowloading Patches in ECPUC List

Unzip and Apply CPU Patch for OCT 2024

Update Database Tier to Latest Autoconfig Code

Create the New appsutil.zip

Autoconfig on DB and APPS

Unzip Apply Other Patches in ECPUC LIST

Run ECPUC.sql again and Check the Report

Hope you found this document informative and gained valuable insights.

About Syed Saad

Related Articles

Oracle ACE PRO Award To Syed Saad Ali 2025

Create Accounting Concurrent Program, Application Erros with ORA-01555: Snapshot Too Old

Purge Concurrent Request and Manager Data – Part1

Check Also

Proudly in the Top 100 Oracle Blogs on the Web

One comment

Leave a Reply Cancel reply