Manage Exascale Database Vaults on Oracle Exadata Database Service on Exascale Infrastructure
You can view, scale, and delete Exascale Database Storage Vaults on Oracle Exadata Database Service on Exascale Infrastructure (ExaDB-XS).
Viewing Exascale Database Storage Vaults
- Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Exascale Infrastructure
- Click Exascale Storage Vaults.
- Select the Vault for which you want to view information.
Deleting Exascale Database Storage Vaults
- Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Exascale Infrastructure
- Click Exascale Storage Vaults.
- Select the Vault that you want to delete.
- Click Actions and select Delete.
- Confirm that you want to delete the Vault.
You can only delete Exascale Database Storage Vaults that no longer have any associated VM Clusters. If you still have associated VM Clusters on the Vault, then you must first delete those VM Clusters, and then return to these steps to delete your Exascale Database Storage Vault.
Scaling Exascale Database Storage Vault
- Open the navigation menu. Under Oracle Database, click Oracle Exadata Database Service on Exascale Infrastructure
- Click Exascale Storage Vaults.
- Select the Vault that you want to scale.
- Click Scale Storage Vault.
- On the Scale Storage Vault dialog, scale the storage manually. You
will also have the option to auto scale the storage up to a predefined limit.
-
Scale the storage capacity manually: Enter storage capacity. This number should be the value for the total storage that you want to have provisioned after the scaling operation completes. In addition to the default flash cache included in the base storage capacity, you can choose to configure additional smart flash cache as a percentage of provisioned storage capacity.
- Scale the storage using storage auto scaling: Enable auto scale on the Vault by selecting Storage auto scaling.
If enabled, specify Auto scaling limit (GB).
Note
- The storage auto scaling feature is not available with Oracle Database 19c.
- Auto scale is primarily intended to accommodate the ongoing, organic growth of databases. For large, sudden data loads or rapid data growth that can exceed 5% of the allocated vault size within a short time period, it is recommended to manually scale storage in advance to avoid potential out-of-space errors.
- Tablespaces with auto-extend enabled can cause out-of-space errors if the auto-extend increment size is greater than 5% of the allocated vault storage. This could be caused if a single, large tablespace auto-extension suddenly exceeds the available space in the vault before crossing the auto scale threshold. Or, it could also be caused by multiple tablespaces extensions occurring concurrently, resulting in the same effect. It is recommended that you manage your tablespace auto-extend increment settings to avoid having more than 5% of the allocated vault storage added at once when using auto scale.
-
- Click Scale.
Parent topic: How-to Guides