Moving Globally Distributed Exadata Database on Exascale Infrastructure Resources

You can move a Globally Distributed Exadata Database on Exascale Infrastructure (Distributed ExaDB-XS) from one compartment to another.

Caution:

If you need to move a Distributed ExaDB-XS resource, please contact Oracle customer support first. There may be unintended consequences to moving any resource within the Distributed ExaDB-XS configuration. See Moving Resources to a Different Compartment for more information.

Note:

  • Move resource is not allowed if any GSM, shard, or catalog is in a failed state.

  • As soon as you move the Distributed ExaDB-XS to a different compartment, the policies that govern the new compartment apply immediately and affect access to the database. Therefore, your access to the database may change, depending on the policies governing your Oracle Cloud user account's access to resources.

    After the Distributed ExaDB-XS move to a new compartment is successful, any work request logs associated with the Distributed ExaDB-XS from the original compartment are no longer available.

To move Distributed ExaDB-XS you must have the right to manage Distributed ExaDB-XS in its current compartment and in the compartment you are moving it to.

  1. On the Globally Distributed Exadata Database on Exascale Infrastructure list page, select a Distributed ExaDB-XS you want to move.
  2. Select the Move resource action.
  3. In the Move to a different compartment dialog, select the compartment to move the Distributed ExaDB-XS to.
  4. Click Move to start the operation.

Parent topic: Create and Manage Oracle Globally Distributed Exadata Database on Exascale Infrastructure