HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Cont.)
2712 MESSAGE Hash key columns may not be updated. (DBERR
2712)
CAUSE You tried to update the value of a column included
in the key for a hash.
ACTION DELETE the tuple with the old key column value.
Then, INSERT a new tuple with the new key column
value.
----------------------------------------------------------------------------
2716 MESSAGE User ! does not have authority to GENPLAN on
table/view !.!.(!) (DBERR 2716)
CAUSE You do not have run authority to GENPLAN on a
specified section.
ACTION Contact your database administrator to get the
required authority or sign on as a user who does
have the required authority.
----------------------------------------------------------------------------
2717 MESSAGE The specified section !.!(!) is not a SELECT,
UPDATE, DELETE or type II INSERT statement. (DBERR
2717)
CAUSE The specified section you included is not an
allowed statement for GENPLAN.
ACTION Check the source file to find the right section
number.
----------------------------------------------------------------------------
2718 MESSAGE Optimizer did not generate an access plan for the
query. (DBERR 2718)
CAUSE Internal Error.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
2719 MESSAGE User ! does not have authority to GENPLAN on
table/view !.!. (DBERR 2719)
CAUSE You do not have the required authority to execute
GENPLAN on the named table or view.
ACTION Contact your database administrator to obtain the
required authority or sign on as a user who does
have the required authority.
----------------------------------------------------------------------------
2720 MESSAGE INSERT/UPDATE/DELETE disallowed on system tables
(!.!). (DBERR 2720)
CAUSE You attempted to INSERT, UPDATE or DELETE to a
system table.
ACTION Re-issue the statement on a non-system table.
----------------------------------------------------------------------------
2724 MESSAGE Command ! is not allowed for views (!.!). (DBERR
2724)
CAUSE You specified a command (ALTER TABLE, UPDATE
STATISTICS, LOCK TABLE) that cannot be performed on
a view.
ACTION No action is necessary. Refer to the ALLBASE/SQL
Reference Manual for additional information on
these commands and the ALLBASE/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
statement.
ACTION Use the DROP VIEW statement 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
statement.
ACTION Use the DROP TABLE statement 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 statement.
ACTION Issue the command again, specifying a value for all
non-null columns.
----------------------------------------------------------------------------
2731 MESSAGE Reset command not valid for table !.!. (DBERR
2731)
CAUSE You cannot issue the RESET statement on the
specified table.
ACTION No action is necessary. The only valid tables for
the RESET statement are SYSTEM.COUNTER and
SYSTEM.ACCOUNT.
----------------------------------------------------------------------------
2732 MESSAGE Invalid number of columns in view column list.
(DBERR 2732)
CAUSE The number of columns in the CREATE VIEW statement
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 statement and the
SELECT statement.
----------------------------------------------------------------------------
2740 MESSAGE Invalid savepoint number. (DBERR 2740)
CAUSE The ROLLBACK WORK statement included a non-existent
savepoint.
ACTION Issue the command again, specifying a valid
savepoint number. Refer to the ALLBASE/SQL
Reference Manual for additional information on the
ROLLBACK WORK statement.
----------------------------------------------------------------------------
2741 MESSAGE Archive not begun. (DBERR 2741)
CAUSE You attempted to COMMIT ARCHIVE without a preceding
BEGIN ARCHIVE statement.
ACTION Issue the BEGIN ARCHIVE statement first followed by
the COMMIT ARCHIVE statement.
----------------------------------------------------------------------------
2742 MESSAGE Archive already begun. (DBERR 2742)
CAUSE The BEGIN ARCHIVE statement was issued twice.
ACTION No action is necessary.
----------------------------------------------------------------------------
[REV BEG]
2743 MESSAGE Archive checkpoint not found. (DBERR 2743)
CAUSE The checkpoint was not found.
ACTION Review the syntax for CHECKPOINT statement.
[REV END]
----------------------------------------------------------------------------
2744 MESSAGE ROLLBACK WORK TO savepointnumber when you have
cursors opened with KEEP CURSOR option. (DBERR
2744)
CAUSE You opened a cursor with the KEEP CURSOR option and
you are trying to use the SAVEPOINT option of the
ROLLBACK WORK statement.
ACTION Revise the program to open the cursor without the
KEEP CURSOR option, or eliminate the TO SAVEPOINT
clause.
----------------------------------------------------------------------------
2749 MESSAGE Procedure cursor !.!(!) has no current result
set. (DBERR 2749)
CAUSE An attempt was made to fetch from a procedure
cursor, either without first issuing an ADVANCE
statement
or
after an ADVANCE returned an sqlcode of 200 (no
more result sets).
ACTION Issue an ADVANCE statement after opening the
cursor, and before trying to fetch results.
or
Check for an sqlcode of 200 on an ADVANCE statement
before attempting to fetch results.
----------------------------------------------------------------------------
2750 MESSAGE Module !.!(!) has DBEFileSet error. (DBERR 2750)
CAUSE You tried to use DECLARE CURSOR or to PREPARE a
section in a non-existent DBEFileSet.
ACTION Check your spelling, and examine the
SYSTEM.DBEFILESET view to make sure that the
DBEFileSet actually exists. Then issue the command
again, specifying a valid DBEFileSet.
----------------------------------------------------------------------------
2752 MESSAGE Module !.!(!) is a cursor. (DBERR 2752)
CAUSE You tried to use the EXECUTE statement 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
statement.
ACTION A cursor must be declared using the DECLARE CURSOR
statement before you refer to it in the other
cursor commands.
----------------------------------------------------------------------------
2754 MESSAGE Cursor !. ! (!) is not open. (DBERR 2754)
CAUSE ALLBASE/SQL automatically rolled back your
transaction causing the cursors to be closed
or
the cursor was never opened.
ACTION Insure that the cursor was opened.
----------------------------------------------------------------------------
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 statement with a
CURRENT OF CURSOR clause without preceding it with
a FETCH statement or you terminated the transaction
between the FETCH and DELETE or UPDATE statement.
ACTION A FETCH statement 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
statement before an update operation can be
performed on that column.
----------------------------------------------------------------------------
2758 MESSAGE Update table different from cursor table. (DBERR
2758)
CAUSE You tried to update a table which was not specified
in the DECLARE CURSOR statement.
ACTION A table must be listed in the DECLARE CURSOR
statement before it can be updated using the UPDATE
statement with a CURRENT OF CURSOR clause.
----------------------------------------------------------------------------
2759 MESSAGE Cursor has no current tuple. (DBERR 2759)
CAUSE You issued an UPDATE or DELETE statement with a
CURRENT OF CURSOR clause when the current tuple had
already been deleted.
ACTION Modify your application so that no UPDATE or DELETE
WHERE CURRENT is attempted once the current tuple
has been deleted.
----------------------------------------------------------------------------
2760 MESSAGE Null value detected and indicator variable not
declared OR attempted to put null value into
non-null column or result. (DBERR 2760)
CAUSE A SELECT or FETCH statement 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 statement by
setting the indicator variable to a negative
number.
or
You specified NOT NULL for a procedure result and a
null value was fetched.
ACTION Modify your program to include indicator variables
with columns that might contain null values
or
issue the INSERT or UPDATE statement again,
specifying only non-null values for columns created
with the NOT NULL option.
or
drop the procedure and recreate it, either omitting
the NOT NULL option in the WITH RESULT clause, or
modifying the procedure SELECT statements so that
no null values will be retrieved.
----------------------------------------------------------------------------
2762 MESSAGE Selectlist has ! items and host variable buffer
has !. (DBERR 2762)
CAUSE The number of select list items in a DECLARE CURSOR
or a SELECT statement does not match the number of
host variables in the corresponding FETCH or SELECT
statement or the number of select list items in the
SELECT statement does not match the number of host
variables in the SELECT statement.
ACTION Modify your program so that the number of variables
in the select list or the SELECT statement matches
the number of host variables. Refer to the
ALLBASE/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 statement 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 ALLBASE/SQL Reference
Manual for additional information on the SELECT
statement.
----------------------------------------------------------------------------
2764 MESSAGE DISTINCT within an aggregate function cannot
reference an expression. (DBERR 2764)
CAUSE The SELECT statement 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 ALLBASE/SQL Reference
Manual for additional information on the SELECT
statement.
----------------------------------------------------------------------------