Sponsored Content
Operating Systems Solaris Scheduling job not triggering Post 302642533 by juan.brein on Thursday 17th of May 2012 02:43:42 PM
Old 05-17-2012
Quote:
Originally Posted by sridhardwh
I am scheduling job using Datastage tool, which tool is installed on solaris server.
I can able to schedule jobs/sequences, its not trigering at specified scheduling trigerring time.
but at specified job not starting automatically. Till that specified schedule time, i can able to see that the job is schedule in datastage tool and even in at.allow and cron.allow files.
But at exact time of schedule,its showing that no job is scheduled.
i can able to see that schedule job and time in at -l, crontab -l .
Please help me out to resolve this issue.
Have you checked crontab is running?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

problem with scheduling a job

I scheduled 2 Oracle jobs to run on IBM AIX 4.3.3 at 06:50 and 06:58 on 02/02/03 with the below syntax: $ at 06:50 02/02/03 /orac/ora11/temp/sun_job1.sh Job oracle.1044175800.a will be run at Sun Feb 2 06:50:00 2003. $ at 06:58 02/02/03 /orac/ora11/temp/sun_job2.sh Job... (1 Reply)
Discussion started by: ted
1 Replies

2. Shell Programming and Scripting

Job Scheduling

Hello, I want to know about job scheduling utilities available in unix. It should not be responsible just for starting the job like in case of cron but should also be able to handle the execution of jobs. Regards, Ritesh (1 Reply)
Discussion started by: turlapaty
1 Replies

3. UNIX and Linux Applications

Job Scheduling

I am working on UNIX AIX system, with Oracle OS. We are not supposed to use any tools to schedule our unix shell scripts. Basically we have to make use of Oracle tables and Shell scripts to manage dependencies, restartability, scheduling, parallelizing,etc. If anyone has worked/ is working... (1 Reply)
Discussion started by: singhabhijit
1 Replies

4. Shell Programming and Scripting

Job Scheduling

I am working on UNIX AIX system, with Oracle OS. We are not supposed to use any tools to schedule our unix shell scripts. Basically we have to make use of Oracle tables and Shell scripts to manage dependencies, restartability, scheduling, parallelizing,etc. If anyone has worked/ is working... (4 Replies)
Discussion started by: singhabhijit
4 Replies

5. UNIX for Advanced & Expert Users

Autosys job scheduling

Hi, I want to schedule a job through Autosys (in Linux server) to run on 1st day of every 3rd month(gap of 90 days). Please someone help me to achive my above requirement Example: Run the sample.sh on 01-Jan-2009, 01-Apr-2009, 01-Jul-2009, 01-Oct-2009. Thanks in advance (4 Replies)
Discussion started by: apsprabhu
4 Replies

6. Shell Programming and Scripting

Cron Job Scheduling

Hi All, I have a script which is scheduled in the Cron. It runs every 10th and 40th min of an hour.The job has to run every 30min. But, I do not want to have the 00:10 MST run every day.Is it possible to exclude that run from the schedule?Or any other way through which i can run my job every... (4 Replies)
Discussion started by: sparks
4 Replies

7. UNIX for Dummies Questions & Answers

Cron is running,but my job is not triggering.

Hi, I have scheduled a job previously and was running fine,but due to some issue i have commented it.Now the issue was solved and i have scheduled as below in crontab. 30 2 * * * /u01/srcdata/CSA/holding/common/script/QPLR_RegValrao.sh PROD Cron is running,but my job is not triggering. ... (1 Reply)
Discussion started by: mvennakula
1 Replies

8. Shell Programming and Scripting

scheduling a job using at command

Hi All, I've been trying to schedule a job using the at command on Solaris 5.10 but i've been running into some issue. ( Not allowed to use cron :wall: ) I have a script that reads a logs file, does some iteration and cat's the output in an email . ## the o/p of /home/myscript.sh is : ... (2 Replies)
Discussion started by: Irishboy24
2 Replies

9. Shell Programming and Scripting

Cron job not triggering.

Hi, I have scheduled a job using cron but the job is not getting triggred because of the following error. line 5: /env/env_setup.sh: No such file or directory But the file env_setup.sh is there in that location. /scripts/env -rwxrwxrwx 1 mysql mysql 974 Oct 24 10:41 env_setup.sh... (5 Replies)
Discussion started by: arijitsaha
5 Replies

10. Shell Programming and Scripting

Job Scheduling

Hi All, I am new to unix and i have a task in front of me. The code part is "android update sdk" . I need to crontab this process. Hence i have written a script that runs the above command and sends a mail once the update is done. The problem with the automation is the installer asks for a... (5 Replies)
Discussion started by: Kashyap
5 Replies
queuedefs(4)						     Kernel Interfaces Manual						      queuedefs(4)

NAME
queuedefs - queue description file for at, batch, and crontab SYNOPSIS
DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue. The format of the lines are as follows: [njob[nice[nwait The fields in this line are: q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by (see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined queues. njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed by setting the variable to 1 in the file. nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). The default value is 2. nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's queue, or because more than 100 jobs were running in all the queues (see njob above). EXAMPLES
Consider the following file: The file is interpreted as follows: The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of 1. Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds before trying again to run it (see cron(1M)). The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2. If a job cannot be run because too many other jobs are running, will wait 90 seconds before trying again to run it. All other queues can have up to 100 jobs running simultaneously. They will be run with a value of 2, and if a job cannot be run because too many other jobs are running, will wait 60 seconds before trying again to run it. SEE ALSO
at(1), nice(1), crontab(1), cron(1M), proto(4). STANDARDS CONFORMANCE
queuedefs(4)
All times are GMT -4. The time now is 07:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy