Schedule Execution
Use this API to schedule Exadata Scale Up or Scale Down execution.
API
/exadata/v1/customers/{customerId}/instances/{instanceId}/executions/{executionId}
Scope and AuthZ
- You must have
mcs:oci:api:Approver
scope to access this API. - You can schedule Exadata Scale Up or Scale Down execution only for your customer instances.
- You can use Exadata Scale Up or Scale Down only if your customer has opted-in for Exadata Scale Up or Scale Down functionality.
Headers
- Authorization: Bearer <Token>
Where <Token> is the OAUTH token returned by the Authorization Server (JWT Token).
- Identifier: <JWKS Identifier>
Where <JWKS Identifier> is the GUID generated when JWKS URI is set by customer admin in self-service platform.
Base Path
/exadata/v1/
Functionality
- This API is used to schedule execution.
custStatus
is customer Status value at MOS.status
is status at MOS.subStatus
is substatus value at MOS.scheduledBy
is email ID of person who scheduled RFC.scheduledEnd
is timestamp for schedule end.scheduledStart
is timestamp at which execution is scheduled for.customerId
is customer ID of customer.instanceId
is instance against which execution was created.
Verb
PUT
Parameters
Name | Type | Description | Mandatory |
---|---|---|---|
customerId |
Path parameter | Customer ID | Yes |
instanceId |
Path parameter | Instance ID of instance against which execution is created | Yes |
executionId |
Path parameter | Execution ID | Yes |
scheduledTime |
json | Schedule timestamp | Yes |
action |
json | Action value for API | Yes |
Sample request
{
"scheduledTime": "2021-10-27T04:00:23Z",
"action": "schedule"
}
Sample response
{
"custStatus": "Review Update",
"scheduledBy": "<email ID>",
"scheduledEnd": "2021-10-27T05:00:23Z",
"scheduledStart": "2021-10-27T04:00:23Z",
"status": "Open",
"subStatus": "Ready for Execution",
"updatedBy": "<email ID>",
"updatedOn": "2021-10-27T03:43:15Z",
"customerId": "4165",
"instanceId": "OMCEBSOR3"
}