Configuration parameter [execution]/default_statement_concurrency_limit set to unsupported value.

[DavidJo]

Hello,

   I found the following warning message in the DBA cockpit.

      Configuration parameter [execution]/default_statement_concurrency_limit set to unsupported value.

   Please check and fix it.

[Craig-Zhang]

Which value is set for default_statement_concurrency_limit?

[simon25 · Accepted solution]

Hello,

If you actually run this script "HANA_Configuration_Parameters_2.00.040+.txt" (Note ##1969700) on tenant level there will be a "recommended_value" column suggestion if HANA determines that the current "default_statement_concurrency_limit" is misconfigured with consideration for the number of "cpu_threads" on the physical server.
(M_HOST_INFORMATION view)

Kind Regards
Simon

[DavidJo · Accepted solution]

Hello, Thank you everyone. Since I am using SAP PCE and SAP manages the HANA DBMS, I initially expected that simply opening a case would result in SAP applying the fix automatically. Now that I know which parameter needs to be changed, I plan to create a separate SR to remove the event. Thanks, David Jo

[RACHID_AITBOUALE]

Hi @DavidJo,

This warning usually pops up when the parameter is manually set to a number that the HANA engine considers 'unsafe' for your current CPU architecture—for instance, setting a limit of 64 on a 32-core system.

From an Industrial Systems Engineering perspective, the most stable approach is to set default_statement_concurrency_limit to 0. This allows the database to dynamically calculate the limit based on the actual workload and available threads, keeping your 'Clean Core' safe from manual misconfiguration.

Steps to fix:

• Navigate to DBA Cockpit > Configuration > execution.

• Locate default_statement_concurrency_limit and change it to 0.

• Save and check if the warning clears—no restart is usually required for this specific parameter.

Are you running on a scale-out or scale-up architecture? Sometimes this warning appears after a hardware migration where the new host has fewer cores than the previous one.