Schedule job don't start

Hi Gurus, for last 2 days, no Jobs are being started in my BI system.
Whenever I schedule or start any job.. it says job started..
But when I check in SM37, I find the start column empty. And the delay(secs) column has the number of seconds increasing.
It goes 500 or even more.. The job actually never get started.
What might be the problem ??
Is it regarding any space issue ?
Have anyone of you faced this problem ?
Please help, Akash

Not sure what those jobs are
You can actually do "Cancel Without Core" but better talk to BASIS and figure out whats happening.

Similar Messages

Sdccn - scheduled jobs don't start

i have scheduled several tasks in the sdccn. but there don't start at the scheduled timed.
is there a backup tasks which must run?

André Smoktun wrote:
> i have scheduled several tasks in the sdccn. but there don't start at the scheduled timed.
> is there a backup tasks which must run?
Check in SM37, whether the task processor job is executed successfully periodically (every hour).
This job executes all tasks, which are due.
Job name /BDL/TASK_PROCESSOR
corresponing report: /BDL/TASK_SCHEDULER
Check scheduling via SDCCN, Settings -> Task processor.
Best regards,
Ruediger

All timer jobs don't start (paused in check job status)

Hello,
Some bad things have happend to our SharePoint Server 2010. All timer jobs suddenly stopped running. The last time they ran successfully was 09/26/11. Since that time all jobs have been scheduled to run according to their schedule but don't actually run.
In the Check Job Status view there is a list of jobs scheduled to run 09/26/11 which are currently paused for some reasons, other jobs don't run at all.
Is it possible to unpause these jobs and let other jobs to run? Any ideas would be very much apprecaited. Thank you in advance.

Hi,
Thanks for your post.
Pausable Timer Jobs
You can now create pausable timer jobs. This is done by inheriting from the
SPPausableJobDefinition and overriding Execute(SPJobState) instead of
Execute(Guid). You can then use the current job state (SPJobState) to store values which are retrieved when the job is resumed.
Running jobs on all content databases
Another new timer job derivative type is the SPContentDatabaseJobDefinition.This is a timer job specifically made to perform actions on content databases. The timer job is distributed on the WFE servers and each content database is only
processed by one job. Override the Execute(SPContentDatabase, SPJobState) to add your own processing. The job supports pausing.
Running jobs on all Site Collections
A really interesting new timer job type is the SPAllSitesJobDefinition. This one is derived from the SPContentDatabaseJobDefinition and has a method called
ProcessSite(SPSite, SPJobState) which you override to process the SPSite object. This could be very useful to build site inventories/directories.
Running job on a specific server
The SPServerJobDefinition is a pausable timer job that is designed to be targeted to a specific server (SPServer).
Running jobs for specific services
The SPServiceJobDefinition is another pausable timer job that runs a job on all servers where a specific
SPService has been provisioned. A very similar job is the
SPFirstAvailableServiceJobDefinition which runs the job on the first available server which has a specific SPService installed. If you would like to run a job an all servers you can easily use SPServiceJobDefinition. Then use the timer job service
(which is installed on all servers, except dedicated database servers) and pass
SPFarm.Local.TimerService as the SPService parameter in the constructor.
All of the new specific timer jobs are essentially smart derivatives of the SPJobDefinition but using these new abstract classes will certainly save you some time when you need to target your timer jobs.
I hope that helps.

Scheduled backups don't start.

I have to launch them manually.
What can I do?
Thank you!

