Not enough memory for full text indexing or search

HCL Domino Domino Forum
1

I’m getting the error in the subject line once a day when the FT indexer hits activity.nsf (at least I think that’s where it’s generating the error).

The error list in the log is

09/13/2007 05:22:23 AM DÙ9/13/2007 05:22:23 AM Chronos: Performing hourly full text indexing

…normal messages not related to the issue

09/13/2007 05:30:31 AM Chronos: Full text indexer terminating

…normal messages not related to the issue, no chronos hourly message on the indexer starting up

09/13/2007 06:14:20 AM Full Text message: Memory allocation error. errcode = 606

09/13/2007 06:14:20 AM Error full text indexing document NT804AF6BA d:\lotus\domino\data\activity.ft (rc=3892) Not enough memory for Full Text Indexing or Search

09/13/2007 06:14:20 AM Error full text indexing activity.nsf: Not enough memory for Full Text Indexing or Search

09/13/2007 06:14:20 AM Updating took over 30 minutes for activity.nsf

…normal messages not related to the issue

09/13/2007 06:22:26 AM DÙ9/13/2007 06:22:26 AM Chronos: Performing hourly full text indexing

Don’t see the errcode = 606 again for another day

I can’t find anything in the forum on the 606 error and don’t want to start mucking about until I have some idea of what I can and can’t do safely.

Activity.nsf is 122 meg

It’s index is about 3.8 meg

The server has 2 gig ram and is, right now, running at 1% utilization.

The drives on the server are only using 10% of available space.

The server is not crashing.

Question - does Activity.nsf need to be full text indexed? I may try just deleting the index to see what happens unless the index is required.

Any ideas?

TIA

Dogu

2

Subject: Not enough memory for full text indexing or search

Sounds like you have plenty of resources, I would probably delete and re-create the index to see if that fixes it.

You might have a corrupt document (NT804AF6BA) in the database with some giant attachment that the indexer does not know how to handle - just a thought.

3

Subject: RE: Not enough memory for full text indexing or search

Randy,

Thanks for the suggestion. I’ve just killed/rebuilt the index (made sure the .ft directory was gone before I rebuilt the index just for good measure).

I’ll see if the error pops back up.

Take care.

Doug

4

Subject: Not enough memory for full text indexing or search

As I recall - there were some fixes for some memory allocation errors in 6.5.5 - it may haven only been ‘3301 memory allocation error’ - but you might want to/have to upgrade your server.

You might try adding the following to your Notes.INI: (not sure if there are supported at 6.5.4)

FTG_USE_SYS_MEMORY=1 ← (Not sure if this is still supported at 6.5.5 and later - but support had me use it.)

FTG_DISABLE_PAGING=1

FTG_SET_INITIAL_BUFLEN=7000

You might have to play with FTG_SET_INITIAL_BUFLEN - I think I ended up increasing mine to 20000 before the errors went away.

Chronos can interfere with Full Text Indexing, add “Debug_Disable_Chronos=1” to your Notes.INI and see if that helps.

Take a look at these:

http://www-111.ibm.com/search/SupportSearchWeb/SupportSearch?action=search&pageCode=MPS&rsid=203&products=SSKTMJ%2CSSKTWP&productInfo=SSKTMJ||Lotus+Domino||463&productInfo=SSKTWP||Lotus+Notes||475&searchLimits=DB510%2BDB520%2BDA440%2BD600%2BD700%2BDB540%2BDA410%2BDA430&searchLimits=DB550&sortBy=1&pageNumber=1&searchTerms=3892&ibm-go.x=0&ibm-go.y=0&ibm-go=Go

5

Subject: RE: Not enough memory for full text indexing or search

Mark,

Thanks for the tips and pointers. I’ll file these for future reference.

Killing and rebuilding the FTI for activity.nsf fixed (at least in the short term) the problem.

If the errors return, I’ll revisit your recommendations.

Thanks again.

Doug