Oracle Integration · REST Adapter (RPST security policy)
RPST and OCI Service Invocation: BucketAlreadyExists
Short answer
A BucketAlreadyExists error through the Oracle Integration REST Adapter can mean the policy only lets the dynamic group read buckets, so creating a bucket fails. Create a policy that allows writing to the bucket.
VerifiedLast verified
01Error text
{"code":"BucketAlreadyExists","message":"Either the bucket '...' in namespace '...' already exists or you are not authorized to create it"}02Likely causes
- A policy was created that only lets the dynamic group read buckets in a compartment.
03How to fix it
- Create a policy that allows writing to the bucket.
04Official documentation
→Related errors
- OAuth: The token has already been consumedThis REST Adapter error in Oracle Integration means the connection could not refresh its access token, because no refresh token was received or the refresh token expired. Verify that the connection receives a refresh token. Make sure the scope includes offline_access.
- OCI Object Storage Search API returns 401 NotAuthenticatedThis 401 from the OCI Object Storage Search API through the Oracle Integration REST Adapter usually points to invalid credentials or an unsupported wildcard search. Make sure the file name being searched does not contain the character.
- RPST and OCI Service Invocation: NamespaceNotFoundA 404 NamespaceNotFound through the Oracle Integration REST Adapter with the RPST and OCI Service Invocation policy means the policy or dynamic group is not set correctly. Set the policy to perform the required operations.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Oracle Integration work:Open Oracle Integration jobsOracle Integration rates and salaries