This is my first time patching and I would like some guidance...:
- I upgraded EPM 188.8.131.52 to EPM 184.108.40.206.000 consisting of Foundation services, Workspace, APS, EAS, Essbase server and Essbase studio components.
Below two patches can be applied on releases: "220.127.116.11.100,18.104.22.168.101,22.214.171.124.102" as per the readme
16171596 - "PATCH SET UPDATE: ORACLE ESSBASE STUDIO SERVER 126.96.36.199.103 (Patch)" for "Oracle Solaris on SPARC (64-bit)"
16171601 - "PATCH SET UPDATE: ORACLE ESSBASE STUDIO CONSOLE MSI 188.8.131.52.103 (Patch)" for "Oracle Solaris on SPARC (64-bit)"
and below patch can be applied on Release "184.108.40.206.100,220.127.116.11.101,18.104.22.168.102,22.214.171.124.103"
16674524 - "MERGE PATCH FOR MULTIPLE DEFECTS FOR STUDIO SERVER 126.96.36.199.103 PSE (Patch)" for "Oracle Solaris on SPARC (64-bit)"
1. So once I apply patches 14400511,14400514 to Essbase Studio 188.8.131.52.000 and upgrade it to 184.108.40.206.100, can I directly apply patches 16171596,16171601 to upgrade to 220.127.116.11.103?
2. If yes, does that mean that 18.104.22.168.103 contains the fixes provided by 22.214.171.124.102 ?
The base release for Essbase products is 126.96.36.199.100 so you will already be at that level.
You should be able apply 16171601 or 16674524, .103 should contain previous patches.
Thank you John.
Hi John / All,
I am planning to patch all components up to the latest patch... I am not sure what strategy would be better. Could someone kindly advice on this...
1. Apply patches Component-wise:
- I could apply all patches for one component and then proceed to the next component..Check if the services are running fine or if the defects are fixed and then proceed.
- Eg. Patch Essbase server to 188.8.131.52.103 from 184.108.40.206.100. Then patch Essbase Studio from 220.127.116.11.000 to 18.104.22.168.103.
2. Patch all components to a particular version :
- Patch all components to the same version. This makes sense to me as patches are rolled out together.. so as having one component with the latest patches might have issues working with a less-recently patched component..
- Eg. Patch Essbase and Essbase studio components to 22.214.171.124.101. Then patch these components to 126.96.36.199.102...
Also, in the case of the below patches:
16171583-PATCH SET UPDATE: HYPERION ESSBASE CLIENT 188.8.131.52.103 (Patch)
16171585-PATCH SET UPDATE: HYPERION ESSBASE RTC 184.108.40.206.103 (Patch)
16171586-PATCH SET UPDATE: HYPERION ESSBASE SERVER 220.127.116.11.103 (Patch)
.. for "Oracle Solaris on SPARC (64-bit)" can be applied on releases: "18.104.22.168.100,22.214.171.124.101,126.96.36.199.102"
3. Can I run opatch for above patches and then proceed with the restart and other mentioned activities..? or is it that every patch needs to be applied individually?
Your approach 1 should also be fine, because as per Oracle readmes, you can apply latest patch (.103) to the base version(.100) as well. So directly going from .100 -> .103 is fine.
As John says, this should cover patches in between. No need to apply every patch (.101 / .102) i.e. individually.
After applying all patches, you can cross check them (patch number & defect fixed) using Opatch lsinventory command.
okay. The thing is, I do not see the defects in .102 or any other intermediate patches, so there is no way to verify whether they got fixed. So from what I have understood how patches should work - if I apply the latest patch that can be applied on some base patch, then the intermediate "bug fixes" would always be part of the latest patch.
As the patch does not say it requires previous patches and says it can be applied to 188.8.131.52.100 then I would take it as cumulative.