Scheduled Job - clock/time change miscalc

Following the clock change at the weekend for British Summer Time (GMT + 1hr) the Process Flow to run our OWB schedule has the next run date as 30 October 2011!
Usually the schedule runs every 2 hours between 06:00 and 18:00 every day, the last successful run was 18:00 on Saturday.
Versions are OWB 10.2.0.3.33 and Oracle 10.2.0.3.
Is this a known bug, any workaround to avoid in future?
Regards
Si

Hi,
Yes, its normal since the schedule discovery setting is different from Ad hoc discovery settings.
Explanation :- Ad hoc discovery gives you the option to check the discovery of the network devices on ad hoc basisi and if you like it, then you can get this settings implemented in the schedule discovery too by using the same settings in schedule discovery.
Similary you can check and run different schedule discovery, that means using different options you can run different schedule discovery and then finally select the one which suits as per your network requirements.
Hope it helps,
Many Thanks,
Gaganjeet

Similar Messages

  • Clock time changes with switch reload

    Hi...
    I am facing problem of Clock time modifies to 1st March whicle 2900 series or 3500xl switches reloads.My IOS is c2950-c3h2s-mz.120-5.3.WC.1.I need to set the clock again every time it reload or poercycled.We have 173 Switches installed in Campus Area Network.It is difficult to check time & change it for every switch.Kidly suggest me solution.
    With regards,
    Shailen Mehta

    Hi Shailen
    Would suggest to go for secured NTP configuration in ur catalyst switches to avoid reentering the time after every reset.
    do have a look into this link which will take you to configure NTP in ur boxes
    http://www.cisco.com/en/US/products/hw/switches/ps628/products_configuration_guide_chapter09186a008007e8bf.html#xtocid13
    regds

  • Database job execution time changing

    Hello,
    I created a job to execute every 15 minutes. What I have noticed is it is not getting executed every 15 minutes, instead period is increasing over 1 or 2 minutes.
    Here is my code for job, is it because of seconds it is making the difference?
    DECLARE
    X NUMBER;
    BEGIN
    SYS.DBMS_JOB.SUBMIT
    ( job => X
    ,what => 'myproc'
    ,next_date => to_date('20/08/2006 07:34:10','dd/mm/yyyy hh24:mi:ss')
    ,interval => 'sysdate+30/2750'
    ,no_parse => TRUE
    END;
    /

    You need to use date functions that evaluate to a FIXED time in the future (see AskTom for further explanation: http://asktom.oracle.com/pls/ask/f?p=4950:8:9447876042389067866::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:13317229864022)
    The preferred method would be to create custom-built function that returns the required interval. The function can use hard-coded logic (like the example below) or it can read from simple "repository" (set of tables with job schedules, maintenance windows etc.).
    Example:
    1) Create next_date function
    CREATE OR REPLACE FUNCTION next_date
    RETURN DATE IS
    v_date_portion_1 VARCHAR2(16);
    v_date_portion_2 PLS_INTEGER;
    v_date_portion_3 PLS_INTEGER;
    v_next_date DATE;
    BEGIN
    v_date_portion_1 := TO_CHAR(sysdate, 'dd.mm.yyyy');
    v_date_portion_2 := TO_CHAR(sysdate, 'hh24');
    v_date_portion_3 := TO_NUMBER(TO_CHAR(sysdate, 'mi'));
    v_next_date:= TO_DATE(v_date_portion_1||' '||
    (CASE
    WHEN v_date_portion_3 < 15 THEN TO_CHAR(v_date_portion_2)||':'||'15'
    WHEN v_date_portion_3 >= 15 AND
    v_date_portion_3 < 30 THEN TO_CHAR(v_date_portion_2)||':'||'30'
    WHEN v_date_portion_3 >= 30 AND
    v_date_portion_3 < 45 THEN TO_CHAR(v_date_portion_2)||':'||'45'
    ELSE TO_CHAR(v_date_portion_2 + 1)||':'||'00'
    END), 'dd.mm.yyyy hh24:mi');
    RETURN v_next_date;
    END next_date;
    2) Change interval
    BEGIN
    DBMS_JOB.CHANGE(<your_job>,
    null,
         null,
         interval=>'next_date');
    END;

  • SCHEDULING JOB@ DEFINED TIMES

    Hi i am venkatesh, i want a help regarding batch jobs, currently i am using Orcale db connect for data source to SAP-BI metadata, i want to daily load operational datas to BI how to find from oracledb whether correct data is loaded to Metadata of BI how and to check since no delta update mechanism is available as for as DB connector is conecrned. How to overcome this problem.
    valuable contribution is highly apreciated

    You put the condition in the Infopackage. Use the ABAP routine in infopackage selection tab,
    Something like this:
    form compute_BUDAT
      tables l_t_range structure rssdlrange
      changing p_subrc like sy-subrc.
          Insert source code to current selection field
    $$ begin of routine - insert your code only below this line        -
    data: l_idx like sy-tabix.
              read table l_t_range with key
                   fieldname = 'BUDAT'.
              l_idx = sy-tabix.
            Set the date selection (Today)
              l_t_range-sign   = 'I'
              l_t_range-option = 'EQ'
              l_t_range-low    = sy-datum.
              modify l_t_range index l_idx.
              p_subrc = 0.
    $$ end of routine - insert your code only before this line         -
    endform.
    Remember: The field "BUDAT" must be set as Selection on datasource, then you can see in your infopackage
    ORACLE SIDE:
    On the Oracle, your table need to be updated in some field to indicate the "Delta":
    First load to BW - FULL UPDATE INFOPACKAGE.
    DATE         CUSTOMER    VALUE     CHANGE_DATE
    01/01/2005   CUSTAAAA    10,00       "Blank"
    01/01/2005   CUSTBBBB    20,00       "Blank"
    01/01/2005   CUSTCCCC    30,00       "Blank"
    01/01/2005   CUSTDDDD    40,00       "Blank"
    Another day, only records created and changed will be loaded:
    DATE         CUSTOMER    VALUE     CHANGE_DATE
    01/01/2005   CUSTAAAA    15,00      02/01/2005 - BW
    01/01/2005   CUSTBBBB    20,00       "Blank"
    01/01/2005   CUSTCCCC    30,00       "Blank"
    01/01/2005   CUSTDDDD    40,00       "Blank"
    02/01/2005   CUSTEEEE    11,00      02/01/2005 - BW
    Only 2 records will be upload with the  DELTA UPDATE INFOPACKAGE.
    Sorry about my English, if you need to contact me, please send me a mail ([email protected]) and I will try to send you a Word with Steps.

  • How to get status of last execution of a scheduler job

    Hi,
    I am trying to write a pl/sql code that can manually the scheduler job (one time type/ not a repetitive) which are in retry scheduled state.
    even after execution is successfull job is not dropped even if i set auto_drop to true.
    I need some way to capture execution status of dbms_scheduler.run_job('job_name');. based on which i can manually drop the job if it is successfull.
    taking the value from dba_scheduler_job_run_details doesn't seem to be good option as there may be multiple logs and we don't what time interval we need to match.
    can anybody help me in this.
    Thanks in advance.

    Hi,
    I'm a little confused at what is happening. It sounds like the following is the case
    - You have created a run-once job and set restartable to TRUE and auto-drop to TRUE. It has failed a few times and is now in the RETRY SCHEDULED STATE .
    - Now you have fixed the issue and want to force a rerun and drop the job if it has succeeded.
    If this is the case you have several options.
    - just wait until the job has retried itself, you can see the next scheduled date in the dba_scheduler_jobs view
    - use dbms_scheduler.run_job(use_current_session=>false) . You will have to monitor dba_scheduler_job_run_details to see the status of the job run but you can easily use log_date to figure out which row is your row. Just select the row with log_date > sysdate when you called run_job. If that run succeeds, you will manually need to call drop_job.
    - use dbms_scheduler.run_job(use_current_session=>true) . Because this runs the job action in the foreground it will hang until the job action has finished. Any error will be thrown as a foreground PL/SQL error. If there is no error, the action has succeeded and you can go ahead and do a drop_job.
    Hope this helps,
    Ravi.

  • Clock/time incorrect after upgrade to bootcamp 5 running windows 8-64

    Since I did the upgrade to bootcamp 5 running windows 8-64, (which solved all the previous problems), the clock/time changes by itself to be off by hours frequently throughout the day.

    I'd suggest you upgrade to OSB10.4.0.1.0 release.
    Webtool taking ages is probably related to some other OS issue, check /var/log/messages and whatever and check your DNS settings are all correct.
    What about obtool commands, are they also slow?
    Thanks
    Rich

  • Dynamically Set date not changing in schedule Job

    Hi,
    I have created a report with "Order Date" as one of the parameters on the selection screen. I have created a variant, say 'X' , to set this date parameter dynamiccaly as "Current date - 31 days".
    I have scheduled this program to run in background with the 'X' variant daily at certain time.
    Now, for the day on which I created this job , the Order Date is set to correct date . For ex if I am scheduling the job tdy it will be set to 06/10/08. However, for next day , that is tom this date is not getting changed. i.e Tommorrow again Order date is 06/10/08 but it should have been 07/10/08.
    So basically this dynamically set date is not chaning in the scheduled job.
    Any idea why this is happening and what is the corrective measure for this.
    Thanks!

    There is an INITIALIZATION event in the program.......
    Do the processing your date in that event only....
    for ex....
    select-options: date for order-date.
    INITIALIZATION.
    date-low = sy-datum or wat ever.
    Thanks
    Saurabh

  • IdM Scheduler and Time Change to Daylight Savings Time GMT to BST

    This isn't really a 'question' , but just a topic for discussion.
    We're not live yet, but will be by the time the clocks go back. So I'm just interest to hear everyone's experiences and any issues with regards to the switching to / from DST
    I did some "interesting" (or not) tests last night to see what happens with Pending Values which are due to take effect at the time change threshold of 01:00 GMT when switching to Daylight Savings Time (BST) GMT +0100.
    It seems as if the IdM scheduler keeps going according to UTC or GMT. However any values provisioned to target systems or to local tables using the ddm.datetime8601 system variable are in local time according to the runtime server or SQL server's locale settings.
    I set up a task to output from a javascript the current system date
    using the following in the functions.
    currentTime = new Date();
    return currentTime.toString(); // returns Locale Time String
    currentTime = new Date();
    return currentTime.toUTCString(); // returns UTC Time String
    in the same pass I also output the ddm.datetime8601 system parameter and the ddm.time24 system parameter.
    This task was to update a comment on an entry and Scheduled to run at 00:00:00 and was executed at 00:00:06 GMT all times were still in GMT as expected.
    Local Time: Sun Mar 27 00:00:06 GMT-0000 (GMT) 2011, UTC Time: Sun, 27 Mar 2011 00:00:06 GMT, ddm.datetime8601: 2011-03-27T00:00:06, ddm.time24: 00:00:06
    This task was scheduled at 01:00:00 in IdM and was exectued at 01:00:08 GMT by the runtime, and you can see the local time is being correctly reported as 02:00:08 BST. Note also the ddmdatetime8061 is also 02:00:08 i.e. BST.
    Local Time: Sun Mar 27 02:00:08 GMT+0100 (BST) 2011, UTC Time: Sun, 27 Mar 2011 01:00:08 GMT, ddm.datetime8601: 2011-03-27T02:00:08, ddm.time24: 02:00:08
    In the database the entry values MXI_VALUES ModifyTime field has the GMT / UTC timestamp.
    I also set up some pending value objects to be applied at 00:59:59 and 01:30:00 to see if the 01:30:00 would be 'skipped' as the locl clock change would've gone from 00:59:59 to 02:00:00. Well the pending values were correctly applied and expired and no 'lost' transactions happened as a result of the change.
    So essentially it seems to me that the IdM runtime and scheduler times are all based on UTC / GMT.
    I guess it's only an issue twice a year if you're expecting something to happen at a specific local time 01:00:00 or if you've got a global user base and their account expiry should be in each user's own country's local time. In these cases, it would seem that you'd need to convert the schedule times and pending value times to UTC first before setting them in the database.
    Has anyone else had any issues, thoughts, questions or suggestioins on scheduling tasks which span the DST time change when switching to and from Daylight Savings Time.
    Edited by: Paul Abrahamson on Mar 27, 2011 10:51 AM

    Read here:
    http://www.appleinsider.com/articles/10/10/11/applesays_ios_software_update_to_fix_pesky_alarm_clockbug.html

  • How to schedule a job occurring time for 1 1/2 hour in sql server

    how to schedule a job occurring time for 1 1/2 hour in sql server

    Hi,
    This is a known issue in the previous SQL Server version and has been fixed in SQL Server 2012. You should be able to set 90 minutes and the change would be saved in SQL Server 2012.
    http://connect.microsoft.com/SQLServer/feedback/details/346786/ssms-does-not-support-job-schedule-frequencies-greater-than-60-minutes
    Currently, you may schedule the job to occur every 1 hour or you may refer to the suggestion by Latheesh to get around this.
    Thank you for your understanding.
    Tracy Cai
    TechNet Community Support

  • Change print recipient in scheduled jobs (SM37)

    Is it possible to change the print recipient in multiple scheduled jobs (SM37) at the same time?
    Thanks,
    Mark

    You have to change it manually one by one... it is not possible to change it in a multiple jobs at a same time.

  • 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.

  • 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.

  • Random Clock Time and Date Changes

    My clock time and date changes randomly. I have reset the iPhone and updated its software but it still changes. Can anyone help?

    That just happened to me too! It started yesterday April 27 and did it today too. I think it changes around like 1pm-1:15pm. In order to get it to change back to the right time, I just turn off my phone then turn it back on. But that doesn't fix the problem. I don't know why its doing this! :[

  • Changing the job priority of scheduled job

    Hi gurus,
           Please let me know how to change the priority of a already scheduled job.I mean to say if a job is scheduled with priority A,now i want to change it to some B or C .How can i do that.Please guide in step wise.....
    Thanks in advance.
    Regards,
    Rakesh.

    A little tip which might help you in future: If the user only has the authority for object S_BTCH_JOB and not S_BTCH_ADM... then they will only ever be able to schedule class "C" jobs.
    When you trace or debug SM37, do not be mislead by the check on S_BTCH_ADM... the user does not need it with the correct S_BTCH_JOB authority. It is only being checked to over-ride the S_BTCH_JOB authority for admins!
    Cheers,
    Julius

  • How to change userid/owner of scheduled jobs

    I can see the 'userid' of the scheduled jobs using sm37.
    This are the BASIS jobs setup during installation/upgrade last year.
    I would like to reassign the userid of to my own userid...as the consultand userid no longer exists.
    Please advise
    Maria

    hi,
    T code SU01 and give user name which u want 2 create and then click on create option.......
    enter the reqired field.... save
    as u enter the client using ur user id and then system will ask 2 give ur new password...
    if useful assign points...
    regards,
    santosh kumar

Maybe you are looking for