Forum Stats

  • 3,758,122 Users
  • 2,251,336 Discussions
  • 7,870,040 Comments

Discussions

Full Collection Rebuild fails

User_Q91MT
User_Q91MT Member Posts: 20 Red Ribbon
edited Jun 28, 2021 2:58PM in WebCenter Content

Upgraded to new 12c WCC and migrated ~4 Million documents( both native & webviewable files ). However running the Full Collection Rebuild fails after around 450k docs with below error. Using ElasticSearch in WCC. Further we see documents appearing in GENWWW.

Few steps performed:

  • Applied latest OIT Apr 21 patch(as some links suggested Library missing in OIT issue)
  • created archiver & deleted genwww docs
  • disabled all custom components
  • restarted Content server
  • restarted the ongoing AUC and Full rebuild but throws same error again.
  • Cancelled the ongoing AUC and started again but got the same error as well.

Documents deleted from WIP queue(in GENWWW status) before changed flag to deleted status in DB but after restarting the AUC/Full rebuild, these same documents are getting into genwww status again.


Error:

">(internal)/6 06.22 15:25:40.107 index update work Unable to index metadata only. This may indicate the collection is damaged. Indexing aborted.

>systemdatabase/6 06.22 15:25:40.107 index update work !csMonitorActiveDbConnections,0

>systemdatabase/6 06.22 15:25:40.107 index update work Connection with id of 'index update work.3' is removed from active connections with key of '482'.

>systemdatabase/6 06.22 15:25:40.107 index update work release pool connection

>(internal)/3 06.22 15:25:40.107 index update work !csIndexerAbortedMsg intradoc.common.ServiceException: !csIndexerMetaOnlyFailed

(internal)/3 06.22 15:25:40.107 index update work at intradoc.indexer.IndexerBulkLoader.handleIndexerResults(IndexerBulkLoader.java:601)

(internal)/3 06.22 15:25:40.107 index update work at intradoc.indexer.IndexerBulkLoader.createBulkLoad(IndexerBulkLoader.java:373)

(internal)/3 06.22 15:25:40.107 index update work at intradoc.indexer.IndexerBulkLoader.doWork(IndexerBulkLoader.java:170)"

Other traces

>taskmanager/6 06.22 06:19:08.173 TextExport_47 task Monitor <[email protected]> exiting

>taskmanager/7 06.22 06:19:08.173 TaskLauncher_TextExport_stderr__47 error reading available bytes from input stream java.io.IOException: Stream closed

taskmanager/7 06.22 06:19:08.173 TaskLauncher_TextExport_stderr__47 at java.io.BufferedInputStream.getInIfOpen(BufferedInputStream.java:159)

taskmanager/7 06.22 06:19:08.173 TaskLauncher_TextExport_stderr__47 at java.io.BufferedInputStream.available(BufferedInputStream.java:410)

taskmanager/7 06.22 06:19:08.173 TaskLauncher_TextExport_stderr__47 at java.io.BufferedInputStream.available(BufferedInputStream.java:410)

taskmanager/7 06.22 06:19:08.173 TaskLauncher_TextExport_stderr__47 at intradoc.taskmanager.TaskProcessStreamMonitor.readInputStream(TaskProcessStreamMonitor.java:353)

taskmanager/7 06.22 06:19:08.173 TaskLauncher_TextExport_stderr__47 at intradoc.taskmanager.TaskProcessStreamMonitor.runStdErrThread(TaskProcessStreamMonitor.java:456)

@Srinath Menon-Oracle @rajeev.y.ranjan-Oracle