SQL/MX 3.2 Messages Manual (H06.25+, J06.14+)

Utility Messages (20000 through 23099)
HP NonStop SQL/MX Release 3.2 Messages Manual—691121-001
19-117
Recovery. Contact your service provider.
SQL 20798
Where active/inactive specifies whether the lock is active or inactive.
Where object specifies whether the object is a table or view.
Where object name is the ANSI fully qualified name of the table or view.
Cause. An inconsistency was found during the VERIFY operation.
Effect. None. This is an informational message.
Recovery. For an inactive DDL lock, contact your service provider. For an active DDL
lock, wait for the operation holding the lock to complete.
SQL 20799
Where object-type is the type of object, which can be CATALOG, SCHEMA,
TABLE, or INDEX.
Where ruid is the UID value of the object stored in the resource fork.
Where muid is the UID value of the object stored in the metadata.
Where file-name is the name of the Guardian file.
Cause. An inconsistency was found. The UID value in the metadata tables does not
match the UID value in the resource fork.
Effect. This mismatch causes operations that depend on these values to be the same
to fail.
Recovery. Run the -ru option of MXTOOL FIXUP to make the UID value in the
resource fork match the UID value in the metadata.
SQL 20800
Where rscheme is the partitioning scheme of the object stored in the resource fork.
20798 There is currently an active/inactive DDL lock for
object (object name).
20799 The object-type UID in the resource fork (ruid) does
not match the UID (muid) in the metadata for Guardian file
(file-name).
20800 The partitioning scheme in resource fork rscheme does
not match the partitioning scheme mscheme defined in the
metadata for Guardian file (file-name).