Procedure to gracefully stop the re-indexing and restart (if required)
Note: This applies to DocuShare 6.5.3 hf1
Sometimes it not enough to simply stop DocuShare. During a re-index, the content.exe can continue running (and working on re-indexing). It's best / cleanest to stop it using one of the methods shown below, or run the risk of corrupting the index. The procedure would be:
1. Stop the Re-Indexing
a. Make a note of the last chunk of documents that completed indexing.
b. Stop DocuShare
c. Check taskmanager to make sure content.exe isn't still running. If content.exe is still listed under the processes tab, skip to step 2 Stop content.exe (listed below)
Warning: Do not try to stop the context.exe by using the End Task option in Task Manager.
d. Reboot the server
e. Start DocuShare (if the service is not set to automatically startup)
f. Restart the reindex again. (skip to the Restarting/Completing the reindex section in this solution)
2. Stop content.exe (if required)
Note: This solution should be used with the content.exe process continues to run even after DocuShare has been stopped.
Option 1:
a. To stop AutonomyIDOLServer.exe, type http://localhost:9002/action=stop in a browser URL
Note: if the command above fails to stop the content.exe then type http://localhost:9012/action=stop in a browser URL and then wait until the content.exe stops.
b. Reboot the server
c. Start DocuShare (if the service is not set to automatically startup)
d. Restart the reindex again. (skip to the Restarting/Completing the reindex section in this solution)
Option 2: The idoltool can also be used to stop idol and content.exe
a. From a command prompt, /bin>idoltool –s stop idol (to stop AutonomyIDOLServer.exe)
b. From a command prompt,/bin>idoltool –s stop content (to stop content.exe)
c. Reboot the server
d. Start DocuShare (if the service is not set to automatically startup)
e. Restart the reindex again. (skip to the Restarting/Completing the reindex section in this solution)
3. Restarting/Completing the reindex
a. Open a Command Prompt window.
b. Change into the \bin directory
Where is the installation directory for DocuShare. Depending on your installation environment the path may vary. The default installation path is C:\Xerox\Docushare.
c. Type dsindex -classname Document -start xx,xxx index and press Enter.
Where xx,xxx = the last chunk completed less a couple hundred chunks. You need to account for documents that may have been deleted during the re-index period. Therefore, start the re-indexing chunk 200, 400, 600 chunks BELOW the last completed chunk. Remember, the number represents the number of document chunks completed, not the total number of objects completed.
Note: If there are custom document types, you'll have to rerun the dsindex -classname .
d. Once the index completes, run the recoveryIndex utilities:
\bin>recoverIndex -report >> reindexreport.txt
e. Check the report and see how many documents failed to index. Try to remediate:
\bin>recoverIndex -recover
Note: All documents in the recoverIndex report will be metadata indexed even if they can't be content indexed, there is no need to manually add a switch to do so.
f. Produce a report of all URLs to Documents that were not indexed within the Database.by running \bin>verifyIndex
Note: The verifyIndex is a new tool only available in DocuShare 6.5.3 and higher.
Note: If there are document URLs that have not been indexed, it will prompt you to do so.