Hi all,

I am trying to schedule a script thru cron and i am getting the error

produced the following output:
/export/home/db2inst1/utility/reorg.sh: ~db2inst1/sqllib/db2profile: not found

When I execute the script individually its working perfect, but when thru cron its giving me error

There are already 4 scripts scheduled thru cron and they are working perfect,
but when I added the new one to the list its erroring me out only for this script.

Can someone help me please, thank u all in advance.

Your .profile is not executed when running cron jobs
You must set your environment in your script
e.g.
. .profile # a space between the . and .

Could you show us the content of your reorg.sh script?

But there are other scripts scheduled thru cron and they are working fine.

Stolze the script is like this. As I said it works fine when I execute it alone.

#!/bin/ksh
. ~db2inst1/sqllib/db2profile

DIR=/export/home/db2inst1/utility
DATE='date'

db2 "connect to capprddb";

db2 "select substr('reorg table '||rtrim(t.tabschema)||'.'||t.tabname||' index '||rtrim(indschema)||'.'||indname||' use tempspace1;'
,1,125) from syscat.indexes i, syscat.tables t where i.tabname =t.tabname and t.type ='T' and (indextype='CLUS' or uniquerule='U' o
r uniquerule='P') order by t.tabschema, t.tabname" > $DIR/reorg.out;

sed -e '1,2d' $DIR/reorg.out > $DIR/reorg.log;

rm $DIR/reorg.out

db2 -tvf $DIR/reorg.log > $DIR/reorg_report.txt

cat $DIR/reorg_report.txt | mailx -s "Reorg Cap One UAT" xxx@xxx.com

db2 connect reset;


Thank you all

Do the other scripts also source the db2profile? If they do, you have probably some sort of strange character in your script (what does a hexdump show?).

You can also try replacing "~db2inst1" with "/export/home/db2inst1". Since you hardcode the directory a couple lines below anyway, I don't see any point in trying to be more flexible in the 2nd line.

Do the other scripts also source the db2profile? If they do, you have probably some sort of strange character in your script (what does a hexdump show?).

You can also try replacing "~db2inst1" with "/export/home/db2inst1". Since you hardcode the directory a couple lines below anyway, I don't see any point in trying to be more flexible in the 2nd line.

Hi Knut, as you said I tried using "/export/home/db2inst1" instead of "~db2inst1" and it worked... Thank you very much.

But how come its working for other scripts using the source db2profile. Any specific reason? And also when you asked me "what does a hexdump show". Where can I find that?

Thank you