TNSPING is very slow
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: TNSPING is very slow

  1. #1
    Join Date
    Mar 2008
    Posts
    2

    TNSPING is very slow

    Dear All,

    We are using Oracle 8i (8.1.7) database in Production. Today suddenly we got a complaint from the production is response time is very low. When we tried to ping the listner with tnsping it is very long time to give a responce. Approximatly it is taking 250000 msc. What may be the problem in this, we tried with restarting the server but problem is not solved.

    Please help us to solve this problem.

    Thanks in advance.

    Kumar

  2. #2
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,554
    your problem is not the server, the problem is the network.
    do a tracert from a client to the database server and see where the bottleneck is.
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

  3. #3
    Join Date
    Mar 2008
    Posts
    2

    tracrt output

    Thank you very much for your reply.

    Find the output from the tracert

    D:\oracle\ora81\bin>tracert -d -h 20 192.168.0.4
    Tracing route to 192.168.0.4 over a maximum of 20 hops
    1 3 ms <1 ms <1 ms 192.168.0.4
    Trace complete.
    D:\oracle\ora81\bin>tracert -d -h 20 192.168.0.4
    Tracing route to 192.168.0.4 over a maximum of 20 hops
    1 <1 ms <1 ms <1 ms 192.168.0.4
    Trace complete.
    D:\oracle\ora81\bin>tracert -d -h 20 192.168.0.4
    Tracing route to 192.168.0.4 over a maximum of 20 hops
    1 <1 ms <1 ms <1 ms 192.168.0.4
    Trace complete.
    D:\oracle\ora81\bin>tracert -d -h 20 192.168.0.4
    Tracing route to 192.168.0.4 over a maximum of 20 hops
    1 <1 ms <1 ms <1 ms 192.168.0.4

    help will great appriciated...

    kumar

  4. #4
    Join Date
    Nov 2000
    Location
    Pittsburgh, PA
    Posts
    3,975
    You should look at your tnsnames.ora file and check to see what the tns entry looks like. If something changed with the dns server and its timing out. You might be able to either hard code the ip, or fins a better way of getting the server name resolved. Did the database server name change recently? What could have changed on your network?
    this space intentionally left blank

  5. #5
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,554
    I notice you are using IP address in your tracert; is TNSNAMES entry also using IP address?

    If TNSNAMES entry is using DNS name please do tracert using DNS names.

    Either way, if your TNSNAMES entry is using DNS name and tracert on DNS name looks ugly go with Gandolf989 solution and replace DNS name with actual IP address.
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

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