Were these files by any chance copied/moved from their original location? The headers to the file, (at least in Universe), create pointers to the physical disk location of the indexes, and if you move the file without adjusting those pointers, you can have all sorts of fun issues.
On 10/13/2011 10:07 AM, [email protected] wrote: > > This information has been extremely helpful! > > I had 11 files have the indexes go bad on them, and they needed to be > completely rebuilt. > The only anomaly is that the "DELETE.INDEX fn ALL" didn't work right away. > > There was an index on the file, a V-field, called "XERP.SQLTRIG". When the > index > went bad, it was there, but not really there. On a file called STUMAST for > example, > I would say: > > :LIST.INDEX STUMAST > No indices created on file "STUMAST" > : > > Then I would say try to create the index: > :CREATE.INDEX STUMAST XERP.SQLTRIG > "XERP.SQLTRIG": can not create multiple indices on same location > No new indices are created > : > > So UniData sort of knows the index was there, but it doesn't really know. And > unfortunately, that is my problem. <SNIP> _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
