 |
» |
|
|
|
|  |  |
- 1012
- MESSAGE
Duplicate TRANSACTION clause defined. (DBERR 1012) - CAUSE
You specified the transaction clause twice in the
START DBE NEW, START DBE, START DBE NEWLOG, or START DBE RECOVER
command. - ACTION
Issue the command again, specifying the transaction clause
only once. Refer to the ALLBASE/SQL Reference Manual for
additional information on the specific command.
- 1013
- MESSAGE
Duplicate BUFFER clause defined. (DBERR 1013) - CAUSE
You specified the BUFFER clause twice in the START DBE
NEW, START DBE, START DBE NEWLOG, or START DBE RECOVER command. - ACTION
Issue the command again, specifying the BUFFER clause only
once. Refer to the ALLBASE/SQL Reference Manual for
additional information on the specific command.
- 1014
- MESSAGE
Statement is not supported yet. (DBERR 1014) - CAUSE
The statement you specified is not supported by ALLBASE/SQL. - ACTION
Refer to the ALLBASE/ISQL Reference Manual and
the ALLBASE/SQL Reference Manual for descriptions
of available commands.
- 1015
- MESSAGE
Invalid file name. (DBERR 1015) - CAUSE
The file name you specified in the CREATE DBEFILE
or START DBE statement is too long. - ACTION
Refer to A Beginner's Guide to HP-UX for
file naming conventions.
- 1016
- MESSAGE
Owner id too long. (DBERR 1016) - CAUSE
The owner name you specified in the command(s) exceeds the
20-character maximum allowed for basic names. - ACTION
Issue the command again, specifying a valid owner
name. Refer to the ALLBASE/SQL Reference Manual for naming
conventions.
- 1017
- MESSAGE
Column number for ORDER BY must be greater than 0. (DBERR 1017) - CAUSE
The column number in the ORDER BY clause was less than
or equal zero. The SELECT statement was aborted. - ACTION
Issue the SELECT statement again, specifying a column number
greater than zero.
- 1018
- MESSAGE
Aggregate functions not allowed in the WHERE clause. (DBERR 1018) - CAUSE
You specified an aggregate function in the WHERE
clause of the query. - ACTION
Move the boolean expression using the aggregate
from the WHERE clause to the HAVING clause. Refer to the ALLBASE/SQL
Reference Manual for additional information on aggregates.
- 1019
- MESSAGE
Parameters not supported yet. (DBERR 1019) - CAUSE
You included a clause which is not valid for the
specified command. - ACTION
Refer to the ALLBASE/SQL Reference Manual for additional
information on the specified command.
- 1020
- MESSAGE
Statement not allowed in PREPARE statement. (DBERR 1020) - CAUSE
You included a statement in the PREPARE statement which
is not valid. - ACTION
Refer to the ALLBASE/SQL Reference Manual for additional
information on the PREPARE statement.
- 1021
- MESSAGE
Semantic error. (DBERR 1021) - CAUSE
You included a clause which is not valid for the
specified statement. - ACTION
Refer to the ALLBASE/SQL Reference Manual for additional
information on the statement.
- 1022
- MESSAGE
Constant number is out of representable range. (DBERR 1022) - CAUSE
The constant you gave in an INSERT statement or
as part of an expression is too large. - ACTION
Refer to the ALLBASE/SQL Reference Manual for additional
information on data data types.
- 1023
- MESSAGE
Duplicate tables in the FROM list. (DBERR 1023) - CAUSE
You specified the same table twice in the FROM clause
of the statement. The statement was not executed. - ACTION
Issue the SELECT statement again, specifying each
table only once. Refer to the ALLBASE/SQL Reference Manual for
additional information on the SELECT statement.
- 1024
- MESSAGE
Table in expression not in FROM list. (DBERR 1024) - CAUSE
You used a column from a table in an expression,
but you did not include the table in the FROM clause. - ACTION
Issue the SELECT statement again adding the specified table
to the FROM list or remove the expression referencing the table
before executing the command again. Refer to the ALLBASE/SQL
Reference Manual for additional information on the SELECT
statement.
- 1025
- MESSAGE
Number of columns does not match number of values. (DBERR 1025) - CAUSE
The number of columns you specified in an INSERT statement
does not match the number of values in the VALUES clause. - ACTION
Issue the INSERT statement again, specifying the
same value in the VALUES clause and the number of columns specified.
Refer to the ALLBASE/SQL Reference Manual for
additional information on the INSERT statement.
- 1026
- MESSAGE
Numeric value too long. (DBERR 1026) - CAUSE
You attempted to enter a TID field greater than
80 digits long. - ACTION
Shorten any TID field greater than 80 digits and
reissue the statement.
- 1027
- MESSAGE
Float precision specified not in valid range. (DBERR 1027) - CAUSE
You specified a precision outside the range 1 -
53 in a column defined to be of type FLOAT(precision). - ACTION
Check your syntax and reissue the command with a
legal precision value.
- 1028
- MESSAGE
UPDATE not allowed with ORDER BY. (DBERR 1028) - CAUSE
You specified both an UPDATE clause and an ORDER
BY clause in the DECLARE CURSOR statement. - ACTION
Modify the command specifying either an UPDATE clause or
an ORDER BY clause, but not both. Refer to the ALLBASE/SQL
Reference Manual for additional information on the DECLARE
CURSOR statement.
- 1030
- MESSAGE
Host variables not allowed in CREATE VIEW. (DBERR 1030) - CAUSE
You specified a host variable in the SELECT statement
of the VIEW command. - ACTION
Remove the host variable from the command. Refer
to the ALLBASE/SQL Reference Manual for additional information
on the CREATE VIEW command and to the appropriate ALLBASE/SQL application
programming guide for additional information on host variables.
- 1031
- MESSAGE
Host variables not allowed in the command to be PREPAREd. (DBERR 1031) - CAUSE
You specified a host variable in the PREPARE statement. - ACTION
Remove the host variable and issue the command again. Refer
the ALLBASE/SQL Reference Manual for additional
information on the PREPARE statement and to the appropriate ALLBASE/SQL
application programming guide for additional information on host
variables.
- 1032
- MESSAGE
Aggregate function can not be nested. (DBERR 1032) - CAUSE
The aggregate function you specified in the SELECT statement
contained an aggregate function. - ACTION
Issue the command again without nesting aggregate functions.
Refer to the ALLBASE/SQL Reference Manual for
additional information on the SELECT statement.
- 1038
- MESSAGE
Two log and file names needed if DUAL LOG. (DBERR 1038) - CAUSE
You specified only one log name and/or file name
in the START DBE NEW or you specified a START DBE NEWLOG statement
and DUAL LOG in the LOG clause. - ACTION
Issue the command again, specifying two log and
file names. Refer to the ALLBASE/SQL Reference Manual for additional
information on the START DBE NEW and START DBE NEWLOG statements.
- 1039
- MESSAGE
Number of columns must match number of host variables
or dynamic parameters. (DBERR 1039) - CAUSE
The number of host variables did not match the number
of columns or dynamic parameters in the INSERT statement. - ACTION
Revise your program to modify the host variable declarations
and/or the INSERT statement references to host variables. Refer
to the ALLBASE/SQL Reference Manual for additional
information on the INSERT statement.
- 1040
- MESSAGE
User id is too long. (DBERR 1040) - CAUSE
The length of the DBEUserID you specified was not
within the range of 1 through 20 bytes. - ACTION
Issue the command again, specifying a valid DBEUserID.
- 1041
- MESSAGE
Duplicate type of authority specified. (DBERR 1041) - CAUSE
You specified the same type of authority twice in
either the GRANT or REVOKE statement. - ACTION
Issue the command again, specifying each type of authority
only once.
- 1042
- MESSAGE
Duplicate columns specified. (DBERR 1042) - CAUSE
The same column was specified twice in the UPDATE option
of either the GRANT or REVOKE statement. - ACTION
Issue the command again, specifying each column
only once.
- 1043
- MESSAGE
Column names required. (DBERR 1043) - CAUSE
You did not specify column names in the CREATE VIEW statement. - ACTION
Issue the command again, specifying the column names
in parentheses. Refer to the ALLBASE/SQL Reference Manual for
additional information on the CREATE VIEW statement.
- 1044
- MESSAGE
Scale must not be larger than precision. (DBERR 1044) - CAUSE
The number of decimal places (scale) was greater
than the the number of digits (precision) specified in the CREATE TABLE
statement. - ACTION
Issue the command again, specifying the scale as
less than or equal to precision.
- 1045
- MESSAGE
DUAL LOG specified multiple times. (DBERR 1045) - CAUSE
The DUAL LOG option was specified more than once
in the START DBE NEW or START DBE NEWLOG statement. - ACTION
Issue the command again, specifying DUAL LOG only once.
Refer to the ALLBASE/SQL Reference Manual for additional
information.
- 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
The location name specified in the CREATE TEMPSPACE statement
is too long. - ACTION
Refer to A Beginner's Guide to HP-UX for file naming conventions.
- 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.
- 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.
- 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.
- 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.
- 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.
- 1124
- MESSAGE
Element in Boolean expression is not allowed in current
procedure statement. (DBERR 1124) - CAUSE
The following elements are not allowed in the
Condition of IF and WHILE statements in a procedure: aggregate functions,
TID functions, long column functions, column references, DATETIME
conversion functions involving columns references, and subquery
expressions. - ACTION
Rewrite your CREATE PROCEDURE statement, eliminating
the illegal elements from the Condition.
- 1125
- MESSAGE
Undefined parameter, local variable
or cursor. (DBERR 1125) - CAUSE
The parameter, variable, or cursor is referenced
inside a procedure without first being defined. - ACTION
Define the parameter, local variable, or cursor
before referencing it in the CREATE PROCEDURE statement.
- 1126
- MESSAGE
Doubly defined parameter, local variable or cursor.
(DBERR 1126) - CAUSE
You defined the parameter, local variable, or cursor
more than once. - ACTION
Check your parameter list, local variable declaration,
or cursor definition and reissue the CREATE PROCEDURE statement.
- 1127
- MESSAGE
Built-in-variable is not allowed in an SQL statement.
(DBERR 1127) - CAUSE
You used a built-in variable in an SQL statement.
Built-in variables can only be used in non-SQL statements inside
a procedure. - ACTION
Check the expressions in the procedure's SQL statements, and
reissue the CREATE PROCEDURE statement.
- 1128
- MESSAGE
A local variable or parameter is required for this
SQL statement in a stored procedure. (DBERR 1128) - CAUSE
You used the SELECT, FETCH, or REFETCH statement inside
a procedure without specifying a local variable or parameter. - ACTION
Reissue the CREATE PROCEDURE statement including the
appropriate local variable or parameter along with the SELECT, FETCH,
or REFETCH.
- 1129
- MESSAGE
OUTPUT option is allowed only for host variables
in EXECUTE PROCEDURE. (DBERR 1129) - CAUSE
You attempted to use the OUTPUT option without specifying
a host variable in the EXECUTE PROCEDURE statement in an application
program. - ACTION
Check the actual parameters of your EXECUTE PROCEDURE
statement and eliminate the illegal use of the OUTPUT option.
- 1130
- MESSAGE
The LONG data type is not allowed for a parameter or
local variable in a stored procedure. (DBERR 1130) - CAUSE
You attempted to declare a parameter or local variable with
the LONG data type in the CREATE PROCEDURE statement. - ACTION
Reissue the CREATE PROCEDURE statement without the
LONG parameter or variable declaration.
- 1131
- MESSAGE
No LABEL is allowed for this procedure statement.
(DBERR 1131) - CAUSE
No label is allowed in the DECLARE Variable statement, the WHENEVER statement, or compound statements. - ACTION
Remove the illegal label and reissue the CREATE PROCEDURE
statement.
- 1132
- MESSAGE
Cursor name must be a single identifier. (DBERR 1132) - CAUSE
You attempted to qualify a cursor name with an owner
or module name. - ACTION
Delete the cursor name qualification in the specified statement
and reissue the CREATE PROCEDURE statement.
- 1133
- MESSAGE
No INTO clause is allowed in the SELECT statement of
a DECLARE CURSOR. (DBERR 1133) - CAUSE
You attempted to use an INTO clause inside a cursor declaration
in a procedure. - ACTION
Check the SELECT portion of your DECLARE CURSOR statement
to make sure there is no INTO clause, and reissue the CREATE PROCEDURE
statement. Use the INTO clause in the FETCH statement.
- 1134
- MESSAGE
Local variable data type is invalid. (DBERR 1134) - CAUSE
You attempted to use a non-integer local variable
or parameter in a SAVEPOINT, ROLLBACK WORK TO SAVEPOINT, or SET
TIMEOUT statement in a procedure. - ACTION
Correct the data type for the local variable or
parameter and reissue the CREATE PROCEDURE statement.
- 1135
- MESSAGE
A local variable/host variable is not allowed in an
inner query block. (DBERR 1135) - CAUSE
You attempted to use a local or host variable in
a nested query block or in any query block in a UNION other than the
first UNION block. - ACTION
Remove the illegal variable reference in the query.
- 1136
- MESSAGE
The number of parameters defined exceeds the maximum of
255. (DBERR 1136) - CAUSE
You attempted to specify more than the maximum of
255 parameters in a CREATE PROCEDURE or EXECUTE PROCEDURE statement. - ACTION
Reissue the CREATE PROCEDURE or EXECUTE PROCEDURE
statement using 255 or fewer parameters.
- 1137
- MESSAGE
The expression in a variable or parameter assignment
statement contains an element that is not allowed in a
stored procedure. (DBERR 1137) - CAUSE
You used one of the following elements, which are
not allowed in the expression of an assignment statement in a procedure:
column reference, subquery, dynamic parameter, aggregate function,
TID function, long column function, or date/time conversion function
involving a column reference. - ACTION
Reissue the CREATE PROCEDURE statement , eliminating
the illegal elements from the expression.
- 1138
- MESSAGE
The expression in an actual parameter
contains an element that is not allowed
in the EXECUTE PROCEDURE statement. (DBERR 1138) - CAUSE
The following elements are not allowed in an expression
in an actual parameter in the EXECUTE PROCEDURE statement: column
reference, subquery, dynamic parameter, aggregate function, TID
function, long column function, or date/time conversion function
involving a column reference. - ACTION
Rewrite your EXECUTE PROCEDURE statement, eliminating
the illegal element from the expression in the actual parameter.
- 1139
- MESSAGE
The OUTPUT option is not allowed for parameters that
contain an expression in the EXECUTE PROCEDURE statement.
(DBERR 1139) - CAUSE
You attempted to use the OUTPUT option with a parameter
that contains an expression in an EXECUTE PROCEDURE statement within
an application program. - ACTION
Check the actual parameters of your EXECUTE PROCEDURE
statement and eliminate the illegal use of the OUTPUT option.
- 1140
- MESSAGE
The language clause is not valid with a non-character
parameter or variable in the CREATE PROCEDURE statement.
(DBERR 1140) - CAUSE
You specified a language for a parameter, variable,
or result of a non-character data type in a CREATE PROCEDURE statement. - ACTION
Reissue the CREATE PROCEDURE statement, omitting the
language clause for any parameter, variable, or result of a non-character
data type.
- 1141
- MESSAGE
No value was provided for a named list parameter in the
EXECUTE PROCEDURE statement. (DBERR 1141) - CAUSE
You specified the name of a parameter in a named parameter
list, but you did not specify a value for the parameter. - ACTION
Check the parameter list included in the EXECUTE PROCEDURE
statement, and ensure that you supply a value for each parameter.
Then reissue the EXECUTE PROCEDURE statement.
- 1142
- MESSAGE
Named list and ordered list parameters cannot be mixed in
the EXECUTE PROCEDURE statement. (DBERR 1142) - CAUSE
You specified one or more named parameters together
with one or more ordered parameters in the same EXECUTE PROCEDURE
statement. A parameter list must be either an ordered list or a
named list and cannot mix parameters of both types. - ACTION
Check the parameter list included in the EXECUTE PROCEDURE
statement, and ensure that you use a consistent parameter type in
the parameter list. Then reissue the EXECUTE PROCEDURE statement.
- 1143
- MESSAGE
Multiple values provided for single parameter in the
EXECUTE PROCEDURE statement. (DBERR 1143) - CAUSE
You used the same parameter name more than once
in a named parameter list in the EXECUTE PROCEDURE statement. - ACTION
Correct the EXECUTE PROCEDURE statement, making sure
that each parameter name is assigned only one value. Then reissue
the EXECUTE PROCEDURE statement.
- 1144
- MESSAGE
The number of result columns defined exceeds the maximum
num of 1024. (DBERR 1144) - CAUSE
You specified more that 1024 result columns in a
CREATE PROCEDURE statement. - ACTION
Reissue the CREATE PROCEDURE statement, specifying no
more than 1024 result columns.
- 1145
- MESSAGE
Dynamic parameters are not allowed in procedure statements.
(DBERR 1145) - CAUSE
You included a dynamic parameter in a statement
inside a parameter. - ACTION
Reissue the CREATE PROCEDURE statement, omitting any
dynamic parameter.
- 1146
- MESSAGE
The WITH RESULT clause is allowed only for a procedure
returning results. (DBERR 1146) - CAUSE
You included the WITH RESULT clause in a CREATE PROCEDURE
statement, but the procedure returns no result sets. - ACTION
Reissue the CREATE PROCEDURE statement, omitting the
WITH RESULT clause.
- 1147
- MESSAGE
DEFAULT clause is not allowed for an OUTPUT ONLY parameter.
(DBERR 1147) - CAUSE
You provided a default value for an OUTPUT ONLY parameter
in the CREATE PROCEDURE statement. - ACTION
Reissue the CREATE PROCEDURE statement, either omitting
the default value, or specifying OUTPUT rather than OUTPUT ONLY.
- 1150
- MESSAGE
Host variables not allowed in CREATE RULE. (DBERR 1150) - CAUSE
You defined a RULE containing a host variable. - ACTION
Check the syntax and remove the host variable from
your CREATE RULE statement.
- 1151
- MESSAGE
Duplicate statement type
specified in CREATE RULE. (DBERR 1151) - CAUSE
You defined a RULE with duplicate statement types. - ACTION
Check the syntax and remove the duplicate statement type
from your CREATE RULE statement.
- 1152
- MESSAGE
TID function disallowed in
CHECK constraint or RULE. (DBERR 1152) - CAUSE
A RULE or CHECK constraint contains a TID function. - ACTION
Check the syntax and remove the TID function from
your CREATE RULE statement or CHECK constraint.
- 1153
- MESSAGE
RETURN clause not permitted in EXECUTE PROCEDURE of
CREATE RULE. (DBERR 1153) - CAUSE
You included a RETURN clause in the EXEC PROCEDURE
clause of a CREATE RULE statement. - ACTION
Remove the RETURN clause from the EXEC PROCEDURE
clause.
- 1154
- MESSAGE
OUTPUT parameters not permitted in EXECUTE PROCEDURE of
CREATE RULE. (DBERR 1154) - CAUSE
You included a parameter defined for OUTPUT in the EXECUTE
PROCEDURE clause of a CREATE RULE statement. - ACTION
Remove the key word OUTPUT from the EXECUTE PROCEDURE
clause.
- 1155
- MESSAGE
Negative Hexstring is not allowed. (DBERR 1155) - CAUSE
You attempted to enter a negative hexstring. - ACTION
Remove the minus sign from the hexstring and reissue
the statement.
- 1156
- MESSAGE
Duplicate ISOLATION LEVEL clause defined. (DBERR 1156) - CAUSE
You have more than one IDOLATION LEVEL clause in the
SET TRANSACTION or SET SESSION statement. - ACTION
Check the specified SET TRANSACTION or SET SESSION
statement.
- 1157
- MESSAGE
Duplicate PRIORITY clause defined. (DBERR 1157) - CAUSE
You specified the PRIORITY clause more than once
in the SET TRANSACTION or SET SESSION statement. - ACTION
Check the specified SET TRANSACTION or SET SESSION
statement.
- 1158
- MESSAGE
Duplicate LABEL clause defined. (DBERR 1158) - CAUSE
You included more than one LABEL clause in the SET TRANSACTION
or SET SESSION statement. - ACTION
Check the specified SET TRANSACTION or SET SESSION
statement.
- 1159
- MESSAGE
Duplicate CONSTRAINTS clause defined. (DBERR 1159) - CAUSE
You included more than one CONSTRAINTS clause in
the SET TRANSACTION or SET SESSION statement. - ACTION
Check the specified SET TRANSACTION or SET SESSION
statement.
- 1160
- MESSAGE
Duplicate DML ATOMICITY clause defined. (DBERR 1160) - CAUSE
You included more than one DML ATOMICITY clause
in the SET TRANSACTION or SET SESSION statement. - ACTION
Check the specified SET TRANSACTION or SET SESSION
statement.
- 1161
- MESSAGE
Duplicate FILL clause defined. (DBERR 1161) - CAUSE
You included more than one FILL clause in the SET SESSION
statement. - ACTION
Check the specified SET SESSION statement.
- 1163
- MESSAGE
Device name specified exceed 44 characters.
(DBERR 1163) - CAUSE
The device name in the CREATE DBEFILE command is too
long. - ACTION
Correct the device specification and reissue the
CREATE DBEFile command.
- 1164
- MESSAGE
The [NOT] CASE SENSITIVE attribute is not applicable on
non-character column. (DBERR 1164) - CAUSE
You applied a CASE SENSITIVE or NOT CASE SENSITIVE
keyword to a column which is not defined as a character column. - ACTION
Avoid applying CASE SENSITIVE or NOT CASE SENSITIVE
keywords to non-character columns.
- 1165
- MESSAGE
Duplicate USER TIMEOUT clause defined. (DBERR 1165) - CAUSE
A duplicate USER TIMEOUT clause was specified. - ACTION
No action required. The duplicate USER TIMEOUT clause will
be ignored.
- 1166
- MESSAGE
Duplicate on TIMEOUT/DEADLOCK clause defined. (DBERR 1166) - CAUSE
A duplicate TIMEOUT/DEADLOCK clause was specified. - ACTION
No action required. The duplicate TIMEOUT/DEADLOCK clause
will be ignored.
- 1167
- MESSAGE
Duplicate TERMINATION clause defined. (DBERR 1167) - CAUSE
A duplicate TERMINATION clause was specified. - ACTION
No action required. The duplicate TERMINATION clause will
be ignored.
- 1168
- MESSAGE
Table name required. (DBERR 1168) - CAUSE
You issued a RENAME TABLE statement without a valid table
name. - ACTION
See syntax for RENAME TABLE in "SQL Statements" chapter
of the ALLBASE/SQL Reference Manual.
- 1169
- MESSAGE
Data type ! not allowed for CAST. (DBERR 1169) - CAUSE
An incorrect data type was specified for CAST. - ACTION
See the table, "Data Types for CAST Function," in
the "Expressions" chapter of the ALLBASE/SQL Reference Manual.
- 1170
- MESSAGE
Format specification is only allowed for date/time data types. (DBERR 1170) - CAUSE
An incorrect format was specified. - ACTION
See the "Expressions" chapter of the ALLBASE/SQL Reference
Manual for the correct syntax.
- 1171
- MESSAGE
Expression may not contain table or column reference. (DBERR 1171) - CAUSE
An incorrect syntax was specified for the expression. - ACTION
See the "Expressions" chapter of the ALLBASE/SQL Reference
Manual for the correct syntax.
- 1600
- MESSAGE
Unidentified DBECON utility error. (RC !, !, !, !) (DBERR 1600) - CAUSE
An unexpected error was encountered. - ACTION
Record as much information as possible and contact
your HP Service Representative or Response Center.
- 1601
- MESSAGE
Cannot open DBECON file. (! !, RC !, !, !) (DBERR 1601) - CAUSE
A file system error was encountered. - ACTION
Check the spelling of the DBEnvironmentName in the
last command that was issued. Refer to the /usr/include/sys/errno.h file for an error
description.
- 1602
- MESSAGE
Cannot close DBECON file. (! !, RC !, !, !) (DBERR 1602) - CAUSE
A file system error was encountered. - ACTION
Refer to the /usr/include/sys/errno.h file for an error description.
- 1603
- MESSAGE
Cannot read DBECON file. (! !, RC !, !, !) (DBERR 1603) - CAUSE
A file system error was encountered. - ACTION
Refer to the /usr/include/sys/errno.h file for an error description.
- 1604
- MESSAGE
Cannot update DBECON file. (! !, RC !, !, !) (DBERR 1604) - CAUSE
A file system error was encountered. - ACTION
Refer to the /usr/include/sys/errno.h file for an error description.
- 1605
- MESSAGE
Cannot store DBECON file. (! !, RC !, !, !) (DBERR 1605) - CAUSE
A file system error was encountered. - ACTION
Refer to the /usr/include/sys/errno.h filefor an error description.
- 1606
- MESSAGE
DBCore INTERNAL error. (FNC !, RC !, ! !, !, !) (DBERR 1606) - CAUSE
An unexpected error was encountered. - ACTION
Record as much information as possible and contact
your HP Service Representative or Response Center.
- 1607
- MESSAGE
Cannot open database or log file. (! !, RC !, !, !)
(DBERR 1607) - CAUSE
A file system error was encountered. - ACTION
Refer to the /usr/include/sys/errno.h file for an error description.
- 1608
- MESSAGE
Cannot update database or log file. (! !, RC !, !, !)
(DBERR 1608) - CAUSE
A file system error was encountered. - ACTION
Refer to the /usr/include/sys/errno.h file for an error description.
- 1609
- MESSAGE
Cannot close database or log file. (! !, RC !, !, !)
(DBERR 1609) - CAUSE
A file system error was encountered. - ACTION
Refer to the /usr/include/sys/errno.h file for an error description.
- 1610
- MESSAGE
Cannot purge database or log file. (! !, RC !, !, !)
(DBERR 1610) - CAUSE
A file system error was encountered. - ACTION
Refer to the /usr/include/sys/errno.h file for an error description.
- 1621
- MESSAGE
Invalid DBECON file. Record length too small. (RC !, !, !, !)
(DBERR 1621) - CAUSE
The file specified is not a DBECON file. - ACTION
Check your spelling. Issue the command again, specifying a
valid DBECON file.
- 1622
- MESSAGE
Invalid DBECON file. Bad Brand. (RC !, !, !, !) (DBERR 1622) - CAUSE
The file specified is not a DBECON file. - ACTION
Check your spelling. Issue the command again, specifying a
valid DBECON file.
- 1623
- MESSAGE
DBEnvironment already exists. (RC !, !, !, !) (DBERR 1623) - CAUSE
You attempted to RESTORE a backup copy of a DBEnvironment,
but it already exists on your system. - ACTION
You must purge all files associated with the DBEnvironment
before RESTORE will successfully execute.
- 1624
- MESSAGE
DBE on StoreFile doesn't match RESTORE parameter.
(RC !, !, !, !)
(DBERR 1624) - CAUSE
You attempted to RESTORE a backup copy of a DBEnvironment,
but the name of the DBEnvironment that is contained on the backup
is not the same as the name of the DBEnvironment that you were attempting
to restore. - ACTION
Issue the command again, specifying the correct
StoreFile and DBEnvironment names.
- 1625
- MESSAGE
Null or invalid StoreFile name. (RC !, !, !, !)
(DBERR 1625) - CAUSE
You attempted to either RESTORE a backup copy of
a DBEnvironment or RESTORELOG a backup copy of a log file, but you
provided an invalid name for the file or tape device containing
the backup. - ACTION
Check your spelling. Issue the command again, specifying a
valid StoreFileName.
- 1626
- MESSAGE
Security Violation. (RC !, !, !, !) (DBERR 1626) - CAUSE
You do not have the required capability for the
operation that was attempted. - ACTION
Refer to the ALLBASE/SQL Reference Manual or the ALLBASE/SQL
Database Administration Guide for information about the capability
that is required for the operation.
- 1627
- MESSAGE
Cannot update DBEnvironment Creator Id. (RC !, !, !, !) (DBERR 1627) - CAUSE
You attempted a command that may only be executed
by the superuser. - ACTION
Issue the command again as the superuser.
- 1628
- MESSAGE
DBEnvironment Creator Id is not in /etc/passwd.
(RC !, !, !, !) (DBERR 1628) - CAUSE
You probably moved a DBEnvironment from one system
to another without using the SQLUtil STORE and RESTORE commands,
or you used the RESTORE command but you were not superuser. - ACTION
You may do either of the following: RESTORE the DBEnvironment as the superuser, specifying
a valid NEW DBECreator Name at the appropriate prompt, or Use the SQLMigrate SHOW "DBEnvironmentName" VERSION
command to determine the Creator Id. Contact your system administrator
to add an entry to the /etc/passwd file using this uid.
- 1629
- MESSAGE
Internal Error. Buffer too small. (RC !, !, !, !)
(DBERR 1629) - CAUSE
An unexpected error was encountered. - ACTION
Record as much information as possible and contact
your HP Service Representative or Response Center.
- 1640
- MESSAGE
SystemFileName could not be CREATED (! !). (DBERR 1640) - CAUSE
A file system error was encountered. - ACTION
Refer to the /usr/include/sys/errno.h file for an
error description.
- 1680
- MESSAGE
NLS routine failed. (!, !, !, !) (DBERR 1680) - CAUSE
An unexpected error occurred while using an internal native
language procedure. - ACTION
Record as much information as possible and contact
your HP Service Representative or Response Center.
- 1682
- MESSAGE
Cannot open message catalog (!). (DBERR 1682) - CAUSE
An unexpected error was encountered when trying
to open the ALLBASE/SQL message catalog. It probably does not exist. - ACTION
Contact your system administrator.
- 1683
- MESSAGE
Message catalog read error. (set !, msg !, !)
(DBERR 1683) - CAUSE
An unexpected error was encountered when trying
to find a message in the ALLBASE/SQL message catalog. - ACTION
Record as much information as possible and contact
your HP Service Representative or Response Center.
- 1684
- MESSAGE
Cannot close message catalog (!). (DBERR 1684) - CAUSE
An unexpected error was encountered when trying
to close the ALLBASE/SQL message catalog. - ACTION
Contact your system administrator.
- 1685
- MESSAGE
Failed loading keyword (!). (DBERR 1685) - CAUSE
An unexpected error occurred while trying to obtain information
from the ALLBASE/SQL message catalog. The version of the message
catalog is probably incompatible with the version of the program. - ACTION
Contact your system administrator.
- 1686
- MESSAGE
Failed to determine minimum uniqueness of keywords (!).
(DBERR 1686) - CAUSE
An unexpected error occurred while trying to obtain information
from the ALLBASE/SQL message catalog. The version of the message
catalog is probably incompatible with the version of the program. - ACTION
Contact your system administrator.
- 1687
- MESSAGE
Failed to obtain string constant (set !, msg !, !).
(DBERR 1687) - CAUSE
An unexpected error occurred while trying to obtain information
from the ALLBASE/SQL message catalog. The version of the message
catalog is probably incompatible with the version of the program. - ACTION
Contact your system administrator.
- 1813
- MESSAGE
The statement is not valid in SETOPT. (DBERR 1813) - CAUSE
The statement is not supported with SETOPT. - ACTION
Do not use the statement in SETOPT.
- 1814
- MESSAGE
Conflict ! statements or conflict conditions on !
statement occur in SETOPT statement. (DBERR 1814) - CAUSE
! statements or conditions on ! statement in SETOPT
are conflicting. - ACTION
Remove incorrect ! statement or incorrect conditions
from ACCESS statement and reexecute SETOPT and the query.
- 1815
- MESSAGE
WITH clause of GENPLAN is not allowed in the GENPLAN on a
section. (DBERR 1815) - CAUSE
You tried to specify a GENPLAN on a section with
a WITH clause. - ACTION
Remove WITH clause from GENPLAN statement.
- 2032
- MESSAGE
Cannot use WITH AUTOCOMMIT if rule enabled. (DBERR 2032) - CAUSE
WITH AUTOCOMMIT was used incorrectly. - ACTION
See the DELETE or VALIDATE statement in the "SQL Statements"
chapter of the ALLBASE/SQL Reference Manual.
- 2033
- MESSAGE
Cannot use WITH AUTOCOMMIT inside atomic block. (DBERR 2033) - CAUSE
WITH AUTOCOMMIT was used incorrectly. - ACTION
See the DELETE or VALIDATE statement in the "SQL Statements"
chapter of the ALLBASE/SQL Reference Manual.
- 2034
- MESSAGE
Cannot use WITH AUTOCOMMIT inside global transaction. (DBERR 2034) - CAUSE
WITH AUTOCOMMIT was used incorrectly. - ACTION
See the DELETE or VALIDATE statement in the "SQL Statements"
chapter of the ALLBASE/SQL Reference Manual.
- 2035
- MESSAGE
Cannot use WITH AUTOCOMMIT if constraints are deferred. (DBERR 2035) - CAUSE
WITH AUTOCOMMIT was used incorrectly. - ACTION
See the DELETE or VALIDATE statement in the "SQL Statements"
chapter of the ALLBASE/SQL Reference Manual.
- 2100
- MESSAGE
ALLBASE/SQL not running. (DBERR 2100) - CAUSE
An SQL statement was issued before a DBE session
was started. - ACTION
Start a DBE session with the CONNECT or START DBE statement,
then issue the SQL statement again.
- 2101
- MESSAGE
ALLBASE/SQL already started. (DBERR 2101) - CAUSE
A START DBE or CONNECT statement was entered after a
DBE session was already started. - ACTION
No action is necessary.
- 2102
- MESSAGE
Command requires a transaction to be in progress. (DBERR 2102) - CAUSE
A COMMIT WORK or ROLLBACK WORK statement was issued
before a transaction was started. - ACTION
No action is necessary. To begin a transaction,
issue a BEGIN WORK statement.
- 2103
- MESSAGE
Transaction already started. (DBERR 2103) - CAUSE
You attempted to start a second transaction before
the current transaction was committed. - ACTION
Issue a COMMIT WORK or ROLLBACK WORK statement to
terminate the previous transaction, then issue a BEGIN WORK statement
to start the next transaction.
- 2105
- MESSAGE
Specified DBEnvironment already exists. (DBERR 2105) - CAUSE
You tried to create a DBEnvironment that already
exists. - ACTION
Issue the START DBE NEW statement again, specifying
a unique name.
- 2106
- MESSAGE
Backward migration is needed - use SQLMigrate. (DBERR 2106) - CAUSE
The release of the ALLBASE/SQL software does not
match the version of the DBEnvironment. - ACTION
Use the migration tool, SQLMigrate, to migrate the DBEnvironment
backward to the proper version or use a newer release of the ALLBASE/SQL
software.
|