Re: Basic query tracing and profiling question...

From: Brian K <brikeener_at_geemail.invalid>
Date: Tue, 17 Apr 2007 20:36:52 GMT
Message-ID: <EdaVh.441159$rN.283702@fe09.news.easynews.com>

sybrandb_at_hccnet.nl wrote:
> On Tue, 17 Apr 2007 19:23:57 GMT, Brian K <brikeener_at_geemail.invalid>
> wrote:
>

>> So, you CAN'T tell me how to identify the currently executing queries?
>>
>> Because, on a one-user test system with a relatively small database, I 
>> don't think I'm really concerned about the rest.

>
> Obviously he can. But he is trying to point out that tuning those
> queries won't help much, as your database configuration runs on too
> few spindles.
> If it really is an one-user test system I should really get concerned
> about the rest. Likely it just won't work ever with multiple users
> connected.
>
> As to your request: v$sqlarea holds all the pertinent data. But of
> course running statspack, forbidden by the vendor (and what has a
> vendor to do with a test system) would identify them right away.
>

v$sqlarea; thank you for your answer.

I grabbed the queries directly referencing the tables in question, and using this I will hopefully eliminate the possibility of missing indexes on this table as a source of the problem.

And this is a one user test system, which is a mirror of production.

There's no doubt that the server has some serious design flaws, that's evident even to my non-Oracle expertise, but I really wasn't looking for an overall critique of the system as much as I was looking for assistance with identifying a specific set of data.

"Fix your system first" is not a remotely helpful response to a simple question. The incoming oracle DBA will "fix our system" when he/she gets here, in the meantime I'm under pressure from the powers-that-be to do SOMETHING right NOW. Received on Tue Apr 17 2007 - 15:36:52 CDT