Chapter 4 ALLBASE/SQL Error Messages: 746-2100

Invalid Constraint Index Type encountered. (DBERR 746)

Internal Error.

Record as much information as possible and contact your HP Service Representative or Response Center.

Invalid Default Type encountered TYPE=<val> (DBERR 747)

Internal Error.

Record as much information as possible and contact your HP Service Representative or Response Center.

Invalid Constraint Type encountered. (DBERR 748)

Internal Error.

Record as much information as possible and contact your HP Service Representative or Response Center.

Syntax error. (DBERR 1001)

You entered the Command incorrectly.

Correct the syntax using the CHANGE or REDO command in ISQL, or use an editor to correct your source code. You can use the ISQL HELP command to verify your syntax.

Identifier too long. (DBERR 1002)

One of the keywords you specified in the SQL statement was too long. This was probably caused by a typographical error such as not leaving a blank space between keywords

or

one of the variable names you specified was too long.

Issue the command again correcting the keywords which were entered incorrectly

or

choose a variable name that is less than or equal to 30 bytes.

Single-quoted string too long. (DBERR 1003)

The string enclosed in single quotes in your SQL statement is too long.

Issue the command again, specifying a string which contains less than or equal to 3,996 bytes.

Expected end of string character. (DBERR 1004)

String was not terminated with a quotation mark.

Issue the command again terminating the string with a quotation mark.

Expected something between the double quotes. (DBERR 1005)

In the command where a database object was referenced, you did not specify an object name within the quotes.

Issue the command again, specifying an appropriate name within quotes.

Unexpected keyword. (DBERR 1006)

The syntax was incorrect for the command specified.

Refer to the ALLBASE/SQL Reference Manual for the correct syntax and issue the command again.

DBEnvironment name is too long. (DBERR 1007)

A DBEnvironment name is restricted to operating system file naming conventions.

Refer to the MPE/iX General User's Reference Manual for file naming conventions.

Query too large. (DBERR 1008)

The internal buffer space has been exceeded.

Break the query into smaller units and issue the command again.

Double-quoted string too long. (DBERR 1009)

The string enclosed in double quotes was too long.

Issue the command again, specifying an object name containing less than or equal to 20 bytes.

Duplicate DBEFile0 clause defined. (DBERR 1010)

You specified the DBEFile0 clause twice in the START DBE NEW statement.

Issue the START DBE NEW statement again, specifying the DBEFile0 only once. Refer to the ALLBASE/SQL Reference Manual for additional information on the START DBE NEW statement.

Duplicate LOG DBEFile clause defined. (DBERR 1011)

You specified the LOG DBEFILE clause twice in the START DBE NEW or START DBE NEWLOG statement.

Issue the command again, specifying the LOG DBEFILE only once. Refer to the ALLBASE/SQL Reference Manual for additional information on the START DBE NEW and START DBE NEWLOG statements.

Duplicate TRANSACTION clause defined. (DBERR 1012)

You specified the transaction clause twice in the START DBE NEW, START DBE, START DBE NEWLOG, or START DBE RECOVER command.

Issue the command again, specifying the transaction clause only once. Refer to the ALLBASE/SQL Reference Manual for additional information on the specific command.

Duplicate BUFFER clause defined. (DBERR 1013)

You specified the BUFFER clause twice in the START DBE NEW, START DBE, START DBE NEWLOG, or START DBE RECOVER command.

Issue the command again, specifying the BUFFER clause only once. Refer to the ALLBASE/SQL Reference Manual for additional information on the specific command.

Statement is not supported yet. (DBERR 1014)

The statement you specified is not supported by ALLBASE/SQL.

Refer to the ISQL Reference Manual for ALLBASE/SQL and IMAGE/SQL and the ALLBASE/SQL Reference Manual for descriptions of available commands.

Invalid file name. (DBERR 1015)

The file name you specified in the CREATE DBEFILE or START DBE statement is too long.

Refer to the MPE/iX General User's Reference Manual for file naming conventions.

Owner id too long. (DBERR 1016)

The owner name you specified in the command(s) exceeds the 20-character maximum allowed for basic names.

Issue the command again, specifying a valid owner name. Refer to the ALLBASE/SQL Reference Manual for naming conventions.

Column number for ORDER BY must be greater than 0. (DBERR 1017)

The column number in the ORDER BY clause was less than or equal zero. The SELECT statement was aborted.

Issue the SELECT statement again, specifying a column number greater than zero.

Aggregate functions not allowed in the WHERE clause. (DBERR 1018)

You specified an aggregate function in the WHERE clause of the query.

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.

Parameters not supported yet. (DBERR 1019)

You included a clause which is not valid for the specified command.

Refer to the ALLBASE/SQL Reference Manual for additional information on the specified command.

Statement not allowed in PREPARE statement. (DBERR 1020)

