Our customer clones their database from production to several non-production instances on a daily basis. When they have interactive report subscription emails, they continue to be sent from the clones. That's understandable, since it is the way APEX IR email subscriptions should work technically after a cloning operation. But it's also not sensible from the customer perspective.
The process that checks for active subscriptions is ORACLE_APEX_WS_NOTIFICATIONS, which checks table WWV_FLOW_WORKSHEET_NOTIFY.
We have some ideas for a process the customer could run after the database is cloned, and for an application-level solution.
Are there any mechanisms in APEX to turn off subscriptions generated on a database instance that is not the current database instance?
Any suggestions?
Skip