Re: Pro*C and cron

crons typically run in an impoverished environment -- perhaps an env var is not set correctly in the cron, but is set OK from the commandline? I typically put:
set | mail jimj
or somesuch in a cron to see what the environment is, then use a wrapper shell script to setup the environment correctly for the binary, and call the wrapper from cron.

In article <4ghrau$ipa_at_slider.bme.ri.ccf.org>, rstewart_at_bio.ri.ccf.org (Ron Stewart) writes:
|> I'm having a problem with a pro*c program running under cron in a Solaris 2.3
|> environment. The pro c program works fine when run from the command line. But from
|> cron, it blows up when it tries to connect to the Oracle database. I get a message:
|>
|> ORA-12546: Unable to open message file (SQL-02113)
|>
|> This message indicates a problem with privileges. We're new to using pro c here. Has
|> anyone experienced and gotten around this?
|>
|> Ron Stewart
|>
|>
 

-- 
Jim Johnstone    |  jimj_at_meaddata.com   | The only thing needed for evil to 
LEXIS-NEXIS      |                      | triumph is for good men to do 
P.O. Box 933     |  Speaking only for   | nothing -- Edmund Burke
Dayton, OH 45401 |       myself         |