Update Exadata Iorm Config
PUT {{baseUrl}}/dbSystems/:dbSystemId/ExadataIormConfig
Updates IORM settings for the specified Exadata DB system.
Note: Deprecated for Exadata Cloud Service systems. Use the new resource model APIs instead.
For Exadata Cloud Service instances, support for this API will end on May 15th, 2021. See Switching an Exadata DB System to the New Resource Model and APIs for details on converting existing Exadata DB systems to the new resource model.
The UpdateCloudVmClusterIormConfig API is used for Exadata systems using the new resource model.
Request Body
{"dbPlans"=>[{"dbName"=>"<string>", "share"=>"<integer>"}, {"dbName"=>"<string>", "share"=>"<integer>"}], "objective"=>"AUTO"}
HEADERS
| Key | Datatype | Required | Description |
|---|---|---|---|
opc-request-id | string | Unique identifier for the request. | |
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. | |||
Content-Type | string | ||
Accept | string |
RESPONSES
status: OK
{"dbPlans":[{"dbName":"\u003cstring\u003e","flashCacheLimit":"\u003cstring\u003e","share":"\u003cinteger\u003e"},{"dbName":"\u003cstring\u003e","flashCacheLimit":"\u003cstring\u003e","share":"\u003cinteger\u003e"}],"lifecycleDetails":"\u003cstring\u003e","lifecycleState":"FAILED","objective":"AUTO"}