Oracle versions numbers can be very long.  Complicating matters further, different product families within Oracle use the version hierarchy differently.  This can make it confusing to determine whether a specific product update has been certified with Oracle E-Business Suite.

Specifically, a customer recently asked whether it was acceptable to apply the Oracle Access Manager 11.1.2.2.8 update to their OAM instance that was integrated with EBS 12.1.3.  They were concerned because our OAM integration documentation for that combination explicitly specified compatibility with OAM 11.1.2.2.0.

The OAM team uses the fifth digit for Bundle Patches, Patch Set Updates (PSU) and Security Patch Updates (SPU).  In this particular case, the fifth-level digit in the Oracle Access Manager version is not relevant.  In other words, the customer could apply OAM 11.1.2.2.8 because it was covered by the OAM 11.1.2.2.0 certification.  

For example, all of the following OAM updates will work with EBS 12.1.3:

  • OAM 11.1.2.2.0 (documented certification)
  • OAM 11.1.2.2.1
  • OAM 11.1.2.2.2
  • OAM 11.1.2.2.3
  • OAM 11.1.2.2.4
  • OAM 11.1.2.2.5
  • OAM 11.1.2.2.6
  • OAM 11.1.2.2.7
  • OAM 11.1.2.2.161018

This is sometimes shown in our documentation in either of the following ways:

  • OAM 11.1.2.2
  • OAM 11.1.2.2.x

The absence of a fifth-digit or the presence of an ‘X’ in the fifth digit’s place means any fifth-digit level updates may be applied to an OAM environment integrated with EBS 12.1.3 without requiring a new certification.  This applies to all environments, including test and production.

 

Related Articles