Paul Bijnens said:
> Gavin Henry wrote:
>
>> /bin/sh: line 1: /usr/bin/find /u01/app/oracle/archdest2/* -mtime +7
>> -exec
>> rm{}\;:
>> No such file or directory
>
> This seems like there are quotes around the whole command, or something
> with a similar effect.  Maybe $IFS got screwed up when cron runs?
> (run a little shell script which prints out the cron environment).
> Verify you do have spaces 0x20 and not no-breakspace 0xA0 instead.

Good point.

>
> Also there should be spaces around the braces:  "... rm {} \;", but that
> should give the above error.

OK.

>
>
>> P.S> I know this makes me look quite unprofessional, but I'm sure we've
>> all hit some kind of stupid brick wall. "Can't see for looking", as the
>> saying goes here in Scotland.
>
>
> Yes, had it way too often :-)
>
> As workaround, you can create little shell scripts that are invoked by
> the cron, and don't need spaces.

That was my next move.

>
>
> --
> Paul Bijnens, Xplanation                            Tel  +32 16 397.511
> Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
> http://www.xplanation.com/          email:  Paul.Bijnens AT xplanation DOT com
> ***********************************************************************
> * I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
> * quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
> * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
> * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
> * kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...    *
> * ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
> ***********************************************************************
>
>
>