ALLBASE/SQL Message Manual (36216-90213)

Chapter 5 151
ALLBASE/SQL Error Messages: 2101-2419
CAUSE The named column appears in an integrity constraint but
was not defined in the CREATE TABLE.
ACTION Re-issue the command with referential constraints defined
on columns being defined in the statement.
2287 MESSAGE Cannot drop a table with a UNIQUE/PRIMARY KEY
constraint supporting another table's FOREIGN
KEY constraint. (DBERR 2287)
CAUSE You tried to drop a table with a UNIQUE or PRIMARY
KEY constraint. This constraint supports a foreign key in
another table.
ACTION You cannot drop the table until the foreign key reference is
dropped.
2288 MESSAGE Unique constraints with identical unique
column lists specified. (DBERR 2288)
CAUSE Table contains duplicate unique constraints.
ACTION Re-issue command without redundant unique constraints.
2289 MESSAGE User ! is using membership in group ! to
support a foreign key. (DBERR 2289)
CAUSE You attempted to remove the specified user from a group,
and that user has created a foreign key using authorities
granted to the group.
ACTION Locate and drop the tables created by the user with
foreign keys, then reissue the REMOVE FROM GROUP.
2290 MESSAGE Group ! is being used to support a foreign
key. (DBERR 2290)
CAUSE The group or its members own a table containing a foreign
key, and that foreign key was allowed to exist due to
authorities granted to the group. Dropping the group
would remove the authority for the foreign key.
ACTION Locate and drop the tables with foreign keys created by
group members, then reissue the DROP GROUP.
2291 MESSAGE 2291 Constraint !.! already exists. (DBERR
2291)
CAUSE A constraint by the specified name already exists, and
thereforethe CREATETABLE/TRANSFER OWNERSHIP
statement cannot be completed.
ACTION If TRANSFER OWNERSHIP, transfer the table to a
different user. If CREATE TABLE, reissue the command
with unique constraint names. Or, drop the table with the
conflicting constraint name.
2292 MESSAGE INSERT/UPDATE/DELETE statement had no effect