Re: Pro*C and cron
Date: 1996/02/24
Message-ID: <4go1k0$c7b_at_metroux.metrobbs.com>#1/1
In article <4ghrau$ipa_at_slider.bme.ri.ccf.org>, rstewart_at_bio.ri.ccf.org
says...
>
>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 fr
>om
>cron, it blows up when it tries to connect to the Oracle database. I get
a messa
>ge:
>
>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
>
>
check your login environment - you should find:
ORACLE_SID=???? - database name (identifier) and ORACLE_HOME=?????? - path to oracle software installation
precompiled programs need these whether or not they are connecting locally or over sql*net
generally, the cron doesn't execute your profile when running jobs which leaves 2 choices:
wrap a shell around your program and set the environment variables up before executing your program - run the shell from the cron. use putenv() from within your program to set the environment (this works nicely if you pass the needed values on the command line - your program will be more portable)
once your program knows oracle home (and presuming the oracle installation in that home was complete) it should be able to find the message files it needs.
--Received on Sat Feb 24 1996 - 00:00:00 CET
>-->-->-->-->-->-->-->-->-->-->-->-->-->-->-->-->-->
| | | Chris Kirke - cakirke_at_metroux.metrobbs.com | | | | the opinions expressed here ..... whatever | | | <--<--<--<--<--<--<--<--<--<--<--<--<--<--<--<--<--<