DBMS_SCHEDULER.RUN_JOB causes scheduled job not to run again

Environment: 10.2.0.2 Linux 64-bit
Hi,
I have some DBMS_SCHEDULER chain jobs scheduled to run every hour which has been running fine with no issues for a while now.
I needed to run a couple of jobs manually in-between scheduled times so I ran the job using DBMS_SCHEDULER.RUN_JOB, and that worked as expected as it has done in the past.
This issue is that the jobs I ran manually haven't run at their scheduled time since I did that. The only way around it was to recreate the job completely.
Any idea if this is normal functionality, or should I be raising this as a possible issue through Oracle Metalink?
Any help or ideas would be much appreciated.
Thanks
Tim

Hi Tim,
This is a known bug which is tracked internally by bug #5705385. It will be fixed in the next patchsets for 10.2 and 11.1 (i.e. 10.2.0.5 and 11.1.0.7) . If you urgently need a fix, an official patch seems to be available for 10.2.0.3 .
There does seem to be a workaround - using run_job again after the first run_job has completed will not do anything but the chain job should again run on schedule.
Hope this helps,
Ravi.

Similar Messages

DPM 2012 R2 Upgrade - Scheduled jobs not running

Hi,
We're having an issue after upgrading to DPM 2012 R2 where the scheduled jobs are not running.
We're running Server 2012 R2 with SQL Server 2008 R2 SP2.
Looking at SQL jobs, if we run the job step we get an error.
Message
[136] Job 18822c3e-8fe 7-47a2-bb6e-0feccecc2952 reported: The process could not be created for step 1 of job 0xA746B176EAD99943A14A57DAF684829F (reason: %1 is not a valid Win32 application)
However, if we place quotes around the triggerjob.exe path in the SQL default job step:
"C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin\TriggerJob.exe" 9b30d213-b836-4b9e-97c2-db03c3eb39d7 18822c3e-8fe7-47a2-bb6e-0feccecc2952 server.domainname.com
It is successful.
We've already uninstalled DPM 2012 R2 and re-installed, restored the database and run dpmsync -sync with the same result. We've checked the DCOM Config Launch and Activation Permissions for Microsoft System Center 2012 R2 Data Protection Manager Service
and has full access.
Has anyone else had this issue and been able to resolve it?
Any help would be greatly appreciated.

Hi,
The below blog may assist with troubleshooting your issue.
http://blogs.technet.com/b/dpm/archive/2014/10/08/how-to-troubleshoot-scheduled-backup-job-failures-in-dpm-2012.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually
answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

Scheduled job not getting executed on a logical standby

Hello,
We have created a job(through dbms_scheduler API). The job is enabled and shows up in the SCHEDULERJOBS view also.
However the job does not get executed. I looked into the following tables there was no relevant entry found for the aforesaid job:
select * from all_scheduler_job_log
select * from dba_scheduler_running_jobs
select * from DBA_SCHEDULER_JOB_RUN_DETAILS order by log_date desc
Is there any limitation that we cannot execute scheduled jobs on a logical standby database. If i execute the relevant program (that is configured to be run as job in this scenario) as an individual procedure from SQL plus, it gets executed successfully implying there is no errors/problem in the subprogram that the job is going to invoke.
Appreciate your thoughts in this regard.
Thanks.

Hi Justin,
Thanks for your response.
As per the app design, the job invokes a stored program(that maps to a stored procedure present in standby db itself) that reads the data from standby and populates the relevant tables/entities in another database(third db, not primary or standby) which acts as a repository. No write operations are to be performed on standby.
So, i have two doubts:
-- Can scheduled jobs execute on logical standby db[Oracle release 10g(R2)]
I was going through few of the oracle docs and it is mentioned that this is a known limitation in 10g
R2 release and has been corrected in 11g. Now we have something called database_role
attribute that needs to be set to 'LOGICAL STANDBY' if you need to execute a job on
standby. However it is available in 11g onwards.
-- If there is no workaround for the above mentioned problem in 10g-R2 release.
Then we may have to schedule a job from third db instance that shall invoke the program(residing on the standby db). Can we have a scheduled job which executes a program that maps to a remote stored procedure instead of local stored procedure?
Appreciate your thoughts.
Thanks

