SQL/MX 3.2 Messages Manual (H06.25+, J06.14+)

Data Definition Language (DDL) Messages (1000
through 1999)
HP NonStop SQL/MX Release 3.2 Messages Manual—691121-001
3-7
SQL 1024
Where error-number is an error originating from the file system.
Where text-string-1 is the file name.
Where text-string-2 is (optionally) additional details about the error.
Cause. Look up this error number in the file system manual to determine the cause.
Effect. The operation fails.
Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose
and correct the problem.
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. NonStop 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.
1024 File system error error-number occurred on text-string-
1. text-string-2.
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.