You included a statement in the PREPARE statement which is not valid.

Refer to the ALLBASE/SQL Reference Manual for additional information on the PREPARE statement.

Semantic error. (DBERR 1021)

You included a clause which is not valid for the specified statement.

Refer to the ALLBASE/SQL Reference Manual for additional information on the statement.

Constant number is out of representable range. (DBERR 1022)

The constant you gave in an INSERT statement or as part of an expression is too large.

Refer to the ALLBASE/SQL Reference Manual for additional information on data data types.

Duplicate tables in the FROM list. (DBERR 1023)

You specified the same table twice in the FROM clause of the statement. The statement was not executed.

Issue the SELECT statement again, specifying each table only once. Refer to the ALLBASE/SQL Reference Manual for additional information on the SELECT statement.

Table in expression not in FROM list. (DBERR 1024)

You used a column from a table in an expression, but you did not include the table in the FROM clause.

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.

Number of columns does not match number of values. (DBERR 1025)

The number of columns you specified in an INSERT statement does not match the number of values in the VALUES clause.

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.

Numeric value too long. (DBERR 1026)

You attempted to enter a TID field greater than 80 digits long.

Shorten any TID field greater than 80 digits and reissue the statement.

Float precision specified not in valid range. (DBERR 1027)

You specified a precision outside the range 1 - 53 in a column defined to be of type FLOAT(precision).

Check your syntax and reissue the command with a legal precision value.

UPDATE not allowed with ORDER BY. (DBERR 1028)

You specified both an UPDATE clause and an ORDER BY clause in the DECLARE CURSOR statement.

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.

Host variables not allowed in CREATE VIEW. (DBERR 1030)

You specified a host variable in the SELECT statement of the VIEW command.

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.

Host variables not allowed in the command to be PREPAREd. (DBERR 1031)

You specified a host variable in the PREPARE statement.

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.

Aggregate function can not be nested. (DBERR 1032)

The aggregate function you specified in the SELECT statement contained an aggregate function.

Issue the command again without nesting aggregate functions. Refer to the ALLBASE/SQL Reference Manual for additional information on the SELECT statement.

Two log and file names needed if DUAL LOG. (DBERR 1038)

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.

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.

Number of columns must match number of host variables or dynamic parameters. (DBERR 1039)

The number of host variables did not match the number of columns or dynamic parameters in the INSERT statement.

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.

User id is too long. (DBERR 1040)

The length of the DBEUserID you specified was not within the range of 1 through 20 bytes.

Issue the command again, specifying a valid DBEUserID.

Duplicate type of authority specified. (DBERR 1041)

You specified the same type of authority twice in either the GRANT or REVOKE statement.

Issue the command again, specifying each type of authority only once.

Duplicate columns specified. (DBERR 1042)

The same column was specified twice in the UPDATE option of either the GRANT or REVOKE statement.

Issue the command again, specifying each column only once.

Column names required. (DBERR 1043)

You did not specify column names in the CREATE VIEW statement.

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.

Scale must not be larger than precision. (DBERR 1044)

The number of decimal places (scale) was greater than the the number of digits (precision) specified in the CREATE TABLE statement.

Issue the command again, specifying the scale as less than or equal to precision.

DUAL LOG specified multiple times. (DBERR 1045)

The DUAL LOG option was specified more than once in the START DBE NEW or START DBE NEWLOG statement.

Issue the command again, specifying DUAL LOG only once. Refer to the ALLBASE/SQL Reference Manual for additional information.

Failed to allocate heap space (DBERR 1046)

There was no memory available for your query.

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.

Failed to free heap space (DBERR 1047)

Internal error.

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.

Number of precision digits for this decimal constant exceeds 27. (DBERR 1048)

A constant specified in the INSERT, UPDATE, SELECT, DELETE, or DECLARE CURSOR statement contained more than 27 digits.

Correct your query so that all constants contain less than or equal to 27 decimal digits.

Dynamic query size exceeds input buffer size. (DBERR 1049)

The query included in the dynamic SQL command (PREPARE or EXECUTE IMMEDIATE) is larger than the input buffer.

Reduce the size of your query or put it in a host variable where it can be up to 32,762 bytes in length.

Statement not allowed in EXECUTE IMMEDIATE statement. (DBERR 1050)

The statement included in the EXECUTE IMMEDIATE cannot be used dynamically.

Use the EXECUTE statement in the regular way through ISQL or the preprocessor, not in EXECUTE IMMEDIATE.

SQL Parser internal NLS error. (DBERR 1051)

An internal Native Language Support error occurred within the parser, probably due to an invalid character in input.

Check your input for invalid bytes, and try again.

Invalid character found in SQL command. (DBERR 1052)

An SQL statement contained an invalid Native Language Support (NLS) character.

Check the NLS characters in the SQL statement and issue it again.

