- Article Type: General
- Product: Aleph
- Product Version: 18
After running util a/17/18 ("Search for Duplicate Keys") you find that the Oracle index -- which had been UNIQUE-- has changed to NONUNIQUE.
util a/17/18 always first builds a non-unique index. The above can happen if, when it gives you the choice of "LIST/DELETE", you choose "LIST". In this case, the duplicates are not deleted and the non-unique index remains.
Though may want to do a run in which you choose "LIST" in order to see the duplicates, this *must* be followed by one of following:
1. a second run of util a/1718 in which you specify "DELETE"; or
2. if there are no duplicates, util a/17/3 to rebuild the Oracle index in question.
- Article last edited: 10/8/2013