Essbase Stack Deployment on Oracle Cloud Infrastructure

Patch and Roll Back - for Version 19.3.0.3.4 and Later

You can patch and roll back an Oracle Essbase stack deployment on Oracle Cloud Infrastructure.

You cannot roll back to a version that is older than the one used to configure the Essbase instance.

Note:

If you created connections or Datasources after applying the patch, and then roll back the patch, you must re-create them. This step is required for drill through and other connection-dependent features to continue working as before.

Note:

If Essbase is configured to use Object Storage buckets or Smart View for Office 365, rolling back to any Essbase version prior to 21.4 is not supported.

Note:

If you are updating a stack image, see the stack deployment instructions, under the General Settings page steps, in Deploy Essbase.

Access the Essbase node using SSH. See Access Oracle Essbase Using SSH.
As opc user, sudo to oracle user:
```
sudo su oracle
```
Then, as oracle user, access scripts in esstools, with this path:
```
cd /u01/config/domains/essbase_domain/esstools/bin
```
Stop Essbase instance, as oracle user, using the script:
```
./stop.sh
```

Set environment variables, as oracle user.

export ORACLE_HOME=/u01/oracle
export OPATCH_NO_FUSER=true

Download the OPATCH patch file from My Oracle Support. If you do not have access to patches in My Oracle Support, please open a service request with Oracle Support.
Copy the downloaded patch zip file to cloud instance, using a tool such as WinSCP, SCP, Filezilla, or others.
If you use WinSCP, for example, on the WinSCP Login page, under Session, enter the Host name, Port number, User name opc, Private key file, and click Login. The file is copied.
Ensure that oracle user has read access to the OPATCH file.
Apply OPATCH, as oracle user. You can apply OPATCH directly, while in zip format. Provide the absolute path of the zip file.
```
 $ORACLE_HOME/OPatch/opatch apply /tmp/Marketplace/<OPATCH_ID>.zip
```
Note: You can optionally unzip the zip file and apply the patch. Provide the absolute path of the unzipped folder.
```
unzip ./<OPATCH_ID>.zip
$ORACLE_HOME/OPatch/opatch apply /tmp/Marketplace/<OPATCH_ID>/ 
```
Start the Essbase cloud instance, as oracle user, and access scripts in esstools with this path: cd /u01/config/domains/essbase_domain/esstools/bin. Start Essbase instance, as oracle user. using the script: ./start.sh.
```
cd /u01/config/domains/essbase_domain/esstools/bin
    ./start.sh
```
Verify the log to see that all binaries patched successfully. Log in to Essbase instance and verify the build number in admin→About.
[OPTIONAL] If you need to roll back the applied patch, do the following steps.
1. If the Essbase instance is running, first stop Essbase system service, as oracle user, as described above.
2. Run the rollback command:
```
$ORACLE_HOME/OPatch/opatch rollback -id <OPATCH_ID>
```
  For example: $ORACLE_HOME/OPatch/opatch rollback -id 30081463
3. Start the Essbase instance after rollback. If you're unable to login in, clear the Essbase related browser cache or open a new browser.