$ORACLE_HOSTNAME is incorrect

orclrunner

Oracle database 11.2.0.1

[email protected] ~]$ echo $ORACLE_HOSTNAME
dub-ImrORA2.dub-ImrORA2.americas.epicor.net

This is incorrect. Should be:

dub-ImrORA2.americas.epicor.net

Listener file:

listener.ora
LISTENER=(ADDRESS=
                (PROTOCOL=TCP)
                (HOST=dub-ImrORA2.americas.epicor.net)
                (PORT=1521)
         )

ADR_BASE_LISTENER = /u01/app/oracle/product/11.2.0 

/etc/hosts

10.20.0.88   dub-ImrORA2.americas.epicor.net   dub-ImrORA2

[[email protected] ~]$ hostname
dub-ImrORA2

When I try to change the value of $ORACLE_HOSTNAME to the correct value it gets reverted back to the original value. This is causing problem with OEM.

[[email protected] ~]$ export ORACLE_HOSTNAME=dub-ImrORA1.americas.epicor.net
[[email protected] ~]$ echo $ORACLE_HOSTNAME
dub-ImrORA1.americas.epicor.net
[[email protected] ~]$ exit
[[email protected] ~]#
[[email protected] ~]# su - oracle
[[email protected] ~]$ echo $ORACLE_HOSTNAME
dub-ImrORA2.dub-ImrORA2.americas.epicor.net

L-MachineGun

Have you checked the (dot).profile or (dot).bash_profile files?

Maybe there is where it's changed.

L-MachineGun

Have you checked the (dot).profile or (dot).bash_profile files?

Maybe there is where it's changed.

orclrunner

That was it!

The .bashrc file was the problem.

Aman....

Yep. Just to clarify for anyone reading it in the future, this environment variable doesn't get any default value but whatever the DBA would set for it in the bash profile. So whatever one sets in the .bash_profile (or any such file) for this variable, Oracle would be using the same. If you think that the name chosen is incorrect, modify the name in the profile file.

Aman....

teachMySelf

"export" would set the environment variable. it will overpower the environment variable in your profile file. BUT, the scope of "export" variable is limited to your session. The moment you exit out of the session, your exports are lost and profile kicks in.

Thanks

Aman....

teachMySelf wrote:

"export" would set the environment variable. it will overpower the environment variable in your profile file. BUT, the scope of "export" variable is limited to your session. The moment you exit out of the session, your exports are lost and profile kicks in.

Thanks

I am aware about what export (or set) would do and explaining that wasn't the point of my reply.

Aman....

teachMySelf

Your Point was to clarify some details for future references. My Point was to clarify your point.

EdStevens

teachMySelf wrote:

"export" would set the environment variable. it will overpower the environment variable in your profile file. BUT, the scope of "export" variable is limited to your session. The moment you exit out of the session, your exports are lost and profile kicks in.

Thanks

The scope of ANY environment variable is limited to the session in which it is set.  The moment you exit out of the session there is nothing for which the profile to "kick in".  The next time you establish a session, certain files are executed as a part of setting up the environment for the session.  First, /etc/profile, then the user's .bash_profile (or simply .profile on some unix's).  The difference between setting a variable with "export somevariable=somevalue" and simply "somevariable=somevalue" is that variables set with "export" will be marked for automatic export to the environment of subsequently executed commands.

teachMySelf

Awesome! Thanks for the detailed clarification.