Dbms_job disappears!!! Tonight on Fox after X-Files... :)

Question

I am experiencing a rather odd situation. Here's the scoop:
I have a stored procedure that I want to call as a dbms_job. Here's the submit job:
VARIABLE jobno number;
BEGIN
DBMS_JOB.SUBMIT(:jobno,
'online_attnd_package.update_attendance;');
COMMIT;
END;
I then select from all_jobs and it shows up:
598
online_attnd_package.update_attendance;
Then I run the job:
SQL> exec dbms_job.run(598)
PL/SQL procedure successfully completed.
But now it's gone from the job queu, without me removing anything!!!!
SQL> select job,what,last_date,broken from all_jobs where job = 598;
no rows selected
Please help!!!!!
-- Matt --

Answer 1

I am experiencing a rather odd situation. Here's the scoop:
I have a stored procedure that I want to call as a dbms_job. Here's the submit job:
VARIABLE jobno number;
BEGIN
DBMS_JOB.SUBMIT(:jobno,
'online_attnd_package.update_attendance;');
COMMIT;
END;
I then select from all_jobs and it shows up:
598
online_attnd_package.update_attendance;
Then I run the job:
SQL> exec dbms_job.run(598)
PL/SQL procedure successfully completed.
But now it's gone from the job queu, without me removing anything!!!!
SQL> select job,what,last_date,broken from all_jobs where job = 598;
no rows selected
Please help!!!!!
-- Matt -- Matt,
You may have written an aynomous package - meaning that it isn't stored in Oracle after you run it. Try giving it a name like:
CREATE OR REPLACE PROCEDURE matt_dbms_job
VARIABLE jobno number;
BEGIN
DBMS_JOB.SUBMIT(:jobno,
'online_attnd_package.update_attendance;');
COMMIT;
END;Then you can call it a stored procedure and it should remain after you execute it.
The Infamous
Eric Cartman