HPE NonStop SQL/MX Error – 20410 object-type model-object-name cannot be used to REPARTITION target-object-name.object-typeis the type of the affected SQL/MX table or index.model-object-nameis the fully qualified ANSI name of the model object.target-object-nameis the fully qualified ANSI name of the target object.

In this blog post, let’s learn about the error message “20410 object-type model-object-name cannot be used to REPARTITION target-object-name.object-typeis the type of the affected SQL/MX table or index.model-object-nameis the fully qualified ANSI name of the model object.target-object-nameis the fully qualified ANSI name of the target object.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

20410 object-type model-object-name cannot be used to REPARTITION target-object-name.object-typeis the type of the affected SQL/MX table or index.model-object-nameis the fully qualified ANSI name of the model object.target-object-nameis the fully qualified ANSI name of the target object.

Reason for the Error

The model object is not compatible with the target object. An accompanying repartitioning error message will state the reason.

Solution

Specify a model object that is compatible with the target object, then retry the MODIFY REPARTITION command

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