PERL DBI Error when run from CRON

bat_man2282 has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: PERL DBI Error when run from CRON by rdfield (Priest) on Nov 14, 2003 at 23:36 UTC
When running scripts as CRON the environment variables aren't set. Best to create a small script which exports the correct values for ORACLE_HOME, ORACLE_SID, NLS_LANG and update the PATH to include ORACLE_HOME/bin and run that as part of your script. Another way is to set ORAENV_ASK=NO and run the oraenv script with your SID. rdfield	[reply]
Re: PERL DBI Error when run from CRON by dws (Chancellor) on Nov 14, 2003 at 23:37 UTC
... but when I run it from cron ... cron jobs start with a truncated environment. (To see this, try a cron job that does a `printenv`.) If OCI is depending on environment variables being set (e.g., for an NLS parameter), you're probably going to need to set that variable in a wrapper script that you invoke from cron.	[reply] [d/l]
Re: PERL DBI Error when run from CRON by etcshadow (Priest) on Nov 15, 2003 at 17:11 UTC
Also, a simple way to get all of your typical environment in is to make your cron entry just source your profile script. If you do anything wacky or shell-specific in your profile script, then this might not work (since your crontab gets run through "sh" the system shell). Something like: `* * * * * source ~me/.bash_profile ; perl my_script.pl etc` [download] ------------ :Wq Not an editor command: Wq	[reply] [d/l]
Re: Re: PERL DBI Error when run from CRON by tilly (Archbishop) on Nov 15, 2003 at 18:45 UTC
But the approach at RE (tilly) 3: Get default login environment should work even if you do something wacky or shell-specific. You would use it like: `%ENV = (get_login_env(), %ENV);` [download]	[reply] [d/l]