1. Essbase Stack Deployment on Oracle Cloud Infrastructure
  2. Manage the Oracle Essbase Stack on Oracle Cloud Infrastructure
  3. Start, Stop, and Destroy an Essbase Stack Instance

Start, Stop, and Destroy an Essbase Stack Instance

You stop, start, and destroy the Essbase stack instance in the Oracle Cloud Infrastructure console.

Topics:

Prepare to Work with an Essbase Stack Instance

Before you can work with the Essbase stack instance, navigate to the instance and find the public IP address.

Navigate to the Essbase Instance in the Oracle Cloud Infrastructure console:

  1. Log in to the Oracle Cloud Infrastructure control panel on cloud.oracle.com.
  2. Open the navigation menu Image of the OCI navigation menu icon. and click Compute, Instances.
  3. Choose your compartment.
  4. Select the Essbase instance you want to manage.
  5. Navigate to the compute instance in the Oracle Cloud Infrastructure console.
  6. Under Primary VNIC Information, find the Public IP Address.

Start the Stack

The stack includes the Autonomous Transaction Processing instance, the compute instance, two block storage volumes, object storage bucket, load balancer, and additional network components.

When starting the stack, you must start the Autonomous Transaction Processing instance first, and then the compute instance. Starting the compute instance starts Essbase.

Start the Autonomous Transaction Processing instance:

  1. Log in to the Oracle Cloud Infrastructure control panel, cloud.oracle.com.
  2. Open the navigation menu. Under Database, select Autonomous Transaction Processing.
  3. Choose your compartment.
  4. In the list of autonomous databases, click on the display name of the database you wish to administer.
  5. Click Start.

Start the Essbase compute:

  1. Confirm in the Oracle Cloud Infrastructure interface that the autonomous database is available.
  2. Navigate to the compute instance on the Oracle Cloud Infrastructure console. See Prepare to Work with an Essbase Stack Instance.
  3. Click Start.

    This takes a few minutes.

Stop the Stack

The stack includes the Autonomous Transaction Processing instance, the compute instance, two block storage volumes, object storage bucket, load balancer, and additional network components.

When stopping the stack, you must stop the compute instance first, and then the Autonomous Transaction Processing instance. Stopping the compute instance stops Essbase.

Stop the compute instance:

  1. Navigate to the compute instance in Oracle Cloud Infrastructure console. See Prepare to Work with an Essbase Stack Instance.
  2. Click Stop.

    This shuts down the instance. After the instance is stopped, the Start button is enabled.

    When you stop your compute instance, billing stops for CPU usage.

Stop the Autonomous Transaction Processing instance:

  1. Confirm in the Oracle Cloud Infrastructure interface that the compute instance is stopped.
  2. Open the navigation menu. Under Database, select Autonomous Transaction Processing.
  3. Choose your compartment.
  4. In the list of autonomous databases, click on the display name of the database you wish to administer.
  5. Click Stop.

    Billing for storage continues when Autonomous Transaction Processing is stopped.

Only the compute instance and the Autonomous Transaction Processing instance are stopped when you stop the stack.

Destroy the Stack

Destroying the stack terminates all resources that were created when the stack was created, including the Essbase compute node, the Autonomous Database instance, and network components.

Note:

The Destroy action is permanent and cannot be reversed.

Before you destroy the stack, ensure that the bucket is empty. For instructions, see "Using the Console" in Managing Objects. The bucket name is backup_databasename.

When using a shared database, delete schemas created by Essbase prior to destroying the stack, or your database may contain orphaned database content. To delete the schemas, ssh to the compute instance and run /u01/vmtools/sysman/drop-schema.sh. You're prompted to enter your database administrator password.

    1. If using a shared, existing database, it's recommended to delete schemas created by Essbase, prior to destroying the stack, or your database may contain orphaned database content. To do this, ssh into the compute instance and run the following: /u01/vmtools/sysman/drop-schema.sh and use the drop-schema.sh tool to drop the schemas from the existing database.
    2. In the object storage bucket for the database backups, manually delete all items.
  2. Click the navigation menu Image of the OCI navigation menu., select Resource Manager, and then click Stacks.
  3. Click on your stack.
  4. Click Terraform Actions, and then select Destroy.
  5. When prompted for confirmation, click Destroy.
  6. Periodically monitor the progress of the Destroy job until it is finished.

    If the destroy job fails, manually terminate the resources that run as part of the stack on Oracle Cloud Infrastructure before you destroy the stack. For example, terminate the networking load balancer (if used), terminate the virtual cloud network (VCN), and terminate the Autonomous database.

    If an email address is associated with your user profile, you receive an email notification.

    Proceed with destroying the stack regardless of whether the job passes or fails.

  7. Click Destroy Stack.

    Note:

    There are cases in which the Destroy job may fail:

    • if private endpoint is chosen for the database; re-run Destroy job
    • if catalog storage is done in object storage bucket: delete the objects in the bucket and then re-run Destroy job
    • if backup operation was performed; delete the backup from the bucket and re-run Destroy job

    Refer to destroy job logs for more information.

  8. When prompted for confirmation, click Delete.