Novell is now a part of Micro Focus

Cool Blog: Quickfinder Tips

Novell Cool Solutions: Feature
By Alex Evans

Digg This - Slashdot This

Posted: 23 May 2006

For the last few weeks (since the Wednesday of Brainshare, in fact) I have been working on an issue that has been very QuickFinder intensive. QuickFinder, for those who don't know, is the process that runs in the POA that indexes all the mail and documents so that searches perform more quickly. In fact, a DMS system is handicapped without QuickFinder, as no searches will complete.

Watching a POA index a post office is a little hypnotic, along the same lines as a bad B movie or, dare I say it, American Idol - you find yourself just sitting and staring at the thing when there are loads better things you can be doing - but the QuickFinder switches described below make the pain a little more bearable.

/qfnousers - Skips indexing of user databases, so each run will only index the libraries in the post office

/qfnopreproc - Skips the preprocessing, though if you are indexing libraries you probably don?t want to add this switch

/qfnolibs - Skips libraries - very useful if you only want to index the users

0 - indexes 1000 items at a time
1 - indexes 500 items on a low priority thread, and skips if fewer than 3 new items
2 - indexes 1000 items on a medium priority thread and does all items
3 - indexes 2000 items on a high priority thread and does all items
99 - indexes 11000 items at a time on a high priority thread - this is the one that I use the most, as it means that the indexing will be done in the least amount of time.

/qfdeleteold - Deletes the old indexes and starts a complete reindex


These last two go hand in hand - you specify the start and end FID that you want to index. This is great if you only want to index a single user. TIDs say that you need to specify the FID in reverse, but that's not true. My FID is DA0, so if I wanted to index only my database I would specify DA0 on both switches.

When the QuickFinder index is running, you will see a database name and a number in parentheses, e.g., USERDAO.DB (14563). This number is the number of items in the database left to index, so on qflevel 2 it would take 15 complete QuickFinder runs to complete. Depending on your QuickFinder settings that could take over two weeks. With qflevel 99, it would be done in 2 runs, or 2 days with the same settings that you may already have. The more times that QuickFinder runs per day, the quicker this whole process will complete.

What I do when working on QuickFinder problems is create a seperate POA instance with its own startup file and add the relevent QuickFinder switches in it. This means that I can start and stop that POA without impacting users.

Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions.

© Copyright Micro Focus or one of its affiliates