HPE NonStop SQL/MX Error – 20799 The object-type UID in the resource fork (ruid) does not match the UID (muid) in the metadata for Guardian file (file-name).

In this blog post, let’s learn about the error message “20799 The object-type UID in the resource fork (ruid) does not match the UID (muid) in the metadata for Guardian file (file-name).” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

20799 The object-type UID in the resource fork (ruid) does not match the UID (muid) in the metadata for Guardian file (file-name).

Reason for the Error

An inconsistency was found. The UID value in the metadata tables does not match the UID value in the resource fork.

Solution

Run the -ru option of MXTOOL FIXUP to make the UID value in the resource fork match the UID value in the metadata

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 error message “1104 Default value string is too long for column column-name.”...
  • Data
  • December 3, 2024
In this blog post, let’s learn about the error message “3165 The precision or exponent value specified in value was...
  • Data
  • December 3, 2024
In this blog post, let’s learn about the error message “2051 Either control optionoption name or value ‘value’is not valid.”...
  • Data
  • December 3, 2024