Error Message Solution
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: Error Message Solution

  1. #1
    Join Date
    Jul 2003
    Posts
    53

    Thumbs up Error Message Solution

    Connecting...ORA-12535: TNSperation timed out
    The test did not succeed.

    Some of the information you provided may be incorrect.
    Press Back to review the information provided for net service name, or Change Login to change username.
    anu

  2. #2
    Join Date
    Dec 2002
    Location
    India
    Posts
    34
    Hi ,

    This info is from Metalink!

    NOTE: PLEASE READ

    Because of ASCII diagrams, this particular document is best viewed
    with a Courier New or Lucida Console font.
    This is normally the default.

    In MS Explorer:
    Set the Plain Text Font to Courier New or Lucida Console

    In Netscape:
    Set the Fixed Width Font to Courier New or Lucida Console 10pt.
    Click "Use my default fonts, overriding document-specified fonts"
    ---------------------------------------------------------------------------



    TROUBLESHOOTING GUIDE FOR ORA/TNS-12535: OPERATION TIMED OUT ERRORS
    ===================================================================


    Table of Contents:

    -Introduction
    -Quick Checks
    -Diagnosing Common Errors
    -Generating & Interpreting Trace Files
    -Q&A
    -Additional Resources


    Introduction:
    =============

    This guide is designed to assist in determining what steps to take to
    troubleshoot and correct ORA-12535/TNS-12535 errors.

    This document is based on reported errors and fixes.
    Where possible, the note numbers are included as a cross reference to reduce
    duplication. It also includes some information on why the error has occurred
    and why the fix works.

    + The TNS-12535 or ORA-12535 error is normally a timeout error associated
    with Firewalls or slow Networks.
    + It can also be an incorrect listener.ora parameter setting for the
    CONNECT_TIMEOUT_ value specified.
    + In essence, the ORA-12535/TNS-12535 is a timing issue between the client and
    server.

    Please be sure to also read documentation on other troubleshooting guides,
    such as "Troubleshooting Tips from the Field - Part # A67440.


    Quick Checks:
    =============

    - Ensure that your Client and Server platforms and versions are supported and
    within Oracle's recommended guidelines.
    - Make sure that any non-supported issues, such as Soft links, shared config
    files, etc., are removed before looking into this document.
    - If you are running Oracle Names Server, then setup a temporary tnsnames.ora
    file and edit the sqlnet.ora file to reflect (TNSNAMES) for the
    names.directory_path.
    - If you are running MTS (Multi Threaded Server), then try the same
    connection with (SERVER=DEDICATED) in the tnsnames.ora alias.


    Diagnosing Common Errors:
    =========================

    From Note:21469.1
    -----------------
    Error: ORA-12535 / TNS-12535
    Text: TNSperation timed out
    ---------------------------------------------------------------------------
    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.


    1. Find out if you are going through any Firewalls or Routers.
    If you are, then see Note A below.

    2. Try to "ping" the ip address or hostname from the client.
    Check the timing response and see if it is acceptable.
    If it is not, then you may need to increase the
    CONNECT_TIMEOUT_ value in the listener.ora file on the
    Server.
    Doing this will correct the connectivity problem, but may be masking the
    real problem of the physical network.

    (See the Sqlnet / Net8 Administrators guide for details on how to make these
    changes)


    Note A
    ------
    1a. If you are going through a Firewall, and your server platforms are UNIX,
    then you must ensure that the port being listened on is open, unless you
    are running the Firewall vendor's Proxy Server, in which case this will
    allow connectivity.

    1b. If you are not running the Firewall vendor's Proxy, and the port is not
    open, then you will have a refusal from the outside into the Firewall zone.

    2. If you are going through a Firewall, and your server platforms are NT,
    then you must ensure that the port being listened on is open as well as
    setting up a SQL*Net/Net8 Proxy, such as Net8 Connection Manager, if none
    is provided by the Firewall vendor.
    The reason is that, even though the port is open, the TCP layer will
    REDIRECT the port to another port.
    This is due to Winsock2 workings under Microsoft.

    (Please see the following notes on Firewalls and related errors - 68652.1).
    (Also see Oracle's White Paper on Firewalls).


    Generating & Interpreting Trace Files:
    ======================================

    A tracing technique that can be incorporated to try and determine what is
    happening, can be outlined as below.

    - Set-up client sqlnet tracing and listener tracing, both set to level 16.
    - What you should find is that a SEND request with the client's address
    will be sent out.
    - Instead of a receive packet being returned with a confirmation address,
    the error will be shown.
    - The client trace will look similar to the following:


    nspsend: packet dump
    nspsend:00 7D 00 00 01 00 00 00 |.}......|
    nspsend:01 36 01 2C 00 00 08 00 |.6.,....|
    nspsend:7F FF 7F 08 00 00 00 01 |........|
    nspsend:00 43 00 3A 00 00 08 00 |.C.:....|
    nspsend:00 00 00 00 00 00 00 00 |........|
    nspsend:00 00 00 00 4C 16 00 00 |....L...|
    nspsend:2C 7A 00 00 00 00 00 00 |,z......|
    nspsend:00 00 28 44 45 53 43 52 |..(DESCR|
    nspsend:49 50 54 49 4F 4E 3D 28 |IPTION=(|
    nspsend:41 44 44 52 45 53 53 3D |ADDRESS=|
    nspsend:28 50 52 4F 54 4F 43 4F |(PROTOCO|
    nspsend:4C 3D 74 63 70 29 28 48 |L=tcp)(H|
    nspsend:4F 53 54 3D 31 30 2E 32 |OST=10.2|
    nspsend:2E 32 31 30 2E 32 32 29 |.210.22)|
    nspsend:28 50 4F 52 54 3D 37 37 |(PORT=77|
    nspsend:37 30 29 29 29 00 00 00 |70)))...|
    nspsend: normal exit
    nscon: exit (0)
    nsdo: nsctxrnk=0
    nsdo: normal exit
    nsmal: entry
    nsmal: 2048 bytes at 0x405985e0
    nsmal: normal exit
    nsdo: entry
    nsdo: cid=3, opcode=68, *bl=2048, *what=9, uflgs=0x0, cflgs=0x3
    nsdo: rank=64, nsctxrnk=0
    nsdo: nsctx: state=2, flg=0x4205, mvd=0
    nsdo: gtn=0, gtc=0, ptn=10, ptc=2047
    nscon: entry
    nscon: recving a packet
    nsprcvs: entry
    nsbal: entry
    nsbgetfl: entry
    nsbgetfl: normal exit
    nsbal: normal exit
    nsprcvs: transport read error
    nsprcvs: error exit
    nserror: entry
    nserror: nsres: id=3, op=68, ns=12535, ns2=12560; nt[0]=505, nt[1]=0, nt[2]=0
    nscon: error exit
    nsdo: nsctxrnk=0
    nsdo: error exit
    nsmfr: entry
    nsmfr: 2048 bytes at 0x405985e0
    nsmfr: normal exit
    nscall: unexpected response
    nsclose: entry
    nstimarmed: entry
    nstimarmed: no timer allocated
    nstimarmed: normal exit
    nsdo: entry
    nsdo: cid=3, opcode=98, *bl=0, *what=0, uflgs=0x40, cflgs=0x2
    nsdo: rank=64, nsctxrnk=0
    nsdo: nsctx: state=2, flg=0x4201, mvd=0
    nsbfr: entry
    nsbaddfl: entry
    nsbaddfl: normal exit
    nsbfr: normal exit
    nsbfr: entry
    nsbaddfl: entry
    nsbaddfl: normal exit
    nsbfr: normal exit
    nsdo: nsctxrnk=0
    nsdo: normal exit
    nsclose: closing transport
    nttdisc: entry
    nttdisc: Closed socket 27
    nttdisc: exit
    nsclose: global context check-out (from slot 3) complete
    nsnadisc: entry
    nsbfr: entry
    nsbaddfl: entry
    nsbaddfl: normal exit
    nsbfr: normal exit
    nsmfr: entry
    nsmfr: 1668 bytes at 0x40597f50
    nsmfr: normal exit
    nsmfr: entry
    nsmfr: 416 bytes at 0x4041fbf0
    nsmfr: normal exit
    nsclose: normal exit
    nscall: error exit
    nricdt: Call failed.


    - On the listener side, there may be a few different traces.

    1. If the Server is on NT and the Firewall has it's port open, then the
    following happens:
    - The client connection request is received by the listener.
    - The listener (from TCP stack) will send a redirect of the port.
    - No other client information will be seen and the listener will eventually
    shut down the connection request, also with a timeout or client gone away.

    2. If the firewall does not have the valid port open, then the following
    happens:
    - No client information can be seen in the listener trace and the listener
    will be waiting on any new connections.


    Additional Resources:
    =====================
    Note:21469.1
    Note:68652.1

    Thanks
    Sridhar

  3. #3
    Join Date
    Sep 2000
    Location
    Chennai, India
    Posts
    865
    As you are using Net8 Configuration Assistant, you need to give the right values for the various params, for the test connection to work.

    Do the following:

    1. For 'Service Name', provide database name.

    2. For 'Network Protocol', select TCP.

    3. For 'Host name', give the ip of the machine where the database server is installed.

    4. For 'Port number', use the standard 1521.

    Now, test connection. Be sure to check if your listener is running. What version of Oracle and what OS are u using?

    HTH.

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