HP SQL Messages 2500 - 2770 [ HP SQL/V Message Manual ]
HP SQL/V Message Manual
HP SQL Messages 2500 - 2770
--------------------------------------------------------------------------
2500 MESSAGE Cannot drop a non-empty DBEFileSet. (DBERR 2500)
CAUSE You attempted to DROP a DBEFileSet which has DBEFiles
associated with it.
ACTION Before dropping the DBEFileSet, drop the DBEFiles then
remove them. Remember that the DBEFiles must be empty
before they can be dropped.
--------------------------------------------------------------------------
2501 MESSAGE DBEFileSet has no DBEFiles. (DBERR 2501)
CAUSE You created a table in an empty DBEFileSet and then
tried to INSERT into that table.
ACTION ADD a DBEFile to the DBEFileSet before attempting an
INSERT command.
--------------------------------------------------------------------------
2502 MESSAGE Data or index space exhausted in DBEFileSet. (DBERR
2502)
CAUSE During an INSERT, UPDATE, or CREATE INDEX command, the
DBEFileSet ran out of space.
ACTION Ask your Database Administrator to add another DBEFile
to the appropriate DBEFileSet.
--------------------------------------------------------------------------
2503 MESSAGE DBEFile not empty. (DBERR 2503)
CAUSE You attempted to REMOVE a non-empty DBEFile from its
DBEFileSet.
ACTION The DBEFile must be empty before it can be removed
from the DBEFileSet.
--------------------------------------------------------------------------
2505 MESSAGE DBEFile size must be between 2 and 32,767 pages.
(DBERR 2505)
CAUSE The file size specified in the CREATE DBEFILE command
was not within the valid range.
ACTION Issue the CREATE DBEFILE command again specifying a
file size within the range of 2 through 32,767 pages.
--------------------------------------------------------------------------
2507 MESSAGE DBEFile must be empty or new type must be mixed.
(DBERR 2507)
CAUSE You attempted to ALTER a non-empty DBEFile to a type
other than mixed.
ACTION The type of a non-empty DBEFile can be changed from
TABLE or INDEX to MIXED. No other changes are allowed.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
2508 MESSAGE DBEFileSet has no DBEFile of the required DBEFile
type. (DBERR 2508)
CAUSE You tried to insert rows into a table whose DBEFileSet
has only INDEX DBEFiles
or
you tried to create an index on a non-empty table
whose DBEFileSet contains only DATA DBEFiles.
ACTION Ask your Database Administrator to CREATE and ADD the
appropriate DBEFiles.
--------------------------------------------------------------------------
2509 MESSAGE Index uniqueness violated. (DBERR 2509)
CAUSE You tried to insert a duplicate key value into a
column used in a unique index.
ACTION Issue the INSERT command again without the specified
row.
--------------------------------------------------------------------------
2510 MESSAGE Table is read only. (DBERR 2510)
CAUSE You tried a LOCK or WRITE operation (DROP, DELETE,
INSERT, LOCK TABLE, UPDATE, UPDATE STATISTICS) on a
read only table.
ACTION No action is necessary. These operations can not be
performed on SYSTEM.CALL, SYSTEM.ACCOUNT, SYSTEM.USER,
SYSTEM.COUNTER, or SYSTEM.TRANSACTION.
--------------------------------------------------------------------------
2511 MESSAGE User ! does not exist. (DBERR 2511)
CAUSE The userid specified in the TERMINATE USER or RESET
SYSTEM.ACCOUNT command is not currently connected to
the DBEnvironment.
ACTION Issue the command again specifying a valid userid.
--------------------------------------------------------------------------
2515 MESSAGE DBEFile is currently associated with a DBEFileSet.
(DBERR 2515)
CAUSE You tried to DROP a DBEFile which was associated with
a DBEFileSet
or
you tried to ADD a DBEFile to a DBEFileSet which
already is associated with another DBEFileSet.
ACTION You must REMOVE the DBEFile from the DBEFileSet before
it can be dropped
or
you must REMOVE the DBEFile from the DBEFileSet with
which it is currently associated before you can ADD it
to a different DBEFileSet.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
2516 MESSAGE This table already has a clustering index. (DBERR
2516)
CAUSE Using the CREATE INDEX command, no more than one index
per table can have the clustering attribute.
ACTION Drop the existing clustering index or create the new
index without the clustering attribute.
--------------------------------------------------------------------------
2600 MESSAGE Integer overflow on operation !. (DBERR 2600)
CAUSE The result of an integer arithmetic operation within
an expression was too big for the hardware to
accommodate.
ACTION Try to break the expression so that divisions occur
before multiplications or break the expression into
multiple expressions.
--------------------------------------------------------------------------
2601 MESSAGE Integer divide by zero. (DBERR 2601)
CAUSE The result of an arithmetic operation within an
expression caused an integer value to be divided by
zero.
ACTION Look at your data to find where this error occurred
and make any necessary changes to your expression.
--------------------------------------------------------------------------
2602 MESSAGE Extended precision overflow on operation !. (DBERR
2602)
CAUSE The result of a float arithmetic operation within an
expression was too big for the hardware to
accommodate.
ACTION Try to modify your expression so that divisions occur
before multiplications or break the expression into
multiple expressions.
--------------------------------------------------------------------------
2603 MESSAGE Extended precision underflow on operation !. (DBERR
2603)
CAUSE The result of a float arithmetic operation within an
expression was too small for the hardware to
accommodate.
ACTION Try to modify your expression so that multiplications
occur before divisions or break the expression into
multiple expressions.
--------------------------------------------------------------------------
2604 MESSAGE Extended precision divide by zero. (DBERR 2604)
CAUSE The result of an arithmetic operation within an
expression caused an extended precision value to be
divided by zero.
ACTION Look at your data to find where this error occurred
and make any necessary changes.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
2605 MESSAGE Packed decimal overflow on operation !. (DBERR 2605)
CAUSE The result of an intermediate decimal operation was
too big for the hardware to accommodate.
ACTION Try to modify your expression so that divisions occur
before multiplications or break the expression into
multiple expressions.
--------------------------------------------------------------------------
2606 MESSAGE Invalid decimal digit in operation !. (DBERR 2606)
CAUSE The decimal number you included through the host
variable in a COBOL program was not valid.
ACTION Correct the decimal so that it is within the range of
0 through 9 and contains either a + or - sign.
--------------------------------------------------------------------------
2607 MESSAGE Packed decimal divide by zero. (DBERR 2607)
CAUSE The result of an arithmetic operation within an
expression caused a packed decimal value to be divided
by zero.
ACTION Look at your data to find where this error occurred
and make any necessary changes.
--------------------------------------------------------------------------
2608 MESSAGE Pascal ! arithmetic error on operation !. (DBERR
2608)
CAUSE An arithmetic error occurred probably due to the
result of your expression being too large for the
hardware to accommodate.
ACTION Try to break the arithmetic expressions in your query
into multiple expressions.
--------------------------------------------------------------------------
2609 MESSAGE Incompatible data types ! and ! in expression. (DBERR
2609)
CAUSE You attempted to mix numeric and character data types
in an expression in the select list, the WHERE clause,
or the SET clause.
ACTION Issue the command again specifying either numeric or
character data only. Refer to the SQL Reference
Manual for additional information on the SET command.
--------------------------------------------------------------------------
2610 MESSAGE Operator ! invalid for data type !. (DBERR 2610)
CAUSE You attempted to perform an arithmetic operation on
char or varchar data, or attempted the LIKE predicate
on numeric data.
ACTION Issue the command again using only appropriate
operators on data types.
--------------------------------------------------------------------------
2611 MESSAGE Invalid source word count in decimal operation !.
(DBERR 2611)
CAUSE An internal arithmetic error was detected by the
hardware in a decimal arithmetic operation.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
2612 MESSAGE Invalid operand length in decimal operation. (DBERR
2612)
CAUSE An internal arithmetic error was detected by the
hardware in a decimal arithmetic operation.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
--------------------------------------------------------------------------
2613 MESSAGE Precision digits lost in decimal operation !. (DBERR
2613)
CAUSE A decimal operation within an expression was completed
successfully, but the target area specified (typically
a host variable) was too small to contain it.
ACTION Try to modify your expression so that divisions occur
before multiplications
or
increase the host variable size. Refer to the HP SQL
Application Programming Guide for the language you are
using for additional information on host variable
size.
--------------------------------------------------------------------------
2614 MESSAGE Invalid decimal operand sign in operation !. (DBERR
2614)
CAUSE An internal arithmetic error was detected by the
hardware in a decimal arithmetic operation.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
--------------------------------------------------------------------------
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 command in the 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 SQL Reference Manual for
additional information.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
2702 MESSAGE INSERT/UPDATE/DELETE disallowed in 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 can not contain a GROUP BY clause. Refer
to the specified command and the CREATE VIEW command
in the SQL Reference Manual for additional
information.
--------------------------------------------------------------------------
2704 MESSAGE SELECT * disallowed with the GROUP BY clause. (DBERR
2704)
CAUSE You attempted a SELECT * in conjunction with a GROUP
BY clause.
ACTION When you use the GROUP BY clause, the select list can
contain only aggregate functions and columns
referenced in the GROUP BY clause; the select list
cannot contain an *. Refer to the SQL Reference
Manual for additional information.
--------------------------------------------------------------------------
2705 MESSAGE Illegal reference to column ! in group operation.
(DBERR 2705)
CAUSE A column specified in the select list was not
referenced in the GROUP BY clause of the SELECT
command.
ACTION Issue the SELECT command again, specifying only
aggregate functions and columns referenced 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. Refer to the CREATE VIEW command in the SQL
Reference Manual for restrictions on updating a view.
--------------------------------------------------------------------------
2711 MESSAGE Qualifier !.! (column !) is different from input
table. (DBERR 2711)
CAUSE The table name specified in the select list or WHERE
clause is different from the table name specified in
the FROM clause of the SELECT command.
ACTION Issue the SELECT command again specifying the same
table name in both the select list or WHERE clause and
the FROM clause. Refer to the SQL Reference Manual
for additional information on the SELECT command.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
2721 MESSAGE ALTER TABLE can only add NULL columns (!.!). (DBERR
2721)
CAUSE You attempted to add a NOT NULL column with the ALTER
TABLE command.
ACTION Issue the ALTER TABLE command again without specifying
the NOT NULL attribute for the new column.
--------------------------------------------------------------------------
2724 MESSAGE Command ! is not for views (!.!). (DBERR 2724)
CAUSE The specified command (ALTER TABLE, UPDATE STATISTICS,
LOCK TABLE) cannot be performed on a view.
ACTION No action is necessary. Refer to the SQL Reference
Manual for additional information on these commands
and the HP SQL Database Administration Guide for
additional information on views.
--------------------------------------------------------------------------
2725 MESSAGE Use DROP VIEW to drop view !.!. (DBERR 2725)
CAUSE You attempted to drop a view using the DROP TABLE
command.
ACTION Use the DROP VIEW command to drop a view.
--------------------------------------------------------------------------
2726 MESSAGE Use DROP TABLE to drop table !.!. (DBERR 2726)
CAUSE You attempted to drop a table using the DROP VIEW
command.
ACTION Use the DROP TABLE command to drop a table.
--------------------------------------------------------------------------
2730 MESSAGE Column ! does not accept nulls. (DBERR 2730)
CAUSE You specified the NULL keyword for a non-null column
in the INSERT or UPDATE command.
ACTION Issue the command again specifying a value for all
non-null columns.
--------------------------------------------------------------------------
2731 MESSAGE Reset command not valid for table !.!. (DBERR 2731)
CAUSE The RESET command cannot be issued on the specified
table.
ACTION No action is necessary. The only valid tables for the
RESET command are SYSTEM.COUNTER and SYSTEM.ACCOUNT.
--------------------------------------------------------------------------
2732 MESSAGE Invalid number of columns in the view column list.
(DBERR 2732)
CAUSE The number of columns in the CREATE VIEW command did
not match the number of columns in the SELECT
statement for the view.
ACTION Issue the command again using the same number of
columns in both the CREATE VIEW command and the SELECT
statement.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
2740 MESSAGE Invalid savepoint number. (DBERR 2740)
CAUSE The ROLLBACK WORK command included a non-existent
savepoint.
ACTION Issue the command again specifying a valid savepoint
number. Refer to the SQL Reference Manual for
additional information on the ROLLBACK WORK command.
--------------------------------------------------------------------------
2741 MESSAGE Archive not begun. (DBERR 2741)
CAUSE You attempted to COMMIT ARCHIVE without a preceding
BEGIN ARCHIVE command.
ACTION Issue the BEGIN ARCHIVE command first followed by the
COMMIT ARCHIVE command. Refer to the SQL Reference
Manual for additional information.
--------------------------------------------------------------------------
2742 MESSAGE Archive already begun. (DBERR 2742)
CAUSE The BEGIN ARCHIVE command was issued twice.
ACTION No action is necessary.
--------------------------------------------------------------------------
2743 MESSAGE Archive checkpoint not found. (DBERR 2743)
CAUSE An archive checkpoint was not written to the log file,
so the log file cannot be used for rollforward
recovery.
ACTION Refer to the HP SQL Database Administration Guide for
additional information on archive checkpoints, and to
the SQL Reference Manual for information on the START
DBE RECOVER, BEGIN ARCHIVE, and COMMIT ARCHIVE
commands.
--------------------------------------------------------------------------
2750 MESSAGE Module !.!(!) has DBEFileSet error. (DBERR 2750)
CAUSE You tried to DECLARE A CURSOR or PREPARE a section in
a non-existent DBEFileSet.
ACTION Check your spelling and the SYSTEM.DBEFileSet table to
make sure that the DBEFileSet actually exists. Then
issue the command again specifying a valid DBEFileSet.
--------------------------------------------------------------------------
2752 MESSAGE Module !.!(!) is not a procedure. (DBERR 2752)
CAUSE You tried to use the EXECUTE command on a cursor.
ACTION The only valid commands for a cursor are OPEN, CLOSE,
FETCH, DESCRIBE, and DECLARE CURSOR.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
2753 MESSAGE Module !.!(!) is not a cursor. (DBERR 2753)
CAUSE You tried to OPEN, CLOSE, FETCH, or DESCRIBE a section
which was not defined with a DECLARE CURSOR command.
ACTION A cursor must be declared using the DECLARE CURSOR
command before you refer to it in the other cursor
commands.
--------------------------------------------------------------------------
2754 MESSAGE Module !.!(!) is not open. (DBERR 2754)
CAUSE HP SQL automatically rolled back your transaction
causing the cursors to be closed. An additional
message will be returned.
ACTION Refer to the cause and action of the additional
message.
--------------------------------------------------------------------------
2755 MESSAGE Module !.!(!) already open. (DBERR 2755)
CAUSE You attempted to OPEN the same cursor twice.
ACTION No action is necessary.
--------------------------------------------------------------------------
2756 MESSAGE Cursor !.!(!) has no current tuple. (DBERR 2756)
CAUSE You issued an UPDATE or DELETE command with a CURRENT
OF CURSOR clause without preceding it with a FETCH
command or you terminated the transaction between the
FETCH and DELETE or UPDATE command.
ACTION A FETCH command must precede any DELETE or UPDATE
WHERE CURRENT operation within the transaction.
--------------------------------------------------------------------------
2757 MESSAGE Update column list not in cursor update column list.
(DBERR 2757)
CAUSE You tried to update a column which was not specified
when the cursor was declared.
ACTION A column must be listed in the DECLARE CURSOR command
before an update operation can be performed on that
column.
--------------------------------------------------------------------------
2758 MESSAGE Update table different than cursor table. (DBERR
2758)
CAUSE You tried to update a table which was not specified in
the DECLARE CURSOR command.
ACTION A table must be listed in the DECLARE CURSOR command
before it can be updated using the UPDATE command with
a CURRENT OF CURSOR clause.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
2760 MESSAGE Null value detected and indicator variable not
declared OR attempted to put null value into non-null
column. (DBERR 2760)
CAUSE A SELECT or FETCH command had no corresponding
indicator variable and a null value was fetched for an
item
or
you attempted to put a null value into a non-null
column using the INSERT or UPDATE command by setting
the indicator variable to a negative number.
ACTION Modify your program to include indicator variables
with columns that might contain null values
or
issue the INSERT or UPDATE command again specifying
only non-null values for columns created with the NOT
NULL option.
--------------------------------------------------------------------------
2761 MESSAGE REAL data type not supported. Use LONGREAL. (DBERR
2761)
CAUSE You defined a host variable as type REAL in a Pascal
program.
ACTION Change the type to LONGREAL.
--------------------------------------------------------------------------
2762 MESSAGE Select list has ! items and host variable buffer has
!. (DBERR 2762)
CAUSE The number of select list items in a DECLARE CURSOR or
a SELECT command does not match the number of host
variables in the corresponding FETCH or SELECT command
or the number of select list items in the SELECT
command does not match the number of host variables in
the SELECT command.
ACTION Modify your program so that the number of variables in
the select list or the SELECT command matches the
number of host variables. Refer to the SQL Reference
Manual for additional information on these commands.
--------------------------------------------------------------------------
2763 MESSAGE DISTINCT within aggregate functions cannot reference
multiple column names. (DBERR 2763)
CAUSE The SELECT command contains more than one aggregate
function containing the DISTINCT option and references
more than one column.
ACTION Modify your statement so that it references only one
column. Refer to the SQL Reference Manual for
additional information on the SELECT command.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
2764 MESSAGE DISTINCT within an aggregate function cannot reference
an expression. (DBERR 2764)
CAUSE The SELECT command contains an aggregate function
containing the DISTINCT option and references a column
containing computed values.
ACTION Modify your statement so that only raw columns are
referenced. Refer to the SQL Reference Manual for
additional information on the SELECT command.
--------------------------------------------------------------------------
2770 MESSAGE INSERT rejected: FORMAT II INSERT cannot insert a
table into itself. (DBERR 2770)
CAUSE The table specified as the target table in the INSERT
command was the same as one of the tables in the
embedded SELECT command.
ACTION Modify your command specifying a different target
table or remove the target table from the embedded
SELECT command.
--------------------------------------------------------------------------