On Apr 24, 12:53=A0am, kerravon <kerra...@[EMAIL PROTECTED]
> wrote:
> We have an insert/update transaction that normally takes 0.2 seconds
> but
> sometimes takes as long as 16 seconds. =A0The granularity of statspack
> is 30
> minutes and that is too long to see if there was anything causing
> delays.
>
> Is there a way of getting Oracle to re****t a reason why any query
> takes
> more than 1 second?
>
> Thanks. =A0Paul.
Event 10046,level 12, will dump all waits to the trace file.
There are various methods to enable this event, and they are version
dependent.
You could of course issue the following code in an after-logon trigger
execute immediate 'alter session set events=3D'10046 trace name forever,
level 12';
--
Sybrand Bakker
Senior Oracle DBA
|
