HP NonStop SQL/MX Messages Manual page 41

Data Definition Language (DDL) Messages (1000
through 1999)
Recovery. Either correct the table name or the constraint name and reissue the
statement.You can use the SHOWDDL statement to display the names of constraints
on the table.
SQL 1053
1053 Unique index index-name could not be created because the
specified column(s) contain duplicate data.
Where index-name is the name specified for the index to create.
Cause. The rows already existing in the table violate the uniqueness constraint
specified in the CREATE INDEX statement.
Effect. The index is not created.
Recovery. Either change the list of columns for the unique index, or change the rows
in the table to remove duplicates. Then reissue the statement.
SQL 1054
1054 Index index-name already exists.
Where index-name is the name specified for the index to create.
Cause. You attempted to create an index with the name of an index that already exists
on the specified table.
Effect. The index is not created.
Recovery. Choose a different name for the index and reissue the statement.
SQL 1055
1055 Object object-name already exists.
Where object-name is the name of an existing SQL/MX object.
Cause. You attempted to create an object with a name that is already in use for a
table, view, or stored procedure in this schema.
Effect. The operation fails.
Recovery. Check that the object name is correct. If the name is not fully qualified,
check that the current schema is set correctly. You can choose a different name, or
drop the existing object with this name and then reissue the statement.
HP NonStop SQL/MX Messages Manual—640324-001
3- 15