Originally posted by anujpathak
use profile as mentioned below and set parameters to control the I/O like :-

LOGICAL_READS_PER_SESSION unlimited LOGICAL_READS_PER_CALL 100

example statement to create profile
read more in doc on profile

CREATE PROFILE clerk LIMIT
SESSIONS_PER_USER 2
CPU_PER_SESSION unlimited
CPU_PER_CALL 6000
LOGICAL_READS_PER_SESSION unlimited
LOGICAL_READS_PER_CALL 100
IDLE_TIME 30
CONNECT_TIME 480;



[Edited by anujpathak on 04-11-2002 at 07:04 AM]
I don't think that solves his problem. He wants queries longer than 2 minutes to be terminated. MAX_ESTIMATED_EXEC_TIME is the best candidate for that. He will not even bother with spending 2 minutes of CPU resources with using that parameter for Oracle will not start it if Oracle estimates that the query will take more than 2 minutes. But he needs to upgrade to 9i.