CLOB fields in Oracle do not allow you to simply compare them to strings. For example:
However this is the sort of code the queryFilter logic will generate when querying against explicit tables. This will cause the queryFilter code to break. There needs to be logic to account for this difference, because several queryFilter queries in the Admin UI filter based on CLOB columns in explicit tables, and as such will fail when using Oracle.