Re: How to tune Oracle database 10.1.0.3.0 on slow performance
Date: Wed, 9 Jan 2008 14:34:08 -0800 (PST)
On Jan 9, 12:15 pm, EdStevens <quetico_..._at_yahoo.com> wrote:
> On Jan 9, 3:02 am, pejantan4u <pejanta..._at_gmail.com> wrote:
> > thanks for ur response.
> > On Jan 9, 3:49 pm, Robert Klemme <shortcut..._at_googlemail.com> wrote:
> > > On Jan 9, 9:33 am, pejantan4u <pejanta..._at_gmail.com> wrote:
> > > > we're running Oracle 10.1.0.3.0 on Linux Redhat ES 4, 12GB memory.
> > > > we are testing application with 50user+ that connect into the database
> > > > oracle 10.1.0.3.0 and i saw graphic performance on my EM, it looks ok.
> > > > and then on top sql, few queries showed percentage 44% and 60%, i
> > > What percentage? Did you look at the execution plans? Why do you say
> > > it looks ok and then you say it isn't? Are there complaints from
> > > users?
> > i saw it on EM in Top SQL section. i said ok when i saw the
> > performance of database on EM performance section, but when i saw in
> > Top sql section, there are few queries that show large activity
> > percentage on EM. Users complaints about, why the database took a long
> > time, when they run the application.
> > > > tried to run the sql tuning advisor but oracle only recomend gather
> > > > statistic, but i think this wasn't enough. what should i do ? could
> > > > anyone help me
> > > Do you _think_ that it was enough or do you _know_ it?
> > I think, because i don't know for sure.
> > > > and in this case of situation, what kind of tuning method that you
> > > > guys recomend, and how the solution beside using ADDM, coz i have
> > > > tried to use ADDM and i still couldn't find the solution
> > > I'd probably get myself a decent book on Oracle Tuning (there are
> > > quite a few out there but you can find recommendations in this group)
> > > and go from there.
> > > Kind regards
> > > robert
> Others have given some good suggestions, but I'd also like to point
> out that it doesn't really appear that you have identified that you
> actually *have* a problem. All you have really presented is the fact
> that OEM is showing you some stuff in the 'top SQL' section. Of
> course, there will always be sql statements reported there. In even
> the most impossibly well designed and well coded system there is
> always a *worst performing* statement, just as there is always a *best
> performing* statement. If you take the absolutely best possible
> course of action to resolve your 'worst performing' statement, some
> other statement will, by definition, become your 'worst performing'
> statement. This does not, of itself, indicate a problem
He did say user complaints. Charles told him to pick a complaining user and look closely at that. In other words, the OP has identified some possibilities, now he needs to drill down to the likely suspects. Eventually the OP should be able to figure out if the top sql is normal or not, but you are right, you can't tell just from such a list. That's just the intelligence you have to apply to use the tools correctly.
-- @home.com is bogus. macs are perfect in every way. http://quickbooksgroup.com/webx/forums/mac/1917 not!Received on Wed Jan 09 2008 - 16:34:08 CST