Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Oracle server max response SQL statements

Oracle server max response SQL statements

Oracle server max response SQL statements


My company uses Sniffer portable for packet captures, and I'm troubleshooting an application that talks TNS between app/database.

My question is what are the exact metrics sniffer is using to calculate the SQL max response times?

Multiple packet captures confirm that the SQL max response times are minimal during normal operation however when users begin reporting slowness is coincides with substantial increases in these SQL response time statements in sniffer.

Our database folks are saying their servers are processing the requests in a timely manner even during slowness issues stating the way the application accesses the DB servers may be an issue. They said it works similar to Kronos in so far as it accesses the DB servers.

RE: Oracle server max response SQL statements

the best way is to identify a TNS/SQL/Slow Database symptom / diagnosis in one of your trace files. Drill into the detail and filter out the TCP connection using the wizzard stick.
Alt F3 and then find the specific diagnosis in the trace detail / decode window.
You will clearly see the delay in the delta time column.
ou can see the difference in transport delay (TCP delay) and database delay.
You will see the database request from the client and if the database is quick the database response will be immediate.
If the database / server is slow you will see the request from the client, and ACK from the server and then later you will see the databse response with the TCP Push bit set.
The time from the initial request till the Ack is the network delay.
The time from the initial request (or even the time from the ack) till the database response is the database delay.
Mark the Ack packet - the Relative Time column from the Ack packet till the database response will be your database response time.

So to answer your question, it is not a metrix that sniffer use, it is an actual measurement from when the request was sent till the reply was received.
You can see the difference in summary in the Connection / Detail - view the Avg Ack time compared to the Max App Response
Hope it helps ...

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close