ALLBASE/SQL Message Manual (36216-90213)

152 Chapter5
ALLBASE/SQL Error Messages: 2101-2419
due to execution errors. (DBERR 2292)
CAUSE No rows were added, altered or removed by your
statement because of an error during execution. Examine
the accompanying error messages to determine the cause.
ACTION Determine the row(s) causing the error and remove them
from the statement's field of effect before reissuing the
command. This can be done by restricting the WHERE
clause of an UPDATE, DELETE, or format 2 INSERT, or
removing the offending rows from a bulk insert.
2293 MESSAGE FOREIGN KEY constraint violated. (DBERR 2293)
CAUSE The statement you issued attempted to modify the data in
a way not allowed by a referential constraint on the target
table. You cannot delete or modify a primary key row if a
foreign key row references it. You cannot insert or modify
a foreign key row if there will be no matching primary key
row unless the rows contain NULL values.
ACTION Determine the row causing the violation by examining the
constraints of the target table, and reissue the statement
with restrictions so that the offending rows are not within
it.
2294 MESSAGE UNIQUE/PRIMARY KEY column ! must specify NOT
NULL. (DBERR 2294)
CAUSE You must define all columns in a UNIQUE/PRIMARY
KEY in the CREATE TABLE statement as NOT NULL.
ACTION Re-issue the CREATE TABLE specifying NOT NULL for
all columns in a UNIQUE/PRIMARY KEY constraint.
2295 MESSAGE Index uniqueness or UNIQUE/PRIMARY
KEY/FOREIGN KEY constraint violated. (DBERR
2295)
CAUSE You tried to insert a duplicate key value into a column
used in a unique index or a unique constraint, or you
attempted to insert, update, or delete a unique constraint
or foreign key constraint in a manner which would leave a
foreign key value without a matching primary key value.
ACTION A foreign key value may be set to NULL until the correct
primary key value is placed in the unique constraint it
references; or a duplicate unique constraint/unique index
violation can be determined. Once this is done, the
command may be reissued without the offending rows.
2296 MESSAGE Data type for LIKE predicate column must be
CHAR or VARCHAR. (DBERR 2296)
CAUSE The data type of the LIKE predicate column is not a
CHAR or VARCHAR.