Re: question about statspack
Date: Wed, 12 Mar 2008 14:22:12 -0400
Statspack shows global aggregate data. It means that the numbers you see are numbers from *all* the sessions running on the server during the one-hour time you mention.
If you are not seeing any specific performance problems, I would not worry about it.
HOWEVER, there may be times when it is the cause of a problem. For example, let's say that you have a job (or user action) that has to finish in 5 seconds and it is not meeting that target. For example, it could be running for 6 or 7 seconds. If this same job is the *only* one that contributed to the calls to "SQL*Net message to client" (or even if it contributed most, say 2secs out of the 3secs), then it might warrant further investigation.
Again, if I were in your position, I would not worry about it if there are no specific problems that you see. BUT if there are performance problems, then I would trace (10046) those user actions and take it from there.
On Wed, Mar 12, 2008 at 9:18 AM, John Smith <john40855_at_gmail.com> wrote:
> I have a statspack report with this line as one of the wait events:
> SQL*Net message to client 7,255,516 0 3 0
> As you can see, the number of waits is very high, but the actual time is
> only 3 seconds in the course of an hour. Is this something I need to be
> concerned about?