Duplicate LANG clause defined. (DBERR 1053)

A command was issued with a duplicate LANG clause.

Correct the command and issue it again.

Invalid LANG specified. (DBERR 1054)

You attempted to specify a language that is not configured on the system possibly because of misspelling.

Specify a valid language, then reissue the command to create the object.

Language clause not valid with non-character column. (DBERR 1055)

You tried to define a non-character column as having a language type.

Specify the language type with the appropriate character column.

DEFAULT NULL is specified, NOT NULL is not allowed. (DBERR 1057)

DEFAULT NULL and NOT NULL cannot be specified at the same time.

Either remove the DEFAULT NULL clause or remove the NOT NULL clause.

Number of referenced columns must match number of foreign key columns. (DBERR 1058)

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.

Check your syntax and correct the number of columns.

Aggregate, subquery, or host variable disallowed in CHECK constraint or rule. (DBERR 1059)

A CHECK constraint or RULE was defined with one of these items in it.

Check the syntax and remove the aggregate, subquery, or host variable from your CHECK constraint or RULE.

Constraint name beginning with SQLCON_ disallowed. (DBERR 1060)

A CONSTRAINT clause was specified with a name starting with 'SQLCON_' in your CREATE TABLE or CREATE VIEW statement.

Remove the CONSTRAINT clause or choose a different constraint name.

The syntax PRIMARY KEY may only be used once in CREATE/ALTER TABLE. (DBERR 1061)

The syntax PRIMARY KEY appears more than once in your CREATE TABLE statement.

Check the syntax and remove all but one of the PRIMARY KEY specifications, or change all but one to UNIQUE.

HASH ON CONSTRAINT clause did not match any unique constraint name. (DBERR 1062)

The constraint named in your HASH ON CONSTRAINT clause was not found in the CREATE TABLE statement.

Check the syntax and use the name of a named unique constraint in the HASH ON CONSTRAINT clause.

HASH/CLUSTERING ON CONSTRAINT used without a PRIMARY KEY. (DBERR 1063)

The syntax HASH/CLUSTERING ON CONSTRAINT is used without a constraint name, and no PRIMARY KEY was defined in the CREATE TABLE statement.

Check the syntax and either define a PRIMARY KEY or add a constraint name to the HASH/CLUSTERING ON CONSTRAINT clause.

CLUSTERING ON CONSTRAINT clause did not match any unique or referential constraint name. (DBERR 1064)

The constraint named in your CLUSTERING ON CONSTRAINT clause was not found in the CREATE TABLE statement.

Check the syntax and use the name of a named unique or referential constraint in the CLUSTERING ON CONSTRAINT clause.

Multiple definition of a column integrity constraint disallowed. (DBERR 1065)

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.

Remove the extra constraint(s); if more than one CHECK exists, the expressions within them can be ANDed together within a single CHECK.

Illegal hexadecimal number specified. (DBERR 1066)

You specified non-hexadecimal characters for the BINARY/VARBINARY field.

Refer to the chapter "Data Types" in the ALLBASE/SQL Reference Manual for proper syntax.

Invalid location name. (DBERR 1067)

You attempted to enter a location name longer than 35 characters.

Replace the location name with one under the maximum length and reissue the statement.

DEFAULT clause is not allowed for LONG data type column. (DBERR 1068)

You specified a DEFAULT clause for a column which is defined as LONG data type.

Remove the DEFAULT clause.

RECOVER option is not supported in START DBE command. (DBERR 1069)

The START DBE RECOVER command is no longer available.

No action necessary. Refer to the ALLBASE/SQL Database Administration Guide for information on recovery.

Syntax combination of dynamic parameter and host variable disallowed. (DBERR 1071)

You used both a dynamic parameter and a host variable in the statement.

Modify your statement to contain only dynamic parameters or only host variables.

Dynamic parameter is allowed in the PREPARE command only. (DBERR 1072)

You used a dynamic parameter in a statement that has not been prepared.

Either prepare the statement using the PREPARE statement or remove the dynamic parameters from the statement.

Dynamic parameter as the argument of an aggregate function disallowed. (DBERR 1073)

You used a dynamic parameter as the argument of an aggregate function.

Modify your statement to not use a dynamic parameter as the argument of an aggregate function.

Two log files specified without DUAL LOG. (DBERR 1074)

You have specified two log files without also specifying DUAL LOG.

Remove one of the log file specifications or specify DUAL LOG.

TID function cannot be used in a HAVING clause. (DBERR 1075)

You cannot specify the TID function in a HAVING clause.

Check and modify the command.

TID function cannot be used along with aggregate function in the SELECT list. (DBERR 1076)

You cannot specify the TID function with an aggregate function in t he select list.

Check and modify the command.

HP SQL internal error in SPALEXI. (DBERR 1077)

Internal error.

Record as much information as possible and contact your HP service representative or Response Center.

