Whilst working on resolving a phantom index issue, John Godfrey from Carys Computing came across a useful little trick for removing the rogue index.
Faced with an unwanted phantom index on a table in his application, John turned to the database manager and diving into the Utilities -> Indexes menu, he ran the option to remove the phantom index. However, nothing happened, the phantom index remained.
John then tried to add the index so that he could then remove it. As expected, OpenInsight duly reported that the new index could not be added as one already existed – the phantom index.
John notes that, at this point, you can turn to the help system in OpenInsight. This points you towards the System Editor, in which you can change field 6 from a 1 to a 0, to indicate that no BTree index is active.
However, John has found a neat, quick resolution to the phantom index issue and one that he asked me to share with everyone through my blog. He states:
“To the errant field add an XRef Index. This magically makes the Index editable and removable. So go back in and remove the XRef and BTree Indexes as required.”
I would like to thank John for this contribution and I will welcome any more tricks like this that anyone comes across and who would like to share with my readers.