"Robert" <grobert@azet.sk> wrote in message news:<bqerou$ccb$1@news.telecom.sk>...
> OK. I will try what you have sugested. Seems it is better idea.
>
> Thanks a lot
> Robert

typically the poorest running queries, the ones that cause a slowdown
have the highest cache/hit ratio or have a ton of sorting and your
sort_area_size is too small.

Its typically the first one. you will often have a small number of
VERY bad queries that do tons of logical I/Os. This causes contention
on the latches in the buffer cache and slows everything else down.

when you run statspack, you can get the most resource intensive
queries. Niall's method of contacting users is a good idea, but you
should also run statspack. it may be a few really bad queries slowing
everything down. Statspack will help to identify them.