Identifying an Object Lock, after the fact... -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Identifying an Object Lock, after the fact...
From: "Graap, Kenneth" <Kenneth.Graap@xxxxxxxxxxxxx>
Date: Tue, 10 Jun 2014 17:26:35 +0000
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I think I already know the answer to this question but….

Is there a way to identify what cause an object lock conflict AFTER the jobs have ended and without having started a Performance Trace prior to the event happening?

Kenneth
AKA … 肯尼思 or 케네스
Kenneth E. Graap
System Administrator
503.226.4211 x5537
http://www.linkedin.com/in/kennethgraap

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Identifying an Object Lock, after the fact... , Michael Schutte

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.