Thanks,
you might want to add/modify that a little like
(SELECT TO_CHAR(SYSDATE, 'HH24:MI:SS') FROM DUAL) Time_now,
(SELECT TO_CHAR(cmn_sch_job_runs.start_date,'MM.DD HH24:MI:SS') FROM DUAL) start_date,
(SELECT TO_CHAR(cmn_sch_job_runs.end_date, 'HH24:MI:SS') FROM DUAL) end_date,
CASE
WHEN cmn_sch_job_runs.end_date is null
THEN TO_CHAR((SYSDATE- cmn_sch_job_runs.start_date)*8*60*60)
ELSE 'DONE'
END
Runtime_now,
cmn_sch_job_runs.total_execution_time/1000 Exec_time_s,
cmn_sch_job_runs.percent_complete pcnt_compl,
cmn_sch_job_runs.Status_code,
concat(concat(cmn_sec_users.last_name,', '),cmn_sec_users.first_name) RUNNER
from cmn_sch_job_runs, cmn_sch_jobs, cmn_sec_users
Where cmn_sch_jobs.id = cmn_sch_job_runs.job_id
and cmn_sch_job_runs.user_id = cmn_sec_users.id
to make it more cleat which jobs are done and which ones are running and for how long or failed and who is getting all the cumulating notifications of completed jobs.
You really need something like that after the OOTB jobs don't give any log entries any more.
Just wondering again...
When I make that into a portlet I don't see timeslicing while querying directly the db I can see timeslicing while it is running.
For that purpose time now and the execution time help catching how long it runs.
Martti K.