HPE NonStop SQL/MX Error – 1151 POS (Partition Overlay Support) was not applied because volume names could not be generated for the partitions. So a simple table table-name was created without partitions.

In this blog post, let’s learn about the error message “1151 POS (Partition Overlay Support) was not applied because volume names could not be generated for the partitions. So a simple table table-name was created without partitions.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

1151 POS (Partition Overlay Support) was not applied because volume names could not be generated for the partitions. So a simple table table-name was created without partitions.

Reason for the Error

When the Partition Overlay Support feature is enabled without setting volume names (through CQD POS_LOCATIONS) for table partitions to reside on, location names are generated automatically. However, NonStop SQL/MX could not generate the location names automatically, and because the CQD POS_RAISE_ERROR is not set, the given table is created as a simple table without partitions as it would be if the Partition Overlay Support feature was not enabled.

Solution

None if a nonpartitioned table is requested. To request a partitioned table, delete the table, verify that disk volumes are available, and resubmit. You can also specify the volume names where the partitions need to be created for the given CREATE TABLE through CONTROL QUERY DEFAULT POS_LOCATIONS, and then retry the request

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