Oracle Alerts 12.0.4 causing blocking locks?
Once it finds a blank attribute20, the alert action runs a SQL Update statement to update attribute20 with a scheduled ship date from the same row.
This alert runs every 30 minutes.
We are noticing that this alert Update statement is a suspect of blocking locks which in turn doesn't allow Order Administrators to query or update data in the system.
My question is does Oracle Alerts do any implicit or explicit locking of database objects when the action is an UPDATE statement on the same database object the alert SQL is on?