Hi all,

let say if I have 2 database on the Linux server and long with that I also had a third party running on the same server. Any way, what I want to ask is the following:

set env for each database, let say if I want to be on the first env along with the third party software to run ok, I have to do:

export ORACLE_SID=test1 (where test1 is the database SID of the first instance)

export SDEHOME=/home/sde/sdeexe83 (where /home/sde/sdeexe83 is the home of the software for the first instance)




so if I want to switch to the second database along with the different home for the third party sfotware I have to do the following:




export ORACLE_SID=test2 (where test2 is the database SID of the second instance)

export SDEHOME=/home/sde/sdeexe83_2 (where /home/sde/sdeexe83_2 is the home of the software for the second instance)


the question is "what can I do to switch env without typing each time, another way, the shorter way to change env)

thanks,

The obvious way : to write a script(s).

Make this executable and place it in your path.
Call it with "<filename> 1" or "<filename> 2"

mikeshaw,

thanks for your advises.

I did save the file as test.sh

so how do we go from here???

is that from the command prompt we do:

$./test.sh

????


once we get the executable from, what we need to do from here????


BTW, you have to my two file for the same scripts that you posted earlier???? change_env_1.sh and change_env_2.sh?????

I'm going to say "./test.sh 1" if you want to export ORACLE_SID=test1 and "./test.sh 2" for test2

However, the naming is slightly different (i tend to not use extensions on scripts...just put them all in a specific directory in my path)..I assume it would work the same, though.
Here's my setup, for reference:
1) create a directory called "scripts" in my home
2) in ~/.bashrc add PATH=$PATH:~/scripts
3) dump all my scripts in ~/scripts
4) chmod 700 ~/scripts/*

No need to specify a path now...I just do "test 1" and it'll run ~/scripts/test with an argument of "1".
"test" isn't really a good name for a script, though, since there's already a commonly used executable called "test"

mikeshaw,

thanks again

ok I save the file as change_env.sh and then I issue the command:

$./change_env.sh 1


obviously the env still point to the first so when I do:

./change_env.sh 2


I check the env by tying:

$env


it still point to the first environment so it's not changing then.

could you please tell me why???

weird....

What happens when you run it without an argument (just "change_env.sh" with no number)? Do you get the "no database specified" response?

yes that's what I get:



no database specified


Did I do somehting wrong???

I don't think so. I asked about the error message just to see if the script was running at all.
If those commands work properly when you run them from commandline, then there's something wrong with my script.
Or perhaps you'd need to check env in a new shell after you run the script before you'll see the changes.
Perhaps it's reading the numbers as numbers rather than strings? Doesn't seem so, but I can't think of anything else at the moment.
Just to humor me, could you change the "1" and "2" to "one" and "two", and see if it makes a difference (if the new shell thingy doesn't work)?

mikeshaw,

I did type:

$env

right after I run your script that how I find out it didn't change the env.

I did change from"1" to "one and "2" to "two", it doesn't work.

What I was getting at was you may have to open a new terminal and check your environment from that. It's possible that the changes won't affect your current bash session