RVR-SYNP-318

Issue Summary

• Error Code: RVR-SYNP-318

The error "RVR-SYNP-318: Failed merging into target table" indicates a problem during the merge process within Azure Synapse using Rivery. The issue often arises from factors such as schema mismatches, conflicts in primary keys, or conflicts during the execution of merge operations, such as issues with data types or constraints not being adhered to.

Action Steps

1. Verify Schema Compatibility:

   • Ensure that the source and target table schemas align properly. Check that the column names, data types, and lengths match between the source and target tables, as any discrepancy may cause merging to fail.

2. Check Merge Conditions:

   • Verify the conditions set for the merge operation are correct. The condition used to join the source and target tables should correctly represent the logic intended for the merge.

3. Review Primary Keys and Constraints:

   • Conflicts can occur if there are primary key violations or if the merge conditions result in duplicate keys. Ensure that primary keys are unique and that constraints are not violated by the data being merged.

4. Logging and Monitoring:

   • Check the Synapse logs for any specific error messages or additional context around the merge failure. This can provide insights into what specific operation or condition caused the error.

5. Additional Debugging:

   • Temporarily simplify the merge logic to isolate the issue, if possible. Running tests with smaller datasets or simulating the merge operation can help identify the point of failure.

6. Permissions and Configuration:

   • Verify that the necessary permissions are set correctly for both source and target tables. Also, ensure that the configuration for Rivery and Azure Synapse is correct and aligned with the operational requirements.

External References

• For more details about using Azure Synapse as a target and configuring Rivery, refer to the official Rivery Documentation on Azure Synapse.

If the issue persists or you need further assistance, please open a ticket with Rivery support.