A bit more details would definitely help.
What happens? Is there an error?
Does anything appear in /Applications/Utilities/Console.app>"All Messages"?
What format is the disk (select it and press ⌘+I). What partition table? (check by opening /Applications/Utilities/Disk Utility.app, selecting the disk that has a manufacturer's name and size, and looking in the bottom right.)
Report back those details, and then we'll be able to help you.
Good luck!
Message was edited by: joshz

Executing Scheduled jobs via Control Centre

Hello Forum,
We have a question on the scheduled jobs in OWB. We have some process flows that are attached to some (corresponding) schedules. Now in the Control Centre, we have two options to get the scheduled jobs executed:
1. We can have the scheduled jobs deployed, but not started, in which case the scheduled jobs would run as our Repository Owner (say OWB).
2. We can have the scheduled jobs deployed AND started, in which case the scheduled jobs would run as OWF (Oracle Workflow User).
(Just to clarify - by "starting" a scheduled job we mean that we make use of the "Start" option available in the right-click menu for every scheduled job that appears under the "Scheduled Jobs" node in the Control Centre.)
We would like to understand what is the advantage/disadvantage of setting up the scheduled jobs (for execution) for the two cases described above.
Any help is much appreciated.
Best Regards,
Piyush
For reference, following is our environment info:
OWB Client Version - 10.2.0.1.31
Repository Version - 10.2.0.1.0
Database Version - 10.2.0.3.0
OWF Version - 2.6.4
-----------------------------------------------------------------------------------------

Hi Sam,
Thanks a lot for your kind inputs. Well the situation that I have at hand is that when I don't "start" the schedules (as in Case 1. described in my earlier post), everything goes fine. However, if I "start" the schedules jobs (as in Case 2. described in my earlier post), the scheduled jobs failed to execute after DB restart. So I feel we are better off by not starting the scheduled jobs so as to make them run as our target workflow user.
Do you think this is the right approach for executing the scheduled jobs?
Best Regards,
Piyush

How to create schedule job and event trigger in XI to start a ABAP program?

Dear All:
Here are what i need to do:
1.To run a ABAP program to start an XI scenario per hour.
2.To run a ABAP program to start an XI scenario per day at 6 PM.
3.To run a ABAP program used event trigger to make sure that XI scenario has finished the process and after that wait for 10 min later and run again.
only i know is used sm36 & sm37 to set up a schedule job.
but what i don't know is how to do it step by step.
especially point 3.
are there any step by step example can show me how?
it better be simple and details...
thanks you all
Regards
Jack Lee

Hi,
If you want to trigger the event manually from within SAP, use transaction
SM64
in SAP this is done by scheduling a job
once a new customer is entered
your scheduled report sends customer master data
you can schedule your report (TCODE - BD12 I think) to one day or every 5 minutes... it depend on your needs and the system performence
Regards,
Surya

All scheduled jobs started suddenly to fail with ORA-01031: insufficient pr

I have a setup of gridcontrol 11g on windows 2008. I've been running successful for weeks until the other day when all my scheduled jobs started to fail with
ORA-01031: insufficient privileges (rman jobs)
ERROR: Invalid username and/or password (sql scripts).
I verified for the accounts being locked, pw correct, expired / grace period, etc.
all good when I try from the command line. running an rman backup from the command line works great, but the same one through the job scheduler fails with ORA-01031.
I've dropped the jobs completely, recreated them again. same thing.
I'm using preferred credentials and dropped and recreated them. same thing.
I don't know where else to look. Only grid control scheduled jobs fail, but all of them do.
I'm using SQLNET.AUTHENTICATION_SERVICES= (NTS) in my sql.ne (always have).
we use a windows domain server / domain authentication for logging into boxes. I haven't changed any of my passwords.
I am probably looking in the wrong places. Anybody able to help?

Hi,
ERROR: Invalid username and/or password (sql scripts).This error message clearly tells that password is incorrect and "insufficient privileges" shows that perhaps you are using SYS user for running the jobs and password for user SYS is incorrect.
If you are specifying passwords in your scripts, i don't think you need to set preferred credentials.
Try following
1) Remove preferred credentials
2) Don't check password of user sys by locally logging in (because if Os authentication is on, even wrong password will allow you loging into the database and you will think that password is correct). Try connecting database using SYS user from a remote machine and check whether it accepts your password and make sure you have same password for your jobs and in sql scripts
3) If still problem, just for test, remove SQLNET.AUTHENTICATION_SERVICES= (NTS) and try
Salman

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

Request vs Actual Start Date in Scheduler Jobs

Hi, I want to run a PL/SQL block, all days, at 1:00 AM
I've defined the following scheduler job, in a new (and empty) Job Class:

SQL> select job_name, repeat_interval, job_class, job_priority from dba_scheduler_jobs where job_class = 'MY_NOCHE_JOB_CLASS';
JOB_NAME...........: UNIFICA_CLIENTES
REPEAT_INTERVAL....: FREQ=DAILY;BYHOUR=1;BYMINUTE=0;BYSECOND=0
JOB_CLASS..........: MY_NOCHE_JOB_CLASS
JOB_PRIORITY.......: 1

However, the process is starting later, for example:

Request Start Date....: Nov 10, 2010 1:00:00 AM -02:00
Actual Start Date.....: Nov 10, 2010 4:06:33 AM -02:00

Why is the difference between Request Start Date and Actual Start Date ?
Is there any way to enforce the start of the Job at any time ?
OS: Solaris 10 8/07 s10s_u4wos_12b SPARC
DB: Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
Thanks in advance

The database is not down since at least 2 months

SQL> select LAST_START_DATE from DBA_SCHEDULER_JOBS where job_class = 'MY_NOCHE_JOB_CLASS';
LAST_START_DATE
────────────────────────────────────
17-NOV-10 04.21.00.447083 AM -02:00

Any advice ?

Starting Scheduled JOB by OMBPLUS

Hi all,
Can OMB+ start a scheduled job ?
I can't find the scripts....
I would promoting to production only using OMB+ !
I'm using OWB 10gr2 on DB 10gr2 and OWF 2.6.4 on UNIX.
Thanks,
Marco

