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

Privilege and Alias Messages (1000 through 1999)
HP NonStop SQL/MX Messages Manual—523730-004
3-7
SQL 1025
Cause. This error can occur when you drop a constraint, index, or table. These
objects cannot be dropped if they have dependent objects and the drop-behavior is
RESTRICT.
Effect. SQL/MX does not perform the operation.
Recovery. For DROP statements that support the CASCADE drop-behavior, you can
reissue the statement specifying CASCADE. For other DROP statements, you must
first drop each of the dependent objects, then drop the object.
SQL 1026
Cause. An attempt was made to drop a schema by someone other than its owner or
the super ID.
Effect. No SQL objects are dropped.
Recovery. The owner of the schema (or super ID) needs to issue the DROP SCHEMA
statement.
SQL 1027
Where definition-schema-name is the name of the definition schema specified.
Cause. You attempted to drop the schema containing the metadata tables for the
catalog.
Effect. No SQL objects are dropped.
Recovery. Use DROP SCHEMA statements to drop all the user-created schemas in
the catalog. Then use the DROP CATALOG statement to drop the catalog. The
schema definition-schema-name is dropped when you drop its catalog.
SQL 1028
Where object-name is the name of an SQL/MX object existing in the schema.
Cause. You attempted to drop a schema that contains one or more objects.
1025 Request failed. One or more dependent objects exist.
1026 Only the schema owner or super ID can drop a schema.
1027 The definition schema definition-schema-name is dropped
when its catalog is dropped.
1028 The schema must be empty. It contains at least one
object object-name.