Re: Transaction table- Keep Pool
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Fri, 6 Aug 2004 15:18:40 +0100
On Fri, 06 Aug 2004 09:42:53 -0400, jaysingh1@xxxxxxxxxxxxx
<jaysingh1@xxxxxxxxxxxxx> wrote:
> Niall
>
> Really appreciate your response.
>
> We have indexes on all predicate columns in the where clause. Explain plan
> looks nice.
Your tkprof output shows that it is using an index on
business_country_id on profileduser and on profileuserid on
extendedattributes. You obviously know what the data is like better
than me, but that just looks like a quicker way to satisfy the joins
to me - nothing to do with filtering out records from the base
tables. You're not looking at an explain plan that shows a nice NL
plan are you?
> What we are thinking is that it is taking more time for any PIO so it
> 1) May be index fragmentation
I have no idea what you mean by this? Indexes don't get fragmented in
any meaningful sense of the word, at least in my understanding (and
assuming they aren't bitmap indexes which I know very little about).
> 2) is because of Hardware inefficiency ( We use SUN Storage for 8i 2 Node OPS
> - Raw device)
>
> Folks recommended that moving to EMC will give significan improvement with
> respect to IO.
Well your *max* wait for disk IO is 4cs and your average IO service
time is 2cs. EMC will be doing well to significantly improve on that
--
Niall Litchfield
Oracle DBA
http://www.niall.litchfield.dial.pipex.com
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
