DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: sqlnet.ora

  1. #1
    Join Date
    Nov 2000
    Posts
    416
    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 ??? )
    An ounce of prevention is worth a pound of cure

  2. #2
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    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
    Thanx
    Sam



    Life is a journey, not a destination!


  3. #3
    Join Date
    Nov 2000
    Posts
    416
    Is it also a must on client side ??
    An ounce of prevention is worth a pound of cure

  4. #4
    Join Date
    Mar 2001
    Posts
    314
    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
    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

  5. #5
    Join Date
    Oct 2000
    Location
    Saskatoon, SK, Canada
    Posts
    3,925
    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
    Thanx
    Sam



    Life is a journey, not a destination!


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width