I was a little concerned that you wanted to stop a system operation.
Although you say here that you are not coming to the list to get a
solution, it seems you already decided that stopping index advice was
the fix - I'm reluctant myself to take that kind of action, but you may
have had more input that suggested doing this.
I have watched this thread from the start - I wasn't getting just what
the impact of these steps were - just how much CPU time did it really
take? Some of the metrics you stated did not seem to be all that much of
a problem, but I admit to reading these posts rather quickly.
The article that Chuck Pence cited did have a way to stop index advice,
right? But it was in the context of cleaning up things, with the intent
of restarting it afterwards. At least that's what I took from it.
I am sure you know that the system catalogs is a lot of views, which
have no index themselves. The indexes to support any queries there are
probably those on the underlying QADB* tables.
This still may be an issue to resolve - I hope you get a satisfactory
On 9/3/2015 9:57 AM, satya tiruveedhi wrote:
I just asked thread whether there is any setting to turn off "Index
Advisor". Other things mentioned were to provide background for the
request. At no point during the discussion, I was asking forum to
provide solutions to fix the application.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.