Thank you for the replies. I did not look at the wait event at that time. The index type comes up as 'normal': 1 select owner, table_name, index_name, index_type 2 from dba_indexes 3* where index_name = 'PS_JRNL_HEADER' SQL> SQL> / OWNER TABLE_NAME INDEX_NAME INDEX_TYPE ------------ ------------------------------ ------------------------------ --------------------------- SYSADM PS_JRNL_HEADER PS_JRNL_HEADER NORMAL On Wed, Jun 15, 2011 at 2:16 PM, Stephane Faroult <sfaroult@xxxxxxxxxxxx>wrote: > Or an IOT? > > > > On 06/15/2011 08:53 PM, Toon Koppelaars wrote: > > Is this a bitmap index? > > On Wed, Jun 15, 2011 at 8:46 PM, Ram Raman <veeeraman@xxxxxxxxx> wrote: > >> Hi >> >> After getting complaints about slow process we found out that one user's >> session was blocking another user's session. I found out that the waiter's >> session was waiting to acquire a lock on an index. This is based on data >> from v$session of the waiting session. >> >> The index was built/rebuilt about 10 months ago - it could not have been >> index rebuild that could have caused the lock. I tried googling to find more >> information about locking of indexes but not able to find anything that can >> help me. ver 10.2. Can anyone explain or point to information on index >> locking. >> >> Thanks. > > > > > -- > Toon Koppelaars > RuleGen BV > Toon.Koppelaars@xxxxxxxxxxx > www.RuleGen.com <http://www.rulegen.com/> > TheHelsinkiDeclaration.blogspot.com<http://thehelsinkideclaration.blogspot.com/> > > (co)Author: "Applied Mathematics for Database Professionals" > www.rulegen.com/am4dp-backcover-text > > > > -- > Stephane Faroult > RoughSea Ltd <http://www.roughsea.com/> > Konagora <http://www.konagora.com/> > RoughSea Channel on Youtube <http://www.youtube.com/user/roughsealtd> >