News, tips and technical guidance to help you run Oracle E-Business Suite on Oracle Cloud.

Important Information About Patching Your EBS Database in OCI

Robert Farrington, and Terri Noyes

[With special thanks to Paul, Sunil, and Scot for their expert contributions.]

This article provides answers to some common questions on how the EBS database is patched in Oracle Cloud, outlining key differences both from on-premises and between different Oracle Cloud services.

Key Questions

The topics are roughly in the order you might expect to encounter them when getting started with EBS on Oracle Cloud, but can be referred to in whatever order you like.

Q1: Is EBS database patching on Oracle Cloud different from on-premises?
A1: It depends on the service your EBS database is going to run on. If you run on Compute, there are no differences, but if you run on a Database Service, there are both differences and similarities. The remaining questions will highlight some key things you need to know.

Q2: I am running my EBS database on a Compute Service. How do I go about patching?
A2: Essentially, the patching strategy here is the same as for on-premises. You can use the same command line utility, OPatch, to apply both one-off patches as well as quarterly database patch updates including Patch Set Updates (PSU), Bundle Patches (BP), and Release Updates (RU). For more information, refer to Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (MOS Note 1594274.1). This is the same note that has the instructions for on-premises patching.

Q3: I am running my EBS database on a Database Service. What differences are there in patching here?
A3: If you're running your EBS database using a Database Service, you can apply interim (one-off) patches with the OPatch utility. However, quarterly database patch updates must be applied using the appropriate command-line utility such as dbcli for VM DB Systems and dbaascli for Exadata DB Systems. Be aware that when your EBS database is running on an OCI Database Service, you must not use OPatch or the Database Service Console to apply quarterly database patch updates.

Q4: Why are there differences in patching EBS databases on Database Services such as VM DB Systems and Exadata DB Systems?
A4: The Database Service offers additional management capabilities. When running your database on a Database Service, it is important to consider the database tooling used to conduct lifecycle management operations upon the database. Note that when the Database Service tools are used to perform updates such as application of quarterly database patch updates, the metadata maintained by the service is also updated, which is essential to allow continued use of the tooling.

Q5: What are the key steps involved in installing a quarterly database patch update on a Database Service?
A5: The high-level steps are:

  1. Upgrade your cloud tooling to the latest version.
  2. Download the latest EBS Technology Checker (ETCC) as Patch 17537119.
  3. Run ETCC to identify the most recent quarterly database update available.
  4. Run the appropriate command-line utility to identify any conflicting patches, then roll them back as necessary.
  5. Apply the relevant quarterly database patch update using the appropriate command-line utility.
  6. Use OPatch to apply any consolidated database fixes required by EBS.
  7. If you are running on a VM DB System, use OPatch to apply the appropriate OJVM Patch Set Update.
  8. Run ETCC again to confirm that all required patches have been applied.

Q6: Where can I find instructions for installing database patch updates on my particular type of Database Service?
A6: Follow the comprehensive steps in the appropriate document from this list:


Related Articles

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.