Run-after: handy command to schedule jobs easily

Hi All
I've created a declarative command to schedule jobs easily, like below;
$ run git push origin master after 5 minutes, 30 seconds
Here it is: https://github.com/azer/run-after
To install:
$ npm install -g run-after
Ideas and recommendations welcome!
Azer

60 % of characters, same result:
sleep 5.5m; git push origin master

Similar Messages

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.

Scheduling jobs procedure

Hi all,
I have two programs which needs to be run in background.
The first program is set run at 12 am everyday and the other program should follow the first the first one.
Can anybody guide me in creation of those jobs
I followed this procedure
1)job name zabc,
job class b
target server xyzz
then selected step icon
then abap program zabc(my first program)
variant ztest
save
then selected the start condition in main screen
selected date tim e format and have provided the date and time
save and again saved in mainn screen
and i followed the same procedure for second program but i used after job condition in start condition and in after job field i have mentioned the the first program job i.e zabc.
and saved it
when i went in sm37 and checked i found only my first job i.e zabc i couldnot locate my second job which is supposed to run after the completion of first job
can you guys tell whether i am following the right procedure or not .
I have one more question whta the difference between scheduled and release jobs which i see in sm37
Hope iam clear

Hi Rich,
I don't think it would work because i have job1 for first prgm and you are saying to place the second prgm in first job as second step then i cannot have option of start condition to run after first prgm because if i select after job option then i have give job1 which is still under process because the second program i.e the second step is schedule to run after first program then i have to mention the time rather than the selecting the after job option.since i won't know how much my first program would take i think this wouldn't be an option.
let me know if iam thinking any wrong

Old Schedule jobs in TBTCO

In a system there are thousands of old jobs in the schedule status.
How this happen? What are the reasons for a job to be left in an schedule status?
It safe to run RSBTCDEL and delete all schedule jobs older than 99 days?
Please help and thanks in advance.

How this happen? What are the reasons for a job to be left in an schedule status?
No idea... maybe they were meant to be release at some stage and no one did or they changed variants and create a new job.
It safe to run RSBTCDEL and delete all schedule jobs older than 99 days?
If they are old enough will hardy be needed ever again so i think is safe to delete them.
Regards
Juan

Scheduled jobs do not run as expected after upgrading to 10.2.0.3 or 4

FYI, we've had a ticket open for several days because our scheduled jobs (dbms_scheduler) would no longer run as scheduled after an upgrade to 10.2.0.4 on HPUX, couldn't find the solution by searching in metalink, nor did I find it here or using Google - obviously I wasn't searching correctly. There is a note id that references a set of steps that appears to have resolved our problem. I am putting this note out here so that if you encountered the same difficulty you may come across this note earlier in your troubleshooting efforts rather than later. The full title of the note is: 'Scheduled jobs do not run as expected after upgrading to either 10.2.0.3 or 10.2.0.4'. The Doc ID is: 731678.1.

Thanks - our ticket should be getting closed out on it (our dba will be updating it), the scheduler has been running reliably since we took the steps in the doc mentioned.

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

How to schedule batch jobs to run after another periodically?

Hi good people,
I want to schedule batch jobs to run periodically one after another.
Here is the problem:
I have scheduled JOB1 to run once a week and I scheduled JOB2 to run after that job (JOB1). The problem is that JOB2 runs only after the first time that JOB1 runs. The second time the JOB1 runs the JOB2 is not started. I presume that the reason for that is that JOB2 is tied to the job number for the JOB1, and since a new job (with the new number) is created every week, the JOB2 is only tied to the first instance of JOB1.
So does anyone have an idea how to get JOB2 to automatically run every week after JOB1? One idea is to use events, but that I'm hoping that there is a bit cleaner solution..
Best Regards,
Armin

