HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Continued)
2639 MESSAGE Invalid format specification in second parameter
of datetime function. (DBERR 2639)
CAUSE A unit within the format specification is not a
valid unit.
ACTION Re-issue the command with a format specification.
----------------------------------------------------------------------------
2641 MESSAGE Redundant fields specified in format
specification. (DBERR 2641)
CAUSE A unit in the format specification was specified
twice, or two units which contain identical units.
ACTION Re-issue the command with a valid format
specification.
----------------------------------------------------------------------------
2642 MESSAGE Invalid data type for second parameter of
datetime function. (DBERR 2642)
CAUSE Data type of second parameter is not valid.
ACTION Please check the documentation for valid format
types.
----------------------------------------------------------------------------
2643 MESSAGE Format specification contains an invalid unit for
data type !. (DBERR 2643)
CAUSE A valid unit was specified in the format
specification, but it is not valid for this
datetime type.
ACTION Please check the documentation for valid format
types for this datetime data type.
----------------------------------------------------------------------------
2644 MESSAGE Datetime input function cannot parse input
parameters. (DBERR 2644)
CAUSE When parsing datetime literal, invalid data was
detected.
ACTION Check validity of datetime literal in first
parameter of datetime input function.
----------------------------------------------------------------------------
2645 MESSAGE Day of week specified does not match date
supplied. (DBERR 2645)
CAUSE Alphabetic day of week specified incorrect for date
literal specified.
ACTION Re-issue command with valid datetime literal.
----------------------------------------------------------------------------
2646 MESSAGE End of datetime literal detected before parsing
end of format specification. (DBERR 2646)
CAUSE Format specification does not match datetime
literal.
ACTION Re-issue command with correct input to datetime
input function.
----------------------------------------------------------------------------
2647 MESSAGE Datetime literal contains a value outside the
valid range for a format specified. (DBERR 2647)
CAUSE A unit in datetime literal is not within boundary
of the unit values allowed.
ACTION Issue command with correct values for units
specified in format specification.
----------------------------------------------------------------------------
2650 MESSAGE Invalid length in VARCHAR. (DBERR 2650)
CAUSE An invalid length field for a VARCHAR data type was
detected in SQLCORE. The most likely cause of this
would be an uninitialized VARCHAR host variable
used in an insert or an uninitialized VARCHAR
length field in the buffer used in a bulk insert.
ACTION Make sure that all VARCHAR host variables are
properly initialized.
----------------------------------------------------------------------------
2651 MESSAGE DEFAULT literal type ! is not compatible with the
corresponding column data type !. (DBERR 2651)
CAUSE The data type of the literal is not compatible with
the one specified for the corresponding column.
ACTION Define a valid default value for the corresponding
column.
----------------------------------------------------------------------------
2652 MESSAGE DEFAULT ! is not compatible with the
corresponding column data type !. (DBERR 2652)
CAUSE You specified a DEFAULT current function, USER, or
NULL, which is not compatible with the one
specified for the corresponding column.
ACTION Define a valid default value for the corresponding
column.
----------------------------------------------------------------------------
2653 MESSAGE Non-supported DEFAULT value type !. (DBERR 2653)
CAUSE You specified a DEFAULT value which is not a
constant, a current function, USER, or NULL.
ACTION Define a valid default value for the corresponding
column.
----------------------------------------------------------------------------
2654 MESSAGE Data type ! invalid for the starting position of
SUBSTRING function. (DBERR 2654)
CAUSE The StartPosition parameter of the SUBSTRING
function is not an integer constant or expression.
ACTION Change the StartPosition parameter to an integer
constant or expression.
----------------------------------------------------------------------------
2655 MESSAGE Data type ! invalid for the substring length of
SUBSTRING function. (DBERR 2655)
CAUSE The Length parameter of the SUBSTRING function is
not an integer constant or expression.
ACTION Change the Length parameter to an integer constant
or expression.
----------------------------------------------------------------------------
[REV BEG]
2656 MESSAGE Source string must contain numeric value. (DBERR
2656)
CAUSE The source character string of the CAST function
contains invalid characters for a numeric
expression.
ACTION Make sure the source character string contains an
appropriate representation of a numeric value with
no extraneous characters added.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2657 MESSAGE CAST target data type too small. (DBERR 2657)
CAUSE The size in bytes of the specified target data type
is too small to hold the value being converted.
ACTION Specify a larger target data type.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2658 MESSAGE Numeric/Binary conversion must be of equal
length. (DBERR 2658)
CAUSE In converting numeric data types to BINARY, the
size in bytes of the source and target must be
equal. If the target is a VARBINARY, the maximum
size of the target must be equal or exceed the
source size invalid character based on the target
data type specified. This error will be reported
if this is not true.
ACTION When converting to BINARY, make sure that the
specified size of the BINARY matches the size of
the source. If converting to VARBINARY, make sure
that the specified size of the VARBINARY is at
least the size of the source. When converting from
BINARY or VARBINARY to a numeric type, string
concatenation (||) or the SUBSTRING function can be
used to make the source the correct size for the
target.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2659 MESSAGE Date/Binary conversion must be of equal length.
(DBERR 2659)
CAUSE In converting Date/Time data types to BINARY, the
size in bytes of the source and target must be
equal. If the target is a VARBINARY, the maximum
size of the target must be equal or exceed the
source size invalid character based on the target
data type specified. This error will be reported
if this is not true.
ACTION When converting to BINARY, make sure that the
specified size of the BINARY matches the size of
the source (16 bytes). If converting to VARBINARY,
make sure that the specified size of the VARBINARY
is at least the size of the source. When
converting from BINARY or VARBINARY to a Date/Time
type, the source should be 16 bytes.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2660 MESSAGE TID/Binary conversion must be of equal length.
(DBERR 2660)
CAUSE In converting TID data types to BINARY, the size in
bytes of the source and target must be equal. If
the target is a VARBINARY, the maximum size of the
target must be equal or exceed the source size
invalid character based on the target data type
specified. This error will be reported if this is
not true.
ACTION When converting to BINARY, make sure that the
specified size of the BINARY matches the size of
the source (8 bytes). If converting to VARBINARY,
make sure that the specified size of the VARBINARY
is at least the size of the source. When
converting from BINARY or VARBINARY to a Date/Time
type, the source should be 8 bytes.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
2661 MESSAGE Invalid TID format. (DBERR 2661)
CAUSE The character string being converted to a TID data
type was not properly formatted.
ACTION The correct syntax for a character string
representation of a TID is:
[0:]filenumber:pagenumber:slot
where:
filenumber is the DBEfile number (0-32767)
pagenumber is the page number (0-16777215)
slot is the slot number (0-255)
[REV END]
----------------------------------------------------------------------------
2700 MESSAGE INSERT/UPDATE/DELETE disallowed on a join.
(DBERR 2700)
CAUSE You attempted to INSERT, UPDATE, or DELETE on a
multiple table view.
ACTION You cannot perform an INSERT, UPDATE, or DELETE on
multi-table views. Refer to the specified command
and the CREATE VIEW statement in the ALLBASE/SQL
Reference Manual for additional information.
----------------------------------------------------------------------------
2701 MESSAGE INSERT/UPDATE disallowed on virtual column (!).
(DBERR 2701)
CAUSE You attempted to INSERT or UPDATE a computed column
in a view.
ACTION Inserting rows through a view is not allowed if any
column of the view is computed in an arithmetic
expression. Refer to the ALLBASE/SQL Reference
Manual for additional information.
----------------------------------------------------------------------------
2702 MESSAGE INSERT/UPDATE/DELETE disallowed on group
operation. (DBERR 2702)
CAUSE You attempted to INSERT, UPDATE, or DELETE rows via
a view which contained a GROUP BY clause in its
definition.
ACTION A view definition for UPDATE, DELETE, and INSERT
operations cannot contain a GROUP BY clause. Refer
to the specified command and the CREATE VIEW
statement in the ALLBASE/SQL Reference Manual for
additional information.
----------------------------------------------------------------------------
2703 MESSAGE INSERT/UPDATE/DELETE disallowed on ORDER BY.
(DBERR 2703)
CAUSE You attempted to declare a cursor containing both
an ORDER BY clause and a FOR UPDATE clause, or you
attempted an UPDATE or DELETE WHERE CURRENT on a
cursor containing an ORDER BY clause.
ACTION Remove the ORDER BY from the cursor if updates
and/or deletes are to be performed with it, or
remove the FOR UPDATE clause from the cursor.
----------------------------------------------------------------------------
2705 MESSAGE Illegal reference to column ! in group operation.
(DBERR 2705)
CAUSE A column you specified in the select list was not
referenced in the GROUP BY clause of the SELECT
statement.
or
you are doing a GROUP BY with a SELECT * and you
have failed to reference all of the columns in the
specified table in the GROUP BY clause.
ACTION Issue the SELECT statement again, specifying only
aggregate functions and columns referenced in the
GROUP BY clause
In the case of SELECT *, be sure to reference all
columns produced by the expansion of the * in the
GROUP BY clause.
----------------------------------------------------------------------------
2706 MESSAGE INSERT/UPDATE/DELETE disallowed on DISTINCT
operation. (DBERR 2706)
CAUSE UPDATE, INSERT, and DELETE operations through a
view are not allowed if the view definition
involves a distinct clause.
ACTION Perform the UPDATE, INSERT, or DELETE operation on
the base table or re-create the view without the
DISTINCT clause.
----------------------------------------------------------------------------
2707 MESSAGE UPDATE/DELETE disallowed on a cursor containing a
subquery. (DBERR 2707)
CAUSE You attempted to UPDATE or DELETE rows accessed
through a cursor which contained a subquery in its
definition.
ACTION Perform the UPDATE or DELETE only through a cursor
which does not contain a subquery.
----------------------------------------------------------------------------
2708 MESSAGE UPDATE/DELETE disallowed with subquery containing
update/delete table. (DBERR 2708)
CAUSE You attempted to UPDATE or DELETE through a view or
with a search condition containing a subquery which
references the target table.
ACTION Perform the UPDATE or DELETE only through views
with search conditions which do not reference the
target table in any subqueries.
----------------------------------------------------------------------------
2709 MESSAGE UPDATE/DELETE disallowed on UNION. (DBERR 2709)
CAUSE You attempted to UPDATE or DELETE through a cursor
containing a UNION.
ACTION Perform the UPDATE or DELETE only through cursors
not containing UNIONs.
----------------------------------------------------------------------------
2710 MESSAGE INSERT or FORMAT II INSERT disallowed on a view
referencing the insert table in a subquery. (DBERR
2710)
CAUSE You attempted to insert through a view, where the
view contains a subquery which references the same
base table the view is based upon. Such an insert
is not allowed.
ACTION Insert directly through the base table, or use a
view not containing subqueries which reference the
same table as the view.
----------------------------------------------------------------------------
2711 MESSAGE Qualifier !.! (column !) is different from input
table. (DBERR 2711)
CAUSE The table name you specified in the select list or
WHERE clause is different from the table name
specified in the FROM clause of the SELECT
statement.
ACTION Issue the SELECT statement again, specifying the
same table name in both the select list or WHERE
clause and the FROM clause. Refer to the
ALLBASE/SQL Reference Manual for additional
information on the SELECT statement.
----------------------------------------------------------------------------