Applying the October 2025 Critical Patch Update (CPU) in EBS R12.2

Oracle E-Business Suite Release 12.2 – Applying the October 2025 Critical Patch Update (CPU)

Overview

This article outlines the high-level procedure for applying the Oracle E-Business Suite (EBS) Release 12.2 October 2025 Critical Patch Update (CPU).

CPU Patch: 38298685

Before beginning the implementation, review My Oracle Support Document 3102287.1 – Oracle E-Business Suite 12.2 Critical Patch Update Availability Document (October 2025) to understand the prerequisites, patch dependencies, and any platform-specific requirements.

Pre-Implementation Checks

1. Verify the Current File System

Confirm that the environment is running from the Run File System.

echo $FILE_EDITION

Expected output:  run

2.  Correct File Permissions

Before starting the patching cycle, ensure the required permissions are available on the Patch File System.

Important: Perform this step only on the Patch File System of both the primary and secondary application nodes. Do not modify permissions on the Run File System.

cd $PATCH_BASE/EBSapps
chmod -R 755 10.1.2

3. Verify ADOP Status

Confirm that no previous online patching cycle is active.

adop -status

4. Start the Prepare Phase

Initialize a new online patching cycle.

adop phase=prepare

5. Check for Invalid Database Objects

Before applying patches, verify the database does not contain unexpected invalid objects.

SELECT COUNT(*)
FROM dba_objects
WHERE status='INVALID';

Validate the object count for both the Run and Patch editions.

Applying the CPU and Required Patches

Verify again that the active edition is the Run File System.

echo $FILE_EDITION

Apply the CPU patch.

adop phase=apply patches=38298685

Apply the remaining prerequisite and dependent patches individually.

adop phase=apply patches=38261405

adop phase=apply patches=37450688

adop phase=apply patches=38180394

adop phase=apply patches=38510732

adop phase=apply patches=37078855

adop phase=apply patches=36453170

adop phase=apply patches=25229413 options=forceapply

Finalize and Cutover

Once all patches have been applied successfully, complete the online patching cycle.

Finalize Phase

adop phase=finalize

Cutover Phase

adop phase=cutover mtrestart=no

Update AutoConfig Code

After the cutover completes, synchronize the configuration files by running AutoConfig.

Verify the active edition.

echo $FILE_EDITION

Expected output:

run

AutoConfig on Application Tier

Source the application environment.

Run AutoConfig in the following sequence:

  • Primary Application Node
  • DMZ Application Node
  • Primary Application Node (final verification run)

After completion, verify invalid database objects again.

SELECT COUNT(*)
FROM dba_objects
WHERE status='INVALID';

Refresh Database AutoConfig Files

Step 1 – Generate a New appsutil.zip

From the application tier:

perl $AD_TOP/bin/admkappsutil.pl

A new appsutil.zip file will be created under:

<INST_TOP>/admin/out

Step 2 – Copy appsutil.zip to the Database Tier

Move the newly generated archive to the database Oracle Home.

cd <RDBMS_ORACLE_HOME>

cp appsutil.zip appsutil.zip_bkp

cp <INST_TOP>/admin/out/appsutil.zip .

Extract the archive.

unzip -o appsutil.zip

Source the database environment before proceeding.

Example:

. ./Test_ebsnode.env

Step 3 – Run AutoConfig on the Database Tier

Execute AutoConfig from the database Oracle Home to synchronize the updated configuration files.

Restart Application Services

After AutoConfig completes successfully:

  • Start services on the Primary Application Node.
  • Start services on the DMZ Application Node.

Confirm that the environment is operating from the Run File System.

echo $FILE_EDITION

Complete the Online Patching Cycle

Execute the cleanup phase to remove obsolete patching objects and reclaim space.

adop phase=cleanup

Post-Implementation Validation

Perform a final validation by checking for invalid objects.

SELECT COUNT(*)
FROM dba_objects
WHERE status='INVALID';

Review the output to ensure no unexpected invalid objects remain.

Summary

Applying the Oracle EBS 12.2 October 2025 Critical Patch Update is more than simply installing the CPU patch. A successful implementation requires careful execution of the complete online patching lifecycle, including:

  • Verifying the environment before patching
  • Preparing the online patching cycle
  • Applying the CPU and all required prerequisite patches
  • Executing the Finalize and Cutover phases
  • Updating AutoConfig on both application and database tiers
  • Restarting services
  • Performing cleanup
  • Validating the environment after completion

Following this structured approach helps minimize downtime, maintains application consistency, and ensures the environment is fully synchronized after the Critical Patch Update.

Recent Posts