Dremio 3.0 - oracle data source - maxClauseCount is set to 1024

Cannot connect to a reasonable big database in Oracle.

Getting this error when trying to open up the schema - maxClauseCount is set to 1024

Hello @bharath_natarajan,

This looks like a bug we have identified in 3.0.0 and are working to fix. Can you give a count of the number of tables in the schema?

Using sqlplus or sqldeveloper,

select owner, count(*) from dba_tables group by owner;
select owner, count(*) from dba_views group by owner;

If you do not have access to dba_ dictionary then use below (connect to sqlplus/sqldeveloper as the same user you are connecting to Dremio)

select count(*) from dba_tables;
select count(*) from dba_views;

The schema I’m looking for has 1396 objects. Over all around 5500.

Also, any ideas when this will be fixed. Can’t proceed with testing without this fix much.

Is there any workaround for that? Such as modify a system property or configuration file?

We also face the same “maxClauseCount is set to 1024” issue while connecting to Elasticsearch as the source. As soon as we try to connect it shows this error in the UI. This started happening in Dremio 3.0. We are able to successfully connect to the same Elasticsearch with Dremio 2.1 and 1.0.

Is there any setting that should be changed in Dremio 3.0?

@bharath_natarajan @pisces312 @igreg Sorry for the troubles. This has been fixed, expect a hotfix patch likely next week to address this

@bharath_natarajan @pisces312 @igreg new hotfix patch is now available - https://www.dremio.com/download/

1 Like

Thanks for the quick turnaround Anthony.

1 Like

I’m still seeing this problem after the patch with Microsoft SQL Server…

“maxClauseCount is set to 1024”

Thanks for the update.

This is still a bug in 3.0.5-201812021947440442-9a23f45

Hi @pisces312

The complete fix for this issue is in 3.0.6. Kindly download from the Dremio Downloads page


Thank you! Could the docker image (dremio/dremio-oss) be updated as well?

This is a critical error that stopped us on PoC as well.

A 3.0.6 docker image for community edition (OSS) has been published.


Thanks @balaji.ramaswamy. I have seen it’s fixed.