HP/SQL internal error in SLNPRE. (DBERR 1078)

Internal error.

Record as much information as possible and contact your HP service representative or Response Center.

HP/SQL internal error in SLNMAIN. (DBERR 1079)

Internal error.

Record as much information as possible and contact your HP service representative or Response Center.

Duplicate DEFAULT PARTITION clause defined. (DBERR 1080)

More than one DEFAULT PARTITION clause appears in the START DBE NEW or START DBE NEWLOG clause.

Check the specified START DBE statement.

Duplicate MAXPARTITIONS clause defined. (DBERR 1081)

The keyword MAXPARTITIONS appears more than once in the START DBE NEW or START DBE NEWLOG clause.

Check the specified START DBE statement.

AUDIT LOG specified multiple times. (DBERR 1082)

You specified the AUDIT LOG clause more than once in the START DBE NEW or START DBE NEWLOG statement.

Check the specified START DBE statement.

ARCHIVE LOG specified multiple times. (DBERR 1083)

You specified the ARCHIVE LOG clause more than once in the START DBE NEWLOG statement.

Check the specified START DBE statement.

Duplicate AUDIT NAME clause defined. (DBERR 1084)

You specified the AUDIT NAME clause appears more than once in the START DBE NEW or START DBE NEWLOG syntax.

Check the specified START DBE statement.

AUDIT NAME too long. (DBERR 1085)

You specified an AUDIT NAME longer than 8 bytes.

Check the specified START DBE statement.

INCREMENT size specified not in valid range. (DBERR 1086)

The INCREMENT size for DBEFile expansion cannot be zero.

Make sure the INCREMENT size is within the valid range.

Duplicate AUDIT ELEMENT specified. (DBERR 1088)

You specified an AUDIT ELEMENT more than once in the AUDIT ELEMENTS clause of the START DBE NEW or START DBE NEWLOG statement.

Check the specified START DBE statement.

Duplicate COMMENT PARTITION clause defined. (DBERR 1089)

You have more than one COMMENT PARTITION clause in the START DBE NEW or START DBE NEWLOG statement.

Check the specified START DBE statement.

Dynamic Parameters cannot be used as both the first and the second operands in a BETWEEN predicate. (DBERR 1090)

You specified dynamic parameters as both the first and the second operands in a BETWEEN predicate.

Modify your statement to not contain dynamic parameters as both the first and second operands of the BETWEEN predicate.

TID function cannot be used as the argument of the aggregate function. (DBERR 1091)

You cannot use the TID function as the argument of an aggregate function.

Check and modify the command.

Duplicate constraint type specified. (DBERR 1092)

You specified the same constraint type more than once in a SET CONSTRAINTS statement.

Remove the duplicate constraint type(s) and reissue the statement.

Default timeout value out of valid range. (DBERR 1093)

The default timeout value you specified is invalid.

Verify that the default timeout value is within the valid range.

Maximum timeout value out of valid range. (DBERR 1094)

The maximum timeout value you specified is invalid.

Verify that the maximum timeout value is within the valid range.

Default timeout value exceeds maximum timeout limit. (DBERR 1095)

The default timeout value is greater than the maximum timeout limit.

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.

DEFAULT TIMEOUT specified multiple times. (DBERR 1096)

You specified the DEFAULT TIMEOUT clause more than once in either the START DBE, START DBE NEW, or STARTDBE NEWLOG statement.

Issue the statement again, specifying the DEFAULT TIMEOUT clause only once.

MAXIMUM TIMEOUT specified multiple times. (DBERR 1097).

You specified the MAXIMUM TIMEOUT clause more than once in either the START DBE, START DBE NEW, or STARTDBE NEWLOG statement.

Issue the statement again, specifying the MAXIMUM TIMEOUT clause only once.

User timeout value out of valid range. (DBERR 1098)

The specified user timeout is invalid.

Verify that the user timeout value is within the valid range.

GENPLAN accepts SELECT, UPDATE, and DELETE statements only. (DBERR 1099)

A SELECT, UPDATE, or DELETE statement is expected.

Issue GENPLAN for a statement of one of the above types.

VariableName in WHERE clause has not been defined in the WITH clause of GENPLAN. (DBERR 1100)

A VariableName in the WHERE clause of the statement contained in GENPLAN has not been defined in the WITH clause of the GENPLAN statement.

Add the VariableName with the appropriate data type to the WITH clause of the GENPLAN statement.

A language, default, or column constraint clause is not allowed in the WITH clause of GENPLAN. (DBERR 1101)

A language, default, or column constraint clause was found in the WITH clause of GENPLAN.

Remove the language, default, or column clause from the WITH clause of GENPLAN.

SQL Linearizer internal NLS error. (DBERR 1102)

Internal error.

Record as much information as possible and contact your HP Service Representative or Response Center.

