HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Continued)
1081 MESSAGE Duplicate MAXPARTITIONS clause defined. (DBERR
1081)
CAUSE The keyword MAXPARTITIONS appears more than once in
the START DBE NEW or START DBE NEWLOG clause.
ACTION Check the specified START DBE statement.
----------------------------------------------------------------------------
1082 MESSAGE AUDIT LOG specified multiple times. (DBERR 1082)
CAUSE You specified the AUDIT LOG clause more than once
in the START DBE NEW or START DBE NEWLOG statement.
ACTION Check the specified START DBE statement.
----------------------------------------------------------------------------
1083 MESSAGE ARCHIVE LOG specified multiple times. (DBERR
1083)
CAUSE You specified the ARCHIVE LOG clause more than once
in the START DBE NEWLOG statement.
ACTION Check the specified START DBE statement.
----------------------------------------------------------------------------
1084 MESSAGE Duplicate AUDIT NAME clause defined. (DBERR
1084)
CAUSE You specified the AUDIT NAME clause appears more
than once in the START DBE NEW or START DBE NEWLOG
syntax.
ACTION Check the specified START DBE statement.
----------------------------------------------------------------------------
1085 MESSAGE AUDIT NAME too long. (DBERR 1085)
CAUSE You specified an AUDIT NAME longer than 8 bytes.
ACTION Check the specified START DBE statement.
----------------------------------------------------------------------------
1086 MESSAGE INCREMENT size specified not in valid range.
(DBERR 1086)
CAUSE The INCREMENT size for DBEFile expansion cannot be
zero.
ACTION Make sure the INCREMENT size is within the valid
range.
----------------------------------------------------------------------------
1088 MESSAGE Duplicate AUDIT ELEMENT specified. (DBERR 1088)
CAUSE You specified an AUDIT ELEMENT more than once in
the AUDIT ELEMENTS clause of the START DBE NEW or
START DBE NEWLOG statement.
ACTION Check the specified START DBE statement.
----------------------------------------------------------------------------
1089 MESSAGE Duplicate COMMENT PARTITION clause defined.
(DBERR 1089)
CAUSE You have more than one COMMENT PARTITION clause in
the START DBE NEW or START DBE NEWLOG statement.
ACTION Check the specified START DBE statement.
----------------------------------------------------------------------------
1090 MESSAGE Dynamic Parameters cannot be used as both the
first and the second operands in a BETWEEN
predicate. (DBERR 1090)
CAUSE You specified dynamic parameters as both the first
and the second operands in a BETWEEN predicate.
ACTION Modify your statement to not contain dynamic
parameters as both the first and second operands of
the BETWEEN predicate.
----------------------------------------------------------------------------
1091 MESSAGE TID function cannot be used as the argument of
the aggregate function. (DBERR 1091)
CAUSE You cannot use the TID function as the argument of
an aggregate function.
ACTION Check and modify the command.
----------------------------------------------------------------------------
1092 MESSAGE Duplicate constraint type specified. (DBERR
1092)
CAUSE You specified the same constraint type more than
once in a SET CONSTRAINTS statement.
ACTION Remove the duplicate constraint type(s) and reissue
the statement.
----------------------------------------------------------------------------
1093 MESSAGE Default timeout value out of valid range. (DBERR
1093)
CAUSE The default timeout value you specified is invalid.
ACTION Verify that the default timeout value is within the
valid range.
----------------------------------------------------------------------------
1094 MESSAGE Maximum timeout value out of valid range. (DBERR
1094)
CAUSE The maximum timeout value you specified is invalid.
ACTION Verify that the maximum timeout value is within the
valid range.
----------------------------------------------------------------------------
1095 MESSAGE Default timeout value exceeds maximum timeout
limit. (DBERR 1095)
CAUSE The default timeout value is greater than the
maximum timeout limit.
ACTION Set the default timeout to a value less than or
equal to the maximum timeout limit
or
set the maximum timeout limit to a value greater
than or equal to the default timeout value.
----------------------------------------------------------------------------
1096 MESSAGE DEFAULT TIMEOUT specified multiple times. (DBERR
1096)
CAUSE You specified the DEFAULT TIMEOUT clause more than
once in either the START DBE, START DBE NEW, or
STARTDBE NEWLOG statement.
ACTION Issue the statement again, specifying the DEFAULT
TIMEOUT clause only once.
----------------------------------------------------------------------------
1097 MESSAGE MAXIMUM TIMEOUT specified multiple times. (DBERR
1097).
CAUSE You specified the MAXIMUM TIMEOUT clause more than
once in either the START DBE, START DBE NEW, or
STARTDBE NEWLOG statement.
ACTION Issue the statement again, specifying the MAXIMUM
TIMEOUT clause only once.
----------------------------------------------------------------------------
1098 MESSAGE User timeout value out of valid range. (DBERR
1098)
CAUSE The specified user timeout is invalid.
ACTION Verify that the user timeout value is within the
valid range.
----------------------------------------------------------------------------
1099 MESSAGE GENPLAN accepts SELECT, UPDATE, and DELETE
statements only. (DBERR 1099)
CAUSE A SELECT, UPDATE, or DELETE statement is expected.
ACTION Issue GENPLAN for a statement of one of the above
types.
----------------------------------------------------------------------------
1100 MESSAGE VariableName in WHERE clause has not been defined
in the WITH clause of GENPLAN. (DBERR 1100)
CAUSE A VariableName in the WHERE clause of the statement
contained in GENPLAN has not been defined in the
WITH clause of the GENPLAN statement.
ACTION Add the VariableName with the appropriate data type
to the WITH clause of the GENPLAN statement.
----------------------------------------------------------------------------
1101 MESSAGE A language, default, or column constraint clause
is not allowed in the WITH clause of GENPLAN.
(DBERR 1101)
CAUSE A language, default, or column constraint clause
was found in the WITH clause of GENPLAN.
ACTION Remove the language, default, or column clause from
the WITH clause of GENPLAN.
----------------------------------------------------------------------------
1102 MESSAGE SQL Linearizer internal NLS error. (DBERR 1102)
CAUSE Internal error.
ACTION Record as much information as possible and contact
your HP Service Representative or Response Center.
----------------------------------------------------------------------------
1103 MESSAGE Duplicate VariableName found in the WITH clause
of GENPLAN. (DBERR 1103)
CAUSE The WITH clause of GENPLAN has a duplicate
VariableName.
ACTION Rename or remove the duplicate VariableName from
the WITH clause of GENPLAN.
----------------------------------------------------------------------------
1104 MESSAGE Duplicate RUN BLOCK clause defined. (DBERR 1104)
CAUSE You specified the RUN BLOCK clause twice in the
START DBE or START DBE NEW statement.
ACTION Issue the command again specifying the RUN BLOCK
clause once.
----------------------------------------------------------------------------
1105 MESSAGE USER not permitted in table CHECK constraint.
(DBERR 1105)
CAUSE You specified a CHECK constraint with USER.
ACTION Remove the use of USER in the CHECK constraint and
reissue the statement.
----------------------------------------------------------------------------
1106 MESSAGE CURRENT_DATE not permitted in table CHECK
constraint. (DBERR 1106)
CAUSE You specified a CHECK constraint with CURRENT_DATE.
ACTION Remove the use of CURRENT_DATE in the CHECK
constraint and reissue the statement.
----------------------------------------------------------------------------
1107 MESSAGE CURRENT_TIME not permitted in table CHECK
constraint. (DBERR 1107)
CAUSE You specified a CHECK constraint with CURRENT_TIME.
ACTION Remove the use of CURRENT_TIME in the CHECK
constraint and reissue the statement.
----------------------------------------------------------------------------
1108 MESSAGE CURRENT_DATETIME not permitted in table CHECK
constraint. (DBERR 1108)
CAUSE You specified a CHECK constraint with
CURRENT_DATETIME.
ACTION Remove the use of CURRENT_DATETIME in the CHECK
constraint and reissue the statement.
----------------------------------------------------------------------------
1109 MESSAGE ! PARTITION value must be non-zero. (DBERR 1109)
CAUSE You specified a DEFAULT, MAXPARTITIONS, or COMMENT
partition value of zero in the START DBE NEW or
START DBE NEWLOG statement.
ACTION Check the specified START DBE statement and replace
the zero in the named partition value with a
non-zero value.
----------------------------------------------------------------------------
[REV BEG]
1110 MESSAGE The label (!) is not an integer. (DBERR 1110)
CAUSE For PASCAL and FORTRAN 77 applications, labels must
be integers. A label was found that was not an
integer.
ACTION Change the label to an integer.
[REV END]
----------------------------------------------------------------------------
[REV BEG]
1111 MESSAGE The label (!) is not an identifier name. (DBERR
1111)
CAUSE For C and COBOL applications, labels must be
identifier names which start with non-numeric
characters. A label was found that started with a
numeric character.
ACTION Change the label to start with a non-numeric
character.
[REV END]
----------------------------------------------------------------------------
1120 MESSAGE Statement not allowed in stored procedure. (DBERR
1120)
CAUSE The current statement is not permitted within a
procedure.
ACTION Issue the CREATE PROCEDURE statement again,
omitting the illegal statement. Refer to the
description of the CREATE PROCEDURE statement in
the "SQL Statements" chapter of the ALLBASE/SQL
Reference Manual for a list of statements that are
not allowed in procedures.
----------------------------------------------------------------------------
1121 MESSAGE Local variable declarations must be at the
beginning of a stored procedure. (DBERR 1121)
CAUSE The DECLARE statement was not at the beginning of
the procedure.
ACTION Define local variables with DECLARE statements at
the beginning of the procedure.
----------------------------------------------------------------------------
1122 MESSAGE Return Status in the RETURN statement must be an
integer value. (DBERR 1122)
CAUSE The status value in the RETURN statement is not an
integer value.
ACTION Use an integer value for the ReturnStatus in the
RETURN statement.
----------------------------------------------------------------------------
1123 MESSAGE Indicator variables are not allowed with
parameters or local variables used in a stored
procedure statement. (DBERR 1123)
CAUSE You attempted to include an indicator variable with
a parameter declaration or with a local variable in
the CREATE PROCEDURE statement.
ACTION Rewrite your CREATE PROCEDURE statement,
eliminating indicator variables.
----------------------------------------------------------------------------