Re: dbms_scheduler jobs stop running after reboot.
Date: Sun, 3 Mar 2019 20:21:29 -0500
Message-ID: <3f36ff24-515f-e724-0754-4e7cb9ca6542_at_gmail.com>
Hi Joan!
Each and every queue process has a trace. To enable an additional trace,
you can use event 10046, level 16 on few of those processes and see
what is going on within the traced processes. Looking into
DBA_SCHEDULER_JOBS, DBA_SCHEDULER_JOB_LOG and
DBA_SCHEDULER_JOB_RUN_DETAILS would also be a good idea. And what was
that about "unsupported page size"? What OS are you using? What version
of Oracle? However, the very first place to look in would be the alert
log. ADRCI can be useful here, too.
Regards
On 2/28/19 11:55 AM, Joan Hsieh wrote:
> Hi List,
>
> We planned to increase the SGA_target from 50G to 64G. Ended up we
> had to change back to 50G due to the page size was not supported.
> However, after the database rebooted all of the scheduler jobs
> stopped to execute. (There are more than 500 jobs, fired every 5 min
> in application)
>
> The last_start_date in dba_scheduler_jobs was the time prior to the
> database rebooting, which was 2/23 9pm, and the state was SCHEDULED.
>
> The job queue is 50, cjg0 is running. we don't use oracle OIM.
>
> The developer had tried to disable/enable the scheduler. They had
> also tried to use exec DBMS_SCHEDULER.run_job to test. The job ran,
> but did not fire after 5 min for the next run.
>
> The database is 4 TB in size. Previously the database had bounced
> several times, but it had never caused any scheduler jobs issue
> before. We are trying to find any resource and had opened an Oracle
> SR for this issue. We just wanted to find out if you have have any
> insight.
>
> Much thanks in advance.
>
> Joan
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Mar 04 2019 - 02:21:29 CET