HPE NonStop SQL/MX Error – 20680 Object has no matching locations.

In this blog post, let’s learn about the error message “20680 Object has no matching locations.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

20680 Object has no matching locations.

Reason for the Error

Specified Guardian File Name pattern or set of patterns does not match any of the table or index partitions.

Solution

Specify the Guardian File Name pattern that matches at least one of the table or index partitions and retry rename operation using MODIFY 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