Collecting Solr based search-related MustGather data for search replication issues

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

Procedure

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, Configuring logging for the Search Server.
For information about how to configure trace strings, see
- Configuring logging for the Search Server
Reproduce the problem.

Record the specific steps that you used to reproduce the problem and any details that might be relevant.
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

Run the following database queries to collect the necessary information from your 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');