Dears,

I have a shell script that uses sacego to collect data from an informix database. The problem is that when I run the script manually it works, but when I schedule it from cron it does not work.

Previously I solved this problem by creating symbolic links to all the libraries in /usr/informix/lib/esql, but now when I apply the same procedure it gives the following error,

ld.so.1: sacego: fatal: libifsql.so: open failed: No such file or directory

the below listings shows the symbolic links,

libifsql.so -> /usr/informix/lib/esql/libifsql.so
libifcobsql.so -> /usr/informix/lib/esql/libifcobsql.so
libiffgisql.so -> /usr/informix/lib/esql/libiffgisql.so
libifgen.so -> /usr/informix/lib/esql/libifgen.so
libifgls.so -> /usr/informix/lib/esql/libifgls.so
libifglx.so -> /usr/informix/lib/esql/libifglx.so
libifos.so -> /usr/informix/lib/esql/libifos.so
libifxa.so -> /usr/informix/lib/esql/libifxa.so
libixcobsql.so -> /usr/informix/lib/esql/libixcobsql.so
libixfgisql.so -> /usr/informix/lib/esql/libixfgisql.so
libixgen.so -> /usr/informix/lib/esql/libixgen.so
libixgls.so -> /usr/informix/lib/esql/libixgls.so
libixglx.so -> /usr/informix/lib/esql/libixglx.so
libixos.so -> /usr/informix/lib/esql/libixos.so
libixsql.so -> /usr/informix/lib/esql/libixsql.so
libixxa.so -> /usr/informix/lib/esql/libixxa.so
libtgen.so -> /usr/informix/lib/esql/libtgen.so
libthgen.so -> /usr/informix/lib/esql/libthgen.so
libthos.so -> /usr/informix/lib/esql/libthos.so
libthsql.so -> /usr/informix/lib/esql/libthsql.so
libthxa.so -> /usr/informix/lib/esql/libthxa.so
libtos.so -> /usr/informix/lib/esql/libtos.so
libtsql.so -> /usr/informix/lib/esql/libtsql.so
libtxa.so -> /usr/informix/lib/esql/libtxa.so

Chances are you're executing this manually as user "informix" (or your personal userID) but cron is trying to execute it as root. If this is true then the job will fail because the .profile associated with userID "informix" (or your userID) is not being executed and important environment variables are not being set correctly.

Try adding something to your scheduled cron job to execute the correct .profile first (to set env variables) & see if the problem persists.

Best of luck with it