JR60578: An error occurs during the search buildindex process.

APAR status

• Closed as program error.

Error description

• An error such as the following is thrown during the buildindex
  process:
  [1/22/19 8:42:26:044 EST] 0000006b id=
  org.apache.solr.common.SolrException E log Exception while
  processing: ProductBean document : SolrInputDocument(fields:
  []):org.apache.solr.handler.dataimport.DataImportHandlerExceptio
  n: Unable to execute query: null Processing Document # 25611
  ...
  at
  org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocB
  uilder.java:476)
  ...
  Caused by: com.ibm.db2.jcc.am.SqlSyntaxErrorException:
  [jcc][t4][10206][10302][4.21.29] Null SQL string passed.
  ERRORCODE=-4461, SQLSTATE=42815
  ...
  at
  com.ibm.db2.jcc.am.Connection.nativeSQLX(Connection.java:1130)
  
  In this case, the error happens for ProductBean and DB2 but it
  can also happen for ItemBean and other DB types.
  

Local fix

• In the wc-data-config-<dbType>.xml, move the following section
  to within the failing entity:
  <xi:include
  href="../../../v3-index-ext/Inventory/x-data-config.xml">
  <xi:fallback>
  <p>
  <!-- No x-data-config.xml is available -->
  </p>
  </xi:fallback>
  </xi:include>
  
  Then rerun the indexing
  

Problem summary

• USERS AFFECTED:
  WebSphere Commerce v9
  
  PROBLEM ABSTRACT:
  An error occurs during the search buildindex process.
  
  BUSINESS IMPACT:
  Unable to index after adding a custom field to the inventory
  index.
  
  RECOMMENDATION:
  

Problem conclusion

• The file wc-data-config.xml has been fixed to accommodate
  product and item customizations.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WC BUS EDITION

• Fixed component ID

  5724I3800

Applicable component levels