Collecting MustGather data for search replication issues

Prepare the following MustGather information before you call IBM Support to help with the troubleshooting process.

Procedure

1. Configure the following trace specifications.

   • In the Search server Docker container:

     *=info:com.ibm.commerce.foundation.*=all: com.ibm.commerce.search.*=all: org.apache.solr.*=all: com.ibm.commerce.solr.*=all

     For information about how to set trace strings, Configure logging for the Search Server.

   For information about how to configure trace strings, see

   • Configure logging for the Search Server

2. Reproduce the problem.

   Record the specific steps that we used to reproduce the problem and any details that might be relevant.

3. Collect the following files. In the In the Search server Docker container:

   • /opt/WebSphere/Liberty/usr/servers/default/resources/search/index/managed-solr/config/v3/*

   • /opt/WebSphere/Liberty/usr/servers/default/resources/search/index/managed-solr/config/v3-index-ext/*

   • /opt/WebSphere/Liberty/usr/servers/default/resources/search/jvm.options

4. Run the following database queries to collect the necessary information from the database (output results in CSV format).

   • SELECT SCCJOBREFNUM FROM SRCH_SCHCONFIG WHERE COMMAND='com.ibm.commerce.search.internal.scheduler.command.SearchFetchIndexCmd';

   • SELECT * FROM SRCH_SCHACTIVE WHERE SCSJOBNBR IN (select SCCJOBREFNUM from srch_schconfig WHERE COMMAND='com.ibm.commerce.search.internal.scheduler.command.SearchFetchIndexCmd');

   • SELECT * FROM SRCH_SCHSTATUS WHERE SCSJOBNBR IN (select SCCJOBREFNUM from srch_schconfig WHERE COMMAND='com.ibm.commerce.search.internal.scheduler.command.SearchFetchIndexCmd');

Related tasks
Configure logging for runtime environments