HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Cont.)
2409 MESSAGE Length of index ! on table !.! exceeds ! bytes.
(DBERR 2409)
CAUSE The index you attempted to create exceeds the
maximum key length.
ACTION Recreate your index using a column or combination
of columns that is less than the maximum number of
bytes.
----------------------------------------------------------------------------
2410 MESSAGE Tuple exceeded maximum length. (DBERR 2410)
CAUSE The maximum tuple length of 4,000 bytes has been
exceeded.
ACTION Check your input source (e.g. load file) and the
original CREATE TABLE statement to make sure that
each tuple is less than or equal to 4,000 bytes
long.
----------------------------------------------------------------------------
2411 MESSAGE Number of sort columns (!) exceeds maximum !.
(DBERR 2411)
CAUSE The ORDER BY, GROUP BY, or DISTINCT clause of the
SELECT statement specifies a number of columns
which exceeded the maximum allowable.
ACTION Issue the command again, specifying no more than
the maximum number of sort columns. Refer to the
ALLBASE/SQL Reference Manual for additional
information on the SELECT statement.
----------------------------------------------------------------------------
2412 MESSAGE Index exceeded maximum length. (DBERR 2412)
CAUSE The maximum index length of 1024 bytes has been
exceeded
or
the ORDER BY or GROUP BY clause uses a column
greater than 1024 bytes.
ACTION Check your input source (e.g. load file) and the
original CREATE INDEX command to make sure that
each index entry is less than or equal to 1024
bytes long
or
reduce the size of the column used by the ORDER BY
or GROUP BY to less than 1010 bytes.
----------------------------------------------------------------------------
2413 MESSAGE Number of boolean factors in predicate expression
exceeds maximum (!). (DBERR 2413)
CAUSE The number of factors in the WHERE clause exceeds
the maximum allowed.
ACTION Try to reduce the number of factors.
----------------------------------------------------------------------------
2414 MESSAGE Length of column ! in table !.! below minimum !
bytes. (DBERR 2414)
CAUSE You tried to create a LONG or CHAR column of length
0.
ACTION Create the column with at least the minimum length.
----------------------------------------------------------------------------
2415 MESSAGE Number of operators in internal predicate exceed
maximum (!). (DBERR 2415)
CAUSE A predicate containing one or more OR operators was
too complicated. When additional factors were
added to the predicate internally for optimization,
the total number of operators exceeded the maximum.
ACTION Try to rewrite the query, simplifying the predicate
as much as possible, and lowering the precedence of
OR operators as much as possible.
----------------------------------------------------------------------------
2416 MESSAGE Hash on table !.! has more than ! columns.
(DBERR 2416)
CAUSE You specified a hash containing more than 16
columns.
ACTION Issue the CREATE TABLE statement again, specifying
no more than 16 columns for the hash key.
----------------------------------------------------------------------------
2417 MESSAGE Length of hash key on table !.! exceeds ! bytes.
(DBERR 2417)
CAUSE You specified a hash key which exceeds the maximum
key length.
ACTION Issue the CREATE TABLE statement again, specifying
a hash key with length no greater than the maximum.
----------------------------------------------------------------------------
2418 MESSAGE Length of parameter ! in procedure !.! exceeds !
bytes. (DBERR 2418)
CAUSE The number of bytes in the specified parameter
exceeded the maximum allowed.
ACTION Issue the CREATE PROCEDURE statement again,
specifying a parameter length no greater than the
maximum specified.
----------------------------------------------------------------------------
2419 MESSAGE Length of parameter ! in procedure !.! below
minimum ! bytes. (DBERR 2419)
CAUSE The number of bytes in the specified parameter was
less than the minimum allowed.
ACTION Issue the CREATE PROCEDURE statement again,
specifying a parameter length no less than the
minimum allowed.
----------------------------------------------------------------------------
2420 MESSAGE INSERT rejected: Values do not match number of
columns. (DBERR 2420)
CAUSE The number of values in the INSERT statement
exceeded the number of columns in the INSERT list
or
the number of select list items did not match the
number of columns in the insert list.
ACTION Issue the INSERT statement again, specifying a
valid number of columns. Use the INFO command to
get a list of columns in the table.
----------------------------------------------------------------------------
2421 MESSAGE Column number exceeds number of SelectList items.
(DBERR 2421)
CAUSE The ORDER BY clause contained a number greater than
the number of select list items.
ACTION Issue the SELECT statement again, specifying no
more columns in the ORDER BY clause than in the
select list. Refer to the ALLBASE/SQL Reference
Manual for additional information on the SELECT
statement.
----------------------------------------------------------------------------
2422 MESSAGE Range violation on value !. Valid range is ! -
!. (DBERR 2422)
CAUSE The source constant number in the query was out of
its valid range
or
a host variable was not defined
or
one of the values in a format node was out of
range.
ACTION Correct your query so that the source constant is
within the valid range
or
make sure that the host variable has been declared
or
in Pascal or C programs, check the value you
specified for data types in the dynamic format
nodes of SQLDA.
----------------------------------------------------------------------------
2423 MESSAGE Number of Selects in command exceeds maximum !.
(DBERR 2423)
CAUSE The maximum number of Selects in a command has been
exceeded.
ACTION Issue the command again, specifying the maximum
number or fewer.
----------------------------------------------------------------------------
2424 MESSAGE SelectList counts are not equal in UNION command.
(DBERR 2424)
CAUSE The number of columns in the individual select
lists in the UNION command are not the same.
ACTION Issue the command again with an equal number of
columns in the select lists.
----------------------------------------------------------------------------
2425 MESSAGE UNION operation disallowed within a Nested Query.
(DBERR 2425)
CAUSE You tried to include a UNION operation in a nested
query.
ACTION UNION of two nested queries is allowed but UNION
cannot be within a nested query.
----------------------------------------------------------------------------
2426 MESSAGE Tuple size exceeds maximum for UNION command !
bytes. (DBERR 2426)
CAUSE Your select list size is greater than the maximum
currently allowed for a UNION command.
ACTION Re-issue the command with a valid tuple size.
----------------------------------------------------------------------------
2428 MESSAGE Sort length of UNION exceeds maximum allowed !
bytes. (DBERR 2428)
CAUSE The UNION command specifies a number of columns
whose total sort tuple length exceeds the maximum
allowable.
ACTION Issue the command again, specifying no more than
the maximum sort tuple length. Refer to the
ALLBASE/SQL Reference Manual for additional
information on the SELECT statement.
----------------------------------------------------------------------------
2429 MESSAGE Sort length of ORDER BY/GROUP BY/DISTINCT/UNION
exceeds maximum allowed ! bytes. (DBERR 2429)
CAUSE The ORDER BY, GROUP BY, DISTINCT, or UNION clause
of the SELECT statement specifies a number of
columns whose total sort tuple length exceeds the
maximum allowable.
ACTION Issue the command again, specifying no more than
the maximum length of the sort tuple. Refer to the
ALLBASE/SQL Reference Manual for additional
information on the SELECT statement. The maximum
sort tuple size can be calculated from the formula
presented in Appendix A of the ALLBASE/SQL Database
Administration Guide.
----------------------------------------------------------------------------
2430 MESSAGE Invalid decimal precision ! - Allowed range is !
- !. (DBERR 2430)
CAUSE The decimal precision you specified was not within
the valid range.
ACTION Refer to the ALLBASE/SQL Reference Manual for valid
decimal precision.
----------------------------------------------------------------------------
2431 MESSAGE Invalid decimal column - Scale ! exceeds
precision !. (DBERR 2431)
CAUSE The decimal scale was greater than the precision
value.
ACTION Refer to the ALLBASE/SQL Reference Manual for valid
decimal numbers.
----------------------------------------------------------------------------
2432 MESSAGE Invalid float precision !- Allowed range is ! -
!. (DBERR 2432)
CAUSE The float precision you specified was not within
the valid range.
ACTION Refer to the ALLBASE/SQL Reference Manual for valid
float precision.
----------------------------------------------------------------------------
2433 MESSAGE Sort length of sort merge join exceeds maximum
allowed ! bytes. (DBERR 2433)
CAUSE The sort merge join query specifies a number of
columns whose total sort tuple length exceeds the
maximum allowable.
ACTION Issue the command again, specifying no more than
the maximum length of the sort tuple. Refer to the
ALLBASE/SQL Reference Manual for additional
information on the SELECT statement.
----------------------------------------------------------------------------
2434 MESSAGE Invalid section number. Valid range is ! - !.
(DBERR 2434)
CAUSE Your command included a value that was invalid.
The first parameter in the error message indicates
the value that was invalid. The second and third
parameters give you the valid range.
ACTION Re-issue your command, specifying a value within
the valid range.
----------------------------------------------------------------------------
2435 MESSAGE Invalid transaction priority. Valid range is ! -
!. (DBERR 2435)
CAUSE You issued a BEGIN WORK with an invalid priority
option.
ACTION Reissue the BEGIN WORK with a priority within the
valid range.
----------------------------------------------------------------------------
2436 MESSAGE Invalid decimal parameter - Scale ! exceeds
precision !. (DBERR 2436)
CAUSE The decimal scale was greater than the precision
value.
ACTION Refer to the "Data Types" chapter in the
ALLBASE/SQL Reference Guide for complete
information about valid decimal values.
----------------------------------------------------------------------------
2437 MESSAGE Invalid decimal result - Scale ! exceeds
precision !. (DBERR 2437)
CAUSE The scale specified was greater than the precision
specified for a procedure result column.
ACTION Issue the CREATE PROCEDURE statement again,
specifying a valid decimal result type. Refer to
the ALLBASE/SQL Reference Manual for valid decimal
data type specifications.
----------------------------------------------------------------------------
2438 MESSAGE Length of result ! in procedure !.! exceeds !
bytes. (DBERR 2438)
CAUSE The number of bytes you specified for a procedure
result column exceeded the maximum allowed.
ACTION Issue the CREATE PROCEDURE statement again,
specifying a number of bytes no greater than the
maximum.
----------------------------------------------------------------------------
2439 MESSAGE Length of result ! in procedure !.! below minimum
! bytes. (DBERR 2439)
CAUSE You tried to create a procedure result column with
a length of 0 bytes.
ACTION Issue the CREATE PROCEDURE statement again,
specifying a length of at least 1 byte.
----------------------------------------------------------------------------
2440 MESSAGE ! should be ! to !. Number ! is invalid. (DBERR
2440)
CAUSE The size you specified for one or more parameters
of the START DBE statement is invalid.
[REV BEG]
ACTION Issue the START DBE statement again, specifying
valid numbers for the following parameters:
DBEFile0 should be 50 to 16,777,215 pages long;
DBELOG should be 250 to 16,777,215 pages long; Max
Transactions should be 2 to 240 concurrent
transactions; Data Buffer range is 15 to 50,000
pages and the Log Buffer range is 24 to 1024
pages.[REV END]
----------------------------------------------------------------------------