Errors in crontab usually happen because the commands there are executed with a very spartanic environment. Put the command 'printenv > /tmp/xyz476' into the crontab (so that it gets executed 2 minutes in the future). You should get the environment used in crontab in the file /tmp/xyz476. Compare that with the output of 'printenv' on the command line. One of the things that changed is responsible for the failure of your script

To add the missing environment variable you might just put the definition of it in front of your script (if you use bash or something similar). Example:

1 2 * * *   PATH=${PATH}:/usr/local/bin sqlloader

[download]

would add /usr/local/bin to the path before executing sqlloader

In reply to Re: sqlldr invocation issue by jethro
in thread sqlldr invocation issue by bungeejumper

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.