“The full text index for this database is in use” on virtual server, not on dedicated server

ibm-domino

Our production Domino server was 32-bit Windows 2003 server where OS, Program Files and Domino Data all were on different disk drives. I don't remember seeing this error on that server ever:

NotesException: Notes error: The full text index for this database is
in use

After we switched to a 64-bit Windows 2008 virtual server with only C: drive we've seen this error a lot.

Today I made a test where I first generated 4000 rather large documents. Then I ran this XPage SSJS code:

for (var i = 0; i < 300; i++) {
    print("FT");
    database.FTSearch("[Form]=Test");
    java.lang.Thread.sleep(100);
}

While the above code was running I run this:

print("START indexing");
database.updateFTIndex(true);
print("END indexing");

I did this two times on both servers. On the 32bit dedicated server I got no errors. The indexing took 4 seconds and there were 32 FT searches while the indexing was ongoing.

On the 64bit virtual server both times there was only 1 FT search after the "START indexing" print and after that I got the error. All these 3 things occurres on the same second (start of indexing, one FT search and error).

Both Domino servers are version 9. On the virtual server there are more than 10GB available (FT index size in the test db is 10MB).

The only reason for this difference I can think of is that the FT indexer uses the other drives on dedicated server for indexing and because of that the error is not occurring there. Is that right and is there documentation about it?

We are not using FTBasePath notes.ini parameter.

Best Answer

Having OS, Program Files and Domino Data on the same disk can/will be a performance issue, but should not cause the issue you are seeing.

As the production server apparently was migrated to the new platform,

  1. Remove all FT indexes (deleted the .ft directories) and recreate all FT indexes on the new machine. Stop the server, deleting the .ft directory of all relevant database, start the server again and recreate the FT index for those databases.
  2. Verify, that all the paths, ... in the notes.ini of the server are correct
  3. Update_Fulltext_Thread=1 is set?

Apart from that, verify that no virusscanners, ... are accessing the FT files, as Simon commented.

Related Topic