Remove a Federated Partition

Federated partitions are not migrated, so when moving your application to another server or version, you need to delete the federated partition and recreate it in the new environment.

When you need to remove a federated partition between Essbase and Autonomous Data Warehouse Serverless, take the following actions to ensure that associated tables are cleaned up in Autonomous Data Warehouse.

1. Ensure that in the application settings, startup is enabled.

   In the Essbase web interface, the setting is controlled by the Allow Users to Start Application check box.

   
   
   
   
   

   In MaxL, the setting is controlled by:

   alter application APP-NAME enable startup;

2. Delete the federated partition from the application. This action removes all of the Essbase helper tables and associated artifacts from Autonomous Data Warehouse (but does not remove the fact table).

   1. Log in to the Essbase web interface as a database manager or higher.

   2. On the Applications page, expand the target application. In the row for the target cube, click the Actions menu, and click Inspect.

   3. Select the Partitions tab.

   4. Click the Actions menu to the right of the partition definition, and click Delete.

   5. Click Yes to confirm you want to delete the partition and allow the application to restart.

3. Remove the connection, if one was created at application level, and was intended only for the federated partition. If the federated partition was designed using a global connection, it is possible that the connection may be in use for additional purposes in your organization. If you aren't sure, check with a system administrator.

4. If the federated partition had to be removed due to a Database port change, you may need to use SQL Developer to manually delete Essbase-generated tables and other artifacts, if they failed to be removed with the federated partition. The table names begin with ESSAV_. For more details, refer to What to Do if the Database Connection Details Changed.