ALLBASE/SQL Error Messages (Continued) [ ALLBASE/SQL Message Manual ] MPE/iX 5.5 Documentation
ALLBASE/SQL Message Manual
ALLBASE/SQL Error Messages (Continued)
2881 MESSAGE Cannot drop ! default DBEFileSet !. (DBERR 2881)
CAUSE You have the space default on the DBEFileSet you
tried to drop.
ACTION Change the space default or modify your command.
----------------------------------------------------------------------------
2882 MESSAGE Cannot revoke ! default on DBEFileSet ! from !.
(DBERR 2882)
CAUSE The authority you tried to revoke is a DEFAULT for
the user.
ACTION Change the space default or modify your command.
----------------------------------------------------------------------------
2884 MESSAGE User ! does not have explicit ! authority on
DBEFileSet !. (DBERR 2884)
CAUSE The authority is not previously granted to you.
ACTION Cannot REVOKE, please modify the command.
----------------------------------------------------------------------------
2885 MESSAGE ! on DBEFileSet ! is not granted for !. (DBERR
2885)
CAUSE The authority is not previously granted to you.
ACTION You must grant the authority to the user before you
run the command.
----------------------------------------------------------------------------
2901 MESSAGE Multiple rows returned in subquery. (DBERR 2901)
CAUSE A subquery within a comparison predicate returns
more than one row. Comparison predicates can only
work with single values.
ACTION For a subquery that returns more than one value,
the EXISTS predicate, IN predicate, or one of the
quantified predicates (SOME, ALL, ANY) must be
used.
----------------------------------------------------------------------------
2902 MESSAGE Multiple columns returned in subquery. (DBERR
2902)
CAUSE You specified more than one column in the select
list of a subquery. If an asterisk was specified,
there was more than one column in the table being
queried. Only the EXISTS predicate allows more
than one column to be specified in a subquery.
ACTION Change the subquery so that only one column is
specified in the select list.
----------------------------------------------------------------------------
2909 MESSAGE Number of output variables does not match the
number of output dynamic parameters in the
referenced section. (DBERR 2909)
CAUSE The number of output values in the USING clause of
an EXECUTE or CLOSE statement is not equal to the
number of output dynamic parameters in the prepared
statement.
ACTION Modify either your EXECUTE or CLOSE statement or
the related PREPARE statement so that there is a
one to one mapping of output dynamic parameters.
----------------------------------------------------------------------------
2910 MESSAGE Number of input values does not match the number
of dynamic parameters in the referenced section.
(DBERR 2910)
CAUSE The number of input values in the USING clause of
an OPEN or EXECUTE statement is not equal to the
number of dynamic parameters in the prepared
statement.
ACTION Modify either your OPEN or EXECUTE statement or the
related PREPARE statement so that there is a one to
one mapping of dynamic parameters.
----------------------------------------------------------------------------
2912 MESSAGE Incompatible conversion from ! to ! for the
dynamic parameter (!). (DBERR 2912)
CAUSE The data type of the input value in the USING
clause of an OPEN or EXECUTE statement is not
compatible with the default data type of the
dynamic parameter in the prepared statement.
ACTION Modify the data type of the referenced input value
to be compatible with the default data type of the
corresponding dynamic parameter.
----------------------------------------------------------------------------
[REV BEG]
2913 MESSAGE Invalid conversion from ! to ! for the dynamic
parameter (!). (DBERR 2913)
CAUSE You attempted an invalid conversion from one
specified type to another.
ACTION Refer to the "CAST Function" in the "Expressions"
chapter of the ALLBASE/SQL Reference Manual for the
correct conversion types.
[REV END]
----------------------------------------------------------------------------
2914 MESSAGE Invalid conversion from DECIMAL (!,!) to DECIMAL
(!,!) for the dynamic parameter (!). (DBERR 2914)
CAUSE The value length, precision, or scale of the
decimal value you specified in the USING clause of
an OPEN or EXECUTE statement is greater than that
of the data type of the corresponding dynamic
parameter in the prepared statement.
ACTION Modify the referenced decimal input value to be
compatible with the corresponding dynamic
parameter.
----------------------------------------------------------------------------
2915 MESSAGE Invalid conversion from !(!) to !(!) for the
dynamic parameter (!). (DBERR 2915)
CAUSE The length of the input value you referenced in the
USING clause of an OPEN or EXECUTE statement is
greater than the length of the data type of the
corresponding dynamic parameter in the prepared
statement.
ACTION Modify the definition of the referenced input value
to be compatible in length with the corresponding
dynamic parameter.
----------------------------------------------------------------------------
2916 MESSAGE Invalid Table/View/Column in the dynamic format
computation. (DBERR 2916)
CAUSE A dynamic parameter is associated with an invalid
table, view, or column in the statement. Its
format cannot be determined.
ACTION Check that the query references existing tables,
views, and columns you are authorized to access and
reissue the statement.
----------------------------------------------------------------------------
2917 MESSAGE No corresponding column for the dynamic
parameter. (DBERR 2917)
CAUSE A dynamic parameter in the VALUE clause of an
INSERT statement has no corresponding column.
ACTION Check that the number of columns in the INSERT
matches the number of values specified, and reissue
the statement.
----------------------------------------------------------------------------
2918 MESSAGE Using Clause is required for the input dynamic
parameters. (DBERR 2918)
CAUSE You attempted to issue an OPEN or EXECUTE statement
on a section that contains dynamic parameters
without passing the values for the dynamic
parameters via the USING clause.
ACTION Add a USING clause to the statement and provide
values for the dynamic parameters with the USING
clause.
----------------------------------------------------------------------------
2919 MESSAGE An invalid NLS data was encountered. (DBERR
2919)
CAUSE NLS data is invalid.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
2920 MESSAGE SQLCORE encountered error from (!) (!). (DBERR
2920)
CAUSE SQLCORE has an error from the above routine.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
2921 MESSAGE Integer or float overflow or underflow on
operation ADD. (DBERR 2921)
CAUSE The result of an addition operation with INTEGER or
FLOAT operands is either too big or too small for
the hardware to accommodate.
ACTION Modify the expression to yield a result within the
limits for the data type.
----------------------------------------------------------------------------
2922 MESSAGE PUBLICROW is not allowed on a hash table. (DBERR
2922)
CAUSE You are trying to define a hash on a PUBLICROW
table, and this combination is not supported.
or
You are trying to alter a hash table to type
PUBLICROW, but this combination is not supported
ACTION Either use a table type of PUBLIC as you define the
hash structure, or else convert to a non-hash
PUBLICROW table by dropping and recreating the
table.
----------------------------------------------------------------------------
3001 MESSAGE Invalid ALLBASE/SQL request block. (DBERR 3001)
CAUSE Internal error. The ALLBASE/SQL request block has
an invalid brand name in its first field. This
could be caused by an invalid request block
pointer.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
3002 MESSAGE Invalid parameter-buffer flag in ALLBASE/SQL
request block. (DBERR 3002)
CAUSE Internal error. The ALLBASE/SQL request block
(JRB) has an invalid value for input parameter
buffer flag. There is a discrepancy between a
module in the program and the stored module.
ACTION If you moved a modified program to your
DBEnvironment you must drop the old module and
reinstall a new module,
or
don't use ISQL to execute a module created with a
preprocessor
or
record as much information as possible and contact
your HP service representative or Response Center.
----------------------------------------------------------------------------
3003 MESSAGE Invalid parameter-buffer address in ALLBASE/SQL
request block. (DBERR 3003)
CAUSE Internal error. The ALLBASE/SQL request block
(JRB) has an invalid pointer pointing to a
parameter buffer.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
3004 MESSAGE Invalid parameter-buffer length in ALLBASE/SQL
request block. (DBERR 3004)
CAUSE Internal error. ALLBASE/SQL request block (JRB)
has an invalid parameter buffer length.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
3005 MESSAGE Invalid data-buffer flag in ALLBASE/SQL request
block. (DBERR 3005)
CAUSE Internal error. ALLBASE/SQL request block (JRB)
has an invalid data-buffer flag.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
3006 MESSAGE Invalid data-buffer address in ALLBASE/SQL
request block. (DBERR 3006)
CAUSE The SQLRowBuf was set to an invalid address for a
dynamic query
or
an internal error occurred.
ACTION Correct the SQLRowBuf and re-preprocess your
program
or
record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
3007 MESSAGE Invalid data-buffer length in ALLBASE/SQL request
block. (DBERR 3007)
CAUSE SQLBufLen was set to an invalid length for a
dynamic query
or
an internal error occurred.
ACTION Correct the SQLBufLen and re-preprocess your
program
or
record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
3008 MESSAGE Invalid number of rows requested in ALLBASE/SQL
request block. (DBERR 3008)
CAUSE SQLNRows was set to an invalid number for a dynamic
query
or
an internal error occurred.
ACTION Correct SQLNRows and re-preprocess your program
or
record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
3024 MESSAGE Column number ! in node ! out of range. (DBERR
3024)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP service representative or Response Center.
----------------------------------------------------------------------------
3025 MESSAGE Null length of ! for value ! is invalid. (DBERR
3025)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
3026 MESSAGE Unsupported data format of type ! length !.
(DBERR 3026)
CAUSE Internal error. ALLBASE/SQL detected an
unsupported data type or invalid data length.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
MPE/iX 5.5 Documentation