| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: writing job dependencies shell script
Hi Elain,=20
Check this out, I've used it successfully in the past http://www.adpc.purdue.edu/DataMgmt/DBA/Stds/sqlscripts.htm
Lisa Koivu
Oracle Monkey
Orlando, FL, USA
-----Original Message-----
From: elain he [mailto:elainhe_at_hotmail.com]=20
Sent: Wednesday, February 18, 2004 10:51 PM
To: oracle-l_at_freelists.org
Subject: writing job dependencies shell script
Hi,
I'm trying to figure out how I can write a shell script that checks the=20
success or failure of DML statements. I have a number of jobs that are
dependent on one another. For eg. if JobA fails do not process jobB, and
likewise if jobB fails, do not process jobC.
Each job looks like the following:
jobA:
=3D=3D=3D
#!/bin/ksh
sqlplus << eof
username/password
update tableA set .....
eof
jobB:
=3D=3D=3D=3D
#!/bin/ksh
sqlplus << eof
username/password
delete tableB .....
eof
I'm trying to write a simple shell script that does the following checks
before executing each job:
#!/bin/ksh
jobA
if [ $? =3D 0 ];then
jobB
if [ $? =3D 0];then
jobC
if [ $? =3D 0];then
jobD
else
exit
fi
else
exit
fi
else
exit
The problem I'm encountering is $? always returns 0 because the sqlplus=20 always completes successfully even though my update or delete statement=20 fails due to rollback seg space or any other issues.
Can someone provide me some pointers on how I can write an error
handling=20
routine? If there is a better way of writing this, please let me know.
thanks.
elain
"The sender believes that this E-Mail and any attachments were free of = any virus, worm, Trojan horse, and/or malicious code when sent. This = message and its attachments could have been infected during = transmission. By reading the message and opening any attachments, the = recipient accepts full responsibility for taking proactive and remedial = action about viruses and other defects. The sender's business entity is = not liable for any loss or damage arising in any way from this message = or its attachments."
 |
 |