INVALID_PARAMETER_VALUE: DBR version 16.4 or higher is required to query table

ikhwan — Wed, 21 Jan 2026 02:21:33 GMT

We are encountering issue lately around 17 January 2026.

We make a Pipeline using DLT and RLS for filtering rows based on user's email. Previously our Row Level Security (RLS) is working fine. Until 3 days ago the dashboard is got into problem said:

INVALID_PARAMETER_VALUE: Query on table with row filter or column mask not supported on assigned clusters.

We use the Serverless which means it's should be the latest stable version of the Databricks Runtime (DBR).

Tried to change from RLS to ABAC but the error persists with another message but seemed to be same rootcause:

INVALID_PARAMETER_VALUE: DBR version 16.4 or higher is required to query table due to it being protected by an ABAC policy.

Please help.

Re: INVALID_PARAMETER_VALUE: DBR version 16.4 or higher is required to query table

ikhwan — Wed, 21 Jan 2026 02:39:40 GMT

Adding more information:

Region: Singapore (ap-southeast-1)
Warehouse type: Serverless
Channel: Both Current (v 2025.35) and Preview (v 2025.35)
The error occurred on two separate Databricks accounts in the same region.

Re: INVALID_PARAMETER_VALUE: DBR version 16.4 or higher is required to query table

ikhwan — Wed, 21 Jan 2026 09:36:25 GMT

I have been trying to create a serverless workspace using us-east-1 and the RLS working fine. I think it's confirmed that only happened in specific region (in my case ap-southeast-1)

Hi @ikhwan, Based on your description, you are seeing two...

SteveOstrowski — Mon, 09 Mar 2026 00:59:11 GMT

Hi @ikhwan,

Based on your description, you are seeing two separate error messages when querying tables that have row filters applied:

1. "Query on table with row filter or column mask not supported on assigned clusters"
2. "INVALID_PARAMETER_VALUE: DBR version 16.4 or higher is required to query table due to it being protected by an ABAC policy"

And you have confirmed this works correctly in us-east-1 but fails in ap-southeast-1 (Singapore), which is a useful data point.

UNDERSTANDING THE ERRORS

Both errors point to how fine-grained access control (FGAC) enforcement works under the hood. When you query a table with row filters or column masks, Databricks uses serverless compute behind the scenes to enforce those policies, even if you are running on a SQL warehouse. For this mechanism to function, the workspace must be enabled for serverless compute, and the serverless infrastructure in that region must support the required DBR version.

The "assigned clusters" error means the compute executing your query does not have the FGAC enforcement path available. The "DBR version 16.4 or higher" error for ABAC specifically tells you the serverless runtime backing your region has not yet been updated to 16.4+.

Since you confirmed this works in us-east-1 but not in ap-southeast-1, this is most likely a regional rollout timing difference for serverless runtime versions. Serverless infrastructure updates roll out progressively across regions, and ap-southeast-1 may not yet have received the runtime version needed for ABAC policy enforcement at the time you tested.

WHAT YOU CAN DO

1. Check your serverless compute enablement: In your workspace, go to Admin Settings, then Compute, and verify that serverless compute is enabled for the workspace. Without this, FGAC enforcement on dedicated/assigned compute will not work.

2. Verify the SQL warehouse version: In your SQL warehouse configuration, check whether you are on "Current" or "Preview" channel. You mentioned you tried both v2025.35 versions, but try switching to the Preview channel if you have not already, as it tends to receive newer runtime versions sooner.

3. Open a support ticket: Since you have confirmed this is region-specific (working in us-east-1, failing in ap-southeast-1) and the errors reference a specific DBR version requirement, your Databricks account team or support can confirm the serverless runtime version currently deployed in ap-southeast-1 and provide an ETA for when 16.4+ will be available there. This is the most direct path to resolution.

4. Temporary workaround: If you need this working immediately, you could consider provisioning your workload in us-east-1 where the feature is already functioning, assuming data residency requirements allow it.

RELEVANT DOCUMENTATION

Row filters and column masks:
https://docs.databricks.com/aws/en/tables/row-and-column-filters

ABAC (attribute-based access control):
https://docs.databricks.com/aws/en/data-governance/unity-catalog/abac/

Dedicated compute and FGAC requirements:
https://docs.databricks.com/aws/en/compute/dedicated-limitations

Features with limited regional availability:
https://docs.databricks.com/aws/en/resources/feature-region-support

* This reply used an agent system I built to research and draft this response based on the wide set of documentation I have available and previous memory. I personally review the draft for any obvious issues and for monitoring system reliability and update it when I detect any drift, but there is still a small chance that something is inaccurate, especially if you are experimenting with brand new features.

If this answer resolves your question, could you mark it as "Accept as Solution"? That helps other users quickly find the correct fix.

topic INVALID_PARAMETER_VALUE: DBR version 16.4 or higher is required to query table in Data Governance

INVALID_PARAMETER_VALUE: DBR version 16.4 or higher is required to query table

Re: INVALID_PARAMETER_VALUE: DBR version 16.4 or higher is required to query table

Re: INVALID_PARAMETER_VALUE: DBR version 16.4 or higher is required to query table

Hi @ikhwan, Based on your description, you are seeing two...