• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1657
  • Last Modified:

Local Replica Indexing - Stubborn User

I have a user which keeps a local replica of all the the dbs he uses. Some of which are 3gb in size.

He often complains that his machine slows down - but doesn't want to remove FT indexing nor indexing of attachments...

Is there a way to control when it occurs?? I know Update frequency doesn't work on clients..

I can't really figure out what triggers it.. although most of the time it follows replication.. it is does not occur immediately after..

His replication schedule is set to run opening and closing notes...

Normally I would tell the user to piss off .. but this one is somewhat of a big shot...
0
miklesw
Asked:
miklesw
  • 4
  • 2
  • 2
  • +1
1 Solution
 
SysExpertCommented:
Tell him that if he wants to  keep such large amonts of data locally and indexed, he needs a new faster machine. That always makes them happy.

Other option is to try Google desktop.

0
 
mikleswAuthor Commented:
This error may be causing the problem.. sounds like a corrupt Index - deleted it ..will see how it goes...

10/05/2006 09:37:53   Full text indexing documents in xxxx
10/05/2006 09:38:19   Looking for replica (80257004:003F121E) on server xxxxx
10/05/2006 09:38:20   Failover on replica ID (80257004:003F121E) from server  to xxxx
10/05/2006 10:32:18   Full Text message: UBM error. File name = c:\notes\data\xxxxx.ft\ftgi\gtr.PLF, UBM error code = 3900, errcode = 3084
10/05/2006 10:32:18   Error full text indexing document NT800B0002 c:\notes\data\xxxx.ft (rc=3857) Full text error; see log for more information
10/05/2006 10:32:19   Error full text indexing xxxx.nsf: Full text error from Topic

However I still would like to find a way to control indexing.. if it exists..
0
 
twizted_teckCommented:
Recreating the index on the local replica might fix some of the error issues. I know on Domino 7 you can control full text indexing's threads, refresh rate and so forth through the notes.ini. I don't know if you would be able to use those type of settings on the clients notes.ini. As far as I know this is new on version 7.X, but I don't know what version you are. Maybe this will point you in the right direction.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
marilyngCommented:
I could be wrong, but aren't "UBM errors" disk errors?  If there are more of these under the events log on the PC, then chkdsk and defrag is the starting point, with reformat and reinstall. That is if the harddisk and not the controller is the problem.   I have never seen these type of errors associated with a Notes File.  Other than the fulltext error ones, which twizted teck answers nicely.  (open database properties, delete the ft, and rebuild)

Then again, I'm not the "sysexpert" here... :)
0
 
SysExpertCommented:
All good info.
Please Remember that I commented BEFORE he posted the log errors !!

0
 
marilyngCommented:
SysExpert,
I honestly don't know, which is why I'm throwing this back to you :)   I don't know if the Notes Log would throw system errors, I've never seen them.
0
 
marilyngCommented:
miklesw,
> Error full text indexing document
Ok, I did a little reading, and it seems that the document with NoteID #NT800B0002 is corrupt and causing the full text index to crash.

The document it would seem is in the c:\notes\data\xxxx.ft  << replace .ft with .nsf and that's the database.

So, create a local replica of the database in question, follow the steps here:  http://www-1.ibm.com/support/docview.wss?rs=0&q1=find+doc+by+noteid&uid=swg21087186&loc=en_US&cs=utf-8&cc=us&lang=en

To locate the document by NoteID and delete it from the database.  Compact, fixup, and replicate up.  Delete the .ft index on the server, then run fixup and compact on that copy.  

I stand corrected about UBM:
Unified buffer manager (UBM) is a shared memory cache for most disk resident
data in Domino databases. It is also a memory cache for temporary files like
external sorting temporary files or containers.

If that doesn't work, then also run the reindex program, you can schedule it:

Program Name: server
Command Line: -c "tell mtc reindex"

Or run it from a command line in the console, "tell mtc reindex"

Let us know!

0
 
mikleswAuthor Commented:
hey maryling,

The index is created on the client not the server (we try to discourage it unless really necessary)..  I deleted the ft folder and i'm waiting for a reply from the user..

So if I'm understanding correctly, the problem is from a doc in the  database not the index itself, right?

Isn't MTC related to the Mail Tracker?
0
 
marilyngCommented:
MTC would be the server indexer.. found the reference in IBM.  Thought this was on a server.. :)

yes, the problem is with the document on the client's side, and deleting the index should resolve it.  If the ft index flag is turned on , then you should delete the index from the database property, and then recreate it from the database property.  If in recreation, you get the same error, then there is a corrupt document that is causing it and you should delete the index again, then delete the document.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 4
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now