Troubleshooting
Problem
Information on DBMS_ALERT
Symptom
PART: Inbound 6.2 SP2 DCS
Information on DBMS_ALERT
Cause
Resolving The Problem
DBMS_ALERT is a standard package comes with Oracle. As far as I know,
DBMS_ALERT_INFO is accessed only by this package
We use DBMS_ALERT for
printing infrastructure. When whbu502 is brought up, we register an alert with
a unique key derived from whse code using DBMS_ALERT.REGISTER (which I think
insert a record into DBMS_ALERT_INFO) and 502 will wait on this alert for any
notification (DBMS_ALERT.WAITONE). When any of the functions submit a print, it
also sends a signal to the same alert ( DBMS_ALERT.SIGNAL). whbu502 will pick
up the signal and will process the print request.
I don't know if any of
these procedures put a row exclusive lock on the DBMS_ALERT_INFO
You can
also check the metalink document 1012173.6 for more info.
Historical Number
PRI49189
Product Synonym
[<p><b>]Fact[</b><p>];
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21535276