I’m trying to create a full text index on a huge mail file, but the process just go on and on and never ends. The mail file is 6,5 gigabytes. (and - no, it’s not an option to delete anything)
I did another try yesterday evening, but after 11 hours of processing I had to kill the process again, as the other users returned to work and demanded reasonable response time from the server.
I’ve examined the size of the .ft folder while the index task is running. The odd thing is that the folder seems to grow to a certain size, about twice the size of the mail file. Then it collapses back to almost nothing and starts to rebuild again until it reaches a certain maximum size. It seems like the process never stops.
Is this a bug, or is there a maximum size of the full text index ? Hmm. I’m worried.
Subject: Strange FT index problem on Domino 6.5.3CF1/SuSE Linux
Hi,
dont know what causes this problem but i run Domino (6.5.3FP1) on SuSe (9.1) as well an have several databases that are nearly that large (no mail files) ft-indexed withour any problems. :-((
Some general ideas (which you properbly already tried):
- try doing a fixup on the database first (force to check all documents ). I have seen corrupted documents and deletion stubs produce ft-errors.
(… do a compact as well !!!)
-
try to completly delete the ft-index as it could be damaged
-
try to modify the ft-settings to create the “smallest” possible FT-Index (no attachments,no case sensitive …)
This will not only speed up your tests but if it works for a limited ft-index then you can start to increase it and find the “error”.
-
try to place the database to a different computer (server or client) and do a ft-index there (if it gets the same error then iyou know at least that it is due to the database content)
-
create a fresh replica of the database and then replace the original with it. :-)) makes not much sense but helps sometimes to resolve database corruptions
Good luck
Hynek