Erm, when you run 'unzip myfile.zip', are you running the command from the directory where myfile.zip is present? What I mean is, does your cron script actually do a 'cd' to the directory where the myfile.zip file is present?

When you run the script you might be running it from the directory where the file is already present. However, when a script runs through cron, the working directory is usually the home directory of the user whose cron is running the script.

Hi,
The locations are given correctly. Even I tried running my script from the home directory, by giving the whole path. Its executing perfect. the only probelm is when i schedule my script in cron, its throwing the error. I do have many operaiton in my script. Like unzip, I use sql loader , sql plus commands too. All are giving error when scheduled in cron. So what else can be done ???

I tried /usr/bin/unizip .. Its telling
ksh : /usr/bin/unizip : not found

Make sure your paths are correct. I see you've got "/usr/bin/unizip" instead of "/usr/bin/unzip". Check for where your commands are using "whereis cmd_name", e.g. %whereis unzip.

Hi,
I gave whereis unzip. Its showing :

unzip:

So i too doubt the location about that command. But still , its working when i run the script manually, instead of using the CRON. As shown above for unzip, the same is coming for sqlldr and sqlplus. So how can i use them with cron ??

I am really confused about this situation..

Is there any chance you can show us your entire script ??

It might be something else that you have in it that's causing it to run standalone and not via cron.

I think posting your script might help.Just out of curiosity: Make sure you have $ sign in front of your commands in your script, e.g. $unzip file_name ,etc.

why is that?