Can you check if the schedule script is doing the required activity or not ? ? if its delivering the result then you can redirect the error to /dev/null
If im correct your running the exp (export command of oracle). Maybe your ORACLE instance / Oracle PATH is not defined to that user , and that users doesnt have permission to run the exp command.
2) most probably , "exp" is an executable that is not being found due to PATH lookup failure ;
-- this second theory can be easily tested as follows :
a) try and run the script directly from the shell prompt (as if it was a `date' command) ;
-> if the same error occurs , then your script is messed up for good , and cron has nothing to do with it ;
-> if the error does NOT occur, then you need to adjust your PATH for cron jobs , because cron does NOT read your ".profile" ;
--> this can be done in many ways , but perhaps the simplest is by calling your special script from within an "envelope" shell script , that in turn prepares your PATH , see :