Results 1 to 8 of 8
  1. #1
    Join Date
    Mar 2007
    Posts
    2

    Exclamation Unanswered: How to solve this connect problem

    Dear All
    >
    > I have one problem. i have installed windows 2000 sever and oracle 8i
    (8.1.7) on sever.
    > from the sever i am able to connect to database.
    > but from the client i am not able to connect to database. it gives me
    error like 'ORA - 12203 TNS : Unable to Connect Destination'.on server
    side listener seveive is up and running . i also get the reply in ping
    command from the client side. tnsping command also reply ok. so i cant
    understand the probelem.

  2. #2
    Join Date
    Jan 2005
    Posts
    362

    Connection

    I found this.
    This may help you.
    Dimis

  3. #3
    Join Date
    Jan 2004
    Location
    Croatia, Europe
    Posts
    4,094
    Provided Answers: 4
    If I understood you correctly, Oracle 8.1.7 was installed on the server which run under MS Windows 2000. Right? Is there any reason for you to install desupported Oracle version? (Not that it can't work, but ...). Also, if I'm not wrong, this combination of operating system and database version is not certified by Oracle.

    What is Oracle client version?

    Text found on dimis2500's link says "not to modify TNSNAMES.ORA"; well, I must admit I don't follow this instruction. How would I add any new database alias if I can't modify this file?!?

    Could you post SQLNET.ORA, TNSNAMES.ORA and LISTENER.ORA file? Perhaps we'll see something in there.

    BTW, this is what Oracle says about the error:
    Quote Originally Posted by Oracle
    ORA-12203: TNS:unable to connect to destination

    Cause: Invalid address specified or destination is not listening. This error can also occur because of underlying network or network transport problems.

    Action: Verify that the net service name you entered was correct. Verify that the ADDRESS portion of the connect descriptor which corresponds to the net service name is correct. Ensure that the destination process (for example the listener) is running at the remote node.

  4. #4
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,799
    Provided Answers: 11
    Is the listener service running?

  5. #5
    Join Date
    Jan 2004
    Location
    Croatia, Europe
    Posts
    4,094
    Provided Answers: 4
    I believe it is; at least, that's how I translated this sentence:
    Quote Originally Posted by fss_10
    on server side listener seveive is up and running

  6. #6
    Join Date
    Nov 2006
    Location
    Indianapolis
    Posts
    90
    That link suggesting not to modify tnsnames.ora - is obviously just instructions specific to that university...

    I used to have problems with older Oracle versions, 8i(?) and back, where hand-edited tnsnames could foul things up. Wouldn't happen every time, but when it did nothing could make it connect, except rebuilding TNS using the manager app.

    Since you're on an old version, you might try creating it from scratch...

  7. #7
    Join Date
    Mar 2007
    Posts
    2
    Hi all this problem accure when we move to another building befor every thing is run fine when we try to link the client to the server we found this problem, every thing dosnt change expect the network i mean the ip's address for the server and for the client also the group policy but i have no idea about them thanks for all one try to help me i will try what you say
    yes,in the client side we have developer 2000

  8. #8
    Join Date
    Jan 2004
    Location
    Croatia, Europe
    Posts
    4,094
    Provided Answers: 4
    IP addresses changed, you say? How does TNSNAMES.ORA look like (I already asked you to post those files)? If you referenced host by IP address (and not its alias), no wonder you can't connect.

Posting Permissions

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