HP NonStop SQL/MX Messages Manual page 484

Utility Messages (20000 through 23099)
Recovery. Correct the field length in the format file and resubmit.
SQL 20023
20023 Object does not exist.
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.
SQL 20024
20024 Object already exists.
Cause. You tried to create a table that already exists.
Effect. The operation fails.
Recovery. Change the name of the table and resubmit.
SQL 20025
20025 An internal error occurred while trying to access
metadata for object object-name. Expecting cache state
(state1) but cache state is (state2).
Where object-name is the name of the table, view, synonym, trigger, and so on.
Where state1/state2 is:
•
[not] opened,
•
[not] closed,
•
[not] modified,
•
[not] created
Cause. Illegal sequence of operations performed by a utility.
Effect. The operation fails.
Recovery. Do not attempt recovery. Contact your service provider.
HP NonStop SQL/MX Messages Manual—640324-001
18- 8