3808526 - Error: Local deadlock detected during data replication proxy creation job

Error occurred. com.successfactors.genericobject.app.exception.MDFSQLException:
com.sap.db.jdbc.exceptions.BatchUpdateExceptionSapDB: [133]: transaction rolled back by detected deadlock:
TrexColumnUpdate failed on table 'XXX' with error: transaction rolled back by
detected deadlock: Local Deadlock detected: owner tid cycle=[(victim) 8713230865, 8713231943], rc=4616(input
position -1)

Employee Central

The error occurs during the Data Replication Proxy Creation Job:

1. In the activity "Manage Data" of the Admin Center of EC select object of "Data Replication Configuration".

2. Perform a correction and set the field "Execute Proxy Creation Job" to "Yes":

3. Save the Data Replication Configuration so that the job "Data Replication Proxy Creation" gets triggered 

This error can occur when a Data Proxy Creation Job is executed and (at the same time) other processes change the same Data Replication Proxy records.

Such other processes can be:

• Running the replication into/from a payroll system
• Changing absences in the EC system
• Using the button "Reprocess" option in the Data Replication Monitor

The Data Replication Proxy Creation Job should be the last option when the replication of existing time data has to be triggered. 

For more information, please refer to the following guides:

• 3018333 - Time Data Replication: Proxy creation job fails when executed with a productive payroll system
• How to Trigger Replication of Existing Time Data | SAP Help Portal 

It is not recommended to use the Data Replication Proxy Creation Job on a regular basis since it can trigger replication of already replicated data again and it can create a high load on the replication process. 

local deadlock, proxy creation, MDFSQLException, time, replication , KBA , LOD-EC-ECP-TIM , Time Data Replication , Problem