Manage Permission for Manual Access to Database (v2)
Use this REST API (v2) to manage permission for manual access to database by Oracle.
This gives you the ability to allow or disallow Oracle personnel to manually access your database in emergency situations when an environment is unresponsive and you have not yet created a service request to investigate the issue.
In an emergency situation, Oracle follows an internal process whereby a high-level development executive, after an independent verification process, permits manual access to the database without your explicit approval. You can also prohibit Oracle from manually accessing the EPM Cloud database, even if a service request to remedy a database issue is open.
This API is version v2
Required Roles
Service Administrator
REST Resource
PUT /interop/rest/v2/services/setmanualdataaccess
Note:
Before using the REST resources, you must understand how to access the REST resources and other important concepts. See Implementation Best Practices for EPM Cloud REST APIs. Using this REST API requires prerequisites. See Prerequisites.
Request
Supported Media Types: application/json
The following table summarizes the request parameters.
Table 10-12 Parameters
Name | Description | Type | Required | Default |
---|---|---|---|---|
accessType |
Allow or revoke the manual access to database by Oracle, where
the value can be allow or
revoke |
Payload | Yes | None |
parameters |
||||
disableEmergencyAccess |
Whether to prohibit all manual access to the database. The
possible values are true and
false . Setting this parameter value to
true stops Oracle from manually accessing the
database even if a service request is open. Oracle does not
recommend setting this parameter value to true
because Oracle cannot access the database if access is required to
troubleshoot and fix a down environment. If the environment is down,
you will not be able to issue this REST API to allow Oracle to
manually access the database.
|
Payload | No | False |
Example URL and Payload
https://<BASE URL>/interop/rest/v2/services/setmanualdataaccess
{
"accessType": "Revoke",
"parameters": {
"disableEmergencyAccess": "False"
}
}
Response
Supported Media Types: application/json
Table 10-13 Parameters
Parameters | Description |
---|---|
details |
In case of errors, details are published with the error string |
status |
See Migration Status Codes |
links |
Detailed information about the link |
href |
Links to API call |
action |
The HTTP call type |
rel |
Can be self and/or Job Status . If set to Job Status , you can use the href to get the status of the import operation
|
data |
null |
Example of Response Body
The following shows an example of the response body in JSON format.
{
"details": null,
"status": 0,
"links": [
{
"href": "https://<BASE-URL>/interop/rest/v2/services/setmanualdataaccess",
"action": "PUT",
"rel": "self",
"data": null
}
]
}
Sample cURL command
curl -X PUT -s -u '<USERNAME>:<PASSWORD>' -o response.txt -D respHeader.txt -H 'Content-Type: application/json' -d '{"accessType":"Revoke","parameters":{"disableEmergencyAccess":"True"}}' 'https://<BASE-URL>/interop/rest/v2/services/setmanualdataaccess'