Replication Services Executions Colliding
Article ID: KB0078091
Updated On:
| Products | Versions |
|---|---|
| TIBCO Cloud Integration - Connect ( Scribe ) | - |
Description
If you see the following error when running RS Solutions, it could be caused by two RS Solutions running simultaneously and attempting to access the same source entity and or the same target datastore.
Error title: Failed to reinsert record.
Error description: Cannot insert duplicate key row in object 'dbo.hso_processorcode' with unique index 'ndx_hso_processorcodeid'. The duplicate key value is (715c53fe-d6f1-e511-80f3-5065f38acac1)
Even if you have set your RS Solutions to run at different time intervals, simply stopping and restarting the Agent could cause the Solutions to run at the same time. Running the RS Solutions at the same time causes a collision because both are trying to access the same records either on the source side or the target side.
Error title: Failed to reinsert record.
Error description: Cannot insert duplicate key row in object 'dbo.hso_processorcode' with unique index 'ndx_hso_processorcodeid'. The duplicate key value is (715c53fe-d6f1-e511-80f3-5065f38acac1)
Even if you have set your RS Solutions to run at different time intervals, simply stopping and restarting the Agent could cause the Solutions to run at the same time. Running the RS Solutions at the same time causes a collision because both are trying to access the same records either on the source side or the target side.
Issue/Introduction
If you see a "Failed to reinsert record" error when running Replication Services (RS) Solutions, it could be caused by two RS Solutions running simultaneously and attempting to access the same source entity and or the same target datastore.
Resolution
As a best practice, do not have similar Solutions processing the same entities and targeting the same database. If absolutely necessary, separate some entities in to their own Solutions. For example, if you have entities for which you need more current information, create a Replication Service Solution just for those entities and schedule it to run more often. Create a second Replication Service Solution for the entities that are not as important, and run that less frequently.
Another option is to only use one Replication Service Solution for the source and target.
Another option is to only use one Replication Service Solution for the source and target.
Feedback
Yes
No
Powered by
