The Initially Index Smart Search Data job might fail with the following error:

SIP-52050: Failed to retrieve the ZooKeeper client instance because the connection to the ZooKeeper client instance timed out.
No collection linked.

After you delete a pending record, you get the following error in the

cmxserver.log

file:

[ERROR] com.informatica.mdm.sss.SmartSearchMDB: SIP-11041: Communication error "invalid stream header: 3C3F786D" occurs when making a request to Process  Server

After you rerun the Initially Index Smart Search Data job to update the outdated indexes of a child business entity node, the Batch Viewer tool of the MDM Hub might not refresh and continue to display the warning icon for the child node. The warning icon indicates that the indexes are outdated.

When you use a search string within double quotes (") to perform an exact search, the search might not return the expected results.

After you set a field as a searchable field, a smart search request might fail.

A smart search request might return one of the following errors:

[SearchService_30027]Exception occured while getting query the constructor

An internal error occurred. Contact an administrator to get more information for the client tool logs. If the administrator cannot determine the cause of the error, contact Informatica Global Customer Support.

The WADL files for the REST services are out of date.

When you search for a negative number or use a negative number to filter the search results, you get the following error:

[SIP-11008] SIP-11008: [SearchServiceClient_00028] You cannot use the following operators in the search string: AND, NOT, -, and OR. Add + before each search word if the search results must contain the word. Do not add + if the search word is optional or single word.

After you restart the application server, the Initially Index Smart Search Data job or a smart search request might return the following error in the application server log file:

No live SolrServers available to handle this request

If you configure Smart Search to display many results, some browsers do not display all the records or become unresponsive.

A smart search request does not facet the dates that are earlier than 1970.

A smart search request searches only the fields that match the language of the search string and does not support cross-language search.

If the composite objects do not include a field named

displayName

, the

Name

column in the Search workspace displays random field values when you perform a smart search.

The Initially Index Smart Search Data job might return incorrect metrics if you run the job more than once.

After you enable smart search on the process server, the application server log file does not include any relevant error message if the collection creation fails due to insufficient memory.

When you search for a negative value, the smart search request returns the positive and negative matching values.

If a non-admin user who does not have any privilege performs a smart search, the Informatica Data Director application displays an unclear error message.

After you create an inactive relationship between two entities and run the Initially Index Smart Search Data job, a smart search request returns the entities that have inactive relationship.