Depending on the application, couldn't
these large pauses be performance problems in the client
program? Not a server tuning issue nor a SQL*Net tuning issue at
all? For example, if the client program was pausing a long time between
FETCH commands, processing previously fetched data? Or would
that just be accounted for under "SQL*Net message from client"
events?
|
- how to reduce SQL*Net more data to client wait event Suhen Pather
- Re: how to reduce SQL*Net more data to client w... Jakob Hammer-Jakobsen
- Re: how to reduce SQL*Net more data to client w... Anjo Kolk
- RE: how to reduce SQL*Net more data to client w... John Kanagaraj
- Re: how to reduce SQL*Net more data to client w... Anjo Kolk
- Re:RE: how to reduce SQL*Net more data to clien... dgoulet
- Re: how to reduce SQL*Net more data to client w... Tim Gorman
- Re: how to reduce SQL*Net more data to client w... Suhen Pather
- RE: how to reduce SQL*Net more data to client w... Johnson, Michael
- Re: how to reduce SQL*Net more data to client w... Anjo Kolk
- RE: how to reduce SQL*Net more data to client w... Johnson, Michael
- Re: how to reduce SQL*Net more data to client w... Tim Gorman