Updating tnsnames ora
(The databases which need to be configured are normally in flux, we'd like a dynamic way of updating the clients oracle configuration.) Two problems: 1.If we modify the either of these files outside of the SQLNet Easy Configuration utility the file(s) are marked as invalid, and the next time you do use the try to use the utility the changes the installtion program made are lost. Also it's a time consuming task to parse through this file and determine if an entry for a database already exists in the file, and if so to update the entry correctly with new information.If you do not change that file as well, then whenever you start SQL*Net Easy Configuration, your changes to tns_will simply be lost!However, if you change this file and then start SQL*Net Easy Configuration and make some dummy changes, then your changes will be interpreted as well.Added: Filemon does not work with newer Windows versions, so you might have to use Process Monitor.Shouldn't it always be "$ORACLE_ HOME/network/admin/tnsnames.ora"? Then you can just do "echo $oracle_ home" or the *nix equivalent. Which reminds me, there's another monkey wrench in the works called TWO_ TASK According TNS_ADMIN is an environment variable that points to the directory where the SQL*Net configuration files (like and tnsnames.ora) are located. There's the agent home and client home, just to name 2, that have their own network/admin directory.
Remember to set your filters so you are not overwhelmed by the chatty file system traffic.
I know there is already a TNSNames file in use on the PC.
I'd like to add mine to it during the installation and setup. I would trust this tool more than editing the TNSNAMES.
Hmmm, possibly there is even a command line utitlity to actually process that file, as SQL*Net Easy Configuration is really run by Oracle Installer.
it does not have the connection name in the drop down. I've tried updating Environment Paths and Registry keys but still can't find a way to get ODBC to see it in the drop down.