Re: Importance of local bin directory while running root.sh
- From: Dan Norris <dannorris@xxxxxxxxxxxxx>
- To: Sundar.Mahadevan@xxxxxxx
- Date: Fri, 16 Jul 2010 12:41:04 -0500
My experience is that these three scripts are generally backward-compatible.
I've always used the most recent versions of them without issue. They do get
updated/modified from release to release, so you can expect updates and
fixes to be most current in the latest releases.
That said, I also haven't had problems using, say, 10g versions of these
scripts when setting the environment for 11g databases. There are also
environments that do not use oraenv at all and the usage of these scripts is
not required, but they're included as a convenience.
FYI, the scripts are always located in $ORACLE_HOME/bin, so you can diff
them between releases if you'd like to see what changes. They're also copied
to your chosen local binary directory (/usr/local/bin by default on most
platforms) for ease of locating them in the $PATH for most users.
Dan
On Fri, Jul 16, 2010 at 11:34 AM, Mahadevan, Sundar <
Sundar.Mahadevan@xxxxxxx> wrote:
> Thanks for your input, Paul. I donot see a version number in dbhome,
> oraenv and coraenv but the header has a date as to when this script was
> created. Do these scripts have any code changes between versions? In that
> case, replacing a 9i dbhome, oraenv and coraenv with a 10g installation
> should be ok but not otherwise? What are your comments?
>
>
>
> --Sundar
> ------------------------------
>
> *From:* Paul.Baumgartel@xxxxxxx [mailto:Paul.Baumgartel@xxxxxxx]
> *Sent:* July 16, 2010 10:34 AM
> *To:* Mahadevan, Sundar; Oracle-L@xxxxxxxxxxxxx
> *Subject:* RE: Importance of local bin directory while running root.sh
>
>
>
> The local bin directory (/usr/local/bin or whatever) does not refer to an
> ORACLE_HOME directory; rather, it identifies a directory for executables and
> binaries used system-wide that aren't part of the vendor's system software.
> The files dbhome and oraenv are shell scripts that are used to set one's
> environment to a particular ORACLE_HOME on a server.
>
>
>
> *Paul Baumgartel*
> UBS AG
> IB Accounting Solutions
> 400 Atlantic Street
> Stamford, CT 06904
>
> 203.719.4368
>
> paul.baumgartel@xxxxxxx
> www.ubs.com
>
>
>
>
> ------------------------------
>
> *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
> oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Mahadevan, Sundar
> *Sent:* Friday, July 16, 2010 10:23 AM
> *To:* Oracle-L@xxxxxxxxxxxxx
> *Subject:* Importance of local bin directory while running root.sh
>
> Hi All,
>
> Good morning. While running root.sh as root during binary installation (any
> version), the questions below come up. What is the importance of
> /usr/local/bin? My understanding is that the value should be the
> $ORACLE_HOME/bin instead of /usr/local/bin. Am I right? When there are many
> ORACLE_HOME with different versions(lets say 9i, 10g and 11g), what impact
> does it have on the setting of local bin directory location? Ideally
> speaking, do I have to set them to their respective $ORACLE_HOME/bin ? Many
> Thanks for your help.
>
>
>
> # /opt/oracle/products/9208/root.sh
>
> Running Oracle9 root.sh script...
>
> The following environment variables are set as:
>
> ORACLE_OWNER= oracle
>
> ORACLE_HOME= /opt/oracle/products/9208
>
> Enter the full pathname of the local bin directory: [/usr/local/bin]:
>
> The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n)
> [n]:
>
> The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
> [n]: y
>
> Copying oraenv to /usr/local/bin ...
>
> The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
> [n]: y
>
> Copying coraenv to /usr/local/bin ...
>
> Adding entry to /var/opt/oracle/oratab file...
>
> Entries will be added to the /var/opt/oracle/oratab file as needed by
>
> Database Configuration Assistant when a database is created
>
> Finished running generic part of root.sh script.
>
> Now product-specific root actions will be performed.
>
>
>
> --Sundar
>
>
>
Other related posts:
