Idle Blockers

David, what version of DPA are you on? With more recent versions (I believe 10.2 and up), on the blocking tab within 1 hour time frame, you can click on show last activity for the idle blocker session which may indeed catch the session and SQL causing the blocking. Keep in mind though that if the SQL ran sub-second, we may have missed it as our methodology is sampling (once per second granularity), so we can miss SQL that runs infrequently AND very quickly (ie: not a performance problem in and of itself). However, for blocking, it can cause downstream effects like you may be observing.

We are running version 11.0.387.  I will try your suggestion.

Thank you,

David

DPA 10.2 included a feature to find the source of an idle blocker, see this post for an example DPA 10.2 Now Available - Root Blockers, Idle Blockers and Deadlocks