HPE NonStop SQL/MX Error – 20161 Resume option of RECOVER command for DUP is possible only if DUP finished the data transfer between the source and target objects. RECOVER cannot be performed.

In this blog post, let’s learn about the error message “20161 Resume option of RECOVER command for DUP is possible only if DUP finished the data transfer between the source and target objects. RECOVER cannot be performed.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

20161 Resume option of RECOVER command for DUP is possible only if DUP finished the data transfer between the source and target objects. RECOVER cannot be performed.

Reason for the Error

You cannot specify the RESUME option before bulk I/O has finished.

Solution

Use the CANCEL option to cancel the request. Start a new DUP request after RECOVER is done

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