Duplicate VariableName found in the WITH clause of GENPLAN. (DBERR 1103)

The WITH clause of GENPLAN has a duplicate VariableName.

Rename or remove the duplicate VariableName from the WITH clause of GENPLAN.

Duplicate RUN BLOCK clause defined. (DBERR 1104)

You specified the RUN BLOCK clause twice in the START DBE or START DBE NEW statement.

Issue the command again specifying the RUN BLOCK clause once.

USER not permitted in table CHECK constraint. (DBERR 1105)

You specified a CHECK constraint with USER.

Remove the use of USER in the CHECK constraint and reissue the statement.

CURRENT_DATE not permitted in table CHECK constraint. (DBERR 1106)

You specified a CHECK constraint with CURRENT_DATE.

Remove the use of CURRENT_DATE in the CHECK constraint and reissue the statement.

CURRENT_TIME not permitted in table CHECK constraint. (DBERR 1107)

You specified a CHECK constraint with CURRENT_TIME.

Remove the use of CURRENT_TIME in the CHECK constraint and reissue the statement.

CURRENT_DATETIME not permitted in table CHECK constraint. (DBERR 1108)

You specified a CHECK constraint with CURRENT_DATETIME.

Remove the use of CURRENT_DATETIME in the CHECK constraint and reissue the statement.

! PARTITION value must be non-zero. (DBERR 1109)

You specified a DEFAULT, MAXPARTITIONS, or COMMENT partition value of zero in the START DBE NEW or START DBE NEWLOG statement.

Check the specified START DBE statement and replace the zero in the named partition value with a non-zero value.

The label (!) is not an integer. (DBERR 1110)

For PASCAL and FORTRAN 77 applications, labels must be integers. A label was found that was not an integer.

Change the label to an integer.

The label (!) is not an identifier name. (DBERR 1111)

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.

Change the label to start with a non-numeric character.

Statement not allowed in stored procedure. (DBERR 1120)

The current statement is not permitted within a procedure.

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.

Local variable declarations must be at the beginning of a stored procedure. (DBERR 1121)

The DECLARE statement was not at the beginning of the procedure.

Define local variables with DECLARE statements at the beginning of the procedure.

Return Status in the RETURN statement must be an integer value. (DBERR 1122)

The status value in the RETURN statement is not an integer value.

Use an integer value for the ReturnStatus in the RETURN statement.

Indicator variables are not allowed with parameters or local variables used in a stored procedure statement. (DBERR 1123)

You attempted to include an indicator variable with a parameter declaration or with a local variable in the CREATE PROCEDURE statement.

Rewrite your CREATE PROCEDURE statement, eliminating indicator variables.

Element in Boolean expression is not allowed in current procedure statement. (DBERR 1124)

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.

Rewrite your CREATE PROCEDURE statement, eliminating the illegal elements from the Condition.

Undefined parameter, local variable or cursor. (DBERR 1125)

The parameter, variable, or cursor is referenced inside a procedure without first being defined.

Define the parameter, local variable, or cursor before referencing it in the CREATE PROCEDURE statement.

Doubly defined parameter, local variable or cursor. (DBERR 1126)

You defined the parameter, local variable, or cursor more than once.

Check your parameter list, local variable declaration, or cursor definition and reissue the CREATE PROCEDURE statement.

Built-in-variable is not allowed in an SQL statement. (DBERR 1127)

You used a built-in variable in an SQL statement. Built-in variables can only be used in non-SQL statements inside a procedure.

Check the expressions in the procedure's SQL statements, and reissue the CREATE PROCEDURE statement.

A local variable or parameter is required for this SQL statement in a stored procedure. (DBERR 1128)

You used the SELECT, FETCH, or REFETCH statement inside a procedure without specifying a local variable or parameter.

Reissue the CREATE PROCEDURE statement including the appropriate local variable or parameter along with the SELECT, FETCH, or REFETCH.

OUTPUT option is allowed only for host variables in EXECUTE PROCEDURE. (DBERR 1129)

You attempted to use the OUTPUT option without specifying a host variable in the EXECUTE PROCEDURE statement in an application program.

Check the actual parameters of your EXECUTE PROCEDURE statement and eliminate the illegal use of the OUTPUT option.

The LONG data type is not allowed for a parameter or local variable in a stored procedure. (DBERR 1130)

You attempted to declare a parameter or local variable with the LONG data type in the CREATE PROCEDURE statement.

Reissue the CREATE PROCEDURE statement without the LONG parameter or variable declaration.

No LABEL is allowed for this procedure statement. (DBERR 1131)

No label is allowed in the DECLARE Variable statement, the WHENEVER statement, or compound statements.

Remove the illegal label and reissue the CREATE PROCEDURE statement.

Cursor name must be a single identifier. (DBERR 1132)

You attempted to qualify a cursor name with an owner or module name.

