This appendix lists common crawler issues and their solutions.
| Crawler Issue | Symptom | Solution |
|---|---|---|
| Crawler process hangs when started on a Windows system | On Windows system, crawler process starts without any further progress after displaying the message "Crawling started at mm/dd/yy hh:mm AM|PM" in the crawler log file. For example:
========= Crawling status ========= [2014-02-27T10:07:04.593-05:00] [search] [NOTIFICATION] [EQG-30304] [oracle.search] [tid: Main Thread] [ecid:0000KHnsbE5FW705Vzt1ic1J3pIO000001,0] Crawling started at 2/27/14 10:07 AM. The following error message is also displayed in the crawler log file: java.io.IOException: Access is denied |
On Windows system, disable the User Access Control (UAC) setting and restart the crawler process. |
| Crawler process does not start on a Solaris system. | On Solaris system, crawler process does not start when maximum heap memory size is set to more than 2 GB. This issue occurs because by default Solaris JVM is launched in 32-bit mode, which cannot support more than 2 GB of heap space. | On Solaris system, launch the crawler using 64-bit JVM by using the "-d64" flag for the CRAWLER_EXEC_PARAMS parameter in the mw_home/Oracle_SES1/bin/clexecutor.sh file.
Example: CRAWLER_EXEC_PARAMS="-d64 -ms70m -mx4g ..." |