RVR-SYNP-317
- 1 Minute to read
- Print
- DarkLight
- PDF
RVR-SYNP-317
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Issue Summary
- The error code
RVR-SYNP-317
associated with Azure Synapse indicates a failure in a merging operation within Rivery's platform. This usually stems from issues associated with the merge process when dealing with data types and expected table schemas. Possible causes might include constraints on primary keys, data type mismatches, or problems with handling NULL values in primary key fields【4:5†source】.
- The error code
Action Steps:
- Check Primary Keys: Ensure that the tables involved in the merge operation have properly defined primary keys. No field selected as a primary key should have NULL values.
- Data Type Verification: Review and ensure that all data types in the source and target tables are compatible. If necessary, cast the columns to the appropriate data types before merging.
- Review Logs: Check the logs related to the merge operation for any additional error messages that may provide more context about why the merge failed.
- Table Schema Updates: If any changes have been made to the table structure (such as adding new columns), ensure that the Rivery integration is updated to reflect these changes.
External References:
- You can refer to Rivery's documentation on Loading Modes for more information about handling upsert-merge operations.
- For detailed Azure Synapse Analytics troubleshooting, you might want to consult Microsoft's documentation.
If the issue persists or you need further assistance, please open a ticket with Rivery support.
Was this article helpful?