Delete the cursor name qualification in the specified statement and reissue the CREATE PROCEDURE statement.

No INTO clause is allowed in the SELECT statement of a DECLARE CURSOR. (DBERR 1133)

You attempted to use an INTO clause inside a cursor declaration in a procedure.

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.

Local variable data type is invalid. (DBERR 1134)

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.

Correct the data type for the local variable or parameter and reissue the CREATE PROCEDURE statement.

A local variable/host variable is not allowed in an inner query block. (DBERR 1135)

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.

Remove the illegal variable reference in the query.

The number of parameters defined exceeds the maximum of 255. (DBERR 1136)

You attempted to specify more than the maximum of 255 parameters in a CREATE PROCEDURE or EXECUTE PROCEDURE statement.

Reissue the CREATE PROCEDURE or EXECUTE PROCEDURE statement using 255 or fewer parameters.

The expression in a variable or parameter assignment statement contains an element that is not allowed in a stored procedure. (DBERR 1137)

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.

Reissue the CREATE PROCEDURE statement , eliminating the illegal elements from the expression.

The expression in an actual parameter contains an element that is not allowed in the EXECUTE PROCEDURE statement. (DBERR 1138)

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.

Rewrite your EXECUTE PROCEDURE statement, eliminating the illegal element from the expression in the actual parameter.

The OUTPUT option is not allowed for parameters that contain an expression in the EXECUTE PROCEDURE statement. (DBERR 1139)

You attempted to use the OUTPUT option with a parameter that contains an expression in an EXECUTE PROCEDURE statement within an application program.

Check the actual parameters of your EXECUTE PROCEDURE statement and eliminate the illegal use of the OUTPUT option.

The language clause is not valid with a non-character parameter or variable in the CREATE PROCEDURE statement. (DBERR 1140)

You specified a language for a parameter, variable, or result of a non-character data type in a CREATE PROCEDURE statement.

Reissue the CREATE PROCEDURE statement, omitting the language clause for any parameter, variable, or result of a non-character data type.

No value was provided for a named list parameter in the EXECUTE PROCEDURE statement. (DBERR 1141)

You specified the name of a parameter in a named parameter list, but you did not specify a value for the parameter.

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.

Named list and ordered list parameters cannot be mixed in the EXECUTE PROCEDURE statement. (DBERR 1142)

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.

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.

Multiple values provided for single parameter in the EXECUTE PROCEDURE statement. (DBERR 1143)

You used the same parameter name more than once in a named parameter list in the EXECUTE PROCEDURE statement.

Correct the EXECUTE PROCEDURE statement, making sure that each parameter name is assigned only one value. Then reissue the EXECUTE PROCEDURE statement.

The number of result columns defined exceeds the maximum num of 1024. (DBERR 1144)

You specified more that 1024 result columns in a CREATE PROCEDURE statement.

Reissue the CREATE PROCEDURE statement, specifying no more than 1024 result columns.

Dynamic parameters are not allowed in procedure statements. (DBERR 1145)

You included a dynamic parameter in a statement inside a parameter.

Reissue the CREATE PROCEDURE statement, omitting any dynamic parameter.

The WITH RESULT clause is allowed only for a procedure returning results. (DBERR 1146)

You included the WITH RESULT clause in a CREATE PROCEDURE statement, but the procedure returns no result sets.

Reissue the CREATE PROCEDURE statement, omitting the WITH RESULT clause.

DEFAULT clause is not allowed for an OUTPUT ONLY parameter. (DBERR 1147)

You provided a default value for an OUTPUT ONLY parameter in the CREATE PROCEDURE statement.

Reissue the CREATE PROCEDURE statement, either omitting the default value, or specifying OUTPUT rather than OUTPUT ONLY.

Host variables not allowed in CREATE RULE. (DBERR 1150)

You defined a RULE containing a host variable.

Check the syntax and remove the host variable from your CREATE RULE statement.

Duplicate statement type specified in CREATE RULE. (DBERR 1151)

You defined a RULE with duplicate statement types.

Check the syntax and remove the duplicate statement type from your CREATE RULE statement.

TID function disallowed in CHECK constraint or RULE. (DBERR 1152)

A RULE or CHECK constraint contains a TID function.

Check the syntax and remove the TID function from your CREATE RULE statement or CHECK constraint.

RETURN clause not permitted in EXECUTE PROCEDURE of CREATE RULE. (DBERR 1153)

You included a RETURN clause in the EXEC PROCEDURE clause of a CREATE RULE statement.

Remove the RETURN clause from the EXEC PROCEDURE clause.

OUTPUT parameters not permitted in EXECUTE PROCEDURE of CREATE RULE. (DBERR 1154)

You included a parameter defined for OUTPUT in the EXECUTE PROCEDURE clause of a CREATE RULE statement.

