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-38
SQL 1151
Where table-name is the name of the table.
Cause. When the Partition Overlay Support feature is enabled without setting volume
names (through CQD POS_LOCATIONS) for table partitions to reside on, location
names are generated automatically. However, SQL/MX could not generate the location
names automatically, and because the CQD POS_RAISE_ERROR is not set, the given
table is created as a simple table without partitions as it would be if the Partition
Overlay Support feature was not enabled.
Effect. The POS feature was not applied. A simple table without partitions was
created.
Recovery. None if a nonpartitioned table is requested. To request a partitioned table,
delete the table, verify that disk volumes are available, and resubmit. You can also
specify the volume names where the partitions need to be created for the given
CREATE TABLE through CONTROL QUERY DEFAULT POS_LOCATIONS, and then
retry the request.
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.
1151 POS (Partition Overlay Support) was not applied as
volume names could not be generated for the partitions. So a
simple table table-name was created without partitions.
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.