Collecting Solr based search-related MustGather data for search build index issues

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

Procedure

Configure the following trace strings.
- In the Transaction server Docker container:
```
*=info:com.ibm.commerce.foundation.*=all:com.ibm.commerce.rest.*=all:com.ibm.commerce.catalog.facade.server.*=finest 
```
  For information about how to set trace strings, see Configuring logging for the Transaction Server.
- 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 Transaction Server
- 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 Transaction server Docker container:
  - /opt/WebSphere/AppServer/profiles/default/installedApps/localhost/ts.ear/xml/search/dataImport/v3/db2/*
- 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/*
Run the following database queries to collect the necessary information from your database (output results in CSV format).
```
select * from SRCHCONF
select * from SRCHCONFEXT
select * from ti_delta_catentry
select * from ti_delta_catgroup
```

Include the output of the following command.

https://<ts_server_hostname>:<ts_https_port>/wcs/resources/admin/index/dataImport/status?jobStatusId=<jobstatusId>

The jobStatusId is the ID of the build index job.