Remove the key word OUTPUT from the EXECUTE PROCEDURE clause.

Negative Hexstring is not allowed. (DBERR 1155)

You attempted to enter a negative hexstring.

Remove the minus sign from the hexstring and reissue the statement.

Duplicate ISOLATION LEVEL clause defined. (DBERR 1156)

You have more than one IDOLATION LEVEL clause in the SET TRANSACTION or SET SESSION statement.

Check the specified SET TRANSACTION or SET SESSION statement.

Duplicate PRIORITY clause defined. (DBERR 1157)

You specified the PRIORITY clause more than once in the SET TRANSACTION or SET SESSION statement.

Check the specified SET TRANSACTION or SET SESSION statement.

Duplicate LABEL clause defined. (DBERR 1158)

You included more than one LABEL clause in the SET TRANSACTION or SET SESSION statement.

Check the specified SET TRANSACTION or SET SESSION statement.

Duplicate CONSTRAINTS clause defined. (DBERR 1159)

You included more than one CONSTRAINTS clause in the SET TRANSACTION or SET SESSION statement.

Check the specified SET TRANSACTION or SET SESSION statement.

Duplicate DML ATOMICITY clause defined. (DBERR 1160)

You included more than one DML ATOMICITY clause in the SET TRANSACTION or SET SESSION statement.

Check the specified SET TRANSACTION or SET SESSION statement.

Duplicate FILL clause defined. (DBERR 1161)

You included more than one FILL clause in the SET SESSION statement.

Check the specified SET SESSION statement.

Device name specified exceed 44 characters. (DBERR 1163)

The device name in the CREATE DBEFILE command is too long.

Correct the device specification and reissue the CREATE DBEFile command.

The [NOT] CASE SENSITIVE attribute is not applicable on non-character column. (DBERR 1164)

You applied a CASE SENSITIVE or NOT CASE SENSITIVE keyword to a column which is not defined as a character column.

Avoid applying CASE SENSITIVE or NOT CASE SENSITIVE keywords to non-character columns.

Duplicate USER TIMEOUT clause defined. (DBERR 1165)

A duplicate USER TIMEOUT clause was specified.

No action required. The duplicate USER TIMEOUT clause will be ignored.

Duplicate on TIMEOUT/DEADLOCK clause defined. (DBERR 1166)

A duplicate TIMEOUT/DEADLOCK clause was specified.

No action required. The duplicate TIMEOUT/DEADLOCK clause will be ignored.

Duplicate TERMINATION clause defined. (DBERR 1167)

A duplicate TERMINATION clause was specified.

No action required. The duplicate TERMINATION clause will be ignored.

Table name required. (DBERR 1168)

You issued a RENAME TABLE statement without a valid table name.

See syntax for RENAME TABLE in "SQL Statements" chapter of the ALLBASE/SQL Reference Manual.

Data type ! not allowed for CAST. (DBERR 1169)

An incorrect data type was specified for CAST.

See the table, "Data Types for CAST Function," in the "Expressions" chapter of the ALLBASE/SQL Reference Manual.

Format specification is only allowed for date/time data types. (DBERR 1170)

An incorrect format was specified.

See the "Expressions" chapter of the ALLBASE/SQL Reference Manual for the correct syntax.

Expression may not contain table or column reference. (DBERR 1171)

An incorrect syntax was specified for the expression.

See the "Expressions" chapter of the ALLBASE/SQL Reference Manual for the correct syntax.

Unidentified DBECON utility error. (RC !, !, !, !) (DBERR 1600)

An unexpected error was encountered.

Record as much information as possible and contact your HP Service Representative or Response Center.

Cannot open DBECON file. (! !, RC !, !, !) (DBERR 1601)

A file system error was encountered.

Check the spelling of the DBEnvironmentName in the last command that was issued. Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

Cannot close DBECON file. (! !, RC !, !, !) (DBERR 1602)

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

Cannot read DBECON file. (! !, RC !, !, !) (DBERR 1603)

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

Cannot update DBECON file. (! !, RC !, !, !) (DBERR 1604)

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

Cannot store DBECON file. (! !, RC !, !, !) (DBERR 1605)

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1for an error description.

DBCore INTERNAL error. (FNC !, RC !, ! !, !, !) (DBERR 1606)

An unexpected error was encountered.

Record as much information as possible and contact your HP Service Representative or Response Center.

Cannot open database or log file. (! !, RC !, !, !) (DBERR 1607)

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

Cannot update database or log file. (! !, RC !, !, !) (DBERR 1608)

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

Cannot close database or log file. (! !, RC !, !, !) (DBERR 1609)

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

Cannot purge database or log file. (! !, RC !, !, !) (DBERR 1610)

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

Invalid DBECON file. Record length too small. (RC !, !, !, !) (DBERR 1621)

The file specified is not a DBECON file.

