Apply a Patch

put

/paas/api/v1.1/instancemgmt/{identityDomainId}/services/dbaas/instances/{serviceId}/patches/{patchId}

Applies a patch to an Exadata Cloud Service database deployment.

Request

Supported Media Types
Path Parameters
  • The value depends on the type of Exadata Cloud Service account that is used to make the request:

    • For a Traditional Cloud Account, specify the Identity Domain Name that is associated with the service.

    • For a Cloud Account with Identity Cloud Service, specify the Identity Service Id that is associated with the service, which has the format idcs-letters-and-numbers.

  • Patch ID. The patch ID can be retrieved via getting the list of available patches.
  • Name of the Exadata Cloud Service deployment.
Header Parameters
Body ()
The request body contains details of the patch request. There are no required values.
Root Schema : Request Body
Type: object
Title: Request Body
Show Source
  • Free-form text to provide additional information about the patching operation.
  • Specifies whether the patch should be applied even if the precheck finds conflicts. Valid values are true and false. When true is specified, patch conflicts or errors discovered during the precheck stage of the patching operation are ignored and the patch is applied (space permitting). Otherwise, if conflicts or errors are discovered, the patch is not applied.

    Default value is false.

  • Specifies whether a Data Guard switchover operation is performed on the primary database before applying the patch. Valid values are true and false.

    Default value is false.

    (Applicable only to deployments associated with a Data Guard configuration.)

Back to Top

Response

Supported Media Types

202 Response

Accepted. See Status Codes for information about other possible HTTP status codes.
Body ()
Root Schema : Response Body
Type: object
Title: Response Body
Show Source
Nested Schema : Details Object
Type: object
Title: Details Object
Show Source
Back to Top

Examples

The following example shows how to apply a patch on an Exadata Cloud Service database deployment by submitting a PUT request on the REST endpoint using cURL.

In this example, the identity domain is usexample and the Oracle Cloud user name and password are serviceadmin and Pa55_word. The name of the database deployment is db12c and the patch identification number is 24968615.

cURL Command

In the following cURL command, the request body is provided directly in the -d option.

curl -i -X PUT --cacert ~/cacert.pem -u serviceadmin:Pa55_word -H "X-ID-TENANT-NAME:usexample" -H "Content-Type:application/json" -d '{ "additionalNote" : "Patch applied using REST API" }' https://dbaas.oraclecloud.com/paas/api/v1.1/instancemgmt/usexample/services/dbaas/instances/db12c/patches/24968615

HTTP Status Code and Response Headers

HTTP/2.0 202
server: Oracle-Application-Server-11g
strict-transport-security: max-age=31536000;includeSubDomains
location: https://dbaas.oraclecloud.com/paas/api/v1.1/instancemgmt/usexample/services/DBaaS/instances/db12c/patches/applied/job/12223582
content-language: en
access-control-allow-headers: Content-Type, api_key, Authorization, X-ID-TENANT-NAME, X-USER-IDENTITY-DOMAIN-NAME
retry-after: 60
access-control-allow-methods: GET, POST, DELETE, PUT, OPTIONS, HEAD
x-oracle-dms-ecid: 005KBA7ktGU6uHFpR0H7id00067c0002Zx
x-oracle-dms-ecid: 005KBA7ktGU6uHFpR0H7id00067c0002Zx
access-control-allow-origin: *
x-frame-options: DENY
content-type: application/json
vary: user-agent
date: Tue, 30 May 2017 00:03:33 GMT

Response Body

{
	"status": "Completed",
	"details": {
		"message": "PATCHING-5068: Patching service with patch [24968615] is submitted as an asynchronous job.",
		"jobId": "12223582"
	}
}
Back to Top