This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


~Tate Breluski
Jun 27, 2014, 7:48 PM
22 Posts

Domain Indexer finished indexing Database Full text error see log for more information

  • Category: Domino Server
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator
  • Tags: Indexer
  • Replies: 3

I have one mail database which is over 9gigs in size.  I indexed it and when it finished indexing (or what ever caused it to stop) I get the message in the subject.  It refers to seeing the log for more details, but I *was* seeing the log at the time.  Attempts to search gives undependable results.  I hope someone has an idea I can pursue.

 

Edit:  The document ID which it stops on is the same (so far I watched it twice).  So how do I find this document so I can delete it?  Must I create a script?  That seems a bit too much.  Following is the message. It gives a short number for the ID, I thought document IDs were very long.

 

[100C:000A-0274] 06/30/2014 10:36:48 AM  Error full text indexing document NT0003F6C6 for database mail\user.nsf in domain index E:\Program Files\Lotus\Domino\data\ftdomain.di\NotesDB\IDX5: Full text error; see log for more information
 

~Sven Nimgerosterflar
Jun 30, 2014, 5:53 PM
46 Posts
Create a view
Create a view in the database reported in the error  with a selection formula of @all and a column that shows the note id such as @Text(@noteid)   you can then do a CTRL +F to  locate the specific document
~Tate Breluski
Jul 1, 2014, 8:00 PM
22 Posts
Thank you both for your reply

Yes, fixup is always my first response.  I added the (hidden) view to my template for future use.  Turns out I would be using it more.  I would remove one bad document and it would find another.  Why would I be able to open the 'bad' document, yet the indexer would not process it?

That second link, near bottom of that page, goes into just what Riccardo mentioned.  The whole page was good information.

Thank you,

 

Durwin


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal