Hi All DB2 8.1 FP 5 (.0.48) on AIX 5.2.0.0

After upgrading to 8.1.5 all my indexes seem
to have chanced the indexed column to the
include parameter and the optimizer rarely
select the index - has anyone experienced
anything similar ?

Thanks

Have you done RUNSTATS follwed by rebind??

Cheers
Sathyaram

Do RUNSTATS and then do an EXPLAIN of your query - I suspect it will choose a new access path once the statistics are updated. If you see a better access path will be taken, rebind the program.

I have - of course - runstatted severeal
times and even tried recreating the index
to no avail.

I'll try the rebind - thanks

One other thing to consider is the cardinality and distribution of keys. Even though an index is defined, the optimizer might decide to ignore using an index if it determines the access path is no better than doing a tablespace scan. As always, it depends.