Have you tried using CRONTAB.
It's very, very easy (given my lack of Unix knowledge!!).
Just do a: $ man crontab in unix for more details.
K.
-Original Message-
Sent: 03 October 2001 17:21
To: Multiple recipients of list ORACLE-L
Hi List,
I am not a Unix person and want to scheduled
Here is an example of a crontab listing:
15 07 * * 1-5 /u001/home/oracle/scripts/filescorp24.sh
00 07 * * * /u001/home/oracle/dbastuff/scripts/monitoring/rmerror.sh
/dev/null 21
00,30 * * * * /u001/home/oracle/dbastuff/scripts/monitoring/cron15min.sh
/dev/null 21
00 10 * * *
It will also run every minute from 1-2.
-Original Message-
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 03, 2001 8:20 PM
To: Multiple recipients of list ORACLE-L
see this
* 1 * * * /mydir/myfile
put the above line in your crontab with your filename. and that will run
man cron
Regards
Lee
-Original Message-
Sent: 03 October 2001 17:21
To: Multiple recipients of list ORACLE-L
Hi List,
I am not a Unix person and want to scheduled a batch job to run on Unix
machine every night at 1:00 AM, if you have any script for this or similar
really appreciate.
Title: RE: Unix Cron Job
* 1 * * * file_to_run
see 'man crontab' for detail.
Rivaldi
-Original Message-
From: Hamid Alavi [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 03, 2001 11:21 AM
To: Multiple recipients of list ORACLE-L
Subject: Unix Cron Job
Hi List,
I am
$crontab -- Press enter
0 1 * * * /blah/blah/blah.sh
-- Press {CTRL}+D
-Original Message-
Sent: 03 October 2001 17:21
To: Multiple recipients of list ORACLE-L
Hi List,
I am not a Unix person and want to scheduled a batch job to run on Unix
machine every night at 1:00 AM, if you have
see this
* 1 * * * /mydir/myfile
put the above line in your crontab with your filename. and that will run
everyday 1.00 am.
srinivas
-Original Message-
Sent: Wednesday, October 03, 2001 1:55 PM
To: Multiple recipients of list ORACLE-L
man cron
Regards
Lee
-Original
You could set up a marker file at the end of job A.
ie
if [ 'successful' ] # insert what ever code you would do to check this.
then
touch job_ok
else
'more code if failure'
fi
# End of script.
When job B kicks in just test for existence of file job_ok before backing up
to
The easiest way, from my perspective is to code the 'A' job to create a
file of zero bytes (touch command) upon successful completion. Then code
job 'B' to remove the file as the first step or exit if not there.
-Original Message-
From: David Jones [SMTP:[EMAIL PROTECTED]]
Sent:
in the cron job write out a file that tells success or not and have job
b read it.
joe
David Jones wrote:
Dear Lister:
I have two cron jobs which run at 10:30 PM 2:00 AM, job A performed a DB
hot backup and job B will put those backup files into tapes. The problem is
job B is based on
If you use "whenever sqlerror exit 9", then you can test the return code
for either "0" or "9" just as you described. ( You can use any number you
choose, 9 is just an example. )
HTH
John Carlson
http://www.cj.com
[EMAIL PROTECTED] 02/27/01 06:46AM
Can you send me shell script you are
11 matches
Mail list logo