I have a development and a production database. On the production database, our file watcher stopped working. After digging through things, I see a row in DBA_SCHEDULER_JOBS that is present in development, but not in production. All the “run-time” data are present in development and production.
Development:
Dev> select owner, program_owner, program_name, schedule_owner, schedule_name, job_name, job_type, job_class
from dba_scheduler_jobs where job_name='FILE_WATCHER';
OWNER PROGRAM_OWNER PROGRAM_NAME SCHEDULE_OWNER SCHEDULE_NAME JOB_NAME JOB_TYPE JOB_CLASS
----- ------------- --------------------- -------------- ---------------------- ------------- -------- --------------------------
SYS SYS FILE_WATCHER_PROGRAM SYS FILE_WATCHER_SCHEDULE FILE_WATCHER SCHED$_LOG_ON_ERRORS_CLASS
Production:
Prod> select owner, program_owner, program_name, schedule_owner, schedule_name, job_name, job_type, job_class
from dba_scheduler_jobs where job_name='FILE_WATCHER';
no rows selected
Database Version:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 Version 19.22.0.0.0
I have looked in vain at the documentation for DBMS_SCHEDULER to find procedure to recreate it; the dba_scheduler_jobs view column JOB_TYPE is null; which seems to be a required value for the various procedures in that package.
This seems to have started after the patch to 19.22.