HPE NonStop SQL/MX Error – 20450 You asked to drop only the data fork data fork name but a resource fork exists (resource fork name).

In this blog post, let’s learn about the error message “20450 You asked to drop only the data fork data fork name but a resource fork exists (resource fork name).” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

20450 You asked to drop only the data fork data fork name but a resource fork exists (resource fork name).

Reason for the Error

You specified invalid options for the GOAWAY command.

Solution

Do not use the DATA/RESOURCE FORK option, and resubmit

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