Symptom
User Connector - SF job failed and in background job details error log is like below:
com.sap.db.jdbc.exceptions.SQLTransactionRollbackExceptionSapDB:transaction rolled back by detected deadlock: xxxxxxxx: line xx col xx: xxxx failed on table 'Schema_name:PA_STUDENT' with error: transaction rolled back by detected deadlock
Environment
SAP SuccessFactors Learning
Reproducing the Issue
- Run a User Connector - SF job
- Occasionally the job might fail with the error: transaction rolled back by detected deadlock
Cause
A deadlock occurs when more than one transactions are made concurrently on the same data, these transactions lock each other and none proceeds.
As the PA_STUDENT table is widely used across Learning, deadlocks on it are likely to occur when another background job is running on the same set of data as the connector is running at the same time. In such cases, deadlock is detected by system and the error is issued.
Resolution
Please run the Connector job again to make sure data is updated. Since this is a rare case, the next run is most likely to be successful.
Keywords
User Connector - SF, background job, exception, PA_STUDENT, transaction rolled back by detected deadlock, error , KBA , LOD-SF-LMS-CON , Connectors , Problem