Odd behavior in dbms_scheduler
Oracle 12.1.0.2 SE2 on Oracle Linux 6
This is a postmortem which may very well be un-solveable at this point, but my curiosity drives me ....
A couple of days ago we got word that a particular load job (loading data from an external source into the DW) was no longer needed. Accordingly my app support person disabled a load job, then found out the job did need to run though today (July 29). She was unable to re-enable the job, and when I tried I got this:
SQL> select job_name from user_scheduler_jobs; JOB_NAME--------------------------------------------------------------------------------JOB_BBTC_LOAD SQL> begin