Results 1 to 5 of 5
  1. #1
    Join Date
    Oct 2003
    Location
    Chicago
    Posts
    3

    Red face Unanswered: ORA-12535 connection error

    Hi !

    These are two days that I am trying to find out where this error comes from:

    I am trying to reach the database server from an Oracle client based outside the firewall. A TNSPING of the database works fine but a connection with SQLPLUS always brings the same error ORA-12535: connexion timed out.

    I have already put the USE_SHARED_SOCKET registry variable to TRUE and reboted the database server.

    My TNSNAMES is as follows :

    TEST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =(PROTOCOL = TCP)(HOST = myserver)(PORT = 1521))
    )
    (CONNECT_DATA =
    (SERVICE_NAME = TEST)(SERVER=DEDICATED)
    )
    )

    I checked the listener.log which is as follows:

    09-OCT-2003 14:29:14 * ping * 0
    09-OCT-2003 14:29:17 * (CONNECT_DATA=(SID=TEST)(SERVER=DEDICATED)(CID=(PR OGRAM=D:\ora81\bin\SQLPLUS.EXE)(HOST=ACHILLES)(USE R=Administrator))) * (ADDRESS=(PROTOCOL=tcp)(HOST=216.80.81.29)(PORT=41 68)) * establish * TEST * 0

    So it seems that the Oracle connection is OK. But the client does not get the information. What's more, all ports are opened through the firewall.

    BUT if I put a VPN between the client and the server, the connection works fine.

    Could anyone have already faced such a problem (and found any solution) ?

    Regards,

  2. #2
    Join Date
    Oct 2003
    Location
    Montreal
    Posts
    10
    I recall seeing something similar.
    I had the mts_dispatchers option commented out in my initSID.ora
    By commenting it I resolved my problem.

  3. #3
    Join Date
    Oct 2003
    Location
    Chicago
    Posts
    3
    No mts_dispatcher in it ...

  4. #4
    Join Date
    Oct 2003
    Location
    Montreal
    Posts
    10
    When looking for you error message in Oracle Documentation, this is what i get :

    Cause: The requested connection could not be completed within the timeout period specified by the CONNECT_TIMEOUT parameter in LISTENER.ORA. This error arises from the TNSLSNR.

    Action: Either reconfigure CONNECT_TIMEOUT to be 0, which means wait indefinitely, or reconfigure CONNECT_TIMEOUT to be some higher value. Or, if the timeout is unacceptably long, turn on tracing for further information.

    Your situation may occur when the routing between your server and the client is not optimal and therefore connection takes longer than your parameter allows it to.

  5. #5
    Join Date
    Oct 2003
    Location
    Chicago
    Posts
    3
    That did not change anything. How could I turn tracing on ?

Posting Permissions

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