Does SQLNET.ORA is optional on the server side or it is a must have and why ?
Also How can I flush client cach when I use names server connectivity ? ( sdns.ora file ??? )
Printable View
Does SQLNET.ORA is optional on the server side or it is a must have and why ?
Also How can I flush client cach when I use names server connectivity ? ( sdns.ora file ??? )
sqlnet.ora is the file that decides the how to solve the connectivity to the server. So, its a must on the server side.
Sam
Is it also a must on client side ??
Sam,Quote:
Originally posted by sambavan
sqlnet.ora is the file that decides the how to solve the connectivity to the server. So, its a must on the server side.
Sam
Is it really a must on the server side?
I seem to be able to start a DB w/o the sqlnet.ora file (8.1.7 on Win2k server) :)
-amar
Folks,
Thanx for pointing out "must" on my previous posting. Normally it is used to fine tune the sqlnet connection. There you would specify the tuning parameters like type of sql authentication that you would like to use, for names. in the case you are using the oracle names server.
So, I personally would consider it to be a must option, to preserve the consistency, over all installation. So, having it and leaving it off, is I presume an individuals choice. ;)
Sam