A few days ago wrote a regular backup Sybase database script, in the shell after writing to try to manually execute, everything OK. The results are written to a cron timed file and are not executed at the time. Very puzzled, and checked a user, permissions, directory permissions, etc. (in fact, manual can carry out the instructions are all right), no problem ah, how is it going?
Then I saw an example of a predecessor and it dawned on me. Sybase's environment variables are in effect when you log in to the shell, but when cron schedules a child shell generated by the backup script to run, you cannot find the Sybase environment variables required for script execution. Therefore, you should execute a script that takes effect on the Sybase environment variable before the database backup script in cron (either in the backup script or in a separate execution).
SUSE Linux:
Source/home/sybase/.bash_profile;
AIX under:
00 10 * * * *. /home/sybase/.profile;/home/sybase/backupdb.sh
(Note: There are spaces between the backup scripts)