Re: TNS_ADMIN environment variable

From: Ban Spam <ban-spam_at_operamail.com>
Date: Wed, 28 Aug 2002 02:15:13 GMT
Message-ID: <Xns9277C3DBFC621SunnySD@68.6.19.6>

"Terry Dykstra" <dontreply_tddykstra_at_forestoil.ca> wrote in news:zHsa9.4987$xc2.352581_at_news0.telusplanet.net:

> I recently came across a site where they set the TNS_ADMIN entry as an
> environment variable on their W2K machines. I always thought it
> should be set only as a registry entry under HKLM/software/oracle.
> Are there any reasons why you would use method above the other?
>
> --
> Terry Dykstra
> Canadian Forest Oil Ltd.
>
>

Another reason can be to allow for local/personal customization so that you can develop & test code against a "TEST" DB and leave the code unchanged when it goes into "production" status. For example the code may contain SQL similar to the following UPDATE DEST_at_PROD SELECT * FROM SOURCE_TABLE_at_REMOTE; By having a custom TNSNAMES.ORA file you could "re-direct" both REMOTE & PROD to a test DB on YOUR machince. Received on Tue Aug 27 2002 - 21:15:13 CDT