Hi Marco,
in 10.2 and asuming you are using DBMS_SCHEDULER, then scheduled jobs are started by the scheduler process itself, which is always running as long as the database is up.
OMB+ is used for object administration, if you will, while the WF Server and Scheduler processes are used for object execution.
Cheers,
Donna

GRC Access Control 5.3: Background Jobs in RAR don't start

Hi experts,
I defined background jobs in RAR (configuration -> background jobs -> schedule jobs) for initial loading. and there are 3 background tasks defined. Unfortunately the jobs are never executed (jobtype= immediately).
Any help to execute the job would be appreciated.
Kind regards,
Max

Hello Max,
Here is what you should be checking :
1) Check if the Background job daemon is running :
URL - http://<server>: port/sap/CCBgStatus.jsp
2) Check if the analysis daemon manager is running :
URL - http://<server>:<port>/sap/CCADStatus.jsp
3) Follow SAP Notes 999785 and 1176262 .
This should help you resolve the issue
Harleen
SAP GRC RIG

Scheduled Job to gather stats for multiple tables - Oracle 11.2.0.1.0

Hi,
My Oracle DB Version is:
BANNER Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
In our application, we have users uploading files resulting in insert of records into a table. file could contain records ranging from 10000 to 1 million records.
I have written a procedure to bulk insert these records into this table using limit clause. After the insert, i noticed my queries run slow against these tables if huge files are uploaded simultaneously. After gathering stats, the cost reduces and the queries executed faster.
We have 2 such tables which grow based on user file uploads. I would like to schedule a job to gather stats during a non peak hour apart from the nightly automated oracle job for these two tables.
Is there a better way to do this?
I plan to execute the below procedure as a scheduled job using DBMS_SCHEDULER.
--Procedure
create or replace
PROCEDURE p_manual_gather_table_stats AS
TYPE ttab
IS
    TABLE OF VARCHAR2(30) INDEX BY PLS_INTEGER;
    ltab ttab;
BEGIN
    ltab(1) := 'TAB1';
    ltab(2) := 'TAB2';
    FOR i IN ltab.first .. ltab.last
    LOOP
        dbms_stats.gather_table_stats(ownname => USER, tabname => ltab(i) , estimate_percent => dbms_stats.auto_sample_size,
        method_opt => 'for all indexed columns size auto', degree =>
        dbms_stats.auto_degree ,CASCADE => TRUE );
    END LOOP;
END p_manual_gather_table_stats;
--Scheduled Job
BEGIN
    -- Job defined entirely by the CREATE JOB procedure.
    DBMS_SCHEDULER.create_job ( job_name => 'MANUAL_GATHER_TABLE_STATS',
    job_type => 'PLSQL_BLOCK',
    job_action => 'BEGIN p_manual_gather_table_stats; END;',
    start_date => SYSTIMESTAMP,
    repeat_interval => 'FREQ=DAILY; BYHOUR=12;BYMINUTE=45;BYSECOND=0',
    end_date => NULL,
    enabled => TRUE,
    comments => 'Job to manually gather stats for tables: TAB1,TAB2. Runs at 12:45 Daily.');
END;Thanks,
Somiya

The question was, is there a better way, and you partly answered it.
Somiya, you have to be sure the queries have appropriate statistics when the queries are being run. In addition, if the queries are being run while data is being loaded, that is going to slow things down regardless, for several possible reasons, such as resource contention, inappropriate statistics, and having to maintain a read consistent view for each query.
The default collection job decides for each table based on changes it perceives in the data. You probably don't want the default collection job to deal with those tables. You probably do want to do what Dan suggested with the statistics. But it's hard to tell from your description. Is the data volume and distribution volatile? You surely want representative statistics available when each query is started. You may want to use all the plan stability features available to tell the optimizer to do the right thing (see for example http://jonathanlewis.wordpress.com/2011/01/12/fake-baselines/ ). You may want to just give up and use dynamic sampling, I don't know, entire books, blogs and papers have been written on the subject. It's sufficiently advanced technology to appear as magic.

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.

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.

How to take inputs in scheduled job

Hi all,
I have a report which is having certain dates to be input on selection screen e.g. Starting date- ending date, Week start date- ending date, and report date.
Now requirement is to schedule job on daily basis..
In this , my query is , I have to give dates logic in program itself.. or there is any option after scheduling job dates change can be done automatically. ?
Thanks in advance to clear my doubts.

Hi,
you can define a selection-screen variant. for the dynamic input in date-fields you can use "dynamic date calculation" for your selection field like:
- current date +/- xxx days
- First day of next month
- and so on
alternative you can use a variable from table TVARVC which you can set with another/previous program
hope this helps
regards
Hans

Schedule job don't start

Similar Messages

Maybe you are looking for