|Oracle® Fusion Applications Administrator's Troubleshooting Guide
11g Release 1 (11.1.4)
Part Number E25450-03
|PDF · Mobi · ePub|
This chapter describes common problems that you might encounter when using Oracle Enterprise Crawl and Search Framework (ECSF) and explains how to solve them.
This chapter includes the following topics:
Some procedures in this chapter reference content in the Oracle Fusion Middleware guides. These guides describe using Fusion Middleware Control. These procedures also apply to Fusion Applications Control.
In addition to this chapter, review the Oracle Fusion Middleware Error Messages Reference for information about the error messages you may encounter.
This section describes common problems and solutions. It contains the following topics:
You do not see any parameters for the search engine instance you created.
Seed data is not set up on your Oracle Fusion Applications database.
ECSF_SEED_DATA.sql script against your Oracle Fusion Applications database.
You are unable to create a search engine instance record.
An existing search engine instance record is present.
Execute the following SQL statement:
select * from ECSF_ENGINE_INSTANCE
Delete the row that contains null values for all fields except the ID and Name fields, and commit the deletion.
Recreate the search engine instance. See the "Creating Search Engine Instances" section in the Oracle Fusion Applications Administrator's Guide.
Your searchable object is not listed in the table of the Add a Searchable Object to Selected Engine Instance dialog.
Following are two possible causes and solutions for this issue:
The searchable object is not in the Oracle Fusion Applications database. You can check by executing the following SQL statement against your Oracle Fusion Applications database:
select * from ECSF_SEARCH_INDEX_OBJECT
Register the searchable object in the Oracle Fusion Applications database. For information, see "Task 2, Register the Searchable Objects" in the Oracle Fusion Applications Administrator's Guide.
The searchable object has already been associated with an engine instance. This is evident when a value exists in the
Disassociate the searchable object from the current engine instance. For information, see "Task 3, Disassociate the Searchable Objects from Search Engine Instances" in the Oracle Fusion Applications Administrator's Guide.
You can identify the engine instance with which the searchable object is associated by executing the following SQL statement:
select * from ECSF_ENGINE_INSTANCE where ID = sei_id_value_of_your_searchable_object_record
Alternatively, you can browse through the engine instances in Fusion Applications Control for ECSF.
Your attempt to deploy a searchable object using Fusion Applications Control for ECSF fails.
Following are two possible causes and solutions for this issue:
The ECSF application, which is deployed to Oracle WebLogic Server, does not contain the search metadata file.
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.
ECSF_RUNTIME_URL search engine instance parameter is not set, or is set incorrectly.
To resolve this issue, ensure the
ECSF_RUNTIME_URL parameter is set correctly by checking the following:
Your attempt to undeploy a searchable object from an engine instance fails.
The searchable object you are trying to undeploy does not exist in the Oracle SES data sources.
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.
Your attempt to deploy the search category to the engine instance fails.
There are no deployed searchable objects associated with the search category.
Make sure you associate searchable objects with the search category before you attempt to deploy the search category. For information, see "Task 3 Associate Searchable Objects with the Search Categories" in the Oracle Fusion Applications Administrator's Guide.
You cannot start, undeploy, or delete the index schedule.
The index schedule is in
ERROR_MANUAL_RECOVERY state, which results from restarting the database.
You must recover the stuck ESS request. For information, see the "Stuck Scheduling Requests" section in Oracle Secure Enterprise Search Administrator's Guide.
You can view the data in feeds, but you receive an error when you attempt to crawl the data into the search engine.
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.
Select a secure attribute when you define searchable attributes. For information, see the "Creating Searchable Objects" chapter in Oracle Fusion Applications Developer's Guide.
You receive the following error during a scheduled crawl:
Error: Invalid Channel Feed type "error".
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.
Manually start the crawl to reset the state of the crawl and enable the searchable object to be crawled. For information, see "Task 5, Start the Index Schedules" in the Oracle Fusion Applications Administrator's Guide.
You receive the following error when you click on a facet value:
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
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.
Determine why the crawl failed, undeploy the searchable object, and then redeploy it to the Oracle SES instance to generate a new index.
A crawl can fail for many reasons, such as running out of Oracle Database space, Oracle SES issues, Oracle Enterprise Scheduler issues, and so on.
You receive the FND-6603 error that halts search functionality.
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.
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.
You can also undeploy the categories that are failing to load. For information, see "Task 1 Undeploy the Search Categories" in the Oracle Fusion Applications Administrator's Guide.
This section describes general approaches for diagnosing ECSF problems. It contains the following topics:
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.bat file is executed.
To diagnose issues related to Fusion Applications Control for ECSF, you can also check for error messages in the log files located in
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).
If you experience failures while deploying or undeploying search categories, check for the following:
The database connection is successful.
The searchable object is available in the Oracle Enterprise Manager repository.
The associated searchable objects are deployed.
The deployed object is available in Oracle SES.