Hi S@R@H, your post leaves a lot to be asked. For instance, what should the script accomplish? Assuming that your script, which is to be run by cron is comprehensive, my approach would be:
- To have everything in a script including the output redirection to file
- Alternatively, rather than cd to directory containing script, use the full path e.g. /home/oracle/sh/rman.sh >> /u01/rman.log
I think the major caveat is that you do not have command seperation. Maybe introducing a colon or preferably '&&' between the directory /home/oracle/sh and you script may help. It will also be great if you try your scripts on the commandline before adding them to cron.