HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Continued)
2278 MESSAGE Referenced column list does not match any UNIQUE
or PRIMARY KEY constraint in table !.!. (DBERR
2278)
CAUSE The column list given for a table in a REFERENCES
clause does not match any candidate key defined on
the table.
ACTION Check the order of the columns, as they must
exactly match the order of the candidate key
columns. Specify a referenced column list in the
same order as some candidate key in the referenced
table.
----------------------------------------------------------------------------
2279 MESSAGE User ! does not have ! authority on needed
columns of table/view !.!. (DBERR 2279)
CAUSE You do not have the authority to access the columns
of a table.
ACTION Check with the database administrator for the
needed authority, sign on as a user with the
required authority.
----------------------------------------------------------------------------
2280 MESSAGE PRIMARY KEY/UNIQUE constraint with HASH index can
not be dropped. (DBERR 2280)
CAUSE You attempted to drop a constraint that was used in
the HASH ON CONSTRAINT clause in the CREATE TABLE
statement. These constraints cannot be dropped
without dropping the whole table.
ACTION Check the constraint type in SYSTEM.CONSTRAINT and
ensure that the type of the constraint is not "H",
for hash.
----------------------------------------------------------------------------
2281 MESSAGE Maximum number of columns allowed in a
UNIQUE/PRIMARY KEY/FOREIGN KEY is !. (DBERR 2281)
CAUSE The unique or referential constraint exceeds the
maximum number of columns allowed in a unique or
referential constraint.
ACTION Define the unique or referential constraint on
columns within this limit.
----------------------------------------------------------------------------
2282 MESSAGE UNIQUE/PRIMARY KEY/FOREIGN KEY length exceeds
maximum length (! bytes). (DBERR 2282)
CAUSE Key length exceeds the maximum.
ACTION Define referential constraints which are within the
key length limit specified in the database
administrator guide.
----------------------------------------------------------------------------
2283 MESSAGE Duplicate column name ! in UNIQUE/PRIMARY
KEY/FOREIGN KEY column list. (DBERR 2283)
CAUSE You specified a column name more than once in a
column list of a unique or referential constraint.
ACTION Re-issue the CREATE TABLE statement without
duplicate column names in the UNIQUE/PRIMARY
KEY/FOREIGN KEY column lists.
----------------------------------------------------------------------------
2284 MESSAGE Invalid data type ! found in column ! specified
in a UNIQUE/PRIMARY KEY/FOREIGN KEY constraint
column list. (DBERR 2284)
CAUSE A column found in a unique or foreign key column
list is of an invalid data type.
ACTION Re-issue the statement using columns of the allowed
data types in your constraints.
----------------------------------------------------------------------------
2285 MESSAGE FOREIGN KEY column ! data type ! doesn't match
data type ! of referenced column. (DBERR 2285)
CAUSE A pair of corresponding columns in the referencing
column list and referenced column list of a foreign
key constraint have data types which are
incompatible for referential constraints.
ACTION Check the data types of the corresponding columns
in your foreign key constraint declarations and
make sure they are the same data type.
----------------------------------------------------------------------------
2286 MESSAGE UNIQUE/PRIMARY KEY/FOREIGN KEY column ! not
defined in CREATE/ALTER TABLE. (DBERR 2286)
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 therefore the CREATE TABLE/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 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.
ACTION Modify the query to have a CHAR or VARCHAR data
type column on the LIKE predicate.
----------------------------------------------------------------------------
2297 MESSAGE FOREIGN KEY column ! data type DECIMAL(!,!)
doesn't match PRIMARY KEY data type DECIMAL(!,!).
(DBERR 2297)
CAUSE You entered a value in the referencing column which
has a different precision and scale than the
precision and scale of the PRIMARY KEY referenced
column.
ACTION Check the precision and scale of the PRIMARY KEY
and change the value entered in the referencing
column to match it.
----------------------------------------------------------------------------
2300 MESSAGE User ! does not have ! authorization. (DBERR
2300)
CAUSE The DBEUserID under which the command was executed
does not have the authority (DBA, RESOURCE, or
CONNECT) to execute the command.
ACTION Contact your database administrator to get the
required authority or sign on as a user who does
have the required authority.
----------------------------------------------------------------------------
2301 MESSAGE User ! does not have ! authority on !.!. (DBERR
2301)
CAUSE The DBEUserID does not have the required table or
view authority to execute the command.
ACTION Contact your database administrator to get the
required authority or sign on as a user who does
have the required authority.
----------------------------------------------------------------------------
2302 MESSAGE User ! does not have ! authority on column !.!.!.
(DBERR 2302)
CAUSE You do not have the specified authority needed to
access the column. UPDATE is needed in the UPDATE
statement, or REFERENCES is needed in the CREATE
TABLE statement.
ACTION Contact your database administrator to get the
required authority or sign on as a user who does
have the required authority.
----------------------------------------------------------------------------
2303 MESSAGE User ! does not have OWNER or DBA authority.
(DBERR 2303)
CAUSE The command requires either OWNER or DBA authority.
ACTION Refer to the ALLBASE/SQL Database Administration
Guide and the ALLBASE/SQL Reference Manual for
statements requiring special authority. Contact
your database administrator to get the required
authority.
----------------------------------------------------------------------------
2304 MESSAGE Cannot revoke DBA authority from session owner !.
(DBERR 2304)
CAUSE You tried to REVOKE DBA authority from yourself.
ACTION Refer to the ALLBASE/SQL Database Administration
Guide for additional information on when you can
revoke DBA authority.
----------------------------------------------------------------------------
2305 MESSAGE Use REVOKE ! to revoke GRANT !. (DBERR 2305)
CAUSE The DBEUserID was granted the specified authority
(UPDATE or REFERENCES) on all columns using the
GRANT statement without specifying column names.
You tried to revoke the authority on individual
columns in the table.
ACTION Revoke the authority on all columns using the
REVOKE statement without specifying column names.
If you want the user to have the authority on some
columns of the table, issue the GRANT statement
specifying the appropriate column names.
----------------------------------------------------------------------------
2306 MESSAGE Special GRANT/REVOKE disallowed for reserved user
!. (DBERR 2306)
CAUSE The DBEUserID specified in the GRANT or REVOKE
statement is a reserved user (PUBLIC, TEMP, SYSTEM,
HPRDBSS). The GRANT or REVOKE statement is ignored.
ACTION Refer to the ALLBASE/SQL Database Administration
Guide explanation of reserved users and their
purposes.
----------------------------------------------------------------------------
2307 MESSAGE User ! does not have OWNER authority. (DBERR
2307)
CAUSE The TRANSFER OWNERSHIP and DROP VIEW statements are
not allowed on system views.
ACTION No action is necessary. Refer to the ALLBASE/SQL
Database Administration Guide for additional
information on system views.
----------------------------------------------------------------------------
2308 MESSAGE Reserved user ! cannot be added to a group.
(DBERR 2308)
CAUSE You attempted to add a RESERVED user (PUBLIC,
SYSTEM, TEMP, or HPRDBSS) to a group using the ADD
GROUP statement.
ACTION No action is necessary. Refer to the ALLBASE/SQL
Database Administration Guide for an explanation of
reserved users and their purposes.
----------------------------------------------------------------------------
2309 MESSAGE User ! neither has DBA authority nor is a member
of group !. (DBERR 2309)
CAUSE The AuthorizationName is different than the
DBEUserID executing the CREATE SCHEMA statement.
You do not have DBA authority, nor are you a member
of a group whose name is the AuthorizationName
specified in the CREATE SCHEMA statement.
ACTION Ensure that you have proper authorization to
execute the CREATE SCHEMA statement.
----------------------------------------------------------------------------
2310 MESSAGE User ! does not have DBA authority. (DBERR 2310)
CAUSE GRANT with BY clause done by someone without DBA
authority.
ACTION This command requires DBA authority to be
performed.
----------------------------------------------------------------------------