This content has been marked as final. Show 9 replies
Hi ,1 person found this helpful
It could be either permission issue .
Did u tried executing job using exec dbms_ijob.run(<id>); from the same priv user who owns the object?
to trace a job:1 person found this helpful
your job's trace should called like:
Where do I get the <id> part? My job name is "DW_ETL_JOB"
Below will give u id ,1 person found this helpful
select job from dba_jobs where what='<job_name>';
I might be mistaken, but it appears to me the OP is talking about Oracle scheduler (DBMS_SCHEDULER), not job manager (DBMS_JOB).1 person found this helpful
In this case the following views could provide details of the execution:
Sorry if I misunderstood the question.
I thank you all,
Well I guess dbms_job is under dbms_scheduler so I need to check all aspects of it :)
There might be error affecting each part.
Its hard to monitor the dba logs tables as there are lots of rows and I dont know the jobs logging it :(
How do I delete all the log tables? Are there other log tables like tha auditing tables that I need to periodically cleanup?
It might cause space problem later.
Is it safe to truncate all the sched log tables?
Oracle Database 11g Enterprise Edition Release 18.104.22.168.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> select count(*) from dba_scheduler_job_run_details; COUNT(*) ---------- 15298 SQL> select count(*) from dba_scheduler_job_log; COUNT(*) ---------- 27132 SQL>
Edited by: KinsaKaUy? on 26-Nov-2012 19:38
Please don't be discouraged by the amount of the information. By default the history is kept for 30 days which is not much. If you wish to keep less data you can always use1 person found this helpful
where N is between 0 and 1000000 days.
exec DBMS_SCHEDULER.SET_SCHEDULER_ATTRIBUTE('log_history', N);
You can also search by job_name which you can find in DBA/ALL_SCHEDULER_JOBS to restrict the amount of info shown. Also there's a timestamp that make it easier to identify the last run.
Edited by: Max Seleznev on Nov 26, 2012 11:10 PM
In Addition ..
1. Use below to identify how many days logs preserved by scheduler views
select max(LOG_DATE),min(LOG_DATE) from dba_scheduler_job_log;
2. Try logging your jobs only when failure occurs
to get job class ..
select job_name,job_class from dba_scheduler_jobs where job_name='<your job name>';
'<job_class>', 'logging_level', DBMS_SCHEDULER.LOGGING_FAILED_RUNS);
Note : You must be granted the MANAGE SCHEDULER privilege to set the logging level of a job class.
3. Purging Logs Manually