Just a heads up, we've been investigating a few indexing issues in OpenInsight 10 and are currently working on putting together a "hotfix" RDK. In the interim, the issues to look out for (and their current work-arounds, if any) are:

• After creating a new index, not all of the required elements are created in the bang (!) file. Workaround: after creating a new index, please rebuild the index, and all required elements are created;
• When doing a comparison with a right-justified indexed field, zero and null ("") are incorrectly treated as the equal;
• A right justified index may not find negative values, especially in indexes on very large tables containing a small range of values.

We hope to have an RDK addressing these index issues available sometime in the coming week.

- Bryan Shumsky

Revelation Software, Inc.

When doing a comparison with a right-justified indexed field, zero and null ( "" ) are incorrectly treated as the equal

This sounds related to this thread discussing changes to Btree.Extract() . My understanding is that the above is the default behaviour for OI10, but setting SYSENV/CFG_RTI_BTREE_EXTRACT to LEGACY overrides this and should prevent Btree.Extract() treating nulls and zeros equivalently.

However I've tried this override in OI10 and it doesn't appear to have any effect! (at least for LT range searches). Perhaps this issue is related to how that was implemented??

Cheers, M@

Vernon Systems

There is also an issue related to OI10 indexing when updating records within Transaction Processing to table(s) with btree indexes causing index corruption, requiring index rebuild.

Question - How do we configure AREV64 to NOT update indexes before running RLIST selects against indexed fields? Setting the AREV environment in AREV64 to 'No' does not seem to prevent the indexes from updating when running RLIST statements. Setting the OI10 database environment checkboxes to not update works as expected when performing OI10 RLIST statements. Maybe I'm not doing the correct configuration in AREV64?

Hi, Mary Jean.

It is indeed something that you should be setting in OI, but there's currently a bug so the correct value isn't getting pulled - it'll be fixed in 10.2.2.

- Bryan Shumsky

Revelation Software, Inc.

Thanks Bryan!

Thanks Bryan!

Is this anyway related to me seeing that SELECT in AREV64 does NOT appear to be updating indexes.

What are ALL the settings I need to ensure the indexes ARE updated before all SELECTs in AREV64

Indexing in Oi10 config is set to OI9

Sorry, but while I am here, are there also known issues with relational indexes that anyone knows of or are also having issues?

View this thread on the Works forum...