ETL Crawl Fails At IM Log Extraction with No space left on device (Doc ID 1598614.1)

Last updated on FEBRUARY 20, 2017

Applies to:

Oracle Knowledge - Version 8.4.6 and later
Information in this document applies to any platform.


 If your ETL job consistently fails at the IM Log Extraction phase, and the Indexer log contains the following:

[170972 Scheduler(8968)] Event(Code=LOG_STORE_EXCEPTION, id=#533B7I8968P42) occurred at 9/22/13 4:00 PM: com.inquira.infra.trnsp.TransportExceptionDO_NOT_ADDcom.inquira.event
[170972 Scheduler (42)] UNKNOWN MESSAGE ID "SCHEDULER_JOB_INITIALIAZTION_FAILURE" called with: "com.inquira.infra.trnsp.TransportException: [Scheduler @ Sun Sep 22 16:00:03 MDT 2013] ([Scheduler @ Sun Sep 22 16:00:03 MDT 2013] (REVISION_LOCK_IOEXCEPTION <INQUIRA_HOME>/production/content/data/revision/default))" No space left on device

unable to process scheduler request: public abstract com.inquira.scheduler.workclient.WorkClientResponse com.inquira.scheduler.SynchronousSchedulerService.requestWork(com.inquira.scheduler.workclient.WorkClientDefinition) throws java.lang.Exception
[170973 Local Workclient-default-statupd(8969)] Event(Code=WORKCLIENT_FAILURE, id=#533B8I8969P7360) with Error occurred at 9/22/13 4:00 PM: Workclient Local Workclient failed due to cause java.lang.reflect.InvocationTargetException No space left on device


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