RE: Deadlock on DBMS_ALERT_INFO

From: McPeak, Matt <vxsmimmcp_at_subaru.com>
Date: Thu, 7 Aug 2014 17:08:15 +0000
Message-ID: <D7864FA3E7830B428CB2A5A5301B63EE01AA3D9D40_at_S7041VA005.soa.soaad.com>

I’ve seen ITL deadlocks that could conceivably by fixed (or reduced anyway) without touching application code.

Also, it *could* be the way you are using the application. For example, the application might lock a record when a user starts to update it. Two users could use such a form to cause a deadlock without it being an application issue. Training the users in procedures that would avoid such deadlocks might be enough.

But, all that said, I agree with everyone else… you’re probably out of luck. :)

Matt

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Phillip Jones Sent: Thursday, August 07, 2014 9:41 AM To: rjoralist3_at_society.servebeer.com Cc: ORACLE-L
Subject: Re: Deadlock on DBMS_ALERT_INFO

DBMS_ALERT is an Oracle supplied package: http://docs.oracle.com/cd/B19306_01/appdev.102/b14258/d_alert.htm

Just saying :)

In total agreement that it's an app issue.

Cheers,

Phil

--
http://www.freelists.org/webpage/oracle-l

Received on Thu Aug 07 2014 - 19:08:15 CEST