06-27-2010
@Jim
Actually there are lot of jobs scheduled using crontab which runs on daily basis.
Those jobs used to update some tables, drop tables etc. Suppose I have a table named 'Details' , I need to check whether that table is used by any of the jobs. If the table 'Details' is not used by any of the jobs, I can drop that table or make some changes , so that it will not affect the jobs. So, I have to write a shell script to check this condition and find the list of tables and views, not being used in any of the jobs.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hey!
I have just configured an backup MX using Mail::Toaster under FreeBSD.
As I'm a novice when it comes to mailservers, I need to ask someone how to check that this backup really does its job.
My primare MX is unfortunately on a Dynamic IP line, but its unsusual for it to change the IP.... (4 Replies)
Discussion started by: noratx
4 Replies
2. UNIX for Dummies Questions & Answers
hi
i'm a bit stuck trying to find the correct syntax in order to run a cron job which just truncates all info from a single table in my database
i have a main database - db1
and i have a table in that database - userips
i wish to create a cron job that truncates or removes all the info... (9 Replies)
Discussion started by: wingchun22
9 Replies
3. Shell Programming and Scripting
I have requirement:
1) Check the record count in table (table in oracle)
2) If records exists generate the file for existing records and wait for some time (Go to sleep mode) and
Again check the record count after 10 min.......... (Loop this process if record count >0).
3) Generate touch... (1 Reply)
Discussion started by: kamineni
1 Replies
4. Shell Programming and Scripting
I have requirement:
1) Check the record count in table (table in oracle)
2) If records exists generate the file for existing records and wait for some time then Go to sleep mode and
Again check the record count after 10 min.......... (Loop this process if record count >0).
3) Generate touch... (1 Reply)
Discussion started by: kamineni
1 Replies
5. UNIX for Advanced & Expert Users
Hi,
I have master job which will run based on the sub jobs status.
In the master job I am giving the condition like,
condition: s(sub_job) f(sub_job)
This scenario will work if the sub job status is success or failed. but I want to run my master job even if the sub_job was... (1 Reply)
Discussion started by: Kattoor
1 Replies
6. Shell Programming and Scripting
I have written a BASH script to autmatically start several jobs. I want to add additional function to the script so it would check these jobs from time to time (the jobs could take as short as 2 hours or as long as 1 day to finish). If a job is done, check the log file and output the error into a... (3 Replies)
Discussion started by: momentum
3 Replies
7. UNIX for Dummies Questions & Answers
Hello All,
I was wondering if someone could take a quick glance at this Cron job and tell me if it's going to do what I am expecting.
I want it to run everyday at 8:00 am and 5:00 pm.
And the line in Crontab looks like:
0 8,17 * * * /usr/local/myScript.sh
Does that look correct?
... (6 Replies)
Discussion started by: mrm5102
6 Replies
8. Shell Programming and Scripting
I have made a table PRD_WORK_LM.test and it contains one field, ctrl_test. This field contains a 0 or a 1. I want to write a unix script that goes like this:
IF ctrl_test = 1 THEN ... ELSE exit FI
How can I write this in a script? Do I have to do this within bteq? or outside bteq? can... (5 Replies)
Discussion started by: katled
5 Replies
9. Shell Programming and Scripting
Hi
I have a requirement like this:A shell script will check a table column if the column name "value" is 'N' then main script start and keep checking within 30 minute whether the column value has changed to 'y'. or not if it has changed to 'y' then stop the server.Please help me to get the... (6 Replies)
Discussion started by: netdbaind
6 Replies
10. Shell Programming and Scripting
I am trying to write a script which allows a user to select the what manipulation he needs to do on a table. I want to check if the table exists or not. If it exists I will continue the other things or else I exit saying table doesn't exist. How might I achieve this. (1 Reply)
Discussion started by: gmatcat
1 Replies
LEARN ABOUT DEBIAN
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. 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 the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) 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 nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)