RE: Deadlock on DBMS_ALERT_INFO

From: Mark W. Farnham <mwf_at_rsiz.com>
Date: Thu, 7 Aug 2014 10:25:25 -0400
Message-ID: <115301cfb24b$6eaee240$4c0ca6c0$_at_rsiz.com>

You asked what you could do as a DBA. There is a possibility:  

Notably the update does not reference a sid.  

IF (note all caps IF) you could verify that this application is only trying to update for its own sid, then you could in theory create a view of DBMS_ALERT_INFO filtered on self sid for folks running this application.  

Name and sid are indexed, so that should mitigate things if indeed the update is only for self sid (you can’t deadlock yourself).  

All the mentions of red flag previously in the thread apply unless this access is buried in Oracle’s application somewhere and they are calling it correctly.  

If this is something monitoring many other sids, ewww.  

mwf  

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 - 16:25:25 CEST