SQL/MX 2.x Messages Manual (G06.24+, H06.03+)

Utility Messages (20000 through 23099)
HP NonStop SQL/MX Messages Manual—523730-004
17-7
Where table2 is the name of the referencing table.
Where const is the name of the constraint for the referencing table.
Cause. SQL/MX found a discrepancy while reading metadata information. The
information returned is inconsistent.
Effect. The operation fails.
Recovery. None. This is an internal error. Contact your service provider.
SQL 20021
Cause. The utility subsystem that reads and maintains metadata encountered an
unexpected data type for a column.
Effect. The operation fails.
Recovery. None. This is an internal error. Contact your service provider.
SQL 20022
Where $0~int0 is the value of the field length specified in the format file.
Where $1~string0 is the corresponding column name.
Where $2~int1 is the required value for the field length.
Cause. The field length provided in the format file (for binary import) and the field
length required by the column are not the same.
Effect. The operation fails.
Recovery. Correct the field length in the format file and resubmit.
SQL 20023
Cause. The utility subsystem that reads and maintains metadata could not find the
requested SQL/MX object. A possible cause is that the catalog, schema, or object
name is misspelled in the request. SQL/MX objects can be catalogs, schemas, tables,
trigger temporary tables, stored procedures, indexes, or MP aliases.
Effect. The operation fails.
Recovery. Check for misspellings and resubmit.
20021 An internal error occurred - invalid column data type.
20022 The field length ($0~int0) for column $1~string0 does
not match the required length ($2~int1).
20023 Object does not exist.