Guessing a little here, but it sounds like a FIFO
problem. Big delete, insertion of newer data,
a thin scattering of old data left behind.
If so, the cleanest fix is a coalesce after the
delete has committed. It keeps the index
size down, allows the maximum amount
of space to be reclaimed, reduces the risk
of node split failure with associated TX
waits and redo generation.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
Author: Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
----- Original Message -----
From: "BN" <bnsarma@xxxxxxxxx>
To: <jonathan@xxxxxxxxxxxxxxxxxx>
Cc: "oracle_L_list" <oracle-l@xxxxxxxxxxxxx>
Sent: Tuesday, October 31, 2006 5:11 PM
Subject: Re: RBO and Rebuild Index !!! sorry We still use RBO !!!!
>
> Sorry, I couldn't get back to you immediatley.
>
> Its a Bulk Delete every 15 minutes, they delete based on inactive flag.
>
>
> --
> Regards & Thanks
> BN
>
Greetings
