Exported variables are not reflected in “env” output?

The scripts only sets the environment inside the subshell it runs in. You should source it.

The scripts only sets the environment inside the subshell it runs in. You should source it: # POSIX . /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/bin/oracle_env.

Sh or # bash/ksh source /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/bin/oracle_env.sh.

Thanks.. it worked for me. – hnm Aug 12 '10 at 16:01.

I believe that when you run a script, bash forks and execs the script in a new shell instance, any exports done in the script doesn't propagate back to your parent shell. However it seems that you can simply execute your script with: prompt$ . /path/to/script.Sh # note the period!

Example: prompt$ echo "export FOO=foobar" > /tmp/tst prompt$ sh /tmp/tst prompt$ echo $FOO prompt$ . /tmp/tst prompt$ echo $FOO foobar.

I believe you should use source to load that script. Source /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/bin/oracle_env. Sh From man source: source filename arguments Read and execute commands from filename in the current shell environment and return the exit status of the last command executed from filename.

Exporting variables only makes them available to children of the shell you export them from. There is no way of changing the environment variables in the parent shell, as you seem to be trying to do. You can change the variables in the same shell by sourcing the script using the "dot" command: .Myscript.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.