Has anyone heard of this problem? Over the weekend we build the indices
for all of our indexed files. One of the builds hung up this past
weekend which stopped any further processing because the file being
indexed was one of our most used files. The process started normally by
locking the file to be indexed then starting all of the phantoms for
each index. There are about 24 indexes on this file and one of them
apparently was locked for some unknown reason. Because the phantom
couldn't lock the index file (INDEX.012) it errored out and the rest of
the processing just hung.
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to