Guyver I wrote:As others have pointed out, the analyze command is still valid for certain operations. The problem with using it to find index compression count is that it locks the table for the duration. In principle you could get an estimate by running some SQL against the table, but I haven't yet written any code to do that; someone recently pinged one of my blog items, though, with an article that included a comment with some SQL that might be helpful:
I'm aware that the ANALYZE statement is now deprecated. Is there an alternative to get the OPT_CMPR_COUNT value of an index, or is there different method to find the recommended compression ratio in Oracle 10g? Thank you.