HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Continued)
2211 MESSAGE Column ! not found. (DBERR 2211)
CAUSE The column you specified in the query does not
exist in any of the specified tables.
ACTION Check your spelling. If you still receive this
error ask your database administrator to check the
SYSTEM.COLUMN view to make sure that the specified
column does exist.
----------------------------------------------------------------------------
2212 MESSAGE Index ! not found in table !.!. (DBERR 2212)
CAUSE A non-existent index was specified in the DROP
INDEX statement
or
the index specified in the DROP command is not
associated with the specified table.
ACTION Check your spelling. If you still receive this
error, ask your database administrator to check the
SYSTEM.INDEX view to make sure that the specified
index does exist in the specified table.
----------------------------------------------------------------------------
2213 MESSAGE Duplicate index !. (DBERR 2213)
CAUSE The index you named in the CREATE INDEX statement
already exists for the specified table.
ACTION Create the index with another name or DROP the old
index before you create the new one.
----------------------------------------------------------------------------
2214 MESSAGE Unrecognizable command or module !.!(!) not
found. (DBERR 2214)
CAUSE One of two error conditions has occurred. Either
the command you entered is not recognizable or the
module specified cannot be found.
ACTION Check your spelling. Ask your database
administrator to check the SYSTEM.SECTION view to
make sure that the module exists in the
DBEnvironment to which the application is
connected.
----------------------------------------------------------------------------
2215 MESSAGE Module !.!(!) already exists. (DBERR 2215)
CAUSE You tried to PREPARE a module or declare a cursor
which already exists.
ACTION Issue the command again, specifying a unique module
name. Use another integer or give the command a
different name. Ask your Database Administrator to
check the SYSTEM.SECTION view for names of existing
modules.
----------------------------------------------------------------------------
2216 MESSAGE Module !.! not found. (DBERR 2216)
CAUSE You tried to execute the OPEN CURSOR statement or
the DROP MODULE statement on a non-existent section
or
the module in the DROP MODULE statement does not
exist.
ACTION Check your spelling. If you still receive this
error, ask your Database Administrator to check the
SYSTEM.SECTION view to make sure that the module
exists in the specified DBEnvironment.
----------------------------------------------------------------------------
2218 MESSAGE TempSpace name ! already defined. (DBERR 2218)
CAUSE You tried to create a TEMPSPACE that was already
created in this DBEnvironment.
ACTION Issue the CREATE TEMPSPACE statement again,
specifying a unique logical tempspace name.
----------------------------------------------------------------------------
2219 MESSAGE TempSpace name ! not found. (DBERR 2219)
CAUSE You tried to access a TEMPSPACE that does not exist
in this DBEnvironment by using the DROP TEMPSPACE
statement.
ACTION Check your spelling. Check the SYSTEM.TEMPSPACE
table to make sure that the specified TEMPSPACE
does exist.
----------------------------------------------------------------------------
2220 MESSAGE Duplicate column found in sort column list.
(DBERR 2220)
CAUSE The ORDER BY clause in the SELECT statement
contains more than one reference to the same
column. The command is not executed.
ACTION Remove the duplicate column and execute the command
again.
----------------------------------------------------------------------------
2221 MESSAGE Duplicate column found in insert column list.
(DBERR 2221)
CAUSE The column list in the INSERT statement contains
more than one reference to the same column.
ACTION Remove the duplicate column and execute the command
again.
----------------------------------------------------------------------------
2222 MESSAGE Table name required to drop index !.!. (DBERR
2222)
CAUSE You attempted to drop an index with an ambiguous
name. The same index name was used in creating
indexes on two tables with the same owner.
ACTION Use the syntax DROP INDEX IndexName FROM
[Owner.]TableName to specify which table's index
should be dropped.
----------------------------------------------------------------------------
2223 MESSAGE Index !.! not found. (DBERR 2223)
CAUSE A non-existent index was specified in the DROP
INDEX statement without an associated table.
ACTION Check your spelling. If you still receive this
error, ask your database administrator to check the
SYSTEM.INDEX view to make sure that the specified
index does exist.
----------------------------------------------------------------------------
2224 MESSAGE ! !.! must have same owner as table !.!. (DBERR
2224)
CAUSE Different owners were given for the named INDEX,
CONSTRAINT, or RULE and the named table, or the
default table owner was different from the
specified INDEX, CONSTRAINT, or RULE owner in the
CREATE INDEX, DROP INDEX, DROP CONSTRAINT, CREATE
RULE, or DROP RULE statement.
ACTION If both owners were specified, check your spelling.
If the table owner was not specified, either
specify one or drop the specification of the INDEX,
CONSTRAINT, or RULE owner. If you still receive
this error, ask your database administrator to
check the SYSTEM.INDEX view, SYSTEM.CONSTRAINT
view, or SYSTEM.RULE view to determine the correct
owner.
----------------------------------------------------------------------------
2225 MESSAGE Out of disc space for all TempSpaces. (DBERR
2225)
CAUSE There is not enough space in the device to support
your sorting operation.
ACTION Use a different device or contact your database
administrator to add more space to the current
device.
----------------------------------------------------------------------------
2226 MESSAGE Location name must be fully qualified with group
and account name. (DBERR 2226)
CAUSE The location name you specified in the CREATE
TEMPSPACE statement was not fully qualified.
ACTION Issue the CREATE TEMPSPACE statement again,
specifying a location name that includes both group
and account name.
----------------------------------------------------------------------------
2227 MESSAGE Duplicate SCHEMA !. (DBERR 2227 )
CAUSE There are existing objects already owned by the
AuthorizationName specified.
ACTION Make sure the AuthorizationName specified is
neither an owner of existing objects in the
DBEnvironment nor a grantor of authority on
existing objects. To check ownership,
query SYSTEM.TABLE and SYSTEM.GROUP. To
check authorities, query SYSTEM.TABAUTH and
SYSTEM.COLAUTH.
----------------------------------------------------------------------------
2228 MESSAGE Duplicate column ! found in joined table. (DBERR
2228)
CAUSE With an explicit three or more table join, a result
table (which participates in a subsequent join
clause) has been produced and it has more than one
column with the same column name. This same column
name is either specified as a join column in the
"ON SearchCondition" clause of the explicit join,
or if a NATURAL...JOIN has been specified, the
column has been chosen by ALLBASE/SQL as a join
column.
ACTION When writing a three or more table join with
explicit join syntax make sure that for any single
result table participating in a join, there are no
duplicate column names which will be named as a
join column. To ensure this, make each join clause
a NATURAL...JOIN or a JOIN...USING (ColumnList),
except for the final join, which may contain these
types or a JOIN...ON SearchCondition3 clause.
Otherwise, ensure that each join clause is a
JOIN...ON SearchCondition3 clause.
----------------------------------------------------------------------------
2229 MESSAGE Duplicate column ! found in USING clause of JOIN.
(DBERR 2229)
CAUSE There is more than one column with the same name in
the USING (ColumnList) clause of an explicit join.
ACTION Remove the duplicate column name from the USING
(ColumnList) clause of the explicit join.
----------------------------------------------------------------------------
2230 MESSAGE Maximum number of parameters (!) exceeded in
procedure !.!. (DBERR 2230)
CAUSE The number of parameters you specified in the
CREATE PROCEDURE statement was greater than the
maximum number allowed.
ACTION Issue the CREATE PROCEDURE statement again,
limiting the number of parameters to 255 or fewer.
----------------------------------------------------------------------------
2231 MESSAGE Procedure parameter data type may not be a LONG
data type. (DBERR 2231)
CAUSE You specified a LONG data type as the parameter
data type in a CREATE PROCEDURE statement.
ACTION Issue the statement again, specifying only a valid
(non-LONG) data type for each parameter.
----------------------------------------------------------------------------
2232 MESSAGE Duplicate parameter !. (DBERR 2232)
CAUSE You specified a parameter name twice in the CREATE
PROCEDURE statement.
ACTION Issue the statement again, specifying unique
parameter names.
----------------------------------------------------------------------------
2233 MESSAGE OUTPUT specified for a parameter not declared as
OUTPUT. (DBERR 2233)
CAUSE In the EXECUTE PROCEDURE statement, you specified
OUTPUT for a non- OUTPUT parameter.
ACTION Re-issue the EXECUTE PROCEDURE statement,
specifying OUTPUT only for parameters that were
declared as OUTPUT parameters in the CREATE
PROCEDURE statement. If necessary, recreate the
procedure specifying OUTPUT for this parameter.
----------------------------------------------------------------------------
2234 MESSAGE No value was provided for non-nullable parameter
! in procedure !.!. (DBERR 2234)
CAUSE A parameter declared as NOT NULL in the CREATE
PROCEDURE statement was not provided with a value
in the EXECUTE PROCEDURE statement.
ACTION Re-issue the EXECUTE PROCEDURE statement, providing
a value for each parameter declared as NOT NULL.
----------------------------------------------------------------------------
2235 MESSAGE Error occurred executing procedure !.! statement
!. (DBERR 2235)
CAUSE An error occurred during procedure execution.
ACTION Refer to the accompanying error message. Use the
statement number to determine which procedure
statement caused the error.
----------------------------------------------------------------------------
2236 MESSAGE Doubly defined LABEL !. (DBERR 2236)
CAUSE You used the same label more than once in a CREATE
PROCEDURE statement.
ACTION Remove the duplicate label definition, and reissue
the CREATE PROCEDURE statement.
----------------------------------------------------------------------------
2237 MESSAGE Undefined LABEL !. (DBERR 2237)
CAUSE You refer to an undefined label in a GOTO statement
in the CREATE PROCEDURE statement.
ACTION Define the label within the CREATE PROCEDURE
statement.
----------------------------------------------------------------------------
2238 MESSAGE Error occurred during evaluation of the
condition in an IF or WHILE statement or the
expression in a parameter or variable assignment.
Procedure execution terminated. (DBERR 2238)
CAUSE An error occurred in evaluating the condition or
expression.
ACTION Refer to the accompanying error message for
additional information.
----------------------------------------------------------------------------
2239 MESSAGE Procedure !.! not found. (DBERR 2239)
CAUSE The procedure you specified in the statement does
not exist in the DBEnvironment.
ACTION Check your spelling of the procedure name and the
procedure's owner name against the content of the
CATALOG.PROCEDURE view. If you still receive this
error, ask your database administrator to check the
SYSTEM.PROCEDURE view to make sure the specified
procedure does exist.
----------------------------------------------------------------------------
2240 MESSAGE Procedure !.! already exists. (DBERR 2240)
CAUSE The procedure you specified in the CREATE PROCEDURE
statement already exists in the DBEnvironment.
ACTION Create the procedure with a different name and/or
owner name.
----------------------------------------------------------------------------
2241 MESSAGE Too many parameter values provided for procedure
!.!. (DBERR 2241)
CAUSE In the EXECUTE PROCEDURE statement, you provided a
greater number of parameter values than the number
of parameters in the procedure.
ACTION Check the procedure specification or the parameter
descriptions in SYSTEM.PARAMETER. Reissue the
EXECUTE PROCEDURE statement, providing no more
parameter values than the number in the procedure.
----------------------------------------------------------------------------