topic Re: Shell Script Quick Help in Operating System - HP-UX

Shell Script Quick Help

Steven Chen_1 — Mon, 08 Mar 2004 15:26:00 GMT

Hi,

Would anyone help with this short script as why it is not getting through?

---------------------------------------
The script is to check Oracle listener whether it is up, if not, start it, if yes, exit.

It runs under Oracle, thus lsnrctl can start right there.

****************************
lsnrctl status > /disk3/test/t1
aaa=`grep 'The command completed successfully' /disk3/test/t1`
bbb='The command completed successfully'
ccc='TNS:no listener'

if [$aaa=$bbb]; then
exit
else
if [$aaa=$ccc]; then
lsnrctl start
fi
fi
exit

******************************

Error:

listen_test[6]: [=The: not found.
listen_test[9]: [=TNS:no: not found.
---------------------------------------

Very appreciated.

Steven

Re: Shell Script Quick Help

Patrick Wallek — Mon, 08 Mar 2004 15:30:16 GMT

Try this:

if [ "$aaa" = "$bbb" ] ; then
exit
else
if [ "$aaa" = "$ccc" ] ; then
lsnrctl start
fi
fi
exit

Note the extra spaces and quotes. What shell are you using for this? If POSIX, do a 'man sh_posix' for information on the syntax for the if statement. It is very syntax dependent.

Re: Shell Script Quick Help

Rodney Hills — Mon, 08 Mar 2004 15:30:27 GMT

Be sure their are spaces around the "[" and "]". Also it is best to enclose your variables in double quotes. Example-

if [ "$aaa" = "$bbb" ] ; then

HTH

-- Rod Hills

Re: Shell Script Quick Help

Patrick Wallek — Mon, 08 Mar 2004 15:34:12 GMT

You probably also should enclose your values for bbb and ccc in double quotes ( " ) instead of single quotes ( ' ). For readability I would also modify aaa to be:

aaa=$(grep "The command completed successfully" /disk3/test/t1)

It will work exactly the same and is much more readable than using the back-ticks ( ` ).

Re: Shell Script Quick Help

A. Clay Stephenson — Mon, 08 Mar 2004 15:35:18 GMT

You have several problems:

if [$aaa=$bbb]
should be:
if [ "${aaa}" = "${bbb}" ]
then
especialy note the white space after '[' and before ']'. Also, your variables should be protected bu quotes so that null strings don't clobber test.

You will also find this test to be much simpler:

lsnrctl status > tmpfile
grep -q "This command completed sucessfully" tmpfile
STAT=${?}
if [[ ${STAT} -eq 0 ]]
then
echo "OK"
else
echo "Bad"
fi

The -q option says only report the status of the grep; 0 = found.

The '[[ ]]' uses the POSIX and Korn shell's internal test whereas '[ ]' spawns the external test command. The internal is more efficient although you can continuey to use the external.

Re: Shell Script Quick Help

Chris Watkins_1 — Mon, 08 Mar 2004 15:36:17 GMT

Argh!
So hard to reply first here :-)
As mentioned... you have two troubles.

Double quote the variables, and space around the brackets.
ie...
[ "${aaa} = "${bbb}" ]

...will work just fine.

Re: Shell Script Quick Help

Chris Watkins_1 — Mon, 08 Mar 2004 15:41:08 GMT

NO points here please.
A typo in the previous post, in my haste to get a response in.

[ "${aaa}" = "${bbb}" ]

missed a doublequote on the previous response.

Re: Shell Script Quick Help

Seth Parker — Tue, 09 Mar 2004 00:13:50 GMT

Steven,

Clay's script should be the only one that actually works, even though everyone else has offered you good advice on syntax.

The reason I say this is because you're checking for "The command completed successfully" using grep on a file. Since you're just running a plain grep, you'll *only* get matches. So, $aaa can *never* match $ccc.

Back to Clay's script. All he's doing is checking to see if there was a match and then doing something with that information. And that's all you really need here. Just modify the "OK" and "Bad" results to do whatever you actually want and you should be fine.

Hehe, having said all this, I sure hope I'm not missing something obvious!!!

Regards,
Seth