Patch and Restore
You can patch Oracle Essbase instances, using OPatch tool, which runs patches to a new version of binaries. You can also roll back an update, if necessary.
Rollback from a patch, to a version that's older than what was used to configure the Essbase instance, is not supported.
Note:
If you created Connections or Datasources after applying the patch, and then roll back the patch, you must re-create the Connections or Datasources.Note:
After you roll back an OPatch, you may need to recreate transparent and replicated partitions, and re-validate the partitions.Note:
When you need to upgrade Java, from JDK 1.8.0_291 or higher, to 1.8.0_331, see Upgrade Java after Configuration to JDK 1.8.0_331 or Higher.To install a software update (patch/upgrade) to an Essbase instance
[Optional] Rollback update if necessary
- Stop the servers.
For Linux:
sh <Oracle_Home>/user_projects/domains/essbase_domain/esstools/bin/stop.sh
For Windows:<Oracle_Home>\user_projects\domains\essbase_domain\esstools\bin\stop.cmd
- Get the Unique OPatch ID.
For Linux:
<Oracle_Home>/OPatch/opatch lsinventory
For Windows:<Oracle_Home>\OPatch\opatch lsinventory
- Roll back the applied OPatch. The following sample syntax shows an OPatch ID example. Use the relevant OPatch ID.
For Linux:
<Oracle_Home>/OPatch/opatch rollback -id 3012639
For Windows:
<Oracle_Home>\OPatch\opatch rollback -id 3012639
- Check the current build number.
For Linux:
cat <Oracle_Home>/essbase/bi-epm-registry/baseproperties/essbase/essbase_registry.properties
For Windows (open essbase_registry.properties using Notepad):<oracle_home>\essbase\bi-epm-registry\baseproperties\essbase\essbase_registry.properties
- Start the servers.
For Linux:
sh <Oracle_Home>/user_projects/domains/essbase_domain/esstools/bin/start.sh
For Windows:
<Oracle_Home>\user_projects\domains\essbase_domain\esstools\bin\start.cmd