RVR-SF-RDBMS-311
Issue summary
- The error "Failed to define bucket name" with Error Code: RVR-SF-RDBMS-311 in the Data Integration platform for an RDBMS Data Connector occurs when there is an issue with specifying or detecting the correct bucket name used for data operations. This error might originate from a misconfiguration in specifying the bucket name or a lack of necessary permissions for accessing it. It is essential to ensure that bucket definitions and permissions have been properly set up in the relevant cloud storage service.
Action steps
To resolve the error, follow these steps:
- Validate that the bucket name is correctly specified in your Data Integration configuration. Cross-check this name with your actual storage setup to ensure there are no typographical errors.
- Ensure to grant the appropriate permissions for accessing the bucket. This may include permissions to list, read, and write to the bucket used by your RDBMS configuration.
- Review your Data Integration connection settings, specifically focusing on any configuration related to the custom file zone or bucket settings in the data source or target configuration.
- If your bucket is available on Amazon S3 or Google Cloud Storage, ensure that the bucket names and regions match those specified in your connection settings. Bucket names in these platforms are case-sensitive and must align perfectly.
- Test the connection after any changes to ensure that it resolves the error. This you can do this within the Data Integration platform by revisiting the connection settings and utilizing any built-in testing tools provided.
External references
- For more detailed guidance on setting up bucket permissions and configurations, refer to:
- Data Integration Documentation on Configuring Cloud Connections
- Amazon S3 bucket policy documentation: Amazon S3 Bucket Policies
- Google Cloud IAM for buckets: Google Cloud Storage IAM Roles
note
If the issue persists or you need help, open a case with Data Integration Support. In the console sidebar, select Help > Contact Us and follow the instructions.