Re: DBA Job Functions

One of the longest procedures I had to tune was process of depersonalization of personal data on big bank database. It lasted more than 3 days when I was asked to tune it first time. Just imagine how huge trace files could be...

On Thu, Mar 8, 2018 at 5:18 PM, Sayan Malakshinov <xt.and.r_at_gmail.com> wrote:

> Mladen,
>
>
>> The whole confusion comes from the fact that we are talking about two
>> different processes.
>
>
> First of all, original question was about troubleshooting. Secondly, it
> doesn't matter what are you talking about, sql trace is still sql trace and
> it still has cons I mentioned previously.
> It's like to use a magnifying glass for any question about unknown
> subject, though you may asked about spectrographic analysis or just find
> a color...
> Moreover usually tuning includes not only simple single session wait
> events analysis, but also performance testing, load testing, stress testing
> using special tools like HP Loadrunner, Jmeter, etc...
> Often such tests are longer than 4-6 hours and sql trace adds notable
> overhead for them. Using real-time tools you can find the problem much
> earlier and you can stop test or fix the issue to save a time. It's very
> important because such testing contains several iterations. It's ok if you
> work on per-hour basis, in other cases it's better to improve own
> productivity.
>
> --
> Best regards,
> Sayan Malakshinov
> Oracle performance tuning engineer
> Oracle ACE Associate
> http://orasql.org
>

-- 
Best regards,
Sayan Malakshinov
Oracle performance tuning engineer
Oracle ACE Associate
http://orasql.org

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