HP NonStop SQL/MX Messages Manual page 28

Data Definition Language (DDL) Messages (1000
through 1999)
SQL 1003
1003 Schema schema does not exist.
Where schema is the ANSI name of the affected schema.
Cause. In a replication context: a REPLICATION SCHEMA operation specified a
schema that does not exist.
Effect. The operation fails.
Recovery. Check that a schema named schema does exist and resubmit.
SQL 1004
1004 Object object-name does not exist or object type is
invalid for the current operation.
Where object-name is the name of an SQL/MX object.
Cause. You attempted an operation on an object that does not exist or attempted an
operation on an object with the wrong type. For example, you tried to drop a view but
specified a table name.
Effect. The operation fails.
Recovery. Check that an object object-name exists. If you did not fully qualify the
name, check that the defaults generate the correct fully qualified name and resubmit.
SQL 1005
1005 Constraint constraint-name does not exist.
Where constraint-name is the name of a column constraint or table constraint.
Cause. The ALTER TABLE statement you attempted requires the existence of a
constraint named constraint-name.
Effect. The operation fails.
Recovery. Check that a constraint named constraint-name exists for the table
specified. You can use the SHOWDDL command to find the names of the constraints
that exist on a table.
HP NonStop SQL/MX Messages Manual—640324-001
3 -2