View the Status of a Patching Precheck Operation



Returns the status of a patching precheck operation.


Path Parameters
  • The value depends on the type of Exadata Cloud at Customer 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 is a character string beginning with idcs-.

  • Job ID of the operation that was returned when the patching precheck was initiated.
  • Name of the Exadata Cloud at Customer deployment.
Header Parameters
Back to Top


Supported Media Types

202 Response

Accepted. See Status Codes for information about other possible HTTP status codes.
Body ()
Root Schema : view-precheck-response
Type: object
The response body includes information about the requested patch prechecks.
Show Source
Nested Schema : jsonResult
Type: object
System messages. This attribute displays only when viewing the status of one patching precheck operation.
Show Source
Nested Schema : preCheckMessages
Type: array
List of patching precheck messages. No patching precheck messages are returned when the precheck completes successfully.
Show Source
Nested Schema : messages
Type: array
Precheck status detailed messages, if any.
Show Source
Back to Top


The following example shows how to view information about the status of a specific patch precheck operation associated with an Exadata Cloud at Customer database deployment by submitting a GET request on the REST endpoint using cURL.

In this example, the identity domain is usexample, the Exadata Cloud at Customer database deployment is db12c and the Oracle Cloud user name and password are serviceadmin and Pa55_word. The job identification number for the patch precheck operation is 12221158.

cURL Command

curl -i -X GET --cacert ~/cacert.pem -u serviceadmin:Pa55_word -H "X-ID-TENANT-NAME:usexample"

HTTP Status Code and Response Headers

HTTP/2.0 202
server: Oracle-Application-Server-11g
strict-transport-security: max-age=31536000;includeSubDomains
content-language: en
access-control-allow-headers: Content-Type, api_key, Authorization, X-ID-TENANT-NAME, X-USER-IDENTITY-DOMAIN-NAME
access-control-allow-methods: GET, POST, DELETE, PUT, OPTIONS, HEAD
x-oracle-dms-ecid: 005KB9Q6YWA6uHFpR05Eid0007dd00010v
x-oracle-dms-ecid: 005KB9Q6YWA6uHFpR05Eid0007dd00010v
access-control-allow-origin: *
x-frame-options: DENY
content-type: application/json
vary: user-agent
date: Mon, 29 May 2017 23:50:30 GMT

Response Body

	"id": 7769,
	"jobId": "12221158",
	"patchId": "24968615",
	"jsonResult": "{\"messages\":[]}",
	"startDate": "2017-05-29T23:47:35.175+0000",
	"endDate": "2017-05-29T23:47:35.285+0000",
	"performedBy": "serviceadmin",
	"inProgress": true,
	"status": "IN_PROGRESS",
	"preCheckMessages": []
Back to Top