HPE NonStop SQL/MX Error – 1271 ALLOCATE failed for object object-name because the number of extents to be allocated number is greater than the MAXEXTENTS for a partition of the object.

In this blog post, let’s learn about the error message “1271 ALLOCATE failed for object object-name because the number of extents to be allocated number is greater than the MAXEXTENTS for a partition of the object.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

1271 ALLOCATE failed for object object-name because the number of extents to be allocated number is greater than the MAXEXTENTS for a partition of the object.

Reason for the Error

A CREATE or ALTER operation specified an ALLOCATE attribute value that was greater than the MAXEXTENTS value for the affected database object, which is not allowed.

Solution

If possible, alter the MAXEXTENTS attribute value to be greater than the desired number of extents to be allocated. The current maximum value for MAXEXTENTS is 768

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