firstname.lastname@example.org wrote:But beware that in all *nix, everything is case sensitive, and those environment variables should be upper case:
Thank you for your help it's helpful for me.......
959855 wrote:Why are you hijacking someone else's thread that is well over 2 years old?
Once I set ORACLD_UNQNAME, then I need to restart or not, to make changes?
rajindrar wrote:That's FIVE old and unrelated threads you've pulled up to post this same response .... whether or not the action you recommend has anything at all to do with the dormant thread you resurrected.
In my experience the oracle_unqname error is trigger by the Oracle database installation process.
The Time Zone in the installation computer should be set to a 'Oracle valid' time zone like London, UK.
It seem like there is a time zone match up between the Installation computer and the Oracle database. When the computer time zone is set to an 'unkown' time zone it messes up the installation.
Do a clean installation with the computer time zone set to a prominent time zone. This works on Windows 7 and Windows Server 2008. May work with other OS.