My Oracle Support Banner

Metadata indexing failing with "ORA-12899 or ORA-904" resulting in content items stuck in GenWWW after changing Metadata field type (Doc ID 1560366.1)

Last updated on JUNE 07, 2018

Applies to:

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

Symptoms

 

After changing the metadata field type of an existing field ( Text to Long Text, or Text/Long Text to Memo), The following two cases are seen:

The issue can be replicated with following steps

1. On Configuration Manager applet, edit an existing field and change the field type.
(e.g. Text -> Long Text)

2. Click [Update Database Design] to apply the change to repository database.

3. Then, check in a content with the long text value to changed field
(For example in case of changing the type from Text to Long Text,
setting 31 chars or more (e.g. "aaaaaaa010aaaaaaa020aaaaaaa030aaaaaaa040aaaaaaa050"))

4. Checking the content information after check in
--> It stays GenWWW status and showing error "Indexing aborted on this content item." (NG: Case-1)
--> When the issue occurs, Content Server log shows the following error

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:600)
at intradoc.indexer.IndexerBulkLoader.createBulkLoad(IndexerBulkLoader.java:384)
at intradoc.indexer.IndexerBulkLoader.doWork(IndexerBulkLoader.java:170)
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)

--> When the issue occurs, the trace shows the following ORA-12899 error

>indexer/6 06.10 04:23:03.289 index update work Unable to execute batch: intradoc.data.DataException: !csDbUnableToExecuteBatch,!$ORA-12899: value too large for column "DEV_OCS"."IDCTEXT1"."XTESTFIELD01" (actual: 50\, maximum: 30)
indexer/6 06.10 04:23:03.289 index update work
indexer/6 06.10 04:23:03.289 index update work at intradoc.jdbc.JdbcWorkspace.handleSQLException(JdbcWorkspace.java:2548)
indexer/6 06.10 04:23:03.289 index update work at intradoc.jdbc.JdbcWorkspace.executeBatch(JdbcWorkspace.java:443)
indexer/6 06.10 04:23:03.289 index update work at intradoc.indexer.OracleTextHandler.batchExecution(OracleTextHandler.java:497)
indexer/6 06.10 04:23:03.289 index update work at intradoc.indexer.OracleTextHandler.updateDocuments(OracleTextHandler.java:429)
indexer/6 06.10 04:23:03.289 index update work at intradoc.indexer.OracleTextHandler.executeIndexer(OracleTextHandler.java:250)
indexer/6 06.10 04:23:03.289 index update work at intradoc.indexer.IndexerExecution.executeIndexer(IndexerExecution.java:597)
indexer/6 06.10 04:23:03.289 index update work at intradoc.indexer.IndexerDriverAdaptor.executeIndexer(IndexerDriverAdaptor.java:144)
indexer/6 06.10 04:23:03.289 index update work at intradoc.indexer.DocIndexerAdaptor.indexList(DocIndexerAdaptor.java:209)
indexer/6 06.10 04:23:03.289 index update work at intradoc.indexer.DocIndexerAdaptor.finishIndexing(DocIndexerAdaptor.java:131)
indexer/6 06.10 04:23:03.289 index update work at intradoc.indexer.IndexerBulkLoader.createBulkLoad(IndexerBulkLoader.java:383)
indexer/6 06.10 04:23:03.289 index update work at intradoc.indexer.IndexerBulkLoader.doWork(IndexerBulkLoader.java:171)
indexer/6 06.10 04:23:03.289 index update work at intradoc.indexer.Indexer.doIndexing(Indexer.java:411)
indexer/6 06.10 04:23:03.289 index update work at intradoc.indexer.Indexer.buildIndex(Indexer.java:319)
indexer/6 06.10 04:23:03.289 index update work at intradoc.server.IndexerMonitor.doIndexing(IndexerMonitor.java:1021)
indexer/6 06.10 04:23:03.289 index update work at intradoc.server.IndexerMonitor$4.run(IndexerMonitor.java:842)

 5. After that, shorten the field's value (e.g. shorten the value 30 chars) and resubmit the content to indexing

--> it succeeds and the content is now Released.

6. In Repository Manager, start indexer rebuild as "fast rebuild".

7. Then, check in a content with any value to the changed field.

8. Checking the content information after check in
--> It stays GenWWW status and showing error "Indexing aborted on this content item." (NG: Case-2)
--> When the issue occurs, Content Server log shows same error as step 4.

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:600)
at intradoc.indexer.IndexerBulkLoader.createBulkLoad(IndexerBulkLoader.java:384)
at intradoc.indexer.IndexerBulkLoader.doWork(IndexerBulkLoader.java:170)
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)

 --> But trace shows the following ORA-904 error instead of ORA-12899.

>indexer/6 06.10 04:38:44.989 index update work Unable to execute batch: intradoc.data.DataException: !csDbUnableToExecuteBatch,!$ORA-00904: "XTESTFIELD01": invalid identifier
indexer/6 06.10 04:38:44.989 index update work
indexer/6 06.10 04:38:44.989 index update work at intradoc.jdbc.JdbcWorkspace.handleSQLException(JdbcWorkspace.java:2548)
indexer/6 06.10 04:38:44.989 index update work at intradoc.jdbc.JdbcWorkspace.executeBatch(JdbcWorkspace.java:443)
indexer/6 06.10 04:38:44.989 index update work at intradoc.indexer.OracleTextHandler.batchExecution(OracleTextHandler.java:497)
indexer/6 06.10 04:38:44.989 index update work at intradoc.indexer.OracleTextHandler.updateDocuments(OracleTextHandler.java:429)
indexer/6 06.10 04:38:44.989 index update work at intradoc.indexer.OracleTextHandler.executeIndexer(OracleTextHandler.java:250)
indexer/6 06.10 04:38:44.989 index update work at intradoc.indexer.IndexerExecution.executeIndexer(IndexerExecution.java:597)
indexer/6 06.10 04:38:44.989 index update work at intradoc.indexer.IndexerDriverAdaptor.executeIndexer(IndexerDriverAdaptor.java:144)
indexer/6 06.10 04:38:44.989 index update work at intradoc.indexer.DocIndexerAdaptor.indexList(DocIndexerAdaptor.java:209)
indexer/6 06.10 04:38:44.989 index update work at intradoc.indexer.DocIndexerAdaptor.finishIndexing(DocIndexerAdaptor.java:131)
indexer/6 06.10 04:38:44.989 index update work at intradoc.indexer.IndexerBulkLoader.createBulkLoad(IndexerBulkLoader.java:383)
indexer/6 06.10 04:38:44.989 index update work at intradoc.indexer.IndexerBulkLoader.doWork(IndexerBulkLoader.java:171)
indexer/6 06.10 04:38:44.989 index update work at intradoc.indexer.Indexer.doIndexing(Indexer.java:411)
indexer/6 06.10 04:38:44.989 index update work at intradoc.indexer.Indexer.buildIndex(Indexer.java:319)
indexer/6 06.10 04:38:44.989 index update work at intradoc.server.IndexerMonitor.doIndexing(IndexerMonitor.java:1021)
indexer/6 06.10 04:38:44.989 index update work at intradoc.server.IndexerMonitor$4.run(IndexerMonitor.java:842)

 

Changes

 This symptom occurs after changed type of an existing field, e.g. Text -> Long Text

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.