× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I like to remove any advisory that hasn't been recommended in a long time.
When I build an index I like to remove it from the recommendations. I don't
want to clear everything. I've found that when a library is deleted, the
recommended indexes cannot be deleted unless the library is recreated.

I used to clear the advisories every month or two. This is a manual
process though and after a while I got out of the habit. It would be nice
to be able to schedule an SQL to clear the table completely or
selectively.

RESET_TABLE_INDEX_STATISTICS looks like what I want. I'm going to have a
look at that.



Gord




On Wed, Aug 8, 2018 at 7:07 PM, Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx
wrote:

That's correct. If you don't want to see the old advisories anymore,
delete them. The system will start building new ones.

Now there is value in having a good sample because the system will tell you
things like how often an index is called for, and several other important
items (materialized query comes to mind) that will change over time and
provide good feedback. I like to see about 90 days or more in there before
I start messing around too much. And then I need a practiced eye for the
application too, so that's where a good user expert can help.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On Wed, Aug 8, 2018 at 4:52 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Cool - I kind of thought I remembered seeing something.

So probably the OP doesn't have to do anything with the table he's
looking
at.

Cheers
Vern

On 8/8/2018 12:42 PM, Jim Oberholtzer wrote:

Vern, I think that's already there. On a periodic basis we simply clear
the advised indexes. Then let the new ones populate.

If we embark on a project to build several indexes then we clear the
advised indexes again and look to see what's being advised after the
work
we did.



Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On Wed, Aug 8, 2018 at 11:36 AM, Vernon Hamberg <
vhamberg@xxxxxxxxxxxxxxx

wrote:

Hey Gord

How about entering and RFE for IBM to provide tooling to manage older
recommended indexes? Or is there already something like that?

Vern

On 8/7/2018 12:57 PM, Gord Hutchinson wrote:

I would like to do some cleanup of the older recommended indexes. As
well,
I have recommendations for indexes in libraries that no longer exist.
Working with the schemas is ACS is cumbersome since it doesn't allow
selecting or positioning when in the index advisor. Each time a
recommendation is deleted the display is refreshed thus losing the
positioning. I find the web navigator slow as well.



Gord




On Tue, Aug 7, 2018 at 10:45 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

"Hard" restrictions can normally be determined by DSPFD and looking at

Allow read operation . . . . . . . . . . . : Yes
Allow write operation . . . . . . . . . . . : Yes
Allow update operation . . . . . . . . . . : ALWUPD *YES
Allow delete operation . . . . . . . . . . : ALWDLT *YES

This file is flagged as all yes (as shown above). I've seen some
which
were not, such as SYSTABLES, and temporal table log files.

This doesn't address your concern about "admonitions".



Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Gord Hutchinson" <gordm1@xxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <
midrange-l@xxxxxxxxxxxx
Date: 08/07/2018 10:32 AM
Subject: Index Advisor
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Are there any restrictions, prohibitions, admonitions on updating
QSYS2.SYSIXADV in SQL or a program?




Gord



--
Gord Hutchinson
TFI International
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: http://amzn.to/2dEadiD


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: http://amzn.to/2dEadiD



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.