HPE NonStop SQL/MX Error – 20413 The attribute for object-type model-object-name must be the same as the attribute for target-object-name.attributeis one of:PARTITION BY columnsBLOCKSIZEPRIMARY KEY (not relevant for an index)STORE BY key (not relevant for an index)number of columnsAUDITCOMPRESSobject-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 “20413 The attribute for object-type model-object-name must be the same as the attribute for target-object-name.attributeis one of:PARTITION BY columnsBLOCKSIZEPRIMARY KEY (not relevant for an index)STORE BY key (not relevant for an index)number of columnsAUDITCOMPRESSobject-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

20413 The attribute for object-type model-object-name must be the same as the attribute for target-object-name.attributeis one of:PARTITION BY columnsBLOCKSIZEPRIMARY KEY (not relevant for an index)STORE BY key (not relevant for an index)number of columnsAUDITCOMPRESSobject-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 for MODIFY REPARTITION differs from the target object on the specified attribute.

Solution

Specify a model object with attribute identical to that of the target object

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