!csDbFieldAlreadyExists2,metadata - error - indexer Not Working after creating new metadata (or install component which creates new metadata) (Doc ID 2145203.1)

Last updated on MARCH 10, 2017

Applies to:

Oracle WebCenter Content - Version 11.1.1.8.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.1.8.0 version, Content Server

Indexer is not working in Webcenter content after Webcenter records adapter is configured for webcenter records management server.

ERROR
-----------------------
Index aborted . Unable to modify collection table "IdcText1". Error occurred

[2016-05-25T14:33:08.633+02:00] [UCM_server1] [ERROR] [UCM-CS-000001] [oracle.ucm.idccs] [tid: index rebuild work] [userId: weblogic] [ecid: 73c555f506b4ee1c:2a2f6a47:154e7765d54:-8000-0000000000001d4a,1:18192] [APP: Oracle Universal Content Management - Content Server] general exception[[
intradoc.common.ServiceException: !csUnableToModifyTextCollectionTable,IdcText1
  at intradoc.indexer.OracleTextCollectionHandler.manageCollection(OracleTextCollectionHandler.java:297)
  at intradoc.indexer.IndexerCollectionManager.doWork(IndexerCollectionManager.java:101)
  at intradoc.indexer.Indexer.doIndexing(Indexer.java:411)
  at intradoc.indexer.Indexer.buildIndex(Indexer.java:319)
  at intradoc.server.IndexerMonitor.doIndexing(IndexerMonitor.java:1021)
  at intradoc.server.IndexerMonitor$4.run(IndexerMonitor.java:842)
Caused by: intradoc.data.DataException: !csDbFieldAlreadyExists2,xVitalPeriod
  at intradoc.jdbc.JdbcWorkspace.alterTable(JdbcWorkspace.java:1840)
  at intradoc.indexer.OracleTextCollectionHandler.manageCollection(OracleTextCollectionHandler.java:290)
  at intradoc.indexer.IndexerCollectionManager.doWork(IndexerCollectionManager.java:102)
  ... 4 more

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. configured for webcenter records management server.
2. Rebuild collection id

BUSINESS IMPACT
-----------------------
The issue has the following business impact: indexer is not working
Due to this issue, users cannot use search.

Changes

 The customer had configured the Records Managements Adapter which automatically creates new metadata : Document:1353344.1 - What Metadata fields are affected when enabling the WCCREC/URM features

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms