HPE NonStop SQL/MX Error – 20372 The resource fork is not accessible.

In this blog post, let’s learn about the error message “20372 The resource fork is not accessible.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

20372 The resource fork is not accessible.

Reason for the Error

The resource fork is either broken or does not exist.

Solution

None. This is an informational message

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