HP NonStop SQL/MX, Messages Manual

Page: 86 / 752

Data Definition Language (DDL) Messages (1000
through 1999)
HP NonStop SQL/MX Messages Manual — 640324-001
3- 60
SQL 1275
Where
constraint1
is the constraint you are trying to drop.
Where
constraint2
is the UNIQUE constraint.
Cause. You attempted to drop a constraint that is needed by a UNIQUE constraint,
which is not allowed because it would leave a UNIQUE constraint on a column, but
without a NOT NULL constraint for that column.
Effect. The operation fails.
Recovery. To drop the constraint, you must remove the UNIQUE constraint or add an
additional NOT NULL constraint to the columns that contain UNIQUE constraints and
only one NOT NULL constraint for that column.
SQL 1276
Where
partition-name
is the partition name or number specified and
table-name
is the SQL/MX view name specified.
Cause. The PARTITION clause was used with an SQL/MX view.
Effect. The statement does not compile.
Recovery. Remove the PARTITION clause and compile the statement again.
SQL 1277
Where
object-name
is the name of the SQL object (table or index).
Cause. NonStop SQL/MX does not recognize the partitioning scheme stored in the
metadata for the named object.
Effect. The named object is considered corrupt and is inaccessible.
Recovery. Do not attempt recovery. HP support will perform recovery operations in
response to an automatically generated dial-out message about this condition.
Consider running the VERIFY operation on the named object to check for
inconsistencies in the metadata with respect to the partitioning scheme.
1275 Constraint constraint1 cannot be dropped because it is
needed by unique constraint constraint2 .
1276 The PARTITION clause cannot be specified for an SQL/MP
Table, SQL/MP view or SQL/MX view. The partition
partition-name was specified for object table-name .
1277 Unrecognized partitioning scheme for object object-name .