Alternatively, you can browse through the engine instances in Fusion Applications Control for ECSF.

19.1.4 Searchable Object Deployment Fails

Your attempt to deploy a searchable object using Fusion Applications Control for ECSF fails.

Following are two possible causes and solutions for this issue:

Problem

The ECSF application, which is deployed to Oracle WebLogic Server, does not contain the search metadata file.

Solution

Make sure the ECSF application contains the search metadata file, and redeploy it to Oracle WebLogic Server. For information, see the "Deploying and Crawling Searchable Objects" chapter in Oracle Fusion Applications Developer's Guide.

Problem

The ECSF_RUNTIME_URL search engine instance parameter is not set, or is set incorrectly.

Solution

Make sure the ECSF_RUNTIME_URL parameter is set correctly.

19.1.5 Searchable Object Undeployment Fails

Your attempt to undeploy a searchable object from an engine instance fails.

Problem

The searchable object you are trying to undeploy does not exist in the Oracle SES data sources.

Solution

Make sure the searchable object you are trying to undeploy is deployed to an engine instance, as indicated when the DEPLOYED flag is set to TRUE, or the Deployed column is checked in Fusion Applications Control for ECSF.

19.1.6 Search Category Deployment Fails

Your attempt to deploy the search category to the engine instance fails.

Problem

There are no deployed searchable objects associated with the search category.

19.1.7 Cannot Start, Undeploy, or Delete the Index Schedule

The index schedule is in ERROR_MANUAL_RECOVERY state, which results from restarting the database.

Solution

You must recover the stuck ESS request. For information, see the "Stuck Scheduling Requests" section in Oracle Secure Enterprise Search Administrator's Guide.

19.1.8 Crawl Fails

You can view the data in feeds, but you receive an error when you attempt to crawl the data into the search engine.

Problem

You did not specify a search plug-in for your searchable object, so the default security plug-in is being used. The default security plug-in requires you to select a secure attribute.

Solution

Select a secure attribute when you define searchable attributes. For information, see the "Creating Searchable Objects" chapter in Oracle Fusion Applications Developer's Guide.

19.1.9 Invalid Channel Feed Type Error

You receive the following error during a scheduled crawl:

Error: Invalid Channel Feed type "error".

Problem

When the crawl was scheduled to start, the crawl state of the searchable object was CRAWLING. ECSF allows a searchable object to be crawled by only one process at a time. If you are certain that the searchable object is not being crawled, then the last crawl was abnormally terminated, and the ECSF metadata was not properly updated to indicate that the crawl had concluded.

19.1.10 ECSF Query Error

unexpected ECSF Query Error: oracle.ecsf.SearchException: Field
'facet_attribute' cannot be used for this query because it has not been
indexed in on the search engine

Problem

You deployed the searchable object to the Oracle SES instance, so it became available for search and the facet tree was rendered with its facet values. However, the crawl had either failed or no documents were indexed, so Oracle SES does not contain the searchable attribute.

Solution

Determine why the crawl failed, undeploy the searchable object, and then redeploy it to the Oracle SES instance to generate a new index.

19.1.11 FND-6603 Error

You receive the FND-6603 error that halts search functionality.

Problem

The search categories could not be fetched, or results could not be obtained from all the selected search categories. There may be other causes for the error.

Solution

You can change the server startup parameters to increase the web service timeout value to 5 minutes (500,000 milliseconds). For information, see the "How to Set the System Parameter for Web Service" section in Oracle Fusion Applications Developer's Guide.

19.2.1 Diagnosing ECSF Command Line Administration Utility Issues

To diagnose issues related to ECSF Command Line Administration Utility, you can check the log file (ecsfCmdLineAdminLog.txt) located in the log subdirectory where runCmdLineAdmin.sh or runCmdLineAdmin.bat file is executed.

19.2.2 Diagnosing Fusion Applications Control for ECSF Issues

To diagnose issues related to Fusion Applications Control for ECSF, you can also check for error messages in the log files located in DOMAIN_HOME/sysman/log.

If the parameters for the selected search engine instance are not configured correctly, a window with error messages appears. The error message contains three entries: a summary of the error, the specific error message from the runtime server, and the detailed stack trace information. The messages in the first and the second entries are internationalized (that is, they are translated to the language of the selected locale).