then you may be behind on PTF's and this may be addressed.
We still have this problem ("not so useful index suggestions on system
files") with Index Advisor on test LPAR which is upgraded to 7.1. Upgrade
is done by IBM. We are not part of this activity. Is it possible that bug
in 5.4 still exists after upgrade to 7.1 (latest TR)? This is the reason I
made this post to find out anyone else on 7.1 has the same problem.
If it isn't providing useful information (and I'll agree with Rob,
that's probably a PTF issue), why worry about it?
My concern is about CPU usage by Index advisor. I am not concerned about
disk space used by Index advisor. The update statement on sysixadv (by
Index advisor) shows up once in a while in top 20 SQLs by total CPU usage.
Index advisor might be spending lot more CPU on analysis compared to update
statement on sysixadv. It might save significant amount of CPU by turning
off Index advisor.
Plus, by giving many,many suggestions, Index advisor is no longer useful.
It takes too much time to review thousands of suggestions. Nowadays, we use
Index advisor report only to review temporary indexes(MTI).
This may be a radical solution
Not sure why this is a radical solution. I manage DB2 LUW database for the
same product and there are lot of things that I can leave it to DB2 or
take control when automation does not suit our system. For example, as a
DBA I can leave it to DB2 to collect statistics continuously (just like
iseries) or do it during nightly maintenance window thru shell scripts. By
collecting statistics during off peak hours, I use CPU more effectively.