RE: Long Parse Time

Very interesting thread. Most interesting was that Ric from Hotsos had
troubles gleaning why the parse time was so long from the 10053 trace file.
I'm not knocking Ric and I'm a firm believer in Method-R and kudos for him
coming to the list looking for an answer, but the thought of then having to
delve into stack traces and then pick some profiler aggregator or even write
my own gives me nightmares and at the end of the day it still comes down to
dropping a hint in place.

I am just extremely thankful for guys like Tanel/Ric and all the other
oracle gurus for making my job easier. I feel like my dad (small city
veterinarian) who told me there were lots of better/smarter vets than him
working on making the profession better so he could do a better job in his
small practice) and that it was his job to keep abreast of what they were
doing and how he could apply it.

So, now I condense this thread into a note and index it via google and add
it to my lexicon and continue to try and do my job better with the help of
everybody out there.

Mike
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Tanel Poder
Sent: Thursday, May 07, 2009 7:09 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: Long Parse Time

Again, if parsing takes minutes or tens of seconds of CPU time then you're
hitting a bug or someone has fiddled with undocumented parameters! Parsing
should not take that long! 

Yes one way is to try to disable "this and that" in hope that the problem
goes away, but the SYSTEMATIC approach would be seeing WHERE the parsing
TIME is spent!




--
http://www.freelists.org/webpage/oracle-l


Other related posts: