Re: dbms_scheduler jobs stop running after reboot.
Date: Wed, 6 Mar 2019 21:18:51 +0000
Message-ID: <DM6PR01MB3914BE600079D8B0D7A1E256CE730_at_DM6PR01MB3914.prod.exchangelabs.com>
From: oracle-l-bounce_at_freelists.org<mailto:oracle-l-bounce_at_freelists.org> <oracle-l-bounce_at_freelists.org<mailto:oracle-l-bounce_at_freelists.org>> on behalf of Chris Taylor <christopherdtaylor1994_at_gmail.com<mailto:christopherdtaylor1994_at_gmail.com>> Sent: Sunday, March 3, 2019 11:32 PM
To: gogala.mladen_at_gmail.com<mailto:gogala.mladen_at_gmail.com>; ORACLE-L Subject: Re: dbms_scheduler jobs stop running after reboot.
Joan,
If you're running 12.1 (maybe 12.2) there's a bug with scheduler jobs not firing after a database restart . Oracle support should have the metalink article as I don't have it in front of me at the moment.
We run into this on our db occasionally.
Chris
On Sun, Mar 3, 2019, 7:22 PM Mladen Gogala <gogala.mladen_at_gmail.com<mailto:gogala.mladen_at_gmail.com> wrote:
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 DXC Technology Company - Headquarters: 1775 Tysons Boulevard, Tysons, Virginia 22102, USA. DXC Technology Company -- This message is transmitted to you by or on behalf of DXC Technology Company or one of its affiliates. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind DXC Technology Company or any of its affiliates to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. --. -- http://www.freelists.org/webpage/oracle-lReceived on Wed Mar 06 2019 - 22:18:51 CET