Destroying the Essbase stack fails if the object storage bucket in the compartment associated with the stack isn't empty.
After a restore from a backup of Autonomous Transaction Processing - Dedicated (ATP-D), Essbase doesn’t restart.
Workaround: Start the administration server and the managed server manually by running the start.sh script, as follows:
- As opc user, sudo to oracle user:
sudo su - oracle
- Then, as oracle user, access scripts in esstools with this path:
- Start the services, using this script: