You must follow your vendor guidelines to stay suported, right?the vendor recommend to have 'job' which will weekly rebuild indexes for few large table.
Also I have my notes here:If you check Metalink, you will find that both the notes you mention are no longer available.
See Oracle MetaLink note 122008.1 for the officially
authorized script to detect indexes that benefit from
rebuilding. This script detects indexes for
rebuilding using these rules: Rebuild the index when
these conditions are true:
- deleted entries represent 20% or more of the
- the index depth is more then 4 levels.
Oracle's index rebuilding guidelines appear in
Metalink note 77574.1 (dated April 2007) recommends
that indexes be periodically examined to see if they
are candidates for an index rebuild:
But nothing was updated, nor made up-to-date, just removed?We hope that Oracle correct their content with valid and up-to-date information
I wonder why they no longer give any advice at all on this popular topic?I wonder why Oracle took too long to take action on this...
But nothing was updated, nor made up-to-date, justYep, just removed... that's why we hope
I wonder why they no longer give any advice at all onThat's because business software (ERPs, CRMs, BI, etc) vendors mostly design the product for one database-abstract-layer, sometimes with slight modifications to fit particular DB infrastructure. Some procedures are valid for specific DB, same are not valid for other DB, but they have generalized the relationship among Application and DB, in a one-solution fits all.
this popular topic?
Sadly, if his vendors says that they must do
something to stay supported, he may not have any
I've seen loads of unnecessary rebuilds done because
a vendor threatended to desupport the customer did
they did not comply . . . .