DeleteDbHome
DELETE {{baseUrl}}/dbHomes/:dbHomeId?performFinalBackup=false
Deletes a Database Home. Applies to bare metal DB systems, Exadata Cloud Service, and Exadata Cloud@Customer systems.
Oracle recommends that you use the performFinalBackup parameter to back up any data on a bare metal DB system before you delete a Database Home. On an Exadata Cloud@Customer system or an Exadata Cloud Service system, you can delete a Database Home only when there are no databases in it and therefore you cannot use the performFinalBackup parameter to back up data.
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. | |||
Accept | string |