Re: seeding code into awr in 11g r2

>
> I think it probably fairly common to see a few important statements in an
>
> application that don't use enough resources to appear in an AWR report, but
>
> which are sufficiently important that you want to keep track of them. This
>
> is particularly relevant if there is some chance of small changes in
>
> execution plan that lead to intermittent changes in performance that are
>
> noticed by the users - even when the effect still doesn't result in capture
>
> by the AWR.
>

Thanks, Jonathan. That's a good point and I appreciate the information.

-Justin Received on Mon May 20 2013 - 06:29:44 CEST