I wrote the other day about an issue I had discovered with view indexes being discarded.

If you are seeing the same issue, the SPR reference is SSARBW4PAW. Unfortunately I have not yet received any information on the underlying cause and any fix.

However, HCL have suggested a possible work-around which is the DBMT “nondiscardable view” functionality. This involves:

a. Getting the “Inherit design from…” value of the affected application databases properties, e.g. AppBaseTemplate

b. Add each application template name to the DBMT_MailTemplate notes.ini setting, e.g.

DBMT_MailTemplate=AppBaseTemplate,App2BaseTemplate,App3BaseTemplate

c. Add a notes.ini setting for each template listing the views that are nondiscardable, e.g.

DBMT_AppBaseTemplate=viewNameOrAlias1;viewNameOrAlias2;viewNameorAlias3
DBMT_App2BaseTemplate=viewNameOrAlias1;viewNameOrAlias2;viewNameorAlias3
DBMT_App3BaseTemplate=viewNameOrAlias1;viewNameOrAlias2;viewNameorAlias3

4. Running DBMT against the applicable application databases (if you are not already using DBMT)

I am currently trying to validate that the suggestion does indeed work-around the issue.

If the work-around does work, I will then need to modify each application design so that every “nondiscardable” view has an additional alias of something like “v1” and “v2” etc. so that the DBMT_TemplateName settings don’t exceed the notes.ini max length.

2 thoughts on “Issue with view indexes being “randomly?” discarded – Update”

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Scroll to Top