Check your spelling. Issue the command again, specifying a valid DBECON file.

Invalid DBECON file. Bad Brand. (RC !, !, !, !) (DBERR 1622)

The file specified is not a DBECON file.

Check your spelling. Issue the command again, specifying a valid DBECON file.

DBEnvironment already exists. (RC !, !, !, !) (DBERR 1623)

You attempted to RESTORE a backup copy of a DBEnvironment, but it already exists on your system.

You must purge all files associated with the DBEnvironment before RESTORE will successfully execute.

DBE on StoreFile doesn't match RESTORE parameter. (RC !, !, !, !) (DBERR 1624)

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.

Issue the command again, specifying the correct StoreFile and DBEnvironment names.

Null or invalid StoreFile name. (RC !, !, !, !) (DBERR 1625)

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.

Check your spelling. Issue the command again, specifying a valid StoreFileName.

Security Violation. (RC !, !, !, !) (DBERR 1626)

You do not have the required capability for the operation that was attempted.

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.

Internal Error. Buffer too small. (RC !, !, !, !) (DBERR 1629)

An unexpected error was encountered.

Record as much information as possible and contact your HP Service Representative or Response Center.

SystemFileName could not be CREATED (! !). (DBERR 1640)

A file system error was encountered.

Refer to the MPE/ix Error Message Manual, Volume 1 for an error description.

NLS routine failed. (!, !, !, !) (DBERR 1680)

An unexpected error occurred while using an internal native language procedure.

Record as much information as possible and contact your HP Service Representative or Response Center.

Cannot open message catalog (!). (DBERR 1682)

An unexpected error was encountered when trying to open the ALLBASE/SQL message catalog. It probably does not exist.

Contact your system administrator.

Message catalog read error. (set !, msg !, !) (DBERR 1683)

An unexpected error was encountered when trying to find a message in the ALLBASE/SQL message catalog.

Record as much information as possible and contact your HP Service Representative or Response Center.

Cannot close message catalog (!). (DBERR 1684)

An unexpected error was encountered when trying to close the ALLBASE/SQL message catalog.

Contact your system administrator.

Failed loading keyword (!). (DBERR 1685)

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.

Contact your system administrator.

Failed to determine minimum uniqueness of keywords (!). (DBERR 1686)

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.

Contact your system administrator.

Failed to obtain string constant (set !, msg !, !). (DBERR 1687)

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.

Contact your system administrator.

Cannot open $STDINX. (! !) (DBERR 1688)

An MPE/iX file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1.

Cannot close $STDINX. (! !) (DBERR 1689)

An MPE/iX file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1.

Cannot read from $STDINX. (! !) (DBERR 1690)

An MPE/iX file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1.

The statement is not valid in SETOPT. (DBERR 1813)

The statement is not supported with SETOPT.

Do not use the statement in SETOPT.

Conflict ! statements or conflict conditions on ! statement occur in SETOPT statement. (DBERR 1814)

! statements or conditions on ! statement in SETOPT are conflicting.

Remove incorrect ! statement or incorrect conditions from ACCESS statement and reexecute SETOPT and the query.

WITH clause of GENPLAN is not allowed in the GENPLAN on a section. (DBERR 1815)

You tried to specify a GENPLAN on a section with a WITH clause.

Remove WITH clause from GENPLAN statement.

Cannot use WITH AUTOCOMMIT if rule enabled. (DBERR 2032)

WITH AUTOCOMMIT was used incorrectly.

See the DELETE or VALIDATE statement in the "SQL Statements" chapter of the ALLBASE/SQL Reference Manual.

Cannot use WITH AUTOCOMMIT inside atomic block.(DBERR 2033)

WITH AUTOCOMMIT was used incorrectly.

See the DELETE or VALIDATE statement in the "SQL Statements" chapter of the ALLBASE/SQL Reference Manual.

Cannot use WITH AUTOCOMMIT inside global transaction. (DBERR 2034)

WITH AUTOCOMMIT was used incorrectly.

See the DELETE or VALIDATE statement in the "SQL Statements" chapter of the ALLBASE/SQL Reference Manual.

Cannot use WITH AUTOCOMMIT if constraints are deferred. (DBERR 2035)

WITH AUTOCOMMIT was used incorrectly.

See the DELETE or VALIDATE statement in the "SQL Statements" chapter of the ALLBASE/SQL Reference Manual.

Cannot use WITH AUTOCOMMIT on a TurboIMAGE table. (DBERR 2036)

WITH AUTOCOMMIT was used incorrectly.

See the DELETE or VALIDATE statement in the "SQL Statements" chapter of the ALLBASE/SQL Reference Manual.

ALLBASE/SQL not running. (DBERR 2100)

An SQL statement was issued before a DBE session was started.

Start a DBE session with the CONNECT or START DBE statement, then issue the SQL statement again.