on 04-19-2016 9:46 PM
Working a new gig these days and they're getting a TON of database deadlocks. They're using, "with(nolock)" on every SQL query as far as I can see. That said, I still don't have PROD access so I can't totally verify that this is true. Still, on everything I've seen, they have the nolock in place so I wouldn't think they'd be seeing this many deadlocks. Has anyone seen an environment getting a lot of these? How did you fix it?
Here's a sample error message from the IDM job log:
Running pass failed with unhandled exception - {err_classname=ToSAPIdentity, err_category=ERROR,
err_passname=AssignABAPprivs, err_where=runToPass,
err_exception=com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 310) was deadlocked
So many possibilities, so little time...
Few things I can think of to check / consider?
Multiple dispatchers on the same server?
Are they using (nolock) in queries?
Take a look at some of Chris Krabsetsve's blog posts. Tons of stuff there as I recall.
Also take a look at IdM Thoughtplace: Some thoughts on database locking in Oracle and Microsoft SQL Server I think there could be some stuff there too.
Matt
PS also check: IdM Thoughtplace: Calling all Dispatchers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Brandon,
Are they using RDS package?
We also had these deadlocks in provisioning framework tasks even though all our custom tasks and jobs had "with(no lock)" hint. SAP advised us to replace the RDS package with standard framework.
Kind regards,
Jai
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.