CodexBloom - Programming Q&A Platform

OCI Data Integration: Failing to Sync from Oracle DB to Object Storage due to 'InvalidBucketName' Error

πŸ‘€ Views: 27 πŸ’¬ Answers: 1 πŸ“… Created: 2025-09-01
oci data-integration object-storage oracle-db JSON

I've been researching this but I've been struggling with this for a few days now and could really use some help. I'm sure I'm missing something obvious here, but I'm currently working on an OCI Data Integration project where I need to sync data from an Oracle Database to OCI Object Storage. I've set up the connection to the Oracle DB successfully, and I can run my data flows without any issues. However, when I try to execute a sync job to push data into Object Storage, I consistently encounter an error message that says `InvalidBucketName`. I've double-checked that the bucket name I'm using adheres to the naming conventions: It’s all lowercase, contains no spaces, and is within the 3-63 character limit. Here's a snippet of my configuration: ```json { "bucketName": "my-data-bucket", "objectStorageNamespace": "my-namespace", "region": "us-phoenix-1" } ``` Despite this, the job fails with the aforementioned error. I've also tried accessing the bucket directly in the OCI console, and it’s definitely there. I’ve also looked through the logs and found nothing that points to a misconfiguration other than this error. Additionally, I've verified that my IAM policy allows the necessary permissions for Data Integration to access Object Storage. The policy looks like this: ```plaintext Allow group data-integration-group to manage objects in compartment my-compartment ``` Still, I can't figure out why I'm getting this `InvalidBucketName` error. Is there a specific aspect of the OCI Data Integration configuration that I might be missing, or is there any known issue with certain characters in bucket names? Any insights would be greatly appreciated! I'm working in a Linux environment. Has anyone else encountered this? I'm on Windows 10 using the latest version of Json. Any ideas what could be causing this?