ODA : Where to locate and how to create OPatch output on ODA : Used for determining if a patch is included in an existing ODA version
(Doc ID 1562277.1)
Last updated on MARCH 04, 2019
Applies to:Oracle Database Appliance Software - Version 188.8.131.52 to 184.108.40.206 [Release 2.1 to 12.1]
Information in this document applies to any platform.
This note will help you confirm the current patchset patches and version that you have installed on your ODA
The process is similar to other GI and RDBMS methods which uses the opatch oraInventory information to confirm known patches
However, the ODA, unlike other RDBMS based products, does not generally include a Patchset exception or backport process
ODA uses Quarterly patches similar to RDBMS. In fact, the ODA includes RDBMS / GI Quarterly patch bundles as part of the ODA Quarterly bundle patchset
ODA quarterly patch bunldes are typically released approximately four to five weeks after the most current RDBMS and GI Q patch bundles are released.
This time period allows ODA dev to maximize current fixes while allowing for comprehensive OneCommand patchset testing.
We need to apply a patch on our ODA but do not know if it is currently installed or will be installed in an existing or upcoming release
Q> What are the steps to check for an existing patch and request a patch if it does not already exist?
Q>Oracle has released a patch that corrects our current problem. How can we confirm this fix exists in our current ODA quarterly patch bundle?
Q> What should we do to get this patch as soon as possible?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!