Results 1 to 6 of 6

Thread: tnsnames.ora

  1. #1
    Join Date
    Dec 2003
    Posts
    1,074

    Unanswered: tnsnames.ora

    We're playing around with the tnsnames.ora file, trying to get failover to work successfully in 10g. In doing so, we noticed that there was a copy of tnsnames.ora on the database server.

    My understanding is that for an Oracle connection to be possible, a tnsnames.ora file on the client must be compatible with a listener.ora on the server.

    Why, then, would tnsnames.ora need to reside on the server?

    Thanks,
    Chuck

  2. #2
    Join Date
    Jan 2004
    Posts
    370
    Unless you make connections to remote databases from the server, use database links, or need to do a loopback to check out any Oracle Net problems, then you probably don't need one.

  3. #3
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    >My understanding is that for an Oracle connection to be possible, a >tnsnames.ora file on the client must be compatible with a listener.ora on the >server.
    You have an incorrect understanding.
    There is NO requirement that the TNSNAMES.ORA file on a client
    must have any lines in it which match what's on the server.

    Client A may have a single line entry to get to Server B in its TNSNAMES.ORA
    Server B could have a single line entry to allow it to connect to Server C.
    It all depends upon the operational requirements and how the DBA wants/needs to manage the environment.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  4. #4
    Join Date
    Dec 2003
    Posts
    1,074

    no?

    So, tnsnames.ora on the client doesn't have to be compatible with the listener.ora file on the server? Then how would you connect to the database? If the server entry didn't match up then you couldn't connect, as I understand it.

    -cf

  5. #5
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    >Then how would you connect to the database?
    By the TNSNAMES.ORA file containing all the necessary information;
    essentially duplicating the NAME=VALUE pairs that would normally be found in the LISTENER.ORA file.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  6. #6
    Join Date
    Apr 2002
    Location
    California, USA
    Posts
    482
    Quote Originally Posted by chuck_forbes
    So, tnsnames.ora on the client doesn't have to be compatible with the listener.ora file on the server? Then how would you connect to the database? If the server entry didn't match up then you couldn't connect, as I understand it.

    -cf
    No need for the server side tnsnames.ora compability with the client. The client uses TNS protocol to resolve its tnsnames.ora TNS alias to HOST, PORT, PROTOCOL and SERVICE_NAME. Once it gets this info from client tnsnames.ora contacts the listener service on the db server and establishes a db connection.


    HTH,

    clio_usa - OCP 8/8i/9i DBA

Posting Permissions

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