My Oracle Support Banner

Maintaining the Search Log, Resetting the Log Directory, Error - Event(Code=LOG_STORE_EXCEPTION... (Doc ID 1041081.1)

Last updated on JANUARY 24, 2019

Applies to:

Oracle Knowledge - Version and later
Information in this document applies to any platform.
The log refered to here is the search binary log. The instance standard out log rotates and should maintain itself.

Note: If the current log is deleted it will crash the instance. Never delete all the logs of a running instance. You can stop the instance and delete all the logs if that is necessary.


After the search log will be automatically purged when a new log is written if the limit conditions are reached.  In addition the The 'Log Purge' job ('Log history purge' task) is working from release and on.  Before this the products 'Log history purge' task in the System Manager and automatic purge has not been working.  The task will hang (run forever without completion) and even should you manually stop it, it may left behind a lock on the logfile file that will lead to ConcurrentUpdateException error in the subsequent content crawl (Full or Incremental) job.  Then, user will need to restart the indexer instance in order to recover (release the left-behind lock) and be able to run the content crawl (Full or Incremental) job again without exception.  It was not recommended for use before

In addition the cleaning up of the log derby database is fixed in 8.6.
The Bug 16284520 - RFA: Log Purge task does not cleanup the growing log/catalog/default/dbms/*

As a result in older versions the log files have to be deleted regularly by a different system or manual process.

If the log directory size is not maintained, the the derby database can become corrupted or out of synch with the tasks being executed.  When this happens LOG_STORE_EXCEPTIONs  can cause crawls log errors and the crawls can fail.

Log errors - these errors can be a symptom that your indexer binary log directory is getting too large.



[5288989 Local Workclient-default-taskrun(279301)] Event(Code=LOG_STORE_EXCEPTION, id=#205B81I279301P279297) occurred at 9/26/12 10:40 PM:
[5288989 Local Workclient-default-taskrun (279297)] Connection refused Connection refused
at Method)

Eventually if ignored the log directory dbms (set of tasks that have been performed by the indexer) will fail to load giving these messages.

These would be at startup of the indexer.  This will cause jobs to run irratically and most likely fail at some point.

Creating new log catalog schema.
Exception in thread "LogCatalogBuilder" com.inquira.infra.InquiraRuntimeException: [LogCatalogBuilder @ Fri Sep 28 03:04:00 EDT 2012] (LOG_CATALOG_DB_ERROR)
at com.inquira.log.LogStoreImpl.getDatasource(
at com.inquira.log.LogStoreImpl.deleteCatalog(
at com.inquira.scheduler.SchedulerServiceImpl$
Caused by: SQL Exception: Failed to start database '/inqapps/inquira8/instances/cisco/development/content/data/log/catalog/default/dbms', see the next exception for details.
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)

You may also experience your disk space getting full as the files under [Indexer Instance Folder]\[environment]\content\data\log\catalog\default\dbms\ can grow really large


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

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