Transactions with Database Events
When a database event is raised within a transaction, notification of the database event is not sent until the transaction is committed. If a rollback of the transaction that raised the database event occurs, the raise event has no effect.
Multiple Oracle sessions can concurrently raise the same database event. Each session, when raising the event, blocks all other concurrent sessions until it commits. This has the effect of serializing the transactions.
Note: This Oracle Alerts behavior differs significantly from the Ingres behavior within transactions.
Note: Gateway sessions that register and raise the same dbevent should issue a commit as soon as possible after executing the raise dbevent statement to avoid Oracle locking errors.