SQL/MX 2.x Messages Manual (H06.10+, J06.03+)

Data Definition Language (DDL) Messages (1000
through 1999)
HP NonStop SQL/MX Messages Manual—544518-011
3-40
SQL 1160
Cause. You attempted to create a table that contains both a NOT DROPPABLE
PRIMARY KEY constraint and a STORE BY clause. The syntax specified is not
correct. The STORE BY column list must be the same as, or a prefix of, the NOT
DROPPABLE PRIMARY KEY column list.
Effect. The operation fails.
Recovery. If you want the STORE BY column list that specifies the clustering key to
be different than the PRIMARY KEY, specify a DROPPABLE PRIMARY KEY. If you
want the PRIMARY KEY to be the same as the STORE BY key, do not specify a
STORE BY clause. Correct the syntax and resubmit.
SQL 1180
Where schema-name is the schema in which the object is being created.
Where subvol-name is the designated subvolume name for that schema.
Cause. One or more LOCATION clauses in the CREATE or MODIFY statement
contained a Guardian location whose subvolume did not match the designated
subvolume for the schema in which the object was being created.
Effect. The object was not created.
Recovery. Either correct the invalid LOCATION clauses or remove them and allow the
system to generate the Guardian locations.
SQL 1181
Where Guardian name is the name of the table, index, view, or routine being
dropped.
Where error is the returned file system error number.
Cause. The object you attempted to drop resulted in file system error error.
1160 A mismatch between the NOT DROPPABLE PRIMARY KEY
constraint and the STORE BY clause was detected. When both
clauses are specified, the STORE BY key column list must be
the same as, or a prefix of, the PRIMARY KEY column list.
This mismatch is caused by differences between the columns
themselves, the order of columns, or the ASC/DESC attribute.
1180 The required subvolume name for locations in schema
schema-name is subvol-name.
1181 Label Guardian name could not be dropped. (file error
error).