Unable To Rebuild Verity Index due to following error: Indexing aborted. Unable to do clean up. csDbUnableToExecuteBatch (Doc ID 1500409.1)

Last updated on APRIL 04, 2024

Applies to:

Symptoms

On : 10.1.3.5.0 version, Content Server

After adding in a a custom metadata field via CMU, a rebuild was kicked off. But the rebuild had to be suspended or placed on hold, while users made some changes and checked in items, once the rebuild was restarted,
the following error occurs.

ERROR
-----------------------

During the "Clean up" state of the Collection Rebuild Cycle, the indexing aborted at "Performing cleanup. (26%)".

prd_consD: Indexing aborted. Unable to do clean up. csDbUnableToExecuteBatch() [jcc][t4][102][10040][3.61.75] Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null com.ibm.db2.jcc.am.BatchUpdateException: [jcc][t4][102][10040][3.61.75] Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null [ Details ]
An error has occurred. The stack trace below shows more information.

!$prd_consD: !csIndexerAbortedMsg!csIndexerUnableToCleanup!csDbUnableToExecuteBatch,!$[jcc][t4][102][10040][3.61.75] Batch failure. The batch was submitted\, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229\, SQLSTATE=null!syExceptionType2,com.ibm.db2.jcc.am.BatchUpdateException,[jcc][t4][102][10040][3.61.75] Batch failure. The batch was submitted\, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229\, SQLSTATE=null
intradoc.common.ServiceException: !csIndexerUnableToCleanup
at intradoc.indexer.Indexer.doCleanUp(Indexer.java:825)
at intradoc.indexer.Indexer.doWork(Indexer.java:278)
at intradoc.indexer.Indexer.doIndexing(Indexer.java:439)
at intradoc.indexer.Indexer.buildIndex(Indexer.java:348)
at intradoc.server.IndexerMonitor.doIndexing(IndexerMonitor.java:1012)
at intradoc.server.IndexerMonitor$4.run(IndexerMonitor.java:832)
Caused by: intradoc.data.DataException: !csDbUnableToExecuteBatch,!$[jcc][t4][102][10040][3.61.75] Batch failure. The batch was submitted\, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229\, SQLSTATE=null
at intradoc.jdbc.JdbcWorkspace.handleSQLException(JdbcWorkspace.java:2371)
at intradoc.jdbc.JdbcWorkspace.executeBatch(JdbcWorkspace.java:525)
at intradoc.indexer.Indexer.cleanUpQueries(Indexer.java:755)
at intradoc.indexer.Indexer.doCleanUp(Indexer.java:821)
... 5 more
Caused by: com.ibm.db2.jcc.am.BatchUpdateException: [jcc][t4][102][10040][3.61.75] Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null
at com.ibm.db2.jcc.am.ed.a(ed.java:404)
at com.ibm.db2.jcc.am.o.a(o.java:365)
at com.ibm.db2.jcc.am.gn.a(gn.java:3332)
at com.ibm.db2.jcc.am.gn.db(gn.java:1609)
at com.ibm.db2.jcc.am.gn.executeBatch(gn.java:1577)
at intradoc.jdbc.JdbcWorkspace.executeBatch(JdbcWorkspace.java:519)
... 7 more

Changes

 The rebuild was suspended, so users can actively check in more items.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.