HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Continued)
2340 MESSAGE User ! already has ! authorization on columns of
!.! from a different grantor. (DBERR 2340)
CAUSE You attempted to GRANT the specified authority on
the table level, and were unable to override column
level authorities on that table from another
grantor.
ACTION Only the DBA, OWNER, or direct grantor can override
column level authorities with table level
authority. Have such a user perform your grant, or
reissue your grant without the specified user
and/or authority.
----------------------------------------------------------------------------
2341 MESSAGE TRANSFER OWNERSHIP of !.! to ! causes a cycle of
! authority. (DBERR 2341)
CAUSE Attempted to transfer a table upon which the
specified authority existed, and that transfer
would cause a cycle of grants in the authority list
for that authority on that table.
ACTION Examine the chain of grants to determine if the
cycle can be broken, or transfer the table to a
different user (if doing so would not cause a
cycle).
----------------------------------------------------------------------------
2342 MESSAGE TRANSFER OWNERSHIP of !.! to ! causes a cycle of
! authority on column !. (DBERR 2342)
CAUSE Attempted to transfer a table upon which the
specified authority existed, and that transfer
would cause a cycle of grants in the authority list
for that authority on that table.
ACTION Examine the chain of grants to determine if the
cycle can be broken, or transfer the table to a
different user (if doing so would not cause a
cycle).
----------------------------------------------------------------------------
[REV BEG]
2343 MESSAGE User ! does not have authority to install modules
for owner !. (DBERR 2343)
CAUSE The user specified does not have the required
authority.
ACTION Use the GRANT INSTALL AS OwnerID TO DBEUserID
statement to give the proper authority to the user.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2346 MESSAGE User ! does not explicit INSTALL AS ! authority.
(DBERR 2346)
CAUSE The user specified does not have INSTALL authority
for this owner.
ACTION Use the GRANT INSTALL statement to grant INSTALL AS
authority to the user.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2347 MESSAGE User ! does not have INSTALL ! authority. (DBERR
2347)
CAUSE The user specified does not have any INSTALL
authority.
ACTION Use the GRANT INSTALL AS OwnerID TO DBEUserID
statement to grant INSTALL authority to the user.
[REV END]
----------------------------------------------------------------------------
2350 MESSAGE !
CAUSE A RAISE ERROR statement was specified without an
error number or with an error number of 2350.
ACTION See the Section "User Defined Error Messages" in
the "Introduction" for discussion of RAISE ERROR
generated errors. Examine the error text to
determine the action to take.
----------------------------------------------------------------------------
2352 MESSAGE RULE !.! WHERE condition invalid. (DBERR 2352)
CAUSE The named RULE definition's WHERE condition will
not be executable and so is not valid.
ACTION Identify the problem with the RULE definition by
examining the error or errors accompanying this
one. Correct the problem of those errors in order
to make the RULE's WHERE condition executable.
----------------------------------------------------------------------------
2353 MESSAGE RULE !.! EXECUTE PROCEDURE invalid. (DBERR 2353)
CAUSE The named rule definition's EXECUTE PROCEDURE
clause will not be executable and so is not valid.
ACTION Identify the problem with the rule definition by
examining the error or errors accompanying this
one. Correct the problem identified in those
errors in order to make the rule's EXECUTE
PROCEDURE clause executable.
----------------------------------------------------------------------------
2354 MESSAGE Rule !.! not found. (DBERR 2354)
CAUSE The named rule was not found.
ACTION Re-issue your DROP RULE statement after verifying
that the proper rule was named.
----------------------------------------------------------------------------
2355 MESSAGE Rule ! not found on table !.!. (DBERR 2355)
CAUSE The named rule was not found on the named table.
ACTION Re-issue your DROP RULE statement after verifying
that the proper table and rule were named, or issue
the statement without the table name.
----------------------------------------------------------------------------
2356 MESSAGE Rule !.! already exists. (DBERR 2356)
CAUSE The name of the rule given in the CREATE RULE
statement is the name of an existing rule.
or
a TRANSFER OWNERSHIP on a table has resulted in a
duplicate rule name.
ACTION Issue the CREATE RULE statement with a rule name
unique for the table owner.
----------------------------------------------------------------------------
2357 MESSAGE Name ! used for both OLD and NEW in rule !.!.
(DBERR 2357)
CAUSE You specified the same correlation name for both
the OLD and NEW correlation names.
ACTION Reissue the statement using the default correlation
names or with distinct OLD and NEW correlation
names.
----------------------------------------------------------------------------
2358 MESSAGE Duplicate column ! in update column list of rule
!.!. (DBERR 2358)
CAUSE You specified the named column more than once in
the UPDATE statement type column list of your
CREATE RULE statement.
ACTION Re-issue your CREATE RULE statement after checking
that no column name is specified more than once in
the UPDATE statement type column list.
----------------------------------------------------------------------------
2360 MESSAGE Error number cannot be NULL for RAISE ERROR.
(DBERR 2360)
CAUSE The error number given to the RAISE ERROR statement
had the NULL value.
ACTION Check the value given to the RAISE ERROR statement
and ensure that it is not null.
----------------------------------------------------------------------------
2361 MESSAGE Error number must be positive for RAISE ERROR.
(DBERR 2361)
CAUSE The error number given to the RAISE ERROR statement
was negative or zero.
ACTION Check the value given to the RAISE ERROR statement
and ensure that it is greater than zero.
----------------------------------------------------------------------------
2362 MESSAGE Error number for RAISE ERROR must have data type
INTEGER or SMALLINT. (DBERR 2362)
CAUSE The error number for RAISE ERROR was an invalid
data type.
ACTION Ensure that the data type of the error number is
INTEGER or SMALLINT.
----------------------------------------------------------------------------
2363 MESSAGE Error text cannot be NULL for RAISE ERROR.
(DBERR 2363)
CAUSE The error text given to the RAISE ERROR statement
had the NULL value.
ACTION Check the value given to the RAISE ERROR statement
and ensure that it is not null.
----------------------------------------------------------------------------
2364 MESSAGE Error text for RAISE ERROR must have data type
CHAR or VARCHAR. (DBERR 2364)
CAUSE The error text for RAISE ERROR was an invalid data
type.
ACTION Ensure that the data type of the error text is CHAR
or VARCHAR.
----------------------------------------------------------------------------
[REV BEG]
2365 MESSAGE Deadlock detected causing rollback query. (DBERR
2365)
CAUSE Deadlock occurred.
ACTION Determine the cause of the deadlock and take
appropriate actions to correct the problem. See
"Resolving Conflicts among Concurrent Transactions"
in the chapter "Currency Control through Locks and
Isolation Levels" in the ALLBASE/SQL Reference
Manual.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2366 MESSAGE Timeout expired (! seconds) causing rollback
query. (DBERR 2366)
CAUSE The timeout expired.
ACTION No action is required.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2367 MESSAGE RENAME COLUMN is not allowed on a check
constraint column. (DBERR 2367)
CAUSE A RENAME COLUMN statement was issued for a check
constraint column.
ACTION Check constraints on a renamed column will be
disallowed. Determine if an incorrect column was
renamed or take other appropriate action.
[REV END]
----------------------------------------------------------------------------
2370 MESSAGE Rule firing invalidated current section (!.!(!)).
(DBERR 2370)
CAUSE Upon completion of a rule, the current section was
found to be invalidated by actions taken by the
rule.
ACTION Check the rules fired by the current statement and
determine if the procedures they invoke invalidate
sections; or take no action.
----------------------------------------------------------------------------
2371 MESSAGE Rule firing invalidated user's statement. (DBERR
2371)
CAUSE Upon completion of the rules fired by the user's
statement, the statement was found to be
invalidated by actions taken by the rules.
ACTION Check the rules fired by the current statement and
determine if the procedures they invoke invalidate
sections; or take no action.
----------------------------------------------------------------------------
2372 MESSAGE Maximum rule firing depth (!) exceeded. (DBERR
2372)
CAUSE Rules chained to a depth greater than the allowed
maximum.
ACTION Determine the cause of exceeding the maximum rule
depth; or take no action.
----------------------------------------------------------------------------
2373 MESSAGE Procedure executed by rule executed ! statement.
(DBERR 2373)
CAUSE A procedure invoked by a rule executed a COMMIT,
ROLLBACK, or SAVEPOINT statement.
ACTION Alter the procedure to not invoke such statements
when fired by a rule, or invoke a different
procedure from the rule.
----------------------------------------------------------------------------
2390 MESSAGE User ! does not have the authority to create
HPODBSS table/view. (DBERR 2390)
CAUSE You attempted to create a table or view with an
owner name of HPODBSS.
ACTION Replace HPODBSS with a non-reserved name and
reissue the statement.
----------------------------------------------------------------------------
2400 MESSAGE Maximum number of columns (!) exceeded on
table/view !.!. (DBERR 2400)
CAUSE The number of columns you specified in the ALTER
TABLE, CREATE TABLE, or CREATE VIEW statement was
greater than the maximum number of columns
allowable.
ACTION Issue the command again ensuring that the total
number of columns does not exceed 1023.
----------------------------------------------------------------------------
2402 MESSAGE Maximum number of tables per module exceeded.
(DBERR 2402)
CAUSE The maximum number of tables for a SELECT statement
has been exceeded.
ACTION Issue the command again, specifying no more than 31
tables.
----------------------------------------------------------------------------
2404 MESSAGE Maximum number of concurrent transactions
exceeded. (DBERR 2404)
CAUSE The maximum number of concurrent transactions has
been exceeded.
ACTION Retry the begin transaction statement again. If it
fails, ask your database administrator for
assistance.
----------------------------------------------------------------------------
2405 MESSAGE Index ! on table !.! has more than ! columns.
(DBERR 2405)
CAUSE The index you specified contains more than 16
columns.
ACTION Check the CREATE INDEX statement to make sure that
the number of columns specified is less than or
equal to 16.
----------------------------------------------------------------------------
2406 MESSAGE SelectList contains more than ! columns. (DBERR
2406)
CAUSE The number of items in the select list exceeded the
maximum number allowable.
ACTION Check your SELECT statement to make sure that the
number of items in the select list is equal to or
less than 1024.
----------------------------------------------------------------------------
2407 MESSAGE Length of column ! in table !.! exceeds ! bytes.
(DBERR 2407)
CAUSE The number of bytes in the specified column
exceeded the maximum number allowable.
ACTION Issue the CREATE TABLE statement again with the
maximum number of bytes or less.
----------------------------------------------------------------------------
2408 MESSAGE Tuple length of table !.! exceeds ! bytes.
(DBERR 2408)
CAUSE You attempted to create a table with a minimum
tuple length greater than the maximum allowed.
ACTION Reduce the minimum tuple length of the table and
reissue the statement.
----------------------------------------------------------------------------