Re: Tracing query inside procedure without 10046

From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Fri, 4 Aug 2023 14:30:45 -0400
Message-ID: <a49d3a08-0c71-3b31-d4b5-010f2c63bf91_at_gmail.com>



On 8/1/23 01:25, Krishnaprasad Yadav wrote:
> DearĀ Gurus,
>
> currently working on slowness issue of procedure which is part of
> procedure
> like : proc_name.subproc_name , over hereĀ i need to figure out the
> query related to subproc_name and not by using 10046 trace .

Well, there are two known application tuning methods: Method-R (my personal preference) and Method-C, based on the buffer cache hit ratio (BCHR). Method-R is based on the 10046 trace. Since you don't want that, the only thing you can fall back to is BCHR witchcraft. You should also collect 4-leaved clover, mandrake, black cats and similar, should you decide to use BCHR. DBMS_HPROF can tell you how much time is your package spending in which procedure, but it will inevitably leave out event based stuff. AWR reports can help with some of that, but, essentially, there is no substitution for SQL trace.

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Aug 04 2023 - 20:30:45 CEST

Original text of this message