How to Schedule Jobs to only run during a time window

I have a long running task that needs to schedule jobs to process data.
I only want these scheduled jobs to start during a specific window of time each day, probably 10:00 PM to 6:00 AM.
If the scheduled jobs do not begin during the specified time frame, they must wait until the next day to start running.
Each scheduled job will only be executed once and then auto dropped.
How should I go about creating these scheduled jobs?

Hi Jeff,
I agree that the documentation isn't clear enough about the purpose of windows.
You can indeed use windows for changing the resource plan, but you can also use them for scheduling your jobs.
I did a simple test in real-time to illustrate the latter.
At around 10.30 am today I created a table that will populated by a job:
CREATE TABLE TEST_WINDOW_TABLE(EVENT_DATE DATE);
Then, I created a window whose start_date is today at 10.40 am :
dbms_scheduler.create_window(
                             window_name     =>'TEST_WINDOW',
                             resource_plan   => NULL,
                             start_date      => to_date('10/04/2014 10:40:00', 'dd/mm/yyyy hh24:mi:ss'),
                             repeat_interval => NULL,
                             duration        =>interval '5' minute
You can see that this window doesn't have a resource plan, and its repeat interval is NULL (so it will be opened only once).
The window will stay open for 5 minutes.
Finally, I created a one-off job whose schedule is the previously created window:
DBMS_SCHEDULER.create_job (
                           job_name      => 'TEST_WINDOW_JOB',
                           job_type      => 'PLSQL_BLOCK',
                           job_action    => 'BEGIN insert into test_window_table values (sysdate); COMMIT; END;',
                           schedule_name => 'SYS.TEST_WINDOW',
                           enabled       => true,
                           auto_drop     => true
Checking the user_scheduler_job_log before 10.40 would return no rows, which mean the job hasn't started yet since the window was not open.
Now, from 10.40, it shows one entry:
SQL> select log_date, status from user_scheduler_job_log where job_name = 'TEST_WINDOW_JOB';
LOG_DATE                                                                         STATUS
10/04/14 10:40:02,106000 +02:00                                                  SUCCEEDED
The TEST_WINDOW_TABLE has also got the row:
SQL> select * from TEST_WINDOW_TABLE;
EVENT_DATE
10/04/2014 10:40:02
Voilà.
In your case, since you want to run the jobs daily between 10 pm and 6 am (duration of 8 hours), the window would look like this:
dbms_scheduler.create_window(
                             window_name     =>'YOUR_WINDOW',
                             resource_plan   => NULL,
                             repeat_interval => 'freq=daily;byhour=22;byminute=0;bysecond=0',
                             duration        =>interval '8' hour
For your jobs, you may need to specify an end_date if you want to make sure the job gets dropped if it couldn't run in its window.

Scheduled jobs fail to run after reboot

A couple of months back we moved our CF 8 server to a VM (VMWare). We have noticed that after the server (Windows OS) is rebooted, all scheduled jobs do not run. There are no errors in the logs. One oddity is that after the reboot in the scheduler log there are a series of entries for all jobs with the ThreadID of "main", after that there are no other entries. Normally when the job runs the ThreadID will be something like “Scheduler-1”. Here is where it gets really strange. Simply logging into the console will “trigger” the jobs and they will run. I do not have to manually initiate on of the jobs. This can be repeated over and over simply by rebooting the server. Manually stopping and starting the service does not trigger this issue nor will it “kick start” the jobs to run.

Update:
I opened up a case with Microsoft Support and resolved the issue. Apperantly this is a known issue and the bug will be addressed in CU6. Microsoft was able to give me a hotfix (QFE_MOMEsc_4724.msi) which I applied on all systems that have SCOM Console. I
am told that this issue occurs when SCOM 2007 R2 CU5 runs on SQL 2008 R2.
I hope it helps to others that run into same problem.
ZMR

Database Scheduled Jobs not working

Hai All,
In my database Scheduled database jobs not working , but it work manullay fine...
All parameter are correct including job_queue_processes.. Where I can start troubleshoot for this problem.
Oracle: Oracle 9.2.0.1.0
Platform : AIX
Please help ...
Shiju

did you enabled the job?Unlikely. DBMS_SCHEDULER was a 10g innovation and as the OP mentioned, they're on 9i.
Oracle: Oracle 9.2.0.1.0Cheers, APC

[OIM 9.1.0.2] Attestation Process scheduled is not automatically running

Hi Gurus,
IHAC that noticed that some attestation processes have not been triggered in the specified scheduled time, . So the Attestation tasks are not displayed into specified Reviewer's inbox (To-Do List).
There is a group responsible for creating the attestation processes and they have created a lot of processes. It seems that for some reason the attestation scheduled task is not automatically running for some cases.
For the attestation processes that were stopped, it is needed to run manually the scheduled task. With this action the attestation task flow runs.
Any tip on what could I check?
Thanks.

Hi,
I checked the Schedule task 'Initiate Attestation Processes'. It is Enabled, with frequency 30 min. Actual status: Inactive.
I got the follow error on the logs:
Something related to Memory.
I am investigating why when I use 'Run Now' option the attestation process work. Any tip?
<28/11/2012 03h32min51s BRST> <Info> <EJB> <BEA-010227> <EJB Exception occurred during invocation from home or business: [email protected]340a3f3 threw exception: java.lang.OutOfMemoryError: Java heap space>
<28/11/2012 03h32min51s BRST> <Notice> <Stdout> <BEA-000000> <ERROR,28 Nov 2012 03:32:51,518,[XELLERATE.SCHEDULER.TASK],Error while resubmitting the attestation process for delegation
Thor.API.Exceptions.tcAPIException: EJB Exception: ; nested exception is:
java.lang.OutOfMemoryError: Java heap space
at Thor.API.Operations.AttestationOperationsClient.updateResponses(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at Thor.API.Base.SecurityInvocationHandler$1.run(Unknown Source)
<28/11/2012 03h34min57s BRST> <Notice> <Stdout> <BEA-000000> <ERROR,28 Nov 2012 03:34:57,977,[XELLERATE.SCHEDULER.TASK],Error: Thor.API.Exceptions.AttestationProcessNotFoundException
Thor.API.Exceptions.AttestationProcessNotFoundException
at com.thortech.xl.ejb.beansimpl.AttestationOperationsBean.initiateAttestationProcess(Unknown Source)
at com.thortech.xl.ejb.beans.AttestationOperationsSession.initiateAttestationProcess(Unknown Source)
at com.thortech.xl.ejb.beans.AttestationOperations_yqqnsm_EOImpl.initiateAttestationProcess(AttestationOperations_yqqnsm_EOImpl.java:1033)
at Thor.API.Operations.AttestationOperationsClient.initiateAttestationProcess(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

Cron jobs not always run

I have cron jobs which do not always run. Has anyone had this problem. These are simple executables which may run one day, but not the next. Very puzzling.

415/2861
Here's in detail how/why it works this way
(and so far still the same in 10.4.4 I think):
A simple example:
http://discussions.apple.com/message.jspa?messageID=1320152#1320152
Peter Sealy:
http://discussions.apple.com/message.jspa?messageID=1384836#1384836
Dr. Smoke:
http://discussions.apple.com/message.jspa?messageID=1362594#1362594
The problem is that they are delayed by sleeps.

Automated Monitoring Scheduled Job not completing - PC

Hello Experts,
When we have scheduled a automated monitoring job, it is not getting executed completely and the status is shown as "In Progress". Also when we open the "Job Step Log" tab of the scheduled job in Automated Monitoring it is blank
What could be the reason for it?
Regards,
Ramakrishna Chaitanya

Hi
Try with Sox export role. Asynchronous mode?

How to setup a daily schedule job that will run a PL/SQL procedures every night

I have an update program that will need to run every night, can I setup a schedule job in data server?

Hi Kane,
You can try to use the package DBMS_JOB.
In the package specification is a description how to use it. The parameter called INTERVAL can be used to start your job every night.
Hope this helps...

Scheduled Job not running properly

Hello Friends,
I have a webservice that sends the mail to 24 or above users at a single go . This functionality I need to schedule . So I designed the job for same purpose , now the problem is that the webservice is running absolutely fine but once the job is scheduled and run , the mails are not send . I tried to send a single mail also with the help of scheduler API and was succefull in doing that but If the webservice needs to send more than one mail , this does not happen through the Scheduler API
I also had encountered problem while runnign the webservice earlier. I was getting the Read timed out error during execution of webservice For its solution I increased the time out period of the webservice mannually ( from the left panel , the time out period can be increased in WebService Navigator ) and the problem got solved , this you cant do once you have scheduled the job so one of the reson may this time out expiration also .
So can any one help me out with the way to increase the time out period for the webservice not mannually rather in a more stabel and permanent way
Edited by: Smriti_techno on May 5, 2009 8:50 AM

hi
refer this link for example of scheduler api
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90a95132-8785-2b10-bda5-90d82a76431e
let me know am i correct or not
bvr

Schedule jobs not running

the user execute the abap job and execute in background, but it is not running. He execute many times, but still sit in schedule state, do you know why? there is no error in SM21, will it be authority issues? how to check? thanks

It looks like it is an authorization issue. Ask them to do that again and immediately in another session, run SU54. This will show all the authorization checks that the user went through and tells you if it failed.
Alternatively, they can just go to SM37 and try to release it. If it comes back with a message, you will know.
Srinivas

ODI 11g Scheduled job stays in running state

Hello All ,
In ODI operator in the integration process ,there arer 3 scenarios scheduled .
When the first is completed it switches to second ,but the next step/process keep running and never comes to an end,though the corresponding backend activity has been completed(which the scenario is supposed to do).
Which ultimately results into timeout.
Please suggest a solution for this.
Thanks in advance ,
ABHIJEET

Hi,
Actually your syntax is exactly right for running a single run-immediate job.
it looks like the slave running your job may have crashed or terminated unexpectedly. You should do a stop_job (force=>true) on your job and you should look through your job slave trace files j0trc for reasons why your job slave did not finish the job. You can also try grepping your job slave traces for the job name 'TEST_JOB' to find the right trace.
Hope this helps,
Ravi.

OEM Scheduled Job Not Assuming OS User File Permissions

I have defined and scheduled a job using OEM Grid Control that executes an OS level command which is a script containing the HP-UX find command. When I run the script at the OS level the script completes successfully. When the job scheduler runs the job it fails because the find command doesn't have permission to recursively traverse the subdirectories even though the subdirectories are owned by the process executing the find command. The preferred credentials for the job are set to the same user that I used to run the job manually. Why would this be happening?
We're using OEM Grid Control 10.2.0.3.0 running on Linux used to manage Oracle 10G on HP-UX. Please help.

Please paste the script and error

DB Control scheduled jobs not start

I've several scheduled RMAN backup jobs in the jobs library of DB Control of a RAC database (not DBMS_JOBS). The problem is these jobs never start. Only start when I select "Execute immediately".
Any clues or log/trace files I could check?
Thanks.

What is the setting of job_queue_processes in the Initialisation parameter of each instance?. Ensure that it is set to something greater than 0.

DBMS_SCHEDULER.RUN_JOB causes scheduled job not to run again

Similar Messages

Maybe you are looking for