Register a target database group for Data Safe onboarding
post
https://EM_HOST:8080/em/api/databases/dataSafeOnboardings/actions/registerTargetDatabaseGroup
Submits the Data Safe registration procedure for the provided EM group and OCI settings.
Request
There are no request parameters for this operation.
Supported Media Types
- application/json
Root Schema : schema
Type:
objectRequest payload for Data Safe registration inputs.
Show Source
-
dataSafeConnectorId(required): string
OCID of the Data Safe on-prem connector.
-
dbSysNamedCredentialName: string
Optional named credential for SYSDBA access.
-
dbTargetGroupName(required): string
EM database group name to onboard.
-
ociCompartmentId(required): string
OCI compartment OCID for Data Safe resources.
-
ociCredentialName(required): string
EM credential name for OCI authentication.
-
region(required): string
OCI region identifier.
Response
Supported Media Types
- application/json
202 Response
Registration procedure submitted successfully.
Headers
-
Location:
URL to poll for the submitted Data Safe onboarding status.
Root Schema : DataSafeOnboardingSubmission
Type:
objectResponse returned after the Data Safe registration procedure is submitted.
Show Source
-
message(required): string
Human-readable submission result.
-
procedureName(required): string
Submitted procedure name.
-
submissionId(required): string
Procedure submission identifier returned by Enterprise Manager.
-
timeSubmitted(required): string
(date-time)
Submission timestamp.
400 Response
Bad Request.
Headers
-
ORCL-EM-RETRY-LINK:
Link of the request that failed.
Root Schema : ErrorResponse
Type:
objectResponse sent in the case of an error.
Show Source
-
code(required): string
Error code.Example:
InvalidParameter -
message(required): string
Error description.Example:
Parameter cannot be empty
401 Response
Unauthorized.
Headers
-
ORCL-EM-RETRY-LINK:
Link of the request that failed.
Root Schema : ErrorResponse
Type:
objectResponse sent in the case of an error.
Show Source
-
code(required): string
Error code.Example:
InvalidParameter -
message(required): string
Error description.Example:
Parameter cannot be empty
403 Response
Forbidden.
Headers
-
ORCL-EM-RETRY-LINK:
Link of the request that failed.
Root Schema : ErrorResponse
Type:
objectResponse sent in the case of an error.
Show Source
-
code(required): string
Error code.Example:
InvalidParameter -
message(required): string
Error description.Example:
Parameter cannot be empty
409 Response
Conflict.
Headers
-
ORCL-EM-RETRY-LINK:
Link of the request that failed.
Root Schema : ErrorResponse
Type:
objectResponse sent in the case of an error.
Show Source
-
code(required): string
Error code.Example:
InvalidParameter -
message(required): string
Error description.Example:
Parameter cannot be empty
500 Response
Internal Server Error.
Headers
-
ORCL-EM-RETRY-LINK:
Link of the request that failed.
Root Schema : ErrorResponse
Type:
objectResponse sent in the case of an error.
Show Source
-
code(required): string
Error code.Example:
InvalidParameter -
message(required): string
Error description.Example:
Parameter cannot be empty
503 Response
Service Unavailable
Headers
-
ORCL-EM-RETRY-LINK:
Link of the request that failed.
Root Schema : ErrorResponse
Type:
objectResponse sent in the case of an error.
Show Source
-
code(required): string
Error code.Example:
InvalidParameter -
message(required): string
Error description.Example:
Parameter cannot be empty