BASH script does not work. Do not understand why.

SteveInTallyFL · 12-01-2008, 07:15 AM

This script file is flagged executable and appears to execute when run from the user's home directory (where script is stored) but the environment does not change. What is wrong with this script (RHEL 4)?

#!/bin/bash
export ORACLE_HOME=/u01/app/oracle/product/10.2.0/http_102
export ORACLE_SID=sudstest
export PATH=.:$ORACLE_HOME/bin:$ORACLE_HOME/opmn/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin

Hangdog42 · 12-01-2008, 07:25 AM

Can I ask why you think the script isn't working? One thing to keep in mind is that if you are running this script from a console, the environment variables are being changed for that console only.

pixellany · 12-01-2008, 07:27 AM

I'm not clear on how you are testing to see if the environment changes...

You might need quotes, especially here:
export ORACLE_HOME="/u01/app/oracle/product/10.2.0/http_102"

This looks questionable:
export PATH=.:$ORACLE<snipped>
(The leading ".:" seems wrong)

Normally you would add to the PATH using:
export PATH="$PATH:<newstuff>"

Hobbletoe · 12-01-2008, 08:19 AM

Are you running the script or sourcing the script? If you run it, then any environment variable that you set is set locally, and not carried back to your initial shell. If it is sourced, then once the script finishes, all of the enviroment variables that you changed are carried back to the shell.

You would run the script like this ...

Code:

$ ./my_script.sh

You would source the script like this ...

Code:

$ . ./my_script.sh

or

Code:

$ source ./my_script.sh

SteveInTallyFL · 12-01-2008, 08:22 AM

Quote:

Originally Posted by Hangdog42

Can I ask why you think the script isn't working? One thing to keep in mind is that if you are running this script from a console, the environment variables are being changed for that console only.

When I echo the $ORACLE_HOME it does not reflect the value in the export statement.

SteveInTallyFL · 12-01-2008, 08:24 AM

Quote:

Originally Posted by Hobbletoe

Are you running the script or sourcing the script? If you run it, then any environment variable that you set is set locally, and not carried back to your initial shell. If it is sourced, then once the script finishes, all of the enviroment variables that you changed are carried back to the shell.

You would run the script like this ...

Code:

$ ./my_script.sh

You would source the script like this ...

Code:

$ . ./my_script.sh

or

Code:

$ source ./my_script.sh

I am running the script.

SteveInTallyFL · 12-01-2008, 08:31 AM

Quote:

Originally Posted by SteveInTallyFL

I am running the script.

Many thanks, Hobbletoe. I need to source these scripts to properly scope the environment variables change. Lesson 1 learned.

Hangdog42 · 12-01-2008, 09:32 AM

One other thing, your PATH statement is destroying any previously set PATH. If that is OK, you can leave it alone, otherwise put the $PATH variable along with the new additions.