HPE NonStop SQL/MX Error – 11041 The calculated key length is greater than the allowed limit of max-key-length bytes.

In this blog post, let’s learn about the error message “11041 The calculated key length is greater than the allowed limit of max-key-length bytes.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

11041 The calculated key length is greater than the allowed limit of max-key-length bytes.

Reason for the Error

You attempted to create a trigger and one or more of the following conditions are true:

The primary key length of the temporary table (which must be created when the first trigger is created) is longer than the allowed maximum length.

The length of the temporary table name is longer than the maximum allowed user table name length.

Solution

If the primary key length is too long, recreate your subject table with a primary key that is 12 bytes shorter than the maximum allowed primary key length. If the table name is too long, recreate your subject table with a name length that is six characters shorter than the maximum allowed table name length

Leave A Reply

Your email address will not be published. Required fields are marked *

You May Also Like

In this blog post, let’s learn about the client error message “EngineNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “EngineVersionNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “IncorrectDBClusterLockMode with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022