My Oracle Support Banner

Auto Update Index Cycle is Failing with "Indexing aborted. Unable to index metadata only. This may indicate the collection is damaged. csDbUnableToExecuteQuery,IcollectionIndexMeta2!$ORA-14400: inserted partition key does not map to any partition" (Doc ID 1488848.1)

Last updated on APRIL 04, 2024

Applies to:

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

Symptoms

The Content Server auto update index cycle is failing.

In content server logs:

Error 08/31/12 8:56:17 AM server: 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.

!$server: !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)

More meaningful information came from indexer and systemdatabase tracing:

systemdatabase 09.04 13:14:58.119 index update work !csDbUnableToExecuteQuery,IcollectionIndexMeta2!$ORA-14400: inserted partition key does not map to any partition

systemdatabase 09.04 13:14:58.119 index update work 754035589 ms. [ORA-14400: inserted partition key does not map to any partition
]
indexer 09.04 13:14:58.119 index update work !csDbUnableToExecuteQuery,IcollectionIndexMeta2!$ORA-14400: inserted partition key does not map to any partition
-exception stack
intradoc.data.DataException: !csDbUnableToExecuteQuery,IcollectionIndexMeta2!$ORA-14400: inserted partition key does not map to any partition

at intradoc.jdbc.JdbcWorkspace.handleSQLException(JdbcWorkspace.java:2371)
at intradoc.jdbc.JdbcWorkspace.execute(JdbcWorkspace.java:650)
at intradoc.indexer.DatabaseFullTextHandler.doUpload(DatabaseFullTextHandler.java:212)
at intradoc.indexer.DatabaseFullTextHandler.executeIndexer(DatabaseFullTextHandler.java:133)
at intradoc.indexer.IndexerExecution.executeIndexer(IndexerExecution.java:593)
at intradoc.indexer.IndexerDriverAdaptor.executeIndexer(IndexerDriverAdaptor.java:141)
at intradoc.indexer.DocIndexerAdaptor.indexList(DocIndexerAdaptor.java:211)
at intradoc.indexer.DocIndexerAdaptor.finishIndexing(DocIndexerAdaptor.java:133)
at intradoc.indexer.IndexerBulkLoader.createBulkLoad(IndexerBulkLoader.java:370)
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)
Caused by: java.sql.SQLException: ORA-14400: inserted partition key does not map to any partition

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
Cause
Solution


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