OracleTextSearch Indexing Is Interrupted with ORA-12899: value too large for column After Increasing Metadata Field Size (Doc ID 1382543.1)

Last updated on APRIL 07, 2017

Applies to:

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

Symptoms

You are using the OracleTextSearch search engine in UCM 10g.

After modifying a metadata field value from Text to Long Text (or Memo), the Update Database Design will modify the docmeta table to fit the new field size and will allow new files to be checked in using a metadata field value longer than 30 characters.

However, when those files are indexed, the indexer will fail / be interrupted, throwing the following errors


In the Content Server Logs:

Indexing aborted. Unable to index metadata only. This may indicate the collection is damaged. Indexing aborted. [ Details ]

An error has occurred. The stack trace below shows more information.

!csIndexerAbortedMsg!csIndexerMetaOnlyFailed
intradoc.common.ServiceException: !csIndexerMetaOnlyFailed
at intradoc.indexer.IndexerBulkLoader.handleIndexerResults(IndexerBulkLoader.java:580)
at intradoc.indexer.IndexerBulkLoader.createBulkLoad(IndexerBulkLoader.java:372)
at intradoc.indexer.IndexerBulkLoader.doWork(IndexerBulkLoader.java:165)
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)

In the server output (<ucm_home>/etc/log) after enabling full verbose tracing for systemdatabase:

systemdatabase 11.24 11:53:28.348 index update work
'csDbUnableToExecuteBatch,!$ORA-12899: value too large for column
"UCM"."IDCTEXT1"."XMODIFIEDFIELD" (actual: 209\, maximum: 200)
at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:343)
at oracle.jdbc.driver.OracleProparedStatement.executeBatch(OracleProparedStatement.java:10768)
at intradoc.jdbc.JdbcWorkspace.executeBatch(JdbcWorkspace.java:519)
at oracletextsearch.indexer.OracleTextHandler.batchExecution(OracleTextHandler.java:527)
at oracletextsearch.indexer.OracleTextHandler.updateDocuments(OracleTextHandler.java:459)
...


A fast rebuild of the ots1/ots2 search index does not modify the IDCTEXT1/IDCTEXT2 column sizes.

A full collection rebuild will rebuild the IDCTEXT1/IDCTEXT2 tables with the new field size but may take considerable time with many documents in the system.

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