ALLBASE/SQL Message Manual (36216-90213)

112 Chapter4
ALLBASE/SQL Error Messages: 746-2100
disallowed. (DBERR 1060)
CAUSE A CONSTRAINT clause was specified with a name
starting with 'SQLCON_' in your CREATE TABLE or
CREATE VIEW statement.
ACTION Remove the CONSTRAINT clause or choose a different
constraint name.
1061 MESSAGE The syntax PRIMARY KEY may only be used once
in CREATE/ALTER TABLE. (DBERR 1061)
CAUSE The syntax PRIMARY KEY appears more than once in
your CREATE TABLE statement.
ACTION Check the syntax and remove all but one of the PRIMARY
KEY specifications, or change all but one to UNIQUE.
1062 MESSAGE HASH ON CONSTRAINT clause did not match any
unique constraint name. (DBERR 1062)
CAUSE The constraint named in your HASH ON CONSTRAINT
clause was not found in the CREATE TABLE statement.
ACTION Check the syntax and use the name of a named unique
constraint in the HASH ON CONSTRAINT clause.
1063 MESSAGE HASH/CLUSTERING ON CONSTRAINT used without a
PRIMARY KEY. (DBERR 1063)
CAUSE The syntax HASH/CLUSTERING ON CONSTRAINT is
used without a constraint name, and no PRIMARY KEY
was defined in the CREATE TABLE statement.
ACTION Check the syntax and either define a PRIMARY KEY or
add a constraint name to the HASH/CLUSTERING ON
CONSTRAINT clause.
1064 MESSAGE CLUSTERING ON CONSTRAINT clause did not match
any unique or referential constraint name.
(DBERR 1064)
CAUSE The constraint named in your CLUSTERING ON
CONSTRAINT clause was not found in the CREATE
TABLE statement.
ACTION Check the syntax and use the name of a named unique or
referential constraint in the CLUSTERING ON
CONSTRAINT clause.
1065 MESSAGE Multiple definition of a column integrity
constraint disallowed. (DBERR 1065)
CAUSE You used the syntax NOT NULL, LANG =, CHECK,
UNIQUE, PRIMARY KEY, or REFERENCES more than
once in a column definition in an ALTER TABLE or
CREATE TABLE statement.