To determine the exact cause of the failure:
-
Check the resource consumption on the Indexer node for the file server or web application. In the Events page under the Origin column you can find the Indexer node where the failure occurs.
Failure to update index with scan data might happen when both the following conditions are met:
-
The memory usage on the Indexer node is high.
-
There is not enough memory for idwriter.exe to process the scan files.
-
Open a command window on the Indexer node for the file server or web application. Change the working directory to DataInsightInstallDir\bin. To check data integrity of indexes, enter:
configcli execute_job IndexCheckJob
To check if the job is complete, enter:
configcli list_jobs
The output of the command displays an asterisk (*) next to the currently running jobs. After the IndexCheckJob job, check the idxcheck.0.log file for any reported index corruption.
-
On the Indexer node, change the working directory to DataInsightInstallDir\bin, if it is not currently your working directory. Change the logging level for services. Enter:
configcli loglevel com.symc.matrix ALL
Move the scan databases from the DataDir\indexer\err folder to the DataDir\inbox directory, and run IndexWriterJob. Enter:
configcli execute_job IndexWriterJob
If scan database files are moved to the DataDir\indexer\err folder again, you may find the reason for update failure in the commd.0.0.log file. The commd.0.0.log file is present in the DataInsightInstallDir\log folder.
If scan database files continue to be moved to the DataDir\indexer\err folder, contact Veritas Technical Support.
Note: The default path for DataInsightInstallDir is C:\Program Files\Symantec\Data Insight, and the default path for DataDir is C:\DataInsight\Data. You can change these default paths during the installation process. In that case, the values of DataInsightInstallDir and DataDir will change accordingly.