Re: Deadlock on DBMS_ALERT_INFO
Date: Thu, 7 Aug 2014 08:28:13 -0500 (CDT)
Message-ID: <44b21eefa1bbae8981cbf1d039c05078.squirrel_at_society.servebeer.com>
Lu writes:
> Have sent the related info to the application vendor, but the vendor’s
> solution is only to increase application retries when deadlock occurs.
Ewww. But Support is right. Deadlocks are an application issue.
> To prevent this kind of deadlocks, is there anything I can do as a DBA?
> Could anyone shed some light on this?
...
> pid: 57 O/S info: user: SYSTEM, term: FHM1PM64DBNA1, ospid: 76664
> program: PASPVTAA.exe
> UPDATE DBMS_ALERT_INFO SET CHANGED = 'Y', MESSAGE = :B2 WHERE NAME =
> UPPER(:B1 )
Having an application that uses SYSTEM to login is one red flag. And given
the deadlocks and Support's response, it would appear that they are using
DML directly on a SYS table -- another large red flag.
A Google search on the exe name shows nothing (perhaps it was obfuscated). But just from what you've shown us here, either this app or its local installation/configuration is scary. My knee-jerk is to run away from this app while frantically waiving your arms in the air and screaming. If that's not an option, document the poor practices and show management how they risk your valuable business data. Convince them that the vendor needs to change or you need to find another vendor.
Just my opinion...
Rich
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Aug 07 2014 - 15:28:13 CEST