SRProc reported Deadlock On S_SRM_REQUEST Table (Doc ID 1088603.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

Customer are running SQL Server 2005 and experiencing deadlocks on the S_SRM_REQUEST table. The majority of the deadlock occur on the SELECT statement when its polling to determine if there are any QUEUED records for components running on a particular server. Please note that the "Server Tables Cleanup" is being run only one server. Having spoken to the SQL Server 2005 DBA, the update statements are deadlocking on the Select statements. The spinlock then chooses to terminate the statement with the least impact (in this case the Select statement is terminated). Customer also noticed that the SRProc recovers from this situation and work gets allocated accordingly.

Below are the errors found in SRproc log:

[SQL Server]Transaction (Process ID 3170) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.