Trouble running jobs with scheduler

Hello,
We have trouble running jobs with scheduler since we upgrade DS4 from 14.0.1.142 to 14.0.2.322. It works fine for several hours and then randomly jobs are not started. There is no error in the log. In AL_RWJobLauncherLog.txt file, there are no "RWJL_EXIT called" in that case :
02_28_2012 09:30:00     CRWJobLauncherApp::InitInstance called.
+02_28_2012 09:30:03     +
02_28_2012 09:30:33     *** RWJL_EXIT called.
02_28_2012 10:00:00     CRWJobLauncherApp::InitInstance called.
02_28_2012 10:30:00     CRWJobLauncherApp::InitInstance called.
02_28_2012 11:00:00     CRWJobLauncherApp::InitInstance called.
02_28_2012 11:30:00     CRWJobLauncherApp::InitInstance called.
+02_28_2012 11:30:03     +
02_28_2012 11:30:33     *** RWJL_EXIT called.
Sever_eventlog file shows that job is not started. Whole server has to be restarted to get it to work again (restarting DI_JOBSERVICE is not enough). Could you help please ?
Regards
Annie

Hi Annie,
Mmmhhh that doesn't make much sense to me, except if you have problems with the repository:
1) Your JobServer or JobLauncher has problems executing jobs
=> reads the repository to get job information
2) Your Management Console (independant from the JobServer - but on same machine) has problems
=> Is connected to the repository to show job status, adapters etc.
3) The Tomcat which is hosting the Management Console is OK
=> No connection to the repository of DS.
Do you have any network or database problems? Can you put the database on the same server?
I could be wrong of course...just the only thing that comes to mind..
Regards
Norbert
P.S:
What about compressing your repository and/or
1395641 - Will truncating the AL_HISTORY and AL_STATISTICS Table compromise the referential integrity of the repository?
There are half a dozen KBAs about these tables..
Edited by: Norbert Klein on Mar 3, 2012 10:37 AM

Similar Messages

DS run longer with scheduled job as compare to manual run

I have scheduled a job through Management Console (MC) to run everyday once at
certain time. After some time, maybe after 15 days of running, the execution
time has increased to double from 17 mins to 67 mins by one time jump. After
that, the job kept running and spent 67 mins to complete.
The nature of the job is to generate around 400 output flat files from a
source db2 table. Under efficient running time, 1 file took around 2 seconds to
generate. But now it became taking 8 seconds to generate one file. The data
volume and nature of the source table didn't change, so that was not the root
cause of increasing time.
I have done several investigations and the results as such:
1) I scheduled again this job at MC to run for testing, it would take 67 mins
to complete. However, if I manually run this job thorough MC, it would take
17 mins efficient time to run.
2) I replicated this job to a second job as a copy. Then I scheduled this
copied job at MC to run, it would take 67 mins to run. But if I manually run
this job through MC, it will take 17 mins to run.
3) I created another test repo and load this job in. I scheduled the job to
run at this new repo, it would take 67 mins to run. If I manually run the job
through MC, it only took 17 mins to run.
4) Finally, I manually executed the job through unix job scripts command,
which is one of the scheduled job entry in the cron file, such as
./DI__4c553b0d_6fe5_4083_8655_11cb0fe230f4_2_r_3_w_n_6_40.sh, the job also would take 17
mins to run to finish.
5) I have recreated the repo to make it clean and reload back the jobs and
recreated again the schedule. Yet it still took 67 mins to run scheduled job.
Therefore, the conclusion is why it takes longer time to run by scheduling
method as compare to manually running method?
Please provide me a way to troubleshoot this problem. Thank you.
OS : HPUX 11.31
DS : BusinessObjects Data Services 12.1.1.0
databasee : DB2 9.1

Yesterday we had done another test and indirectly made the problem to go
away. We changed the generated output flat file directory from current directory
of /fdminst/cmbc/fdm_d/bds/gl to /fdminst/cmbc/fdm_d/bds/config directory to
run, to see any difference would make. We changed the directory pointing
inside Substitution Parameter Configurations windows. Surprisingly, job had
started to run fast and completed in 15 minutes and not 67 minutes anymore.
Then we shifted back and pointed the output directory back to original
/fdminst/cmbc/fdm_d/bds/gl and the job has started to run fast ever since and all
completed in 15 minutes. Even we created ad hoc schedule to run and it was
still running fast.
We not sure why it was solved by shifting directory away and shifting back,
and whether this had to do with BODS problem or HP Unix system environment
problem. Nonetheless, the job is started to run normally and fast now as we
test.

