There is a condition checking when Job Scheduler starts: If the database is 10g or above, it uses dbms_scheduler package; if it is below 10g, it uses dbms_job
– and then it works just like Job Manager does.
So if the database you are connecting to is above 10g, you will not be able to see any jobs created by dbms_job.submit. This is how the Job Scheduler was decided.
Job Manager was always shipped as a standalone executable and the company stop maintaining it a few years ago. That’s why we decided not to include it from now on. However, SQLNAV-1643 is now created as an ER to implement functions to manage jobs created dbms_job
package. We will let you know once it is implemented.