When enabled, messages are displayed whenever a query or expand is
executed that fails to find an associated index. A message is output for each
item in the query or expand that could be in an index (an attribute or basic
property). The intent of this tracing is to highlight queries and expands that
use indexable items, none of which are the first item in any index (so no index
is used to optimize the
operation).
To enable the index trace messages, run the following
MQL
command:
trace type INDEX on;
To set the environment variable in enovia.ini (Windows) or mxEnv.sh
(UNIX):
MX_INDEX_TRACE=true
When this trace type is enabled, trace messages will be displayed in
the format:
No index found for attribute[NAME1],attribute[NAME2],BASIC3…
The items in the trace message may or may not be in a defined index.
However, even if they are part of an enabled index, they are not the first item
in it, and so the index is not usable for that query or expand.
A developer can conclude that adding at least some of the listed fields
to a new or existing index (making one of the items first) may improve system
performance.