DeleteDatabase
DELETE {{baseUrl}}/databases/:databaseId?performFinalBackup=false
Deletes the specified database. Applies only to Exadata systems.
The data in this database is local to the Exadata system and will be lost when the database is deleted. Oracle recommends that you back up any data in the Exadata system prior to deleting it. You can use the performFinalBackup
parameter to have the Exadata system database backed up before it is deleted.
Request Params
Key | Datatype | Required | Description |
---|---|---|---|
performFinalBackup | boolean | Whether to perform a final backup of the database or not. Default is false. |
If you previously used RMAN or dbcli to configure backups and then you switch to using the Console or the API for backups, a new backup configuration is created and associated with your database. This means that you can no longer rely on your previously configured unmanaged backups to work.
This parameter is used in multiple APIs. Refer to the API description for details on how the operation uses it. |
HEADERS
Key | Datatype | Required | Description |
---|---|---|---|
if-match | string | For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match | |
parameter to the value of the etag from a previous GET or POST response for that resource. The resource | |||
will be updated or deleted only if the etag you provide matches the resource's current etag value. | |||
opc-request-id | string | Unique identifier for the request. | |
Accept | string |