OWB Scheduled job generates infrastructure problem..

Hi everyone,
I'm experincing a strange problem while scheduling a process flow using OWB schedule. The job is created and started fine. But the job throws up an exception of the kind 'Infrastructure Problem' etc when the machine is shut down after I start the job from the Control Center. The oracle enterprise manager shows that the job is scheduled and enabled after the job is started via the Control Center.
Can anyone suggest anything regarding this?
Thanks in advance.
Regards,
Sayantan

Hi Sayantan,
Which machine is being shut down, the design client? If so do you use the control center on that machine?
JP

Similar Messages

  • KM Scheduler job

    Hi
    I created several KM scheduler jobs.
    The problem is that they are running in the context of Guest user, and i could find any way to change this.
    Because of that when i try to call new InitialContext () for calling some remote ejbs i get caller not autorized.
    So does somebody know how i can change this?
    Florin

    hi,
    if you ejb connect to backend, you need to configure an service user who has authorized to call
    the rfc functions in R/3.
    Kind regards
    Ben.J.

  • Problem editing scheduled jobs

    I just had a problem where 3.1, EA1 and EA2 all failed to edit a scheduled job in sqldev. A coworker was able to make the same edit using the same database ID, except he did it through SQL*Plus - that made me suspect a bug in sqldev.
    Here are the symptoms:
    In sqldev 3.1 (any flavor) > Scheduler > Jobs > edit an existing job > try to edit the JOB_ACTION field. In 3.1, double-clicking in the field only highlights the current word - it does not give me a cursor, and I cannot edit the contents.
    In sqldev 3.0.4, editing the same job works as expected. I can edit the field, and save the changes.
    Note that the server that I connect to is remote - it is hosted by Oracle OnDemand.

    Doesn't work for me either;
    Here's the exception dumped in the console when selecting Edit:
    oracle.classloader.util.AnnotatedNoClassDefFoundError:
              Missing class: antlr.TokenStream
            Dependent class: org.antlr.stringtemplate.language.DefaultTemplateLexer
                     Loader: ide-global:11.1.1.0.0
                Code-Source: /C:/Archivos%20de%20programa/sqldeveloper3.1.06.82/sqldeveloper/lib/stringtemplate-3.1b1.jar
              Configuration: <classpath> in /file:/C:/Archivos de programa/sqldeveloper3.1.06.82/sqldeveloper/extensions/oracle.sqldeveloper.jar!/META-INF/extension
    .xml
    The missing class is not available from any code-source or loader in the system.
            at oracle.classloader.PolicyClassLoader.defineClass(PolicyClassLoader.java:2387)
            at oracle.classloader.PolicyClassLoader.findLocalClass(PolicyClassLoader.java:1546)
            at oracle.classloader.SearchPolicy$FindLocal.getClass(SearchPolicy.java:226)
            at oracle.classloader.SearchSequence.getClass(SearchSequence.java:119)
            at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoader.java:1728)
            at oracle.classloader.PolicyClassLoader.access$000(PolicyClassLoader.java:143)
            at oracle.classloader.PolicyClassLoader$LoadClassAction.run(PolicyClassLoader.java:331)
            at java.security.AccessController.doPrivileged(Native Method)
            at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1692)
            at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1674)
            at org.antlr.stringtemplate.StringTemplateGroup.<clinit>(Unknown Source)
            at oracle.dbtools.scheduler.generator.DBMSSchedulerCodeGenerator.initGroupLoader(DBMSSchedulerCodeGenerator.java:321)
            at oracle.dbtools.scheduler.generator.DBMSSchedulerCodeGenerator.<init>(DBMSSchedulerCodeGenerator.java:298)
            at oracle.dbtools.scheduler.generator.DBMSSchedulerCodeGenerator.getInstance(DBMSSchedulerCodeGenerator.java:309)
            at oracle.dbtools.scheduler.dialogs.newjob.NewJobCreateBase2$ListTask.getQuery(NewJobCreateBase2.java:94)
            at oracle.dbtools.raptor.backgroundTask.utils.DatabaseQueryTask.<init>(DatabaseQueryTask.java:62)
            at oracle.dbtools.raptor.backgroundTask.utils.DatabaseQueryTask.<init>(DatabaseQueryTask.java:48)
            at oracle.dbtools.scheduler.dialogs.newjob.NewJobCreateBase2$ListTask.<init>(NewJobCreateBase2.java:86)
            at oracle.dbtools.scheduler.dialogs.newjob.NewJobCreateBase2.getListTask(NewJobCreateBase2.java:58)
            at oracle.dbtools.scheduler.panels.common.ActionDialogBase.launch(ActionDialogBase.java:29)
            at oracle.dbtools.scheduler.dialogs.newjob.NewJobCreateBase2.launch(NewJobCreateBase2.java:81)
            at oracle.dbtools.raptor.controls.sqldialog.ObjectActionController.handleEvent(ObjectActionController.java:192)
            at oracle.ide.controller.IdeAction.performAction(IdeAction.java:529)
            at oracle.ide.controller.IdeAction.actionPerformedImpl(IdeAction.java:884)
            at oracle.ide.controller.IdeAction.actionPerformed(IdeAction.java:501)
            at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
            at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
            at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
            at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
            at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
            at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:809)
            at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:850)
            at java.awt.Component.processMouseEvent(Component.java:6289)
            at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
            at java.awt.Component.processEvent(Component.java:6054)
            at java.awt.Container.processEvent(Container.java:2041)
            at java.awt.Component.dispatchEventImpl(Component.java:4652)
            at java.awt.Container.dispatchEventImpl(Container.java:2099)
            at java.awt.Component.dispatchEvent(Component.java:4482)
            at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
            at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
            at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
            at java.awt.Container.dispatchEventImpl(Container.java:2085)
            at java.awt.Window.dispatchEventImpl(Window.java:2478)
            at java.awt.Component.dispatchEvent(Component.java:4482)
            at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:644)
            at java.awt.EventQueue.access$000(EventQueue.java:85)
            at java.awt.EventQueue$1.run(EventQueue.java:603)
            at java.awt.EventQueue$1.run(EventQueue.java:601)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
            at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
            at java.awt.EventQueue$2.run(EventQueue.java:617)
            at java.awt.EventQueue$2.run(EventQueue.java:615)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
            at java.awt.EventQueue.dispatchEvent(EventQueue.java:614)
            at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
            at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
            at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
            at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
            at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
            at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)And consecutive tries:
    java.lang.NoClassDefFoundError: Could not initialize class org.antlr.stringtemplate.StringTemplateGroup
            at oracle.dbtools.scheduler.generator.DBMSSchedulerCodeGenerator.initGroupLoader(DBMSSchedulerCodeGenerator.java:321)
            at oracle.dbtools.scheduler.generator.DBMSSchedulerCodeGenerator.<init>(DBMSSchedulerCodeGenerator.java:298)
            at oracle.dbtools.scheduler.generator.DBMSSchedulerCodeGenerator.getInstance(DBMSSchedulerCodeGenerator.java:309)
            at oracle.dbtools.scheduler.dialogs.newjob.NewJobCreateBase2$ListTask.getQuery(NewJobCreateBase2.java:94)
            at oracle.dbtools.raptor.backgroundTask.utils.DatabaseQueryTask.<init>(DatabaseQueryTask.java:62)
            at oracle.dbtools.raptor.backgroundTask.utils.DatabaseQueryTask.<init>(DatabaseQueryTask.java:48)
            at oracle.dbtools.scheduler.dialogs.newjob.NewJobCreateBase2$ListTask.<init>(NewJobCreateBase2.java:86)
            at oracle.dbtools.scheduler.dialogs.newjob.NewJobCreateBase2.getListTask(NewJobCreateBase2.java:58)
            at oracle.dbtools.scheduler.panels.common.ActionDialogBase.launch(ActionDialogBase.java:29)
            at oracle.dbtools.scheduler.dialogs.newjob.NewJobCreateBase2.launch(NewJobCreateBase2.java:81)
            at oracle.dbtools.raptor.controls.sqldialog.ObjectActionController.handleEvent(ObjectActionController.java:192)
            at oracle.ide.controller.IdeAction.performAction(IdeAction.java:529)
            at oracle.ide.controller.IdeAction.actionPerformedImpl(IdeAction.java:884)
            at oracle.ide.controller.IdeAction.actionPerformed(IdeAction.java:501)
            at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
            at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
            at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
            at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
            at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
            at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:809)
            at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:850)
            at java.awt.Component.processMouseEvent(Component.java:6289)
            at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
            at java.awt.Component.processEvent(Component.java:6054)
            at java.awt.Container.processEvent(Container.java:2041)
            at java.awt.Component.dispatchEventImpl(Component.java:4652)
            at java.awt.Container.dispatchEventImpl(Container.java:2099)
            at java.awt.Component.dispatchEvent(Component.java:4482)
            at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
            at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
            at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
            at java.awt.Container.dispatchEventImpl(Container.java:2085)
            at java.awt.Window.dispatchEventImpl(Window.java:2478)
            at java.awt.Component.dispatchEvent(Component.java:4482)
            at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:644)
            at java.awt.EventQueue.access$000(EventQueue.java:85)
            at java.awt.EventQueue$1.run(EventQueue.java:603)
            at java.awt.EventQueue$1.run(EventQueue.java:601)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
            at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
            at java.awt.EventQueue$2.run(EventQueue.java:617)
            at java.awt.EventQueue$2.run(EventQueue.java:615)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
            at java.awt.EventQueue.dispatchEvent(EventQueue.java:614)
            at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
            at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
            at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
            at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
            at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
            at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)Hope that helps for debugging,
    K.

  • Scheduling jobs in OWB 10.2

    I'm busy with a migration of OWB 10.1 to 10.2 and I had almost everything up and running
    except
    the scheduled jobs.
    In 10.1 my predecessors made scheduled jobs which started in their turn a procedure which then started the process flow with wb_rt_api_exec.
    After migration I could not get those jobs going anymore.
    After investigation I could see that the procedures (starting the proess flows) ran when started with the runtime rrepository owner as launcher.
    Even te jobs ran when they were started with the session credentials (iow the credentials from the logged on user being the runtime repository owner).
    I've seen the atricles telling that you need to set the preferred credentials to the runtime repository owner in oem if you want to get it running from there.
    Anyhow I could start it by recreating the jobs with the runtime repository owner as the creator.
    Doens anybody know why it could run in owb 10.1 with sys as creator and why it nn longer works in 10.2.
    I checked the 10.1 installation and I haven't found any priviileges granted to sys that where not granted in the 10.2 installation, so there is no diff.
    Any help would be welcome.

    Hi,
    You cannot schedule direct mapping. You need create Process flow then u need to attach calendar for that. Go to Control Centre Deploy process flow and schedule and further click on start.
    Regards,
    Ava

  • Stopping a scheduled job in OWB

    I need to re-deploy a scheduled job and cannot do so because the job is running. How do I stop the job from the OWB control center (or elsewhere)?
    Thanks,
    Dave

    Hi,
    I don't know if there is an easier way but this should work:
    1. run the script list_requests.sql (it should exist inside your owb home at owb\rtp\sql) using the workspace name as parameter
    2. the job should be listed on the EXECUTIONS section
    3. run the script deactivate_execution (same location as list_requests.sql) passing the audit_id and your workspace as parameteres
    Regards,
    Bruno

  • OWB 11g  Control Centre, Want to Remove Schedule Jobs list

    I am having a problem to deleting the list of Schedule Jobs in Control Centre which are not required any more. The Schedule has been disabled but unable to remove them from control centre, How we can achieve that.
    Thanks

    Hi,
    the first remove sheduled records from target database via deployment with Deploy Action = Drop.
    Then clear (unset) configuration property Referred Calendar on mapping/processflow (corresponding to scheduled job) - click on checkbos None.
    Usually job has name in format <object name>_JOB (where <object name> - name of scheduled mapping or processflow)
    Regards,
    Oleg

  • Problem with variable in scheduled job

    I'm trying to get the following scheduled job to run:
    switch(config)# scheduler job name backup_job
    switch(config-job)# cli var name timestamp $(TIMESTAMP) ; copy running-config bootflash:/$(SWITCHNAME)-cfg.$(timestamp) ; copy bootflash:/$(SWITCHNAME)-cfg.$(timestamp) tftp://1.2.3.4/
    switch(config-job)# exit
    switch(config)# scheduler schedule name backup_timetable
    switch(config-schedule)# job name backup_job
    switch(config-schedule)# time daily 1:23
    switch(config-schedule)# exit
    switch(config)# exit
    This job is taken directly from multiple Cisco MDS and Nexus documents. From what I can tell, the purpose of this job is to save the running configuration to a file on bootflash with date & time in the file name and then to copy the file from bootflash to tftp server.
    I can create the job and schedule successfully:
    switch(config)#show scheduler job name backup_job
    Job Name: backup_job
    cli var name timestamp $(TIMESTAMP)
    copy running-config bootflash:/$(SWITCHNAME)-cfg.$(timestamp)
    copy bootflash:/$(SWITCHNAME)-cfg.$(timestamp) tftp://1.2.3.4
    ==============================================================================
    switch(config)#show scheduler schedule name backup_timetable
    Schedule Name       : backup_timetable
    User Name           : admin
    Schedule Type       : Run every day at 10 Hrs 48 Mins
    Last Execution Time : Tue Mar  6 10:48:00 2012
    Last Completion Time: Tue Mar  6 10:48:00 2012
    Execution count     : 1
         Job Name            Last Execution Status
    backup_job                        Success (0)
    ==============================================================================
    The scheduled job runs successfully but the files that are created have the variable $(TIMESTAMP) in the file name instead of the actual date and time e.g. switch-cfg.$(TIMESTAMP)
    The logfile contains the following:
    Schedule Name  : backup_timetable                  User Name : admin
    Completion time: Tue Mar  6 10:59:26 2012
    --------------------------------- Job Output ---------------------------------
    `cli var name timestamp $(TIMESTAMP)`
    `copy running-config bootflash:/PEN-9509-2-cfg.$(TIMESTAMP) `
    Copy complete, now saving to disk (please wait)...
    `copy bootflash:/PEN-9509-2-cfg.$(TIMESTAMP) tftp://1.2.3.4 `
    Trying to connect to tftp server......
    Connection to server Established. Copying Started.....
    It looks to me that the $(timestamp) variable is being created successfully and is being replaced with the $(TIMESTAMP) variable but this is not being replaced with the actual date and time.
    The thing I don't get is that this looks to me that we're trying to nest variables and the same Cisco documents from which I get this configuration also state that nested variables are not allowed.
    I have tried this on different hardware - MDS9500, MDS9100, Nexus 5000, Nexus 7000 and different software - SAN-OS 3.3, NX-OS 4.1, NX-OS 5.2 but cannot get it to work. I have also tried to put the commands in a script and run with the run-script command but it still does not work.
    There is probably another method to achieve what this configuration is trying to achieve (and I would like to know if there is) but I want to know if this particular configuration will work.
    Can anyone tell me if they have got this working or can see what I'm doing wrong or can try running this in a lab please?

    I managed to get this resolved with a bit of a workaround. If I put the copy commands in a script and pass the variable to the run-script command as part of the scheduled job then it works ok. Trying to create the variable within the script (or as a separate scheduled job command) still doesn’t work.
    So, creating a script file (script) as follows:
    copy running-config bootflash:/$(SWITCHNAME)-cfg.$(timestamp)
    copy bootflash:/$(SWITCHNAME)-cfg.$(timestamp) tftp://1.2.3.4
    and creating a scheduled job with the following command:
    run-script bootflash:script timestamp=”$(TIMESTAMP)”
    achieves the desired result.

  • Schedule Job Execution problem

    Hi All,
    The schedule jobs are taking more time.... to complete
    We have schdule jobs which will run for every hour,soo to execute the job sometimes it is taking 1hr and sometime 30mins
    please help me to have the Job execution total time to be constant to near 30mins.

    preethi wrote:
    Hi All,
    The schedule jobs are taking more time.... to complete
    We have schdule jobs which will run for every hour,soo to execute the job sometimes it is taking 1hr and sometime 30mins
    please help me to have the Job execution total time to be constant to near 30mins.Thread: HOW TO: Post a SQL statement tuning request - template posting
    HOW TO: Post a SQL statement tuning request - template posting

  • Problem in Date info at scheduling jobs....

    Hi...
    I have defined a materialized view ..
    create materialized view mv_ekkrem_vlavon
      build immediate
      refresh on demand
      as
    select distinct seq_code_eidos .....I want to create a scheduled job using the DBMS_SCHEDULER which will refresh this materialized view ... doing a full refresh of its contents....
    so....i following the following steps...-connected as sys:
    begin
      dbms_scheduler.drop_job('mv_ekkrem_vlavon_job');
    end;
    begin
      dbms_scheduler.drop_schedule('mv_ekkrem_vlavon');
    end;
    begin
    dbms_scheduler.create_schedule
    ('mv_ekkrem_vlavon','15/08/2007 17:20:00','FREQ=DAILY;INTERVAL=1');
    end;
    exec dbms_scheduler.create_job(job_name=>'mv_ekkrem_vlavon_job',schedule_name=>'mv_ekkrem_vlavon',job_type=>'PLSQL_BLOCK',job_action=> 'BEGIN dbms_mview.refresh(''mv_ekkrem_vlavon''); END;');
    exec dbms_scheduler.enable('mv_ekkrem_vlavon_job');However , after 17:20:00 local time (db time) the mv refresh did not take place....
    Trying to find out what may be the reason... i issued the following command:
    SQL> select job_name,schedule_name,start_date,repeat_interval,last_start_date,next_run_date from dba_scheduler_jobs
      2  where job_name='MV_EKKREM_VLAVON_JOB';
    JOB_NAME                       SCHEDULE_NAME                                                                    START_DATE                                                                       REPEAT_INTERVAL                                                                  LAST_START_DATE                                                                  NEXT_RUN_DATE
    MV_EKKREM_VLAVON_JOB           MV_EKKREM_VLAVON                                                                 15/08/20 07:17:20,000000 +03:00                                                                                                                                                                                                                    15/08/20 07:17:20,000000 +03:00and issuing the command:
    SQL> select to_char(NEXT_RUN_DATE,'dd/mm/rrrr hh24:mi') from dba_scheduler_jobs where job_name='MV_EKKREM_VLAVON_JOB';
    TO_CHAR(NEXT_RUN_DATE,'DD/MM/R
    15/08/2020 07:17
    SQL> Select to_char(START_DATE,'dd/mm/rrrr hh24:mi') from dba_scheduler_jobs where job_name='MV_EKKREM_VLAVON_JOB'
    2 /
    TO_CHAR(START_DATE,'DD/MM/RRRR
    15/08/2020 07:17
    Can you find out which is the error in the job definition...????
    Needless to write that i use Oracle Db10g.
    Many thanks,
    Simon

    Hi,
    The repeat_interval gets its timezone from the start_date parameter so if you want the job to run every 9am in a particular timezone XXX you would need to do something like
    START_DATE => SYSTIMESTAMP at time zone 'XXX',
    REPEAT_INTERVAL => 'FREQ=DAILY; BYHOUR=9;byminute=0;bysecond=0',
    XXX can be something like -2:00 or a named time zone.
    There is a dedicated dbms_scheduler forum at
    Scheduler
    Hope this helps,
    Ravi.

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

  • Control Center status running scheduled jobs stops when DB is shutdown

    I have scheduled jobs in the Control Center of OWB, and the status is "Running" (Green Arrow ->), but everytime we stop and start the database I have to start the schedule job again under Status.
    Is there any way to fix this so that when the database stops and restarts somebody does not have to go into the Control Center and restart the jobs that are scheduled?
    Thanks

    I'm been told that it's a bug in the current version of OWB and to fix this problem we should upgrade to 10.2.0.3.

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

  • Empty "scheduled jobs" list in control center

    Hi all,
    due to a move to a new data warehouse environment i added a new configuration
    to my OWB project with new locations, control center etc.
    I was able to deploy and run all of the owb stuff into the new environment except all
    the scheduled jobs to deploy into OEM,
    which owb generates for all the process flows that have a schedule assigned ("Referred Calendar" in Configuration).
    The list of "Scheduled Jobs" in control center for the target location just appears empty.
    Are there any additional settings or privileges missings,
    i.e. for target location, owb repository owner, configuration, location, ...?
    Old env is Oracle DB 10.2.0.2 on Win Server 2003 32 bit, Workflow Server 2.6.4, OWB Client 10.2.0.1.31, OWB-Repository 10.2.0.1.0.
    New env is Oracle DB 10.2.0.2 on Redhat 64 bit, Workflow Server 2.6.4, OWB Client 10.2.0.1.31, OWB-Repository 10.2.0.1.0.
    Any hints would be appreciated.
    Thanks,
    Matthias

    Hi,
    I found out that I have to create a new schedule module.
    In the create module wizard you'll have to define a location where schedules
    are deployed to and there I defined the new target location.
    It is not possible to assign different deployment locations for same schedule
    module in each configuration.
    I don't know if it is a bug or a feature, but with the new seperate schedule module
    it works.
    Just to let you know,
    Matthias

  • Scheduled job doesn't appear in Control center

    Hi,
    I am facing a strange problem. I installed OWB 10g R2 and I have my target and source both on Oracle 10g DB. I created lots of mappings, and when it came to scheduling them, I installed Oracle Workflow.
    In any of the OWB documents, nowhere it is specified that if OWB is already installed and Oracle Workflow Server is installed later, what are the steps to link them.
    Then I created a schedule and spplied them to the mapping by editing its configurations. Then as per documents I checked in Control center. But, there was no job created and so didnt appear there.
    I am wondering what can be the reason for this. I simply didn't get any documentation that tells that, what if the scheduled job doesn't get created? or how do you check from OWB whether the Oracel Workflow is properly working?
    Please provide a clue!
    Thanks
    Goga

    Means it cannot detect any airplay devices.

  • How to remove scheduled jobs from Control Center?

    Hi,
    My control center shows a bunch of jobs in the "scheduled" tab that no longer exist.
    They do not exist in Control Center and they also do not exist in the Design Center anymore.
    Is there a way I can delete entries from the list of schedule jobs?
    I am on OWB 10gR2
    Thanks,
    Sam
    PS, I saw this thread that talks about my problem. However the solution provided seems to only work if the jobs still exist
    in your control and design centers.
    OWB 11g  Control Centre, Want to Remove Schedule Jobs list

    Could it be that some process flows are still attached to a schedule? Perhaps you've made a copy of a Process Flow?

Maybe you are looking for