Running job with a specific background ID...

I have a program and a background ID created. I want to run that job in background immediately using that background ID defined by basis. How can I do that ?
Regards,
Rajesh.

Hi,
YOu can create a separate program with Input parameters as job id.
Now submit the program using SUBMIT statement along with Job id, jobname which are created.
Usually, we will be creating job id using JOB_OPEN function module, and then will be submitting a background job using SUBMIT statement and finally closing the job using JOB_CLOSE function module.
Regards,
AShok

Trouble Running Simulation with VCS for OpenSPARCT1

Hi,
I've been trying to run the regression test using VCS without any luck. I am running a 64-bit system and it looks like some of the libraries that VCS is trying to link against from OpenSPARC are 32-bit so the compilation fails. I run " sims -sim_type=vcs -group=core1_mini -novera_build " try run the regression, and I get the following errors. I did a diff and the libraries in OpenSPARCT1/tools/Linux/x86_64/lib are the same as the ones in OpenSPARCT1/tools/Linux/i686/lib (they're all 32-bit). So my question is, can I recompile these libraries from some sources available somewhere or are they available anywhere for download?
g++ -o ../simv -Wl,-E main.o 5NrI_d.o <<snip>> /usr/synopsys/vcs/amd64/lib/libvirsim64.a -L/home/oleg/OpenSPARC/OpenSPARCT1/tools/Linux/x86_64/lib -lnsl -lm -lc -lsjm -ljbus_mon -liob -ljpcommon -lsocket_pli -lmonitor -lutility_pli -lmem_pli /usr/synopsys/vcs/amd64/lib/libvcsnew.so -ldl -lm -lc -ldl
/usr/bin/ld: skipping incompatible /home/oleg/OpenSPARC/OpenSPARCT1/tools/Linux/x86_64/lib/libsjm.a when searching for -lsjm
/usr/bin/ld: cannot find -lsjm
collect2: ld returned 1 exit status
make: *** [product_timestamp] Error 1
Make exited with status 2
CPU time: 142.620000 seconds to compile + .010000 seconds to elab + .450000 seconds to link
set: 1: Illegal option -h
sims: Caught a SIGDIE. failed building model at /home/oleg/OpenSPARC/OpenSPARCT1/tools/src/sims/sims,1.262 line 2019.
sims: Caught a SIGDIE. Could not build model for regression at /home/oleg/OpenSPARC/OpenSPARCT1/tools/src/sims/sims,1.262 line 1272.
Oleg

Thanks, unfortunately that utility didn't quite work out of the box and there were a few issues I had to resolve.
Issue #1: Since "uname -p" on my system returns "unknown", I needed to change all those instances to "uname -m" which will actually return x86_64.
Issue #2: Files $DV_ROOT/tools/pli/iop/device.h and $DV_ROOT/tools/pli/iop/pcx.h have an extra qualification, namely "void pcx::clean();" in pcx.h needed to be changed to "void clean();" and a similar change needed to be made in device.h. I'm fairly certain that this won't break functionality with any older compilers and will help to not break it for newer ones.
Issue #3: ar would abort because $DV_ROOT/verif/env/iss/pli/sjm/c/Templates.DB was empty on my linux system. Looking at the Makefile in that directory,
I saw line 29 was "TEMPLATE_OBJS = ./Templates.DB/*.o" which was causing it to choke. I changed this to "TEMPLATE_OBJS += ./Templates.DB/*.o" as I saw from another part of the makefile and this fixed the issue, though I don't know enough about scripting to say that this is strictly correct.
Issue #4: $DV_ROOT/verif/env/iss/pli/common/c/CircularLinkedList.cc failed to compile because line 174 was "head = null" instead of "head = NULL".
Finally, after resolving all of these, I was able to compile the libraries, yay. I mention all of these firstly to help those who run into similar problems, but also to ask the more general question of who should I be passing these bugs along to. Perhaps you can brush off some of these to some crazy setup I may have, but at least Issue #4 really needs changing somewhere if it hasn't already.

Jobs with running status in OEM while it was already finished

Hi
We have rebooted our server and all the jobs which are suppose to run some scripts in the server are showing running state for more than 16hours now! checking the scripts logs it was successfully executed and finished. When trying to delete the running jobs and schedule a new one it refuses to stop (although its not even running in reality). What can we do to clear this running status and let oem to schedule new ones? or how can we resolve this situation?
We are running Enterprise manager 10g
Swaid

Hi Jozsef,
I've tried to follow the instructions in that Metalink note and the job seems to be deleted from mgmt_job table as well as the executions for that job in mgmt_job_execution; but still everything is hanging and when i checked in the EM page it still shows the job in running state! how can I clean it? and why is it hanging in the first place?
I've looked into the agent trace and its not getting updated since the problem has started and here is a bit of the last messages we have in the trace:
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Host, value = snmsmaster:3938
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Connection, value = Keep-Alive, TE
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = TE, value = trailers, deflate, gzip, compress
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = User-Agent, value = RPT-HTTPClient/0.3-3
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Accept-Encoding, value = gzip, x-gzip, compress, x-compress
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Content-type, value = application/octet-stream
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Content-length, value = 593
2009-04-17 12:05:09 Thread-2413 ERROR http: --- Error context dump end for incoming request ---
The emoms trace is getting updated with some repeated error messages that looks like below:
2009-04-18 15:56:57,114 [HealthMonitor] ERROR em.jobs pingPastDue.604 - Job step continuing
2009-04-18 15:57:13,362 [HealthMonitor] ERROR emd.main run.291 - HealthMonitor : Found errant task : TaskRegn:ID3440,Callback:class oracle.sysman.emdrep.jobs.JobWorker,Iterative:true,Duration:900,DueTime:1240059433359
2009-04-18 15:57:13,363 [HealthMonitor] ERROR em.jobs pingPastDue.602 - Entry - 15 Minute timeout error for jobstep:Stepname: Command
Commandname: remoteOp
Commandtype: Short-Running
StepId: 97914
jobIdStr: 679733b18b7a5698e04400144fa10220
executionIdStr: 67bd0ff86c9b4268e04400144fa10220
iterateParam: null
iterateParamIndex: -1
Swaid

How to stop a running job in 10g Scheduler?

The following is a duplicate post. I posted the following to the general database forum before seeing that otn has a new scheduler forum:
I am not able to find in the Admin Guide a method to stop a currently running instance of a job in the 10g scheduler.
In 9i, I run the following script calling DBMS_JOB.broken and DBMS_JOB.remove to shut down currently running jobs:
DECLARE
jobid NUMBER;
CURSOR c1
IS
SELECT job
FROM dba_jobs
WHERE priv_user = 'ME';
BEGIN
OPEN c1;
LOOP
FETCH c1
INTO jobid;
EXIT WHEN c1%NOTFOUND;
DBMS_JOB.broken (jobid, TRUE);
COMMIT;
DBMS_JOB.remove (jobid);
COMMIT;
END LOOP;
CLOSE c1;
END;
How may I create similar code to shut down currently running jobs using DBMS_SCHEDULER in 10g? According to the Admin Guide, disabling jobs with the force option will still allow the job to finish.
How can I terminate a running job in 10g?

You can stop a currently running job using the STOP_JOB api.
STOP_JOB Procedure
This procedure stops currently running jobs or all jobs in a job class. Any instance of the job will be stopped. After stopping the job, the state of a one-time job will be set to SUCCEEDED whereas the state of a repeating job will be set to SCHEDULED or COMPLETED depending on whether the next run of the job is scheduled.
Syntax
DBMS_SCHEDULER.STOP_JOB (
job_name IN VARCHAR2
force IN BOOLEAN DEFAULT FALSE);
Parameters
Table 83-44 STOP_JOB Procedure Parameters
Parameter Description
job_name
The name of the job or job class. Can be a comma-delimited list. For a job class, the SYS schema should be specified.
If the name of a job class is specified, the jobs that belong to that job class are stopped. The job class is not affected by this call.
force
If force is set to FALSE, the Scheduler tries to gracefully stop the job using an interrupt mechanism. This method gives control back to the slave process, which can update the status of the job in the job queue to stopped. If this fails, an error is returned.
If force is set to TRUE, the Scheduler will immediately terminate the job slave. Oracle recommends that STOP_JOB with force set to TRUE be used only after a STOP_JOB with force set to FALSE has failed.
Use of the force option requires the MANAGE SCHEDULER system privilege.
Setting force to TRUE is not supported for jobs of type executable.
Usage Notes
STOP_JOB without the force option requires that you be the owner of the job or have ALTER privileges on that job. You can also stop a job if you have the CREATE ANY JOB or MANAGE SCHEDULER privilege.
STOP_JOB with the force option requires that have the MANAGE SCHEDULER privilege.

Job submission failed : error occurred while scheduling the job. org.quartz.objectalreadyexistsexception: unable to store job with name

Experts,
Please help me out here,Am facing this issue while scheduling a job in BIPublisher.
job submission failed : error occurred while scheduling the job. org.quartz.objectalreadyexistsexception: unable to store job with name
Thanks,

You are probably installing on a hardened machine.
The "installation guide" says that if you are doing so, you need to create a file named libx11.so.4 and update your LD_LIBRARY_PATH (see http://docs.iplanet.com/docs/manuals/messaging/ims52/ig/unix/overview.htm)but:
1- the library name is libX11.so.4 and
2- for jre a common file is not enough, you need to install SUNWxwplt at least. This will install the library on /usr/openwin/lib.
You can check the results running <server-root>/bin/base/jre/bin/jre
Hope that helps and sorry about my poor english.

Job with Multiple Schedule of same time & only one is executed, Why

Hi ALL,
I've Created a package to notify report in email as excel, which is using a path to render report and save it as excel.
This package was need to be schedule every first day of month and on every Friday even at morning 7 AM.
So logically these are two events.
But if we see on 1 May 2015 we have Friday and plus first day of month
So technically this should fail.
either for IO operation for render &
storing data over same location with same file name.
To replicate this i created two three schedule
Below is the job history, job is invoked by only one schedule
Question-
1) Why one one schedule execute?
2) why "sched2" only , it could be "sched3" only or "DentalOperationStackAndRank-Sched1" Only?
Another this i result into error if different job executing same package at same schedule.
FYI- package is deployed at database level
HS

Hi HS,
As described in this
article, more than one job can run on the same schedule, and more than one schedule can apply to the same job.
And I make a test about your scenario, when configuring a SQL Server job with three schedules that reference same dates and times, my job behaves as yours that only one schedule is executed, but the job is invoked by schedule2 or schedule 3 in my environment.
It is a normal behavior of SQL Server job in my opinion. For more details about such scenario, you can track the job following this
blog.
However, when I configure three jobs that run on the same schedule, everything works well and the three jobs all run successfully.
I recommend you configure three different jobs that execute same package at same schedule .
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

How can you get the schedule of a single reoccurring job with Restart ability in Redwood to pause when it has failed...?

We need the Request Restart ability when scheduling a single reoccurring job in Redwood. Most of our jobs are scheduled in CHAINs which offers the Final Status Handler on Step level, and the schedule is "paused" when a job in the CHAIN has failed ( the next instance does not populate until the OP MSG has been Replied to) , and once the OPERATOR message is replied to, the CHAIN can resume running again ( desired ) . But we need this same ability when scheduling a single job not in a CHAIN. In our testing, we set up a job with Request Restart chosen on the Error , Killed and Unknown selections on the Restart Behavior Tab. But we found when a job is scheduled say once a day at 8AM, and when it fails, an OPERATOR msg appears allowing a Restart choice ( desired), but the next day's schedule also populates ( undesired) and we do NOT want the schedule to continue on yet because we need a chance to fix the error before the next insance runs for business reasons. So how can you get the schedule of a single reoccurring job with Restart ability in Redwood to pause when it has failed...?

Hello Fran,
You can wrap the job chain in a master job chain in the first step and set the final status handler there.
You can also set the Restart Behavior to 'Stop Submit Frame', in that case you will have to resubmit the job once you are finished troubleshooting.
Regards Gerben

How to run a background job with the cloud_scheduler package

Hi,
Is the cloud_scheduler package able to run background jobs as documented? When you try to run a job in another session using:
cloud_scheduler.run_job(job_name=>'MYJOB', use_current_session=>false);
The call fails with:
ORA-20002: Cannot run job MYJOB. Adhoc background execution is disallowed. Please enable the job instead.
If you try to use cloud_scheduler.enable to run the job then the job does not run when scheduled.
Rod West

Hi Rod,
Yes, I believe so. Here's a test case that I just ran successfully from SQL Workshop in my database trial service:
create table myjob_test (aa timestamp with time zone);
begin
    cloud_scheduler.create_job (
        job_name        => 'MYJOB',
        job_type        => 'PLSQL_BLOCK',
        job_action      => 'begin insert into myjob_test values (systimestamp); commit; end;',
        repeat_interval => 'freq=minutely; interval=3' );
end;
begin
    cloud_scheduler.enable ( name => 'MYJOB' );
end;
select job_name, state, run_count, failure_count, last_start_date, next_run_date, systimestamp from sys.user_scheduler_jobs;
select * from myjob_test order by aa;Is the next_run_date in the past for your job? If it is, try disabling/enabling the job to "reinitialize" the job's schedule.
-- Vlad

Schedule a job with email destination in BOXI R2 with email format as html

Hello Guys, would it to possible to schedule a job with email destination in BOXI R2 with email format as html? we are able to get it running with plain text email format. we use Java SDK to interface with BO Enterprise servers.
thanks for your thoughts,
Venkat

Hi
your job should SMOF_DOWNLOAD can bring new material master if you set up correctly.
as a smart method smof_download is the best way.
doble check your filter condition. it should work as you expected. because we dont involve in manual pulling...
check your variant once again. in vari table,
can you check r3ac1 - filter settings- source seetingsa--> source site nmae --> backendlogical system and filter sync..
br
Muthu

"BBP_SC_TRANSFER_GROUPED" to run as a scheduled job

Hi,
I need to make the program BBP_SC_TRANSFER_GROUPED, run as a scheduled job. please guide me the steps to do that. Thanks in advance.

Hi Krishna Vardhan,
You can schedule this report using SA38txn.
Input the report name and click on Background tab on the menu bar and in the next screen click on Variants tab on the menu bar and in the next screen click on create tab next to the variant field and create a variant.
Enter the criteria for the variant and click on attributes and enter the short description for variant and also choose the preferences for various attributes and clcik the save icon to save the variant.
Then goto SA38 txn again and input the report name and clcik on the with variant tab on the menu bar and click background tab and enter the required variant name in the next screen and click on Schedule tab and schedule the job periodically based on your requirement.
Hope this makes you more clear and helps in resolving your issue. Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

Job with multiple event schedules

Is it possible to create a job with multiple schedules? Can you have multiple schedule names?
DBMS_SCHEDULER.CREATE_JOB (
job_name => 'my_new_job2',
job_type => 'PLSQL_BLOCK',
job_action => 'BEGIN SALES_PKG.UPDATE_SALES_SUMMARY; END;',
schedule_name => 'my_saved_schedule, my_saved_schedule2'); <------------------ like this?
END;
thanks.

I am using oracle 10g and have installed the file arrival package. I want my job to run when multiple files arrive. I have created the file arrival event schedules. I know i can create chain event steps to respond, but my chain has to be running for the steps to respond to the events. I want the chain (or rather the job that starts the chain) to kick off when 2 or more files arrive.
thanks.

Who scheduled a job with service user

Hi,
In my one of the system one job is running with service user. As service user cannot log into system. One of the dialog user logged in to system and scheduled one job with service user. this job is running more than 2 months. Now we want to know who is that dialog user scheduled this job with service user. I have checked in job details it is not showing dialog user who has sheduelded first time.
Pls someone help me in this case.
Kind regards,
Ram
<subject_modified>
Use a proper subject
Read the "Rules of Engagement"
Edited by: Juan Reyes on Jul 1, 2009 10:25 AM

Just check the job owner.... If the Owner is the service user then most likely the user was changed to service user after the job creation. Also be aware that some jobs are generated by the system.
Regards
Juan

ORA-27492: unable to run job scheduler unavailable

Hello Fellow Oracle users, this is the first post in this forum but I need some help with my Oracle Scheduler.
This morning when I came into office, I realize from the Oracle Enterprise Manager (11g) that all of my scheduled jobs did not run at all. So I tried to do a manual run by choosing the job and clicking "Run Now".
This error was shown (job not real name)
java.sql.SQLException: ORA-27492: unable to run job "SCHEMA.DATA1": scheduler unavailable Check the log/trace file for more Details+
I have no idea where to look up the log/trace file , so I could not find any reasons why this happen.
https://forums.oracle.com/forums/thread.jspa?threadID=646581
I've looked up this thread and tried the suggestions posted there and I believe it ain't the problem with queue process nor job process limits.
I've tried select * from dba_scheduler_global_attribute where attribute_name='SCHEDULER_DISABLED' and I don't get any row selected.
I hope I'm clear enough on the issue I'm facing, hope I'll get some answers to fixing this. Thank you very much.
Regards,
Matthew

Hi,
I am not an expert on this, i am learning.
Check you history:
select client_name,window_name,to_char(job_start_time,'yy-mon-dd hh24:mi:ss') job_start_time,job_status
from DBA_AUTOTASK_JOB_HISTORY;Are you in windows? In you server services check make sure OracleJobSchedulerXXX is running.
Also you can check the logs with:
http://docs.oracle.com/cd/E11882_01/server.112/e25494/scheduse008.htm#CHDGIDFD
I hope this help.
Best,

Trouble running jobs with scheduler

Similar Messages

Maybe you are looking for