1. Essbase Stack Deployment on Oracle Cloud Infrastructure
  2. Back Up and Restore Essbase
  3. Back Up and Restore an Essbase Instance
  4. Back Up and Restore: Version 21.1 and Prior

Back Up and Restore: Version 21.1 and Prior

There are two backup/restore use cases for Essbase version 21.1 and older. Your choice of schema database and the number of Essbase instances you have deployed in it defines how you will need to take backups.

Note:

The steps in Oracle-Scripted and Non-Oracle Scripted Backup processes, mentioned in this documentation are only applicable for Autonomous Transaction Processing database.

Oracle-Scripted Backup and Restore:

When you deploy an Essbase stack, the default behavior is to deploy a new Autonomous Transaction Processing database as part of the stack. If you have a single Essbase stack with schemas deployed into a single Autonomous Transaction Processing database, you can take your backups using the scripts provided with Essbase 19c or 21.1.

Non-Oracle-Scripted Backup and Restore:

If you did not use an Autonomous Transaction Processing database or you have deployed multiple Essbase stacks into a single relational database, you cannot use the backup scripts that come with Essbase 19c or 21.1. Instead, you will back up the data block volume and Essbase database schema as instructed in this chapter.

We’ve made some assumptions to limit the size and scope of this chapter. All examples assume that:
  • Autonomous Transaction Processing is the relational database into which Essbase schemas are deployed.
  • Oracle Identity Cloud Service (IDCS) is the security provider for the Essbase deployment.
  • The Essbase system admin user name (stored in WebLogic; it is the only non-IDCS user in the system) is the same between the source and the target Essbase stacks.
  • At the time of restore, the source instance backup has at least one valid Oracle Identity Cloud Service user with an Essbase system administrator role.