topic Oracle Database auditory in Operating System - HP-UX

Oracle Database auditory

jpcast_real — Thu, 01 Sep 2005 00:53:00 GMT

Hello,

I have an Oracle 9i running over hp-ux 11i .Many applications use this database and I am quite sure that any of them is making a really bad query which blocks my system . I must know what kind of queries this application makes . Is is possible to the db in auditory mode or something like that ?? How can I get a log file which tell me which transation has been executed in each moment??

Thanks

Re: Oracle Database auditory

Alex Lavrov. — Thu, 01 Sep 2005 01:32:04 GMT

You can enable trace on some session and then examine it. Not very comfortable and requires some skills to understand it, you can see here how to do it:

http://www.google.com/search?ie=UTF-8&oe=UTF-8&q=oracle+trace+session

Or, the better option, if your company have some money, it's a good idea to buy monitoring tool. There are some great tools available like Precise (originaly from Israel, then Veritas, now Symantec), very very very good and also very expensive (can reach 80K) and there are some other less expensive, but also less featured by Quest (the father of Toad).

Alex.

Re: Oracle Database auditory

Yogeeraj_1 — Thu, 01 Sep 2005 02:16:28 GMT

hi Javier,

Look into the Statspack tool provided with Oracle.

If you take 15 minutes snap at the "peak" period, you should be getting a quite informative report on your database performance and what major problem areas exists on your system.

hope this helps!

kind regards
yogeeraj

Re: Oracle Database auditory

Jean-Luc Oudart — Thu, 01 Sep 2005 05:12:22 GMT

Javier

find attached a document from Oracle Metalink : Note:262946.1 "Performance Issues After Increasing Workload"

Regards
Jean-Luc

Re: Oracle Database auditory

Ariel Cary — Fri, 02 Sep 2005 08:47:34 GMT

Javier

You can take a look at v$sql. Zero in on buffer_gets and elapsed_time to find candidates for excesive LIO.
PIO is bad, but LIO is not that good. So if you find too much LIO for a particular query that could indicate the query is executing an inefficient plan, and usually a suitable index would solve this.

HTH,

ARC