HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Cont.)
1046 MESSAGE Failed to allocate heap space (DBERR 1046)
CAUSE There was no memory available for your query.
ACTION Report this error to your database administrator
and try you again later. If the problem persists,
record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
1047 MESSAGE Failed to free heap space (DBERR 1047)
CAUSE Internal error.
ACTION Report this error to your database administrator.
If the problem persists, record as much information
as possible and contact your HP Service
Representative or Response Center.
----------------------------------------------------------------------------
1048 MESSAGE Number of precision digits for this decimal
constant exceeds 27. (DBERR 1048)
CAUSE A constant specified in the INSERT, UPDATE, SELECT,
DELETE, or DECLARE CURSOR statement contained more
than 27 digits.
ACTION Correct your query so that all constants contain
less than or equal to 27 decimal digits.
----------------------------------------------------------------------------
1049 MESSAGE Dynamic query size exceeds input buffer size.
(DBERR 1049)
CAUSE The query included in the dynamic SQL command
(PREPARE or EXECUTE IMMEDIATE) is larger than the
input buffer.
ACTION Reduce the size of your query or put it in a host
variable where it can be up to 32,762 bytes in
length.
----------------------------------------------------------------------------
1050 MESSAGE Statement not allowed in EXECUTE IMMEDIATE
statement. (DBERR 1050)
CAUSE The statement included in the EXECUTE IMMEDIATE
cannot be used dynamically.
ACTION Use the EXECUTE statement in the regular way
through ISQL or the preprocessor, not in EXECUTE
IMMEDIATE.
----------------------------------------------------------------------------
1051 MESSAGE SQL Parser internal NLS error. (DBERR 1051)
CAUSE An internal Native Language Support error occurred
within the parser, probably due to an invalid
character in input.
ACTION Check your input for invalid bytes, and try again.
----------------------------------------------------------------------------
1052 MESSAGE Invalid character found in SQL command. (DBERR
1052)
CAUSE An SQL statement contained an invalid Native
Language Support (NLS) character.
ACTION Check the NLS characters in the SQL statement and
issue it again.
----------------------------------------------------------------------------
1053 MESSAGE Duplicate LANG clause defined. (DBERR 1053)
CAUSE A command was issued with a duplicate LANG clause.
ACTION Correct the command and issue it again.
----------------------------------------------------------------------------
1054 MESSAGE Invalid LANG specified. (DBERR 1054)
CAUSE You attempted to specify a language that is not
configured on the system possibly because of
misspelling.
ACTION Specify a valid language, then reissue the command
to create the object.
----------------------------------------------------------------------------
1055 MESSAGE Language clause not valid with non-character
column. (DBERR 1055)
CAUSE You tried to define a non-character column as
having a language type.
ACTION Specify the language type with the appropriate
character column.
----------------------------------------------------------------------------
1057 MESSAGE DEFAULT NULL is specified, NOT NULL is not
allowed. (DBERR 1057)
CAUSE DEFAULT NULL and NOT NULL cannot be specified at
the same time.
ACTION Either remove the DEFAULT NULL clause or remove the
NOT NULL clause.
----------------------------------------------------------------------------
1058 MESSAGE Number of referenced columns must match number of
foreign key columns. (DBERR 1058)
CAUSE The number of columns in the column list following
REFERENCES was greater than one for a column-level
constraint, or did not match the number of columns
in a FOREIGN KEY column list for a table level
constraint in a CREATE TABLE statement.
ACTION Check your syntax and correct the number of
columns.
----------------------------------------------------------------------------
1059 MESSAGE Aggregate, subquery, or host variable disallowed
in CHECK constraint or rule. (DBERR 1059)
CAUSE A CHECK constraint or RULE was defined with one of
these items in it.
ACTION Check the syntax and remove the aggregate,
subquery, or host variable from your CHECK
constraint or RULE.
----------------------------------------------------------------------------
1060 MESSAGE Constraint name beginning with SQLCON_
disallowed. (DBERR 1060)
CAUSE A CONSTRAINT clause was specified with a name
starting with 'SQLCON_' in your CREATE TABLE or
CREATE VIEW statement.
ACTION Remove the CONSTRAINT clause or choose a different
constraint name.
----------------------------------------------------------------------------
1061 MESSAGE The syntax PRIMARY KEY may only be used once in
CREATE/ALTER TABLE. (DBERR 1061)
CAUSE The syntax PRIMARY KEY appears more than once in
your CREATE TABLE statement.
ACTION Check the syntax and remove all but one of the
PRIMARY KEY specifications, or change all but one
to UNIQUE.
----------------------------------------------------------------------------
1062 MESSAGE HASH ON CONSTRAINT clause did not match any
unique constraint name. (DBERR 1062)
CAUSE The constraint named in your HASH ON CONSTRAINT
clause was not found in the CREATE TABLE statement.
ACTION Check the syntax and use the name of a named unique
constraint in the HASH ON CONSTRAINT clause.
----------------------------------------------------------------------------
1063 MESSAGE HASH/CLUSTERING ON CONSTRAINT used without a
PRIMARY KEY. (DBERR 1063)
CAUSE The syntax HASH/CLUSTERING ON CONSTRAINT is used
without a constraint name, and no PRIMARY KEY was
defined in the CREATE TABLE statement.
ACTION Check the syntax and either define a PRIMARY KEY or
add a constraint name to the HASH/CLUSTERING ON
CONSTRAINT clause.
----------------------------------------------------------------------------
1064 MESSAGE CLUSTERING ON CONSTRAINT clause did not match any
unique or referential constraint name. (DBERR
1064)
CAUSE The constraint named in your CLUSTERING ON
CONSTRAINT clause was not found in the CREATE TABLE
statement.
ACTION Check the syntax and use the name of a named unique
or referential constraint in the CLUSTERING ON
CONSTRAINT clause.
----------------------------------------------------------------------------
1065 MESSAGE Multiple definition of a column integrity
constraint disallowed. (DBERR 1065)
CAUSE You used the syntax NOT NULL, LANG =, CHECK,
UNIQUE, PRIMARY KEY, or REFERENCES more than once
in a column definition in an ALTER TABLE or CREATE
TABLE statement.
ACTION Remove the extra constraint(s); if more than one
CHECK exists, the expressions within them can be
ANDed together within a single CHECK.
----------------------------------------------------------------------------
1066 MESSAGE Illegal hexadecimal number specified. (DBERR
1066)
CAUSE You specified non-hexadecimal characters for the
BINARY/VARBINARY field.
ACTION Refer to the chapter "Data Types" in the
ALLBASE/SQL Reference Manual for proper syntax.
----------------------------------------------------------------------------
1067 MESSAGE Invalid location name. (DBERR 1067)
CAUSE You attempted to enter a location name longer than
35 characters.
ACTION Replace the location name with one under the
maximum length and reissue the statement.
----------------------------------------------------------------------------
1068 MESSAGE DEFAULT clause is not allowed for LONG data type
column. (DBERR 1068)
CAUSE You specified a DEFAULT clause for a column which
is defined as LONG data type.
ACTION Remove the DEFAULT clause.
----------------------------------------------------------------------------
1069 MESSAGE RECOVER option is not supported in START DBE
command. (DBERR 1069)
CAUSE The START DBE RECOVER command is no longer
available.
ACTION No action necessary. Refer to the ALLBASE/SQL
Database Administration Guide for information on
recovery.
----------------------------------------------------------------------------
1071 MESSAGE Syntax combination of dynamic parameter and host
variable disallowed. (DBERR 1071)
CAUSE You used both a dynamic parameter and a host
variable in the statement.
ACTION Modify your statement to contain only dynamic
parameters or only host variables.
----------------------------------------------------------------------------
1072 MESSAGE Dynamic parameter is allowed in the PREPARE
command only. (DBERR 1072)
CAUSE You used a dynamic parameter in a statement that
has not been prepared.
ACTION Either prepare the statement using the PREPARE
statement or remove the dynamic parameters from the
statement.
----------------------------------------------------------------------------
1073 MESSAGE Dynamic parameter as the argument of an aggregate
function disallowed. (DBERR 1073)
CAUSE You used a dynamic parameter as the argument of an
aggregate function.
ACTION Modify your statement to not use a dynamic
parameter as the argument of an aggregate function.
----------------------------------------------------------------------------
1074 MESSAGE Two log files specified without DUAL LOG. (DBERR
1074)
CAUSE You have specified two log files without also
specifying DUAL LOG.
ACTION Remove one of the log file specifications or
specify DUAL LOG.
----------------------------------------------------------------------------
1075 MESSAGE TID function cannot be used in a HAVING clause.
(DBERR 1075)
CAUSE You cannot specify the TID function in a HAVING
clause.
ACTION Check and modify the command.
----------------------------------------------------------------------------
1076 MESSAGE TID function cannot be used along with aggregate
function in the SELECT list. (DBERR 1076)
CAUSE You cannot specify the TID function with an
aggregate function in t he select list.
ACTION Check and modify the command.
----------------------------------------------------------------------------
1077 MESSAGE HP SQL internal error in SPALEXI. (DBERR 1077)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP service representative or Response Center.
----------------------------------------------------------------------------
1078 MESSAGE HP/SQL internal error in SLNPRE. (DBERR 1078)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP service representative or Response Center.
----------------------------------------------------------------------------
1079 MESSAGE HP/SQL internal error in SLNMAIN. (DBERR 1079)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP service representative or Response Center.
----------------------------------------------------------------------------
1080 MESSAGE Duplicate DEFAULT PARTITION clause defined.
(DBERR 1080)
CAUSE More than one DEFAULT PARTITION clause appears in
the START DBE NEW or START DBE NEWLOG clause.
ACTION Check the specified START DBE statement.
----------------------------------------------------------------------------