Cecile,

a couple of thoughts :

1-Have you tried SITEST with the "Full" option on the database ?

2-Structural changes (using DBGeneral) leave the database disabled for
logging, and sometimes the CIUPDATE flag is off also.

3-Structural changes (again using DBGeneral) temporarily disable indexing
and then re-enable it if all goes well. Maybe Adager follows a similar
methodology and a structural change was incomplete.

4-Indexing can of course be disabled with DBUTIL (but not enabled -at least
not "properly" I think)

5-We have noticed "strange" behavior in our Transact/iX applications when
we add or remove a Superdex index without recompiling (but that of course
wouldn't affect or explain QUERY)

and finally a couple of (hopefully thought provoking) questions :

1-Having re-indexed the datasets, does DBUTIL say indexing is enabled ?

2-Can you get at the SI set using Adager ? is it full ? can you change it's
capacity ? can you delete all indexes, disable indexing, purge/erase the SI
set (if it's still there), and then start over ?

Pretty obvious stuff really, but you never know.

Good luck,

Costas