EDQ java.lang.IndexOutOfBoundsException (Code 201,108)) Thrown when Running Jobs
(Doc ID 2234950.1)
Last updated on DECEMBER 06, 2019
Applies to:
Oracle Enterprise Data Quality - Version 12.2.1 and laterInformation in this document applies to any platform.
Symptoms
EDQ 12.2.1.2.0 reports the following in some cases in which external lookups had been moved to staged data (presumably hoping to improve performance):
SEVERE: 14-Feb-2017 18:58:03: [EDQ-06919] [process <PROCESS_NAME> [1641]/job:<JOB_NAME> (808):[7800]] : runtime process terminated uncleanly: java.lang.IndexOutOfBoundsException (Code: 201,108)
com.datanomic.director.runtime.AbortedProcessException: java.lang.IndexOutOfBoundsException (Code: 201,108)
at com.datanomic.director.runtime.engine.RuntimeProcessCloud.execute(RuntimeProcessCloud.java:1068)
at com.datanomic.director.runtime.coordination.BasicExecutionCoordinator.run(BasicExecutionCoordinator.java:130)
at com.datanomic.director.runtime.coordination.AbstractExecutionCoordinator.execute(AbstractExecutionCoordinator.java:166)
at com.datanomic.director.runtime.engine.jobs.RuntimeProcessJob.runTask(RuntimeProcessJob.java:484)
...
com.datanomic.director.runtime.AbortedProcessException: java.lang.IndexOutOfBoundsException (Code: 201,108)
at com.datanomic.director.runtime.engine.RuntimeProcessCloud.execute(RuntimeProcessCloud.java:1068)
at com.datanomic.director.runtime.coordination.BasicExecutionCoordinator.run(BasicExecutionCoordinator.java:130)
at com.datanomic.director.runtime.coordination.AbstractExecutionCoordinator.execute(AbstractExecutionCoordinator.java:166)
at com.datanomic.director.runtime.engine.jobs.RuntimeProcessJob.runTask(RuntimeProcessJob.java:484)
...
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 |
References |