APEX 5.1.2
This blog post has some nice tips for how to handle long running PL/SQL processes from an APEX page. Few questions/comments
1. In a multi-user environment, how can we make sure that only one instance of the job is scheduled? Add an APEX page validation to make sure a row doesn't already exist in USER_SCHEDULER_JOBS with STATUS=RUNNING?
2. When the job terminates unexpectedly, the row in V$SESSION_LONGOPS seems to stick around forever. Is there a way to get rid of it so it doesn't show up on the status report as a duplicate? So if my scheduler job name is LONGRUN, ideally I would like just one row in v$session_longops with that OPNAME
Help? Thanks