If Oracle ATG Web Commerce Search returns no results at all when results are expected, consider the following checklist of possible causes:
Was the index created and deployed without errors? Use Search Administration to view the indexing history.
Is the correct index being searched? The correct partition? Check the
home/logs/searchEngineActivity/engineinfo.xmlactivity log.Are the items in the index? If not, it might be a problem with your catalog or repository, or with the
IndexingOutputConfigconfiguration. You can view the XHTML files and use index inspection tools (see Using Index Review) to see if the content was processed.Was the content indexed in the language being searched in? Check your Text Processing Option sets, selected language customizations. You can use index inspection tools (see Using Index Review) to highlight language usage, and the
request.xmlto pinpoint query options (see the ATG Search Query Guide for details on the XML).Is the item text in question being searched? Check for errors in the query form handlers, and look at the
request.xmlfile foractiveSolutionZonessettings that may be excluding content items.Do the terms in the query match any item text? There are many possible causes for this problem, which can be diagnosed by viewing the
request.xml,response.xml(docMin=0means no items found by any term), and Query Console:boolean logic failure—Only one of the entered terms matches, when your settings require all terms to match. Check the
modeattribute on the query.term operators—Query operators might require a match on multiple terms, where only one term matches.
stop words—The user may be searching on a term that has been excluded from indexing (see the Dictionaries chapter of this guide for information). Use Dictionary Inspection to resolve this issue.
relevancy threshold—Check the
minScoreattribute in therequest.xmlfile. The default is 0, which is fine for most circumstances; if it is set higher, you may be excluding results that should be returned.constraints—Constraints on the query may eliminate all results, or restrict the search to particular catalogs, categories, or facet values. See the
request.xmlfile.
Have values that limit the query been set too low? Check the
request.xmlfile for the following possible problems (see the ATG Search Query Guide for details on the XML):pageSize=0responseNumberSettingsrelQuestSettings
Search configurations (which are created in Oracle ATG Web Commerce Merchandising and are also known as Merchandising Search Configurations) or query rules may exclude results; see the request and response XML files to view constraints and rules that have been used.
