RVR-RDBMS-301

1. Issue Summary

   • You encountered an error with the code RVR-RDBMS-301 related to the RDBMS data connector in Rivery. This error description, "Failed to get data on resource," suggests that the system is unable to access or retrieve data from the database resource. This can often occur due to synchronization or setup issues, particularly in environments using SQL Server with Change Tracking enabled.
   • Initial diagnosis indicates the issue may be associated with the absence of a valid synchronization version, likely caused by automated cleanup processes within your database settings【4:2†source】.

2. Action Steps:

   • Investigate Change Tracking Configuration:
     • Ensure that Change Tracking is enabled on both your database and the specific tables involved. Use the appropriate SQL queries to verify this configuration【4:2†source】.
   • Check for Cleanup Processes:
     • Review the cleanup settings in your SQL Server to ascertain if changes are being cleaned up too frequently, which could delete synchronization data important for the river's operation. Adjust settings if necessary【4:0†source】.
   • Reinitialize Table:
     • If synchronization issues persist, reinitialize the table data within Rivery by navigating to your River's Schema and selecting "Set initiate migration for all tables." This will reset the synchronization version【4:4†source】.
   • Review SQL Server Logs:
     • Analyze logs for any messages regarding synchronization or other relevant errors. This can provide insights into why data retrieval is failing【4:0†source】.
   • Cross-check Concurrent Usage:
     • Ensure that no concurrency issues are present, which can occur if multiple processes are attempting to synchronize data simultaneously. Adjust server or application settings to mitigate such conflicts【4:2†source】.

3. External References:

   • Learn more about SQL Server Change Tracking in the Rivery context here: Rivery Documentation.
   • For detailed troubleshooting regarding SQL Server's change tracking cleanup processes and configurations, consider checking SQL Server's official documentation or community forums for best practices.

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