Oracle jobs appear to be running but..... [message #457243] |
Sat, 22 May 2010 08:08 |
shajju
Messages: 29 Registered: August 2009
|
Junior Member |
|
|
Hi
I have a number of oracle jobs set up to do the same thing and to run every second. These jobs, run a package which summarizes data in tables. All was working fine until a few days ago. Before the server was shut down, the jobs were not disabled. When the server was restarted and the db brought back online, things seemed normal apart from these jobs not doing what they had been doing for the last 5 years. i.e., no output.
The script of the job is:
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
( job => X
,what => 'begin
aesdem.work_summary.do_work;
commit;
end;
'
,next_date => to_date('22/05/2010 15:03:11','dd/mm/yyyy hh24:mi:ss')
,interval => 'SYSDATE+1/86400'
,no_parse => TRUE
);
SYS.DBMS_OUTPUT.PUT_LINE('Job Number is: ' || to_char(x));
END;
/
commit;
This job runs the work_summary package but it seems it is not doing so as I can't see any output from that package. If I run the package manually, it works fine and I see output.
dba_running_jobs=100
CJQo process exists.
dba_jobs shows all the jobs.
Can see jnnn processes too.
Is there any other way I can confirm that the jobs are really running? And track what happens when the job runs?
Regards
Shajju
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Oracle jobs appear to be running but..... [message #457767 is a reply to message #457695] |
Tue, 25 May 2010 22:27 |
shajju
Messages: 29 Registered: August 2009
|
Junior Member |
|
|
Hmmm, ok and thanks for the info. I thought, to debug the steps an oracle job is going through you have to insert the debugging code into the pl/sql of the job.
So using UTL_FILE in the code of the package will tell me why the job is not able to pick it up?
Hmmmm
|
|
|
Re: Oracle jobs appear to be running but..... [message #457768 is a reply to message #457767] |
Tue, 25 May 2010 22:39 |
|
BlackSwan
Messages: 26766 Registered: January 2009 Location: SoCal
|
Senior Member |
|
|
>So using UTL_FILE in the code of the package will tell me why the job is not able to pick it up?
Or add INSERT statements which would leave audit trail.
You keep stating that job does not start.
Michel & I believe the job does start.
So by either UTL_FILE or INSERT done as very first action in the procedure, you can quickly conclude if/when job really starts.
Does aesdem.work_summary.do_work contain an EXCEPTION handler that would result in any error being silently ignored?
|
|
|