Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Troubleshooting Search

Troubleshooting Search

If you encounter issues with search, use the following information to troubleshoot.

In a WebSphere-based environment, the Initially Index Smart Search Data batch job fails to run.

The Initially Index Smart Search Data batch job might fail because of the cache-related issues. You must clear the cache and run the job again.
If the Initially Index Smart Search Data batch job fails to run, perform the following tasks:
  1. In the
    cmxcleanse.properties
    file, verify whether you have configured the
    pingSolrOnStartup
    property.
  2. If you do not configure the
    pingSolrOnStartup
    property or you set the
    pingSolrOnStartup
    property to false, perform the following tasks:
    1. Set the
      pingSolrOnStartup
      property to true.
    2. Restart the application server.
    3. Run the Initially Index Smart Search Data batch job again.
  3. If the Initially Index Smart Search Data batch job fails even when the
    pingSolrOnStartup
    property is set to true, perform the following tasks:
    1. Stop the WebSphere profile.
    2. Open a command prompt, and run the following file:
      • On Windows.
        <WebSphere installation directory>\profiles\<Application server profile name>\bin\osgiCfgInit.bat
      • On UNIX.
        <WebSphere installation directory>/profiles/<Application server profile name>/bin/osgiCfgInit.sh
      The
      osgiCfgInit.bat
      and
      osgiCfgInit.sh
      files clear the OSGi cache for the WebSphere profile.
    3. Run the following file:
      • On Windows.
        <WebSphere installation directory>\profiles\<Application server profile name>\bin\clearClassCache.bat
      • On UNIX.
        <WebSphere installation directory>/profiles/<Application server profile name>/bin/clearClassCache.sh
      The
      clearClassCache.bat
      and
      clearClassCache.sh
      files clear the class cache that the JVM uses.
    4. Start the WebSphere profile.
    5. Run the Initially Index Smart Search Data batch job again.

When you start the Batch Viewer tool in a search-enabled environment, the Batch Viewer tool does not respond.

In a search-enabled environment, the Batch Viewer tool might not respond when the Hub Console fails to connect to the ZooKeeper server.
To fix this issue, perform the following tasks:.
  1. Open the following file in a text editor:
    <MDM Hub Installation Directory>\hub\server\resources\cmxserver.properties
  2. Manually add the following property to the
    cmxserver.properties
    file:
    cmx.ss.dirtyIndex.disable=true
    The
    cmx.ss.dirtyIndex.disable
    property allows the Batch Viewer tool to start and prevents the warning icon that indicates an outdated index from being displayed in the Batch Viewer tool.
  3. Save the file.
  4. Validate the schema, redeploy the Informatica Data Director application, and restart the Hub Console.

0 COMMENTS

We’d like to hear from you!