Jan 2024 Updates to EBS Critical Patch Update Checker (ECPUC)

January 20, 2024 | 3 minute read
Elke Phelps
Product Management Director
Text Size 100%:

EBS Critical Patch Update Checker (ECPUC) has been updated with the January 2024 Critical Patch Update (CPU). We strongly recommend that you run the latest ECPUC against your EBS environment to:

  •     Identify your environment's current EBS CPU patch level.
  •     Identify required EBS CPU patches and security fixes for your environment.

Obtaining ECPUC

ECPUC is avaialble with Patch 35583866.  Instructions for running ECPUC are documented in the README.txt file included with the patch.  


Patch 35583866 provides a script, ECPUC.sql. When run, ECPUC.sql generates the ECPUC.lst report which includes your current EBS CPU level and a list of all required EBS CPU patches and security fixes for your environment for a given quarterly EBS CPU.

Usage Tips

Read the README carefully.  The README for this patch includes a number of usage scenarios and examples.

Always use the latest version of ECPUC. New EBS CPU patches and fixes will not be checked by older versions of the utility.

As part of your quarterly CPU patching activity:

  • Run ECPUC before applying EBS CPU patches and fixes. You should run ECPUC before applying the latest EBS CPU patches to identify the patches and bug fixes that are required for your environment.
  • Apply all recommended patches as soon as possible. If ECPUC reports recommended patches or fixes, you should apply these to your enviornment as soon as possible.
  • Run ECPUC after applying EBS CPU patches and fixes. You should run ECPUC after applying patches and performing cutover to confirm that all recommended patches and fixes were applied successfully.

Run ECPUC to review and report on your EBS CPU level. You may be required to review and report on the EBS CPU level of your environment. To check the EBS CPU level in your environment, run ECPUC and review the ECPUC.lst report to determine your EBS CPU level and identify any recommended patches.

Note:  You should always apply patches and fixes to non-production envrionments prior to promoting and applying to production.

Additional References

Related Articles

Elke Phelps

Product Management Director

Elke is a Product Manager in the Oracle E-Business Suite Applications Technology Group.  She joined Oracle in 2011 after having been an Oracle customer and Oracle Technologist (Oracle Database Administrator, Oracle Applications DBA, Technical Architect and Technical Manager of an Oracle Applications DBA Team) since 1993.  As part of the Oracle E-Business Suite Applications Technology Product Management Team, her scope of responsibility includes security, database certifications and advanced architectures for on-premises and Oracle Cloud deployments.  She is a frequent contributor and editor of the Oracle E-Business Suite Technology Blog.

Elke is the lead author of the Oracle Applications DBA Field Guide (Apress 2006) and Oracle R12 Applications DBA Field Guide (Coqui Tech and Press 2010).  Elke is also the founder of the Oracle Applications User Group (OAUG) E-Business Suite Applications Technology Special Interest Group (SIG) and served as President of the SIG from February 2005 - August 2011.  Elke has been a speaker at the Oracle OpenWorld and Collaborate conferences since 2004.  Prior to joining Oracle, Elke was designated an Oracle ACE (2007) and Oracle ACE Director (2009).  She received the OAUG Oracle Ambassador of the Year award in 2015.

Elke has a Computer Science Degree and a Masters of Business Administration from the University of Oklahoma.  In her spare time, Elke enjoys traveling especially to Europe, Puerto Rico and the amazing US National Parks.  Elke also enjoys hiking, antiquing, gardening and cooking. 


Previous Post

JRE 1.8.0_401 Certified with EBS Release 12.2

Tahir Ahmad | 3 min read

Next Post

Upgrade Support for Oracle Database and

Elke Phelps | 2 min read