APEX 19, Oracle19
We use Supporting Objects (SO) to create upgrade scripts.
When creating scheduler jobs through SO the jobs are owned by APEX_PUBLIC_USER (APU) and not the underlying/proxied schema name.
This is usually OK as APU has all the privileges of the underlying schema except for a few third party packages that we use which refer to 'USER' to confirm that they are being called by a valid user. When the scheduler job calls these packages, it appears as APU and is refused access.
I was hoping that there was some way of invoking/a wrapper the dbms_scheduler package so that it created the jobs under the schema owner (a bit like APEX_SPATIAL does for insert_geom_metadata).
Any ideas?