Aha.. Your job_queue_processes parameter was set to 0!!
Starting with Oracle Database release 11.2.0.1, setting JOB_QUEUE_PROCESSES to 0 causes both DBMS_SCHEDULER and DBMS_JOB jobs to not run.
Previosly, it was not like that.. (setting JOB_QUEUE_PROCESSES to 0 caused DBMS_JOB jobs to not run, but DBMS_SCHEDULER jobs were unaffected and would still run)
If you would mention that, no jobs could be running , we could go to the solution faster.. :)
on my production database, my JOB_QUEUE_PROCESSES is set to 1000. However, the job which I scheduled is still in scheduled state. Can you please advise what can cause it not to run?
connect to the database.
use "select sysdate from dual" and "SELECT SYSTIMESTAMP FROM DUAL;" to check the date of the database (default date), then set your job time accordingly.
You can also use the following to check:
select systimestamp,current_timestamp from dual;
SYSTIMESTAMP -> current timestamp on database serve
current_timestamp ->timestamp on client machine