HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Cont.)
2242 MESSAGE Error(s) occurred processing statement ! during
procedure creation/validation. (DBERR 2242)
CAUSE One or more errors occurred while processing an SQL
statement in a procedure. The statement was not
stored as an invalid section, since it can never be
validated. The procedure was not created.
ACTION Use the statement number in the message to
determine which procedure statement generated the
error. Refer to the accompanying messages for more
information.
----------------------------------------------------------------------------
2243 MESSAGE Execution of procedure of !.! was invalidated.
(DBERR 2243)
CAUSE The procedure executed a statement that invalidated
any further execution of the procedure, such as
DROP PROCEDURE or TRANSFER OWNERSHIP of the
procedure.
ACTION Modify the procedure definition if you did not
intend to invalidate the procedure during its
execution. Otherwise, no action is required.
----------------------------------------------------------------------------
2244 MESSAGE Invalid parameter name ! provided for procedure
!.!. (DBERR 2244)
CAUSE The name of a parameter in the EXECUTE PROCEDURE
statement is not defined in the parameter list of
the CREATE PROCEDURE statement.
ACTION Check the parameter lists of both the EXECUTE
PROCEDURE statement and the CREATE PROCEDURE
statement and ensure that the two lists match.
Then reissue the EXECUTE PROCEDURE statement.
----------------------------------------------------------------------------
2245 MESSAGE OUTPUT ONLY specified for a parameter not
declared as OUTPUT ONLY. (DBERR 2245)
CAUSE You specified OUTPUT ONLY for a parameter in an
EXECUTE PROCEDURE statement, but the parameter was
not declared OUTPUT ONLY in the CREATE PROCEDURE
statement.
ACTION Re-issue the EXECUTE PROCEDURE statement,
specifying OUTPUT instead of OUTPUT ONLY. Be sure
to initialize the parameter value.
----------------------------------------------------------------------------
2246 MESSAGE Number of items in select list does not match
number of result columns for procedure. (DBERR
2246)
CAUSE The select list in a procedure SELECT statement
with no INTO clause is incompatible with the format
specified in the WITH RESULT clause of the CREATE
PROCEDURE statement.
ACTION Re-write the CREATE PROCEDURE statement, either
omitting the WITH RESULT clause, or ensuring that
all multiple row result sets returned from the
procedure are compatible with the format specified.
----------------------------------------------------------------------------
2247 MESSAGE The KEEP option is not allowed for a procedure
cursor. (DBERR 2247)
CAUSE The KEEP option was included on an OPEN cursor
command, but the cursor was defined on an EXECUTE
PROCEDURE statement.
ACTION Re-issue the OPEN command, omitting the KEEP
option.
----------------------------------------------------------------------------
2248 MESSAGE The ADVANCE statement is allowed only for a
procedure cursor. (DBERR 2248)
CAUSE The ADVANCE statement was issued against a cursor,
but the cursor was not defined on an EXECUTE
PROCEDURE statement.
ACTION There is no need for the ADVANCE statement for a
non-procedure cursor. Use the OPEN, FETCH, and
CLOSE statements.
----------------------------------------------------------------------------
[REV BEG]
2249 MESSAGE Duplicate column found in update set columns.
(DBERR 2249)
CAUSE The same column was specified twice in the SET
clause of the UPDATE statement.
ACTION Remove one of the duplicate column assignments.
[REV END]
----------------------------------------------------------------------------
2250 MESSAGE CHECK constraint ! on column ! references other
columns. (DBERR 2250)
CAUSE The named CHECK constraint you defined on a single
column contains references to other columns.
ACTION Either remove the references to the other columns,
or make the check constraint a table level check
constraint.
----------------------------------------------------------------------------
2251 MESSAGE CHECK constraint ! contains host variables.
(DBERR 2251)
CAUSE You defined the named CHECK constraint with host
variables in it.
ACTION Remove the host variable from your CHECK
constraint.
----------------------------------------------------------------------------
2252 MESSAGE CHECK constraint ! contains aggregate functions.
(DBERR 2252)
CAUSE You defined the named CHECK constraint with
aggregate functions in it.
ACTION Remove the aggregate from your CHECK constraint.
----------------------------------------------------------------------------
2253 MESSAGE CHECK constraint ! contains subqueries. (DBERR
2253)
CAUSE You defined the named CHECK constraint with
subqueries in it.
ACTION Remove the subquery from your CHECK constraint.
----------------------------------------------------------------------------
2254 MESSAGE Table CHECK constraint violated. (DBERR 2254)
CAUSE A table CHECK constraint on the target table of the
INSERT or UPDATE was violated during its execution.
ACTION Identify the constraint violated and determine the
proper value for the INSERT or UPDATE.
----------------------------------------------------------------------------
2255 MESSAGE View CHECK OPTION constraint violated. (DBERR
2255)
CAUSE A check constraint on the view named for the INSERT
or UPDATE was violated during its execution.
ACTION Identify the view definition violated (under the
topmost WITH CHECK OPTION view) and determine the
proper value for the INSERT or UPDATE.
----------------------------------------------------------------------------
2256 MESSAGE CHECK constraint ! invalid. (DBERR 2256)
CAUSE The named CHECK constraint will not be executable
and so is not valid.
ACTION Identify the problem with the CHECK constraint by
examining the error or errors prior to this one.
Correct the problem of those errors in order to
make the CHECK constraint executable.
----------------------------------------------------------------------------
2257 MESSAGE View defined WITH CHECK OPTION contains
non-updatable query. (DBERR 2257)
CAUSE The view definition cannot be part of a WITH CHECK
OPTION since no INSERT or UPDATE can be applied to
the view.
ACTION Either remove the WITH CHECK OPTION clause or
modify the view definition to make it updatable.
Refer to the ALLBASE/SQL Reference Manual for a
definition of updatable views.
----------------------------------------------------------------------------
2258 MESSAGE !.! (!) is not a procedure cursor. (DBERR 2258)
CAUSE The USING clause was included in a CLOSE cursor
statement, but the cursor was not defined on an
EXECUTE PROCEDURE statement.
ACTION Re-issue the CLOSE statement, omitting the USING
clause, or re-issue the CLOSE statement with the
USING clause, specifying the correct cursor name.
----------------------------------------------------------------------------
2259 MESSAGE The RESULT option is allowed only for a procedure
returning results. (DBERR 2258)
CAUSE The RESULT option was specified in a DESCRIBE
statement, but the statement described is not an
EXECUTE PROCEDURE statement.
ACTION For statements other than EXECUTE PROCEDURE, the
DESCRIBE RESULT statement is not necessary. If the
sqlmproc field of the SQLDA is 0 after DESCRIBE
OUTPUT, there is no need to DESCRIBE RESULT.
----------------------------------------------------------------------------
2260 MESSAGE Unnamed CHECK constraint on column ! references
other columns. (DBERR 2260)
CAUSE You defined an unnamed CHECK constraint on a single
column contains references to other columns.
ACTION Identify the unnamed constraint which fits this
condition and either remove the references to the
other columns or make the check constraint a table
level check constraint.
----------------------------------------------------------------------------
2261 MESSAGE Unnamed CHECK constraint contains host
variables. (DBERR 2261)
CAUSE You defined an unnamed CHECK constraint with host
variables in it.
ACTION Identify the unnamed constraint which fits this
condition and remove the host variables from that
CHECK constraint.
----------------------------------------------------------------------------
2262 MESSAGE Unnamed CHECK constraint contains aggregate
functions. (DBERR 2262)
CAUSE You defined an unnamed CHECK constraint with
aggregate functions in it.
ACTION Identify the unnamed constraint which fits this
condition and remove the aggregate functions from
that CHECK constraint.
----------------------------------------------------------------------------
2263 MESSAGE Unnamed CHECK constraint contains subqueries.
(DBERR 2263)
CAUSE You defined an unnamed CHECK constraint with
subqueries in it.
ACTION Identify the unnamed constraint which fits this
condition and remove the subqueries from it.
----------------------------------------------------------------------------
2264 MESSAGE Input value provided for OUTPUT ONLY parameter.
(DBERR 2264)
CAUSE In the EXECUTE PROCEDURE statement, an actual
parameter was provided for an OUTPUT ONLY
parameter, but OUTPUT ONLY was not specified.
ACTION Re-issue the EXECUTE PROCEDURE statement, either
omitting the actual parameter completely, or
passing an OUTPUT ONLY host variable for the actual
parameter.
----------------------------------------------------------------------------
2265 MESSAGE DEFAULT value provided for OUTPUT ONLY parameter
!. (DBERR 2265)
CAUSE In the CREATE PROCEDURE statement, a default value
was provided for an OUTPUT ONLY parameter.
ACTION Re-issue the CREATE PROCEDURE statement, either
omitting the default value, or specifying OUTPUT
rather than OUTPUT ONLY.
----------------------------------------------------------------------------
2266 MESSAGE Unnamed CHECK constraint invalid. (DBERR 2266)
CAUSE An unnamed CHECK constraint will not be executable
and so is not valid.
ACTION Identify the unnamed constraint which fits this
condition and identify the problem with this CHECK
constraint by examining the error or errors prior
to this one. Correct the problem of those errors
in order to make the CHECK constraint executable.
----------------------------------------------------------------------------
2267 MESSAGE Column ! must allow nulls since table !.! is not
empty. (DBERR 2267)
CAUSE A NOT NULL specification in an ALTER TABLE
statements requires that the table be empty, or
that a non-null DEFAULT clause be used.
ACTION Include a non-null DEFAULT clause.
----------------------------------------------------------------------------
2268 MESSAGE CONSTRAINT !.! for table ! not found. (DBERR
2268)
CAUSE ConstraintID specified is not a valid constraintID
stored in the database.
ACTION Re-issue the DROP CONSTRAINT statement with a valid
ConstraintID.
----------------------------------------------------------------------------
2269 MESSAGE PRIMARY KEY can not be dropped since it is
referenced by a FOREIGN KEY. (DBERR 2269)
CAUSE PRIMARY KEY constraints can only be dropped when
they are not being referenced by any FOREIGN KEY.
ACTION Verify whether you want to drop the FOREIGN KEY
references before executing this statement again.
----------------------------------------------------------------------------
2270 MESSAGE PRIMARY KEY already exists in table !.!. (DBERR
2270)
CAUSE A PRIMARY KEY is already defined in the table, and
only 1 PRIMARY KEY is allowed in a table.
ACTION You may want to drop the defined PRIMARY KEY if it
is not the intended PRIMARY KEY for this table.
----------------------------------------------------------------------------
2275 MESSAGE Referenced table in foreign key cannot be a view
(!.!). (DBERR 2275)
CAUSE The table named in a REFERENCES clause was a view.
ACTION Change the table to the base table on which the
view is based.
----------------------------------------------------------------------------
2276 MESSAGE User/group ! is using ! authority to support a
foreign key. (DBERR 2276)
CAUSE You attempted to revoke an authority which is
currently depended on by the specified user, class
or group (directly or indirectly) to authorize a
foreign key.
ACTION Re-issue the revoke with CASCADE specified, or have
your DBA or the owner of the foreign key remove the
table in which the foreign key resides, or remove
the foreign key (using DROP TABLE or DROP
CONSTRAINT) and then reissue the revoke.
----------------------------------------------------------------------------
2277 MESSAGE Table !.! does not have a primary key, or number
of columns in primary key does not match number in
foreign key. (DBERR 2277)
CAUSE The table specified in a REFERENCES clause without
a column list has no PRIMARY KEY to use as an
implicit column list, or the number of columns in
the PRIMARY KEY does not match the number specified
in the foreign key list.
ACTION Specify a column list with the table referenced, or
check the number of columns in the primary key of
the table referenced.
----------------------------------------------------------------------------