We have a number of windows servers running application with different Oracle clients (versions 10 & 11, 32bit 64 bit) that use a centralized network located TNSnames. Lets say z:\tns\tnsnames.ora
Im having an issue with a couple of them and I want to put SQLnet tracing on but if I put SQLnet tracing parameters on the network version of SQLnet.ora it will turn on tracing for all the clients connecting which I dont want
Is there anyway to give them a local version of SQLnet.ora from their local client homes while still have them use the network version of tnsnames.ora
I could point them to a local version of tnsnames just for this testing period while I trace and not so much of a problem to do this but interested to see could the SQLnet be separated from the tnsname.
AFAIK you can't separate tnsnames.ora and sqlnet.ora. But as you say you can create a local copy of the centralized one for your test system even overwrite TNS_ADMIN in your application shell/environment only.
Sqlnet.ora parameters are picked up from more than one location;
Depending on the nature of this "application", perhaps you could try this: in the client program's directory (where the .exe lives), create a sqlnet.ora file with your tracing parameters.