Comments on: Clearing the Oracle environment in a Unix session

By: jpiwowar

jpiwowar — Mon, 01 Dec 2008 14:48:40 +0000

Hi Richard,

I suggest going for a separate script. I would definitely recommend against modifying the oraenv script itself, for two reasons:
1) Doing so is almost certainly unsupported, and
2) You risk having your changes overwritten by a patch.

Thanks for visiting, and for the comment!

Regards,

John P.

By: Richard Bartholomew

Richard Bartholomew — Mon, 01 Dec 2008 14:09:00 +0000

This was very timely for me as I've just started looking into the best way of controlling the Oracle environment. Having just modified your script to work on our AIX platform, I now need to decide the best way to set them up, ie separate script or modified oraenv! Any thoughts, please?

By: Log Buffer #125: a Carnival of the Vanities for DBAs

Log Buffer #125: a Carnival of the Vanities for DBAs — Fri, 28 Nov 2008 17:46:36 +0000

[...] Once you have your Ibex or Fedora up and running, check out Only Four Left, where John Piwowar has some tips for clearing the Oracle environment in a Unix session. [...]

By: jpiwowar

jpiwowar — Mon, 24 Nov 2008 23:47:10 +0000

Hi Gary,

thanks for the comment; you make a very good point. Improperly set NLS variables have certainly caused headaches for me in the past. It's been a while since I've worked on a system where NLS variables had to be set differently on a per-ORACLE_HOME basis, which is probably why I neglected to include the NLS variables in my example. For completeness' sake, though, they should definitely be in there.

Thanks for visiting!

Regards,

John P.

By: Gary

Gary — Mon, 24 Nov 2008 22:22:34 +0000

Can I recommend adding NLS variables to this too.
Had an incident once where a script that ran fine from the command prompt buggered up from a scheduler tool because NLS_TERRITORY wasn't set there, which caused it to interpret to_char(date,'D') differently (whether the week starts on a Sunday or a Monday).