Hi
Try scheduling both JOB1 & JOB2 in a single job in steps.
First schedule JOB1 & then give JOB2 in steps.
Kindly check the following link to do job scheduling in steps:
http://help.sap.com/saphelp_47x200/helpdata/en/c4/3a7ed1505211d189550000e829fbbd/frameset.htm
In the above help documentation, look for the topic <b>"job steps"</b> in
"Background Processing: Concepts and Features"
hope it helps!
best regards,
Thangesh

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.

Cron job help- Need to run the Autobuddy command every night...

I have not written anything in the form of a Unix script for YEARS and YEARS. Our XServe was built in Advanced mode, currently running 10.5.4 Server. On this box, we are running Wiki and iChat. Since we built this box as an Advanced box the "Autobuddy" option was not available.
I have since enabled it at the command line, but I am told by Apple that there still needs to be a command run after every time a user logs in if you want others to Autobuddy. That command is this:
"sudo /usr/bin/jabber_autobuddy -m"
Now I think this would be pretty easy to setup as an automatic cron script, but like I said, I have not written something like this in forever. Not to mention, I am not 100% sure what needs to happen since running the script with an sudo command will prompt for the root password.
I was wondering if anyone would be able to help me write the script up, and give me some instructions on how to install it. I just want it run everyday, midnight is fine, I don't really care. All I know is that we have a dept of 150 people, and it grows and shrinks all the time. They can deal with a new user not being seen for 24-48 hours, I just want to get this automated.
Any helps would be GREATLY appreciated!
Thanks
Tom

If you want to keep it simple try [CronniX|http://www.abstracture.de/projects-en/cronnix] a graphical tool for setting up CRON jobs on OSX. Whilst I have not actually done an autobuuddy in this way, I cannot see any reason why it will not run as a Cron Job.
The proper way ideally would be to use the launchd service.
Something like this should work:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>org.jabber.dailyautobuddy</string>
<key>ProgramArguments</key>
<array>
<string>/usr/bin/jabber_autobuddy</string>
<string>-m</string>
</array>
<key>LowPriorityIO</key>
<true/>
<key><UserName></key>
<string>admin</string>
<key>StartCalendarInterval</key>
<dict>
<key>Hour</key>
<integer>0</integer>
<key>Minute</key>
<integer>05</integer>
</dict>
</dict>
</plist>
(not sure why, but tabs are not showing up, making this hard to read)
Message was edited by: Tim Harris

How to schedule job to execute after 5 seconds gap using the program

Hi ALL,
How to schedule the program to run after 5 seconds to execute using JOB_OPEN,JOB_CLOSE,SUB_SUBMIT function modules in which parameter I should give this 5 secnods?
Regards
mahesh

Hi,
You can use the import parameters of function module JOB_CLOSE
SDLSTRTDT & SDLSTRTTM
to pass the required start date and time (respectively) of your background job. That is, if you want the job to be scheduled and start at a fixed time (as in your case 5 seconds in the future), you can determine the start date and time as 5 seconds ahead of sy-uzeit and pass the resultant values to the mentioned importing parameters.
Cheers,
Aditya

DBMS scheduler jobs running twice

Hi,
I have 4 DBMS scheduler jobs , which checks for a specific job status in DB and sends an email , when i started the schedule for the first week the jobs executed fine from next week I am getting two emails from each job , when i check the logs USER_SCHEDULER_JOB_RUN_DETAILS I see only one run , which seems weird to me so i disabled one job and left the three jobs in schedule , next time i got two emails from 3 jobs and one from disabled job . After checking logs i see that there is no entry of the disabled job execution . I am not sure where is the problem i can't find any log from where the disabled job executing. Please help me
Job schedule is to run every Saturday
Interval setup :
start_date => trunc(SYSDATE)+ 8.5/24,
repeat_interval => 'TRUNC(LEAST(NEXT_DAY(SYSDATE,''SATURDAY'') )) + 8.5/24'
Suresh

Hi,
I tried to schedule the same jobs using DBMS_JOB but i still get the same problem , I created the procedure with all code in and scheduled it using dbms job , first day it run once second day it run twice ( sending two emails) Inow i am not sure if issue is with my code or scheduler
Procedure
Declare
v_count number;
v_Recipient VARCHAR2(400) := '[email protected]';
v_Subject VARCHAR2(80) := 'TEST_Email';
v_Mail_Host VARCHAR2(30) := 'localhost';
v_Mail_Conn utl_smtp.Connection;
crlf VARCHAR2(2) := chr(13)||chr(10);
BEGIN
select count(*) into v_count from TEC_CODERETURN@RPRD where interface like 'FOR002B' and trunc(rundate) =trunc(sysdate);
if v_count = 0
then
v_Mail_Conn := utl_smtp.Open_Connection(v_Mail_Host, 25);
utl_smtp.Rcpt(v_Mail_Conn, '[email protected]');
UTL_SMTP.OPEN_DATA(v_Mail_Conn);
utl_smtp.WRITE_RAW_DATA(v_Mail_Conn, UTL_RAW.CAST_TO_RAW(
'Date: ' || to_char(sysdate, 'Dy, DD Mon YYYY hh24:mi:ss') || UTL_TCP.CRLF ||
'From: ' || '[email protected]' || UTL_TCP.CRLF ||
'Subject: '|| v_Subject || UTL_TCP.CRLF ||
'To: ' || v_Recipient || UTL_TCP.CRLF ||
'This is a test Alert'|| UTL_TCP.CRLF
UTL_SMTP.CLOSE_DATA(v_mail_conn);
utl_smtp.Quit(v_mail_conn);
end if;
EXCEPTION
WHEN utl_smtp.Transient_Error OR utl_smtp.Permanent_Error then
raise_application_error(-20000, 'Unable to send mail: '||sqlerrm);
END;
DBMS job creation
DECLARE
jobno NUMBER;
BEGIN
DBMS_JOB.submit
(job => jobno,
what => 'TEST_ALERT;',
next_date => trunc(sysdate)+0.1/24,
interval => 'SYSDATE + 1',
no_parse => TRUE );
DBMS_OUTPUT.put_line ('Created Job - the job number is:' || TO_CHAR (jobno));
COMMIT;
END;
Suresh

Scheduled jobs are not running DPM 2012 R2

Hi,
Recently upgraded my dpm 2012 sp1 to 2012 R2 and upgrade went well but i got 'Connection to the DPM service has been lost.(event id:917 and other event ids in the eventlog errors ike '999,997)'. Few dpm backups are success and most of the dpm backups consistenancy
checks are failed.
After investigating the log files and found two SQL server services running in the dpm 2012 r2 server those are 'sql server 2010 & sql server 2012 'service. Then i stopped sql 2010 server service and started only sql server 2012 service using (.\MICROSOFT$DPM$Acct).
Now 'dpm console issue has gone (event id:917) but new issue ocurred 'all the scheduled job are not running' but manully i can able to run all backup without any issues. i am getting below mentioned event log errors
Log Name: Application
Source: SQLAgent$MSDPM2012
Date: 7/20/2014 4:00:01 AM
Event ID: 208
Task Category: Job Engine
Level: Warning
Keywords: Classic
User: N/A
Computer:
Description:
SQL Server Scheduled Job '7531f5a5-96a9-4f75-97fe-4008ad3c70a8' (0xD873C2CCAF984A4BB6C18484169007A6) - Status: Failed - Invoked on: 2014-07-20 04:00:00 - Message: The job failed. The Job was invoked by Schedule 443 (Schedule 1). The last step to
run was step 1 (Default JobStep).
Description:
Fault bucket , type 0
Event Name: DPMException
Response: Not available
Cab Id: 0
Problem signature:
P1: TriggerJob
P2: 4.2.1205.0
P3: TriggerJob.exe
P4: 4.2.1205.0
P5: System.UnauthorizedAccessException
P6: System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal
P7: 33431035
P8:
P9:
P10:
Log Name: Application
Source: MSDPM
Date: 7/20/2014 4:00:01 AM
Event ID: 976
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
The description for Event ID 976 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
The DPM job failed because it could not contact the DPM engine.
Problem Details:
<JobTriggerFailed><__System><ID>9</ID><Seq>0</Seq><TimeCreated>7/20/2014 8:00:01 AM</TimeCreated><Source>TriggerJob.cs</Source><Line>76</Line><HasError>True</HasError></__System><Tags><JobSchedule
/></Tags></JobTriggerFailed>
the message resource is present but the message is not found in the string/message table
plz help me to resolve this error.
jacob

Hi,
i would try to reinstall DPM
Backup DB
uninstall DPM
Install DPM same Version like before
restore DPM DB
run dpmsync.exe -sync
finished
Seidl Michael | http://www.techguy.at |
twitter.com/techguyat | facebook.com/techguyat

Event based scheduler job - 2 events at the same time only 1 run

Hi,
i converted our dbms_job - jobs to the newer package dbms_scheduler.
It is a 10.2.0.4 patch 23(8609347) database on an windows server 2003 R2 Enterprise x64 Edition SP2.
The Jobs(about 130) are nothing special ... only some statistics, matview-refreshes and so on.
For the notification of failed jobs and jobs which run over the max_run_duration i downloaded and installed the job notification package.
The jobs are assigned to different departments and the corresponding developer teams in our company.
I created a notification job for each department and if a job fails we (the database administrators) and the corresponding deverlopers will be informed.
Now i ascertained that only 1 email will be send if 2 jobs of the same department fails at the same time.
The emailer-jobs are auto-generated by the job notification package. I only modified them to look after all jobs of special department and not only after one job. (--> event_condition ... object_name LIKE 'XXX%')
example for dba-jobs(copy of the script output of TOAD):
SYS.DBMS_SCHEDULER.CREATE_JOB
       job_name        => 'DBA_JOBS_EMAILER'
      ,start_date      => NULL
      ,event_condition => tab.user_data.object_name LIKE ''DBA%'' AND tab.user_data.event_type in (''JOB_FAILED'',''JOB_OVER_MAX_DUR'')'
      ,queue_spec      => 'SYS.SCHEDULER$_EVENT_QUEUE, JOB_FAILED_AGENT'
      ,end_date        => NULL
      ,program_name    => 'SYS.EMAIL_NOTIFICATION_PROGRAM'
      ,comments        => 'Auto-generated job to send email alerts for jobs "DBA%"'
    );I thought that a queue is used to manage all events from the scheduler jobs. So i made a test with 2 dba jobs and simulated a failure at the same time but i received only one mail.
So what is happend with the second event? I looked for the events in the qtab(SCHEDULER$_EVENT_QTAB) which belongs to the event queue(SYS.SCHEDULER$_EVENT_QUEUE) and no event was missing.
So i think the emailer job has to run 2 times.
Is anyone able to explain or to find my mistake?
I know that the easiest way is to create one emailer job for each normal job but i think this is a little bit costly because all the arguments are the same for one department.
Thanks & Regards

Thanks for your fast answer.
You are right with the "enabled => TRUE;" part and i only forgot to post it.
So the Job is enabled (otherwise it would not send any mail). Because it is sending one mail i think it is also not necessary to hand over a job_type.
Additionally the job starts a program ... so it is right to set the job_type='STORED_PROCEDURE' isn't it?
And also right ... i already added the agent as subscriber to the queue.
Anyway i think the whole thing do what it have to do. So in my oppinion there are no big mistakes in creating the job or at adding the subscriber.
There are also no problem in raising the events by itself and enqueue them in the scheduler event queue.
There is only a problem when 2 jobs fails (or run out ouf max duration) at exactly the same time.
If i understand it right:
The agent/subscriber will find the "JOB_FAILED"-event for the first Job in the queue and starts the emailer Job.
The agent will also find the "JOB_FAILED"-event for the second Job and wants to start the emailer Job again.
I don't know if this is really the problem but perhaps the emailer-job can not be started in consequence of the second event because ist is already running.
I also don't know if this is a mistake of the agent or of the emailer-job by itself.
I only want that it runs two times (one run for each event). I my case it also doesn't matter which email is send at first.

Oracle automatic statistics optimizer job is not running after full import

Hi All,
I did a full import in our QA database, import was successful, however GATHER_STATS_JOB is not running after sep 18 2010 though its enable and scheduled, i did query last_analyzed table to check and its confirmed that it didnt ran after sep18,2010.
Please refer below for the output
OWNER JOB_NAME ENABL STATE START_DATE END_DATE LAST_START_DATE NEXT_RUN_D
SYS GATHER_STATS_JOB TRUE SCHEDULED 18-09-2010 06:00:02
Oracle defined automatic optimizer statistics collection job
=======
SQL> select OWNER,JOB_NAME,STATUS,REQ_START_DATE,
to_char(ACTUAL_START_DATE, 'dd-mm-yyyy HH24:MI:SS') ACTUAL_START_DATE,RUN_DURATION
from dba_scheduler_job_run_details where
job_name='GATHER_STATS_JOB' order by ACTUAL_START_DATE asc; 2 3 4
OWNER JOB_NAME STATUS REQ_START_DATE ACTUAL_START_DATE
RUN_DURATION
SYS GATHER_STATS_JOB SUCCEEDED 16-09-2010 22:00:00
+000 00:00:22
SYS GATHER_STATS_JOB SUCCEEDED 17-09-2010 22:00:02
+000 00:00:18
SYS GATHER_STATS_JOB SUCCEEDED 18-09-2010 06:00:02
+000 00:00:26
What could be the reason for GATHER_STATS_JOB job not running although its set to auto
SQL> select dbms_stats.get_param('AUTOSTATS_TARGET') from dual;
DBMS_STATS.GET_PARAM('AUTOSTATS_TARGET')
AUTO
Does anybody has this kind of experience, please share
Apprecitate your responses
Regards
srh

?So basically you are saying is if none of the tables are changed then GATHER_STATS_JOB will not run, but i see tables are updated still the job is not running. I did >query dba_scheduler_jobs and the state of the job is true and scheduled. Please see my previous post on the output
Am i missing anything here, do i look for some parameters settings
So basically you are saying is if none of the tables are changed then GATHER_STATS_JOB will not run,GATHER_STATS_JOB will run and if there are any table in which there's a 10 percent change in data, it will gather statistics on that table. If no table data have changes less than 10 percent, it will not gather statistics.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/stats.htm#i41282
Hope this helps.
-Anantha

BI Publisher (Obiee 11g) Scheduled jobs start randomly after services restarting

Hi everybody,
I've a problem with scheduled jobs on BI Publisher that start randomly after server restarting.
For example if there's a job scheduled every day at 8.00 am it works fine until the server is not restarted but when I restart it next job running start at 9.28 am (it is an example because the real start time is very unpredictable).
In my case bi publisher is integrated with obiee 11g (11.1.1.6.2) and I've scheduled jobs with administrative user (weblogic). For this user I've set the Bi Publisher Preferences (report locale = Italiano-Italia, Report Time Zone = GMT +1:00) from obiee analytics user account preferencies.
Can anyone have this problem too and help me?
Thanks
Annalisa

These are not helpful. The first link is to OBIEE 10g and the second is just an install guide. I am having the same issue with BI Publisher returning java.lang.NullPointerException in OBIEE 11g. Any help would be appreciated. Thanks,
Paul
Edited by: pneedleman on Nov 17, 2010 10:15 AM

Run-after: handy command to schedule jobs easily

Similar Messages

Maybe you are looking for