Re: Index as hot block

Hi
 

The application also uses selects with range predicates and that pretty much rules out a reverse key indexes.
 

The index block is hot because there are multiple sessions which perform a insert into this table.
 

• On Mon, 10/5/10, troach_at_gmail.com <troach_at_gmail.com> wrote:

From: troach_at_gmail.com <troach_at_gmail.com> Subject: Re: Index as hot block
To: hrishys_at_yahoo.co.uk
Date: Monday, 10 May, 2010, 13:36

Try a reverse key index.
Sent from my Verizon Wireless BlackBerry

From: hrishy <hrishys_at_yahoo.co.uk>
Date: Mon, 10 May 2010 11:08:52 +0000 (GMT) To: <oracle-l_at_freelists.org>
Subject: Index as hot block

Hi
 

I have a partitioned table called mytable (a,b,c,d,e,f) partitioned by range on column a.

I need to enforce a unique constraint
currently the uniqueness is enforced by creating a locally partitioned index on myindx(c,b,a)
and this has become a hot block.

I was thinking of rebuilding that index and using myindx(a,b,c) can you guys let me know what your thoughts are ?
 

regards

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