My Oracle Support Banner

'Exception maxClauseCount is set to 202' Error Generated In Oracle Watchlist Screening (OWS) (Doc ID 1395021.1)

Last updated on DECEMBER 02, 2016

Applies to:

Oracle Watchlist Screening - Version 4.2.1 and later
Oracle Enterprise Data Quality - Version 7.2.0 and later
Information in this document applies to any platform.

Symptoms

when running a search in Case Management we see the following error:

com.datanomic.director.casemanagement.exceptions.CaseException: An error occurred with the search, please see logs for further details.
maxClauseCount is set to 202 (Code: 300,134) (Code: 300,138)
at com.datanomic.director.casemanagement.search.SearchExecutionManager$ExecutionBean.call(SearchExecutionManager.java:238)
at com.datanomic.director.casemanagement.search.SearchExecutionManager$ExecutionBean.call(SearchExecutionManager.java:201)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source

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!

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