Chapter 7 ALLBASE/SQL Error Messages 2413-2770

Number of boolean factors in predicate expression exceeds maximum (!). (DBERR 2413)

The number of factors in the WHERE clause exceeds the maximum allowed.

Try to reduce the number of factors.

Length of column ! in table !.! below minimum ! bytes. (DBERR 2414)

You tried to create a LONG or CHAR column of length 0.

Create the column with at least the minimum length.

Number of operators in internal predicate exceed maximum (!). (DBERR 2415)

A predicate containing one or more OR operators was too complicated. When additional factors were added to the predicate internally for optimization, the total number of operators exceeded the maximum.

Try to rewrite the query, simplifying the predicate as much as possible, and lowering the precedence of OR operators as much as possible.

Hash on table !.! has more than ! columns. (DBERR 2416)

You specified a hash containing more than 16 columns.

Issue the CREATE TABLE statement again, specifying no more than 16 columns for the hash key.

Length of hash key on table !.! exceeds ! bytes. (DBERR 2417)

You specified a hash key which exceeds the maximum key length.

Issue the CREATE TABLE statement again, specifying a hash key with length no greater than the maximum.

Length of parameter ! in procedure !.! exceeds ! bytes. (DBERR 2418)

The number of bytes in the specified parameter exceeded the maximum allowed.

Issue the CREATE PROCEDURE statement again, specifying a parameter length no greater than the maximum specified.

Length of parameter ! in procedure !.! below minimum ! bytes. (DBERR 2419)

The number of bytes in the specified parameter was less than the minimum allowed.

Issue the CREATE PROCEDURE statement again, specifying a parameter length no less than the minimum allowed.

INSERT rejected: Values do not match number of columns. (DBERR 2420)

The number of values in the INSERT statement exceeded the number of columns in the INSERT list or the number of select list items did not match the number of columns in the insert list.

Issue the INSERT statement again, specifying a valid number of columns. Use the INFO command to get a list of columns in the table.

Column number exceeds number of SelectList items. (DBERR 2421)

The ORDER BY clause contained a number greater than the number of select list items.

Issue the SELECT statement again, specifying no more columns in the ORDER BY clause than in the select list. Refer to the ALLBASE/SQL Reference Manual for additional information on the SELECT statement.

Range violation on value !. Valid range is ! - !. (DBERR 2422)

The source constant number in the query was out of its valid range

or

a host variable was not defined

or

one of the values in a format node was out of range.

Correct your query so that the source constant is within the valid range

or

make sure that the host variable has been declared

or

in Pascal or C programs, check the value you specified for data types in the dynamic format nodes of SQLDA.

Number of Selects in command exceeds maximum !. (DBERR 2423)

The maximum number of Selects in a command has been exceeded.

Issue the command again, specifying the maximum number or fewer.

SelectList counts are not equal in UNION command. (DBERR 2424)

The number of columns in the individual select lists in the UNION command are not the same.

Issue the command again with an equal number of columns in the select lists.

UNION operation disallowed within a Nested Query. (DBERR 2425)

You tried to include a UNION operation in a nested query.

UNION of two nested queries is allowed but UNION cannot be within a nested query.

Tuple size exceeds maximum for UNION command ! bytes. (DBERR 2426)

Your select list size is greater than the maximum currently allowed for a UNION command.

Re-issue the command with a valid tuple size.

Sort length of UNION exceeds maximum allowed ! bytes. (DBERR 2428)

The UNION command specifies a number of columns whose total sort tuple length exceeds the maximum allowable.

Issue the command again, specifying no more than the maximum sort tuple length. Refer to the ALLBASE/SQL Reference Manual for additional information on the SELECT statement.

Sort length of ORDER BY/GROUP BY/DISTINCT/UNION exceeds maximum allowed ! bytes. (DBERR 2429)

The ORDER BY, GROUP BY, DISTINCT, or UNION clause of the SELECT statement specifies a number of columns whose total sort tuple length exceeds the maximum allowable.

Issue the command again, specifying no more than the maximum length of the sort tuple. Refer to the ALLBASE/SQL Reference Manual for additional information on the SELECT statement. The maximum sort tuple size can be calculated from the formula presented in Appendix A of the ALLBASE/SQL Database Administration Guide.

Invalid decimal precision ! - Allowed range is ! - !. (DBERR 2430)

The decimal precision you specified was not within the valid range.

Refer to the ALLBASE/SQL Reference Manual for valid decimal precision.

Invalid decimal column - Scale ! exceeds precision !. (DBERR 2431)

The decimal scale was greater than the precision value.

Refer to the ALLBASE/SQL Reference Manual for valid decimal numbers.

Invalid float precision !- Allowed range is ! - !. (DBERR 2432)

The float precision you specified was not within the valid range.

Refer to the ALLBASE/SQL Reference Manual for valid float precision.

Sort length of sort merge join exceeds maximum allowed ! bytes. (DBERR 2433)

The sort merge join query specifies a number of columns whose total sort tuple length exceeds the maximum allowable.

Issue the command again, specifying no more than the maximum length of the sort tuple. Refer to the ALLBASE/SQL Reference Manual for additional information on the SELECT statement.

Invalid section number. Valid range is ! - !. (DBERR 2434)

Your command included a value that was invalid. The first parameter in the error message indicates the value that was invalid. The second and third parameters give you the valid range.

Re-issue your command, specifying a value within the valid range.

Invalid transaction priority. Valid range is ! - !. (DBERR 2435)

You issued a BEGIN WORK with an invalid priority option.

Reissue the BEGIN WORK with a priority within the valid range.

Invalid decimal parameter - Scale ! exceeds precision !. (DBERR 2436)

The decimal scale was greater than the precision value.

Refer to the "Data Types" chapter in the ALLBASE/SQL Reference Guide for complete information about valid decimal values.

Invalid decimal result - Scale ! exceeds precision !. (DBERR 2437)

The scale specified was greater than the precision specified for a procedure result column.

Issue the CREATE PROCEDURE statement again, specifying a valid decimal result type. Refer to the ALLBASE/SQL Reference Manual for valid decimal data type specifications.

Length of result ! in procedure !.! exceeds ! bytes. (DBERR 2438)

The number of bytes you specified for a procedure result column exceeded the maximum allowed.

Issue the CREATE PROCEDURE statement again, specifying a number of bytes no greater than the maximum.

Length of result ! in procedure !.! below minimum ! bytes. (DBERR 2439)

You tried to create a procedure result column with a length of 0 bytes.

Issue the CREATE PROCEDURE statement again, specifying a length of at least 1 byte.

! should be ! to !. Number ! is invalid. (DBERR 2440)

The size you specified for one or more parameters of the START DBE statement is invalid.

Issue the START DBE statement again, specifying valid numbers for the following parameters: DBEFile0 should be 50 to 16,777,215 pages long; DBELOG should be 250 to 16,777,215 pages long; Max Transactions should be 2 to 240 concurrent transactions; Data Buffer range is 15 to 50,000 pages and the Log Buffer range is 24 to 1024 pages.

TRANSFER OWNERSHIP OF MODULE is not supported. (DBERR 2449)

You specified the MODULE option of the TRANSFER OWNERSHIP statement. However, the ownership of modules cannot be transferred.

DROP the existing modules and preprocess the program with the -o option.

BEGIN WORK MULTI is not supported. (DBERR 2450)

You attempted to use the MULTI option for the BEGIN WORK statement.

You can have only one active transaction at a time. Issue a COMMIT WORK or ROLLBACK WORK statement before beginning the second transaction.

Clustering index not allowed on table on which hash structure has already been defined. (DBERR 2452)

You tried to create a clustering B-tree index on a table on which a hash structure already existed.

Issue the CREATE INDEX statement again, omitting the CLUSTERING option

or

UNLOAD the data from the table. DROP the table. ReCREATE the table, omitting the HASH option. Issue the CREATE INDEX statement again to create a clustering B-tree index. LOAD the data.

Non-unique hash is not supported. (DBERR 2453)

You tried to create a table with a non-unique hash structure.

Issue the CREATE TABLE statement again, including the UNIQUE keyword with the HASH option.

Cannot drop a non-empty DBEFileSet. (DBERR 2500)

You attempted to DROP a DBEFileSet which has DBEFiles associated with it.

Before dropping the DBEFileSet, drop the DBEFiles then remove them. Remember that the DBEFiles must be empty before they can be dropped.

DBEFileSet has no DBEFiles. (DBERR 2501)

You created a table in an empty DBEFileSet and then tried to INSERT into that table.

ADD a DBEFile to the DBEFileSet before attempting an INSERT statement.

! space exhausted in DBEFileSet !. (DBERR 2502)

The first parameter is the setting for the DBEFile's TYPE attribute. Valid settings are INDEX, TABLE, and MIXED. This message can have several meanings as follows:

Add new DBEFiles of the appropriate type to the DBEFileSet. If space has been exhausted in the System.DBEFileSet during a query, try adding more tempspace and more contiguous physical disk space.

DBEFile not empty. (DBERR 2503)

You attempted to REMOVE a non-empty DBEFile from its DBEFileSet.

The DBEFile must be empty before it can be removed from the DBEFileSet.

DBEFile size must be between ! and ! pages. (DBERR 2505)

The file size you specified in the CREATE DBEFILE statement was not within the valid range.

Issue the CREATE DBEFILE statement again, specifying a valid file size.

TempSpace file size limit must be between ! and ! pages. (DBERR 2506)

The file size you specified in the CREATE TEMPSPACE statement was not within the valid range.

Issue the CREATE TEMPSPACE statement again, specifying a valid file size.

DBEFile must be empty or new type must be mixed. (DBERR 2507)

You attempted to ALTER a non-empty DBEFile to a type other than mixed.

The type of a non-empty DBEFile can be changed from TABLE or INDEX to MIXED. No other changes are allowed.

DBEFileSet has no DBEFile of required DBEFile type. (DBERR 2508)

You tried to insert rows into a table whose DBEFileSet has only INDEX DBEFiles

or

you tried to create an index on a non-empty table whose DBEFileSet contains only DATA DBEFiles.

Ask your database administrator to CREATE and ADD the appropriate DBEFiles.

Index uniqueness or UNIQUE/PRIMARY KEY constraint violated. (DBERR 2509)

You tried to insert a duplicate key value into a column used in a unique index or a unique constraint.

Issue the INSERT or UPDATE statement again without the duplicate row.

Table is read only. (DBERR 2510)

You tried a LOCK or WRITE operation (DROP, DELETE, INSERT, LOCK TABLE, UPDATE, UPDATE STATISTICS) on a read only table.

No action is necessary. These operations cannot be performed on SYSTEM.CALL, SYSTEM.ACCOUNT, SYSTEM.USER, SYSTEM.COUNTER, or SYSTEM.TRANSACTION.

User ! does not exist. (DBERR 2511)

The DBEUserId you specified in the TERMINATE USER or RESET SYSTEM.ACCOUNT command is not currently connected to the DBEnvironment.

Issue the command again, specifying a valid userid.

Session ID ! does not exist. (DBERR 2512)

You attempted to terminate a session ID that does not exist, or you do not have the authority to terminate it.

Check that a valid session ID was used. If the session ID is valid, have your DBA issue the statement.

Number of primary pages must be between ! and !. (DBERR 2513)

You specified a number of primary pages for the hash in the CREATE TABLE statement which was not within the valid range.

Issue the CREATE TABLE statement again, specifying a valid number of primary pages.

Hash key uniqueness or UNIQUE/PRIMARY KEY constraint violated. (DBERR 2514)

You tried to insert a duplicate key value into a column used in a unique hash structure, which might be supporting a unique constraint.

Issue the INSERT statement again without the duplicate row.

DBEFile is currently associated with a DBEFileSet. (DBERR 2515)

You tried to DROP a DBEFile which was associated with a DBEFileSet

or

you tried to ADD a DBEFile to a DBEFileSet which already is associated with another DBEFileSet.

You must REMOVE the DBEFile from the DBEFileSet before it can be dropped

or

you must REMOVE the DBEFile from the DBEFileSet with which it is currently associated before you can ADD it to a different DBEFileSet.

This table already has a clustering index. (DBERR 2516)

When you use the CREATE INDEX statement, no more than one index per table can have the clustering attribute.

Drop the existing clustering index or create the new index without the clustering attribute.

DBEFile in use for hash. (DBERR 2518)

You tried to DROP or ALTER a DBEFile that is allocated for hash table data.

First DROP the hash table. Then, the DBEFile may be DROPped or ALTERed.

Exceeded maximum number of DBEFiles for hash space (!). (DBERR 2519)

The DBEFileSet specified for the hash table does not contain DBEFiles large enough that the primary pages for the hash table can be allocated using 16 or fewer DBEFiles.

Create additional DBEFiles large enough that the primary pages for the hash table can be allocated using 16 or fewer DBEFiles.

Not enough space in DBEFileset for hash primary pages. (DBERR 2520)

There is not enough space in the empty table or mixed DBEFiles in the DBEFileSet specified for the number of primary pages specified.

Create additional DBEFile(s) with enough space for the primary pages, and add them to the specified DBEFileSet. If you create the files in the same transaction as you create the table with the hash structure, you can ensure that no other transaction will be able to use the files.

Maximum size for DBEFile expansion exceeds ! pages. (DBERR 2521)

The maximum size that a DBEFile can be expanded, as specified in the MAXPAGES clause, exceeds the DBEFile maximum limit. The maximum size may not be exactly the same size specified with MAXPAGES, because it could be a rounded number.

Make sure the maximum DBEFile size specified is within the system limit.

DBEFile INCREMENT size must be between ! and ! pages. (DBERR 2522)

The size you specified in the INCREMENT clause for DBEFile expansion is not within the range.

Specify a valid INCREMENT size for the corresponding DBEFile.

Maximum size ! pages for DBEFile expansion is less than the initial size ! pages. (DBERR 2523)

The maximum size that a DBEFile can be expanded, as specified in the MAXPAGES clause, is less than the initial DBEFile size specified in the WITH PAGES clause. The maximum size may not be exactly the same size specified with MAXPAGES, because it could be a rounded number.

Make sure the maximum DBEFile size specified is at least equal to the initial DBEFile size, and that it is a multiple of the INCREMENT size. If dynamic DBEFile expansion is required, the maximum size must be greater than the initial size.

Connection ID ! does not exist. (DBERR 2524)

The Connection ID specified does not exist.

Use a valid Connection ID.

Transaction ID ! does not exist. (DBERR 2525)

The Transaction ID specified does not exist.

Use a valid Transaction ID.

Attempting to terminate current query. (DBERR 2526)

The current query is being terminated.

Take appropriate action for this query.

There is no transaction for Connection ID !. (DBERR 2527)

There was an attempt to terminate a transaction for the specified Connection ID, but no transaction was in progress.

No action is required.

Attempting to terminate persistent transaction. (DBERR 2528)

There is an attempt to terminate a persistent transaction.

The SQLUtil command cannot be used to terminate a persistent transaction.

The user termination level does not allow this type of termination. (DBERR 2529)

The user attempted to perform an unauthorized termination.

A user can terminate a transaction or query if the user is the owner or the user has DBA authority. No action required.

Query was aborted externally. (DBERR 2530)

The query was aborted by an external process.

Resume the query at an appropriate time.

Integer overflow on operation !. (DBERR 2600)

The result of an integer arithmetic operation within an expression was too big for the hardware to accommodate.

Try to modify your expression so that divisions occur before multiplications or break the expression into multiple expressions.

Integer divide by zero. (DBERR 2601)

The result of an arithmetic operation within an expression caused an integer value to be divided by zero.

Look at your data to find where this error occurred and make any necessary changes to your expression.

Extended precision overflow on operation !. (DBERR 2602)

The result of a float arithmetic operation within an expression was too big for the hardware to accommodate.

Try to modify your expression so that divisions occur before multiplications or break the expression into multiple expressions.

Extended precision underflow on operation !. (DBERR 2603)

The result of a float arithmetic operation within an expression was too small for the hardware to accommodate.

Try to modify your expression so that multiplications occur before divisions or break the expression into multiple expressions.

Extended precision divide by zero. (DBERR 2604)

The result of an arithmetic operation within an expression caused an extended precision value to be divided by zero.

Look at your data to find where this error occurred and make any necessary changes.

Packed decimal overflow on operation !. (DBERR 2605)

The result of an intermediate decimal operation was too big for the hardware to accommodate.

Try to modify your expression so that divisions occur before multiplications or break the expression into multiple expressions.

Invalid decimal digit in operation !. (DBERR 2606)

The decimal number you included through the host variable in a COBOL program was not valid.

Correct the decimal so that it is within the range of 0 through 9 and contains either a + or - sign.

Packed decimal divide by zero. (DBERR 2607)

The result of an arithmetic operation within an expression caused a packed decimal value to be divided by zero.

Look at your data to find where this error occurred and make any necessary changes.

Incompatible data types ! and ! in expression. (DBERR 2609)

You attempted to mix numeric and character data types in an expression in the select list, the WHERE clause, or the SET clause.

Issue the command again, specifying either numeric or character data only.

Operator ! invalid for data type !. (DBERR 2610)

You attempted to perform an arithmetic operation on char or varchar data, or attempted the LIKE predicate on numeric data.

Issue the command again using only appropriate operators on data types.

Datetime value contains a field greater than valid range allowed. (DBERR 2615)

You tried to insert a datetime value which was not valid.

Verify that all fields of all datetime literals are within the valid range.

Datetime value contains a field less than valid range allowed. (DBERR 2616)

You tried to insert a datetime value which was not valid.

Verify that all fields of all datetime literals are within the valid range.

Datetime data value does not match default format specification. (DBERR 2617)

You tried to insert a datetime value which did not meet the default specification criteria of "YYYY-MM-DD HH:MI:SS.FFF."

Verify that all fields of all datetime literals match the default format specification.

ALLBASE/SQL internal error in datetime conversion routine. (DBERR 2618)

ALLBASE/SQL internal software problem.

Contact your HP Service Representative or Response Center.

Invalid date entered, February 29th invalid for non-leap year. (DBERR 2619)

You tried to insert a datetime value which was not valid.

Enter the correct date.

Result of DATE/TIME arithmetic exceeds maximum value allowed. (DBERR 2620)

The arithmetic produced a value greater than the maximum allowed.

Verify that the requested arithmetic should produce a result which exceeds maximum values specified.

Result of DATE/TIME arithmetic less than minimum value allowed. (DBERR 2621)

The arithmetic produced a value less than the minimum allowed.

Verify that the requested arithmetic should produce a result which is less than the minimum values specified.

Size of datetime literal less than valid default size. (DBERR 2622)

You tried to insert a datetime value of incorrect length.

Verify that all datetime literals in the query are of the correct size.

Date value contains a field greater than valid range allowed. (DBERR 2623)

You tried to insert a date value which was not valid.

Verify that all fields of all date literals are within the valid range.

Date value contains a field less than valid range allowed. (DBERR 2624)

You tried to insert a date value which was not valid.

Verify that all fields of all date literals are within the valid range.

Date data value does not match default format specification. (DBERR 2625)

You tried to insert a date value which did not meet the default specification criteria.

Verify that all datetime literals in the query are specified in the default specification "YYYY-MM-DD."

Size of date literal less than valid default size. (DBERR 2626)

You tried to insert a date value of incorrect length.

Verify that all date literals in the query are of the correct size.

Time value contains a field greater than valid range allowed. (DBERR 2627)

You tried to insert a time value which was not valid.

Verify that all fields of all time literals are within the valid range.

Time value contains a field less than valid range allowed. (DBERR 2628)

You tried to insert a time value which was not valid.

Verify that all fields of all time literals are within the valid range.

Time data value does not match default format specification. (DBERR 2629)

You tried to insert a time value which did not meet the default specification "HH:MI:SS."

Verify that all time literals match the default format specification.

Size of time literal less than valid default size. (DBERR 2630)

You tried to insert a time value of incorrect length.

Verify that all time literals in the query are of the correct size.

Interval value contains a field greater than valid range allowed. (DBERR 2631)

You tried to insert an interval value which was not valid.

Verify that all fields of all interval literals are within the valid range.

Interval value contains a field less than valid range allowed. (DBERR 2632)

You tried to insert an interval value which was not valid.

Verify that all fields of all interval literals are within the valid range.

Interval data value does not match default format specification. (DBERR 2633)

You tried to insert an interval value which did not meet the default specification criteria.

Verify that all interval literals in the query are specified in the default specification "DDDDDDD HH:MI:SS.FFF" where "DDDDDDD" can be 1 to 7 digits.

Size of interval literal less than valid default size. (DBERR 2634)

You tried to insert an interval value of incorrect length.

Verify that all interval literals in the query are of the correct size.

Real precision overflow on operation !. (DBERR 2635)

The result of a real arithmetic operation within an expression was too big for the hardware to accommodate.

Try to modify your expression to convert the real values in it to floats or to have a target host variable of type FLOAT.

Real precision underflow on operation !. (DBERR 2636)

The result of a real arithmetic operation within an expression was too small for the hardware to accommodate.

Try to modify your expression to convert the real values in it to floats or to have a target host variable of type FLOAT.

Format specification exceeds maximum length (! bytes). (DBERR 2637)

You specified a date/time format length which exceeds the maximum length of 72 bytes.

Issue the command again with the length less than 72 bytes.

End of format specification detected before parsing end of datetime literal. (DBERR 2638)

Datetime literal does not match format specification given. Extra characters exist in datetime literal after parsing end of format specification.

Ensure the compatibility between the format specification and datetime literal specified in the datetime input function.

Invalid format specification in second parameter of datetime function. (DBERR 2639)

A unit within the format specification is not a valid unit.

Re-issue the command with a format specification.

Redundant fields specified in format specification. (DBERR 2641)

A unit in the format specification was specified twice, or two units which contain identical units.

Re-issue the command with a valid format specification.

Invalid data type for second parameter of datetime function. (DBERR 2642)

Data type of second parameter is not valid.

Please check the documentation for valid format types.

Format specification contains an invalid unit for data type !. (DBERR 2643)

A valid unit was specified in the format specification, but it is not valid for this datetime type.

Please check the documentation for valid format types for this datetime data type.

Datetime input function cannot parse input parameters. (DBERR 2644)

When parsing datetime literal, invalid data was detected.

Check validity of datetime literal in first parameter of datetime input function.

Day of week specified does not match date supplied. (DBERR 2645)

Alphabetic day of week specified incorrect for date literal specified.

Re-issue command with valid datetime literal.

End of datetime literal detected before parsing end of format specification. (DBERR 2646)

Format specification does not match datetime literal.

Re-issue command with correct input to datetime input function.

Datetime literal contains a value outside the valid range for a format specified. (DBERR 2647)

A unit in datetime literal is not within boundary of the unit values allowed.

Issue command with correct values for units specified in format specification.

Invalid length in VARCHAR. (DBERR 2650)

An invalid length field for a VARCHAR data type was detected in SQLCORE. The most likely cause of this would be an uninitialized VARCHAR host variable used in an insert or an uninitialized VARCHAR length field in the buffer used in a bulk insert.

Make sure that all VARCHAR host variables are properly initialized.

DEFAULT literal type ! is not compatible with the corresponding column data type !. (DBERR 2651)

The data type of the literal is not compatible with the one specified for the corresponding column.

Define a valid default value for the corresponding column.

DEFAULT ! is not compatible with the corresponding column data type !. (DBERR 2652)

You specified a DEFAULT current function, USER, or NULL, which is not compatible with the one specified for the corresponding column.

Define a valid default value for the corresponding column.

Non-supported DEFAULT value type !. (DBERR 2653)

You specified a DEFAULT value which is not a constant, a current function, USER, or NULL.

Define a valid default value for the corresponding column.

Data type ! invalid for the starting position of SUBSTRING function. (DBERR 2654)

The StartPosition parameter of the SUBSTRING function is not an integer constant or expression.

Change the StartPosition parameter to an integer constant or expression.

Data type ! invalid for the substring length of SUBSTRING function. (DBERR 2655)

The Length parameter of the SUBSTRING function is not an integer constant or expression.

Change the Length parameter to an integer constant or expression.

Source string must contain numeric value. (DBERR 2656)

The source character string of the CAST function contains invalid characters for a numeric expression.

Make sure the source character string contains an appropriate representation of a numeric value with no extraneous characters added.

CAST target data type too small. (DBERR 2657)

The size in bytes of the specified target data type is too small to hold the value being converted.

Specify a larger target data type.

Numeric/Binary conversion must be of equal length. (DBERR 2658)

In converting numeric data types to BINARY, the size in bytes of the source and target must be equal. If the target is a VARBINARY, the maximum size of the target must be equal or exceed the source size invalid character based on the target data type specified. This error will be reported if this is not true.

When converting to BINARY, make sure that the specified size of the BINARY matches the size of the source. If converting to VARBINARY, make sure that the specified size of the VARBINARY is at least the size of the source. When converting from BINARY or VARBINARY to a numeric type, string concatenation (||) or the SUBSTRING function can be used to make the source the correct size for the target.

Date/Binary conversion must be of equal length. (DBERR 2659)

In converting Date/Time data types to BINARY, the size in bytes of the source and target must be equal. If the target is a VARBINARY, the maximum size of the target must be equal or exceed the source size invalid character based on the target data type specified. This error will be reported if this is not true.

When converting to BINARY, make sure that the specified size of the BINARY matches the size of the source (16 bytes). If converting to VARBINARY, make sure that the specified size of the VARBINARY is at least the size of the source. When converting from BINARY or VARBINARY to a Date/Time type, the source should be 16 bytes.

TID/Binary conversion must be of equal length. (DBERR 2660)

In converting TID data types to BINARY, the size in bytes of the source and target must be equal. If the target is a VARBINARY, the maximum size of the target must be equal or exceed the source size invalid character based on the target data type specified. This error will be reported if this is not true.

When converting to BINARY, make sure that the specified size of the BINARY matches the size of the source (8 bytes). If converting to VARBINARY, make sure that the specified size of the VARBINARY is at least the size of the source. When converting from BINARY or VARBINARY to a Date/Time type, the source should be 8 bytes.

Invalid TID format. (DBERR 2661)

The character string being converted to a TID data type was not properly formatted.

The correct syntax for a character string representation of a TID is:

INSERT/UPDATE/DELETE disallowed on a join. (DBERR 2700)

You attempted to INSERT, UPDATE, or DELETE on a multiple table view.

You cannot perform an INSERT, UPDATE, or DELETE on multi-table views. Refer to the specified command and the CREATE VIEW statement in the ALLBASE/SQL Reference Manual for additional information.

INSERT/UPDATE disallowed on virtual column (!). (DBERR 2701)

You attempted to INSERT or UPDATE a computed column in a view.

Inserting rows through a view is not allowed if any column of the view is computed in an arithmetic expression. Refer to the ALLBASE/SQL Reference Manual for additional information.

INSERT/UPDATE/DELETE disallowed on group operation. (DBERR 2702)

You attempted to INSERT, UPDATE, or DELETE rows via a view which contained a GROUP BY clause in its definition.

A view definition for UPDATE, DELETE, and INSERT operations cannot contain a GROUP BY clause. Refer to the specified command and the CREATE VIEW statement in the ALLBASE/SQL Reference Manual for additional information.

INSERT/UPDATE/DELETE disallowed on ORDER BY. (DBERR 2703)

You attempted to declare a cursor containing both an ORDER BY clause and a FOR UPDATE clause, or you attempted an UPDATE or DELETE WHERE CURRENT on a cursor containing an ORDER BY clause.

Remove the ORDER BY from the cursor if updates and/or deletes are to be performed with it, or remove the FOR UPDATE clause from the cursor.

Illegal reference to column ! in group operation. (DBERR 2705)

A column you specified in the select list was not referenced in the GROUP BY clause of the SELECT statement.

or

you are doing a GROUP BY with a SELECT * and you have failed to reference all of the columns in the specified table in the GROUP BY clause.

Issue the SELECT statement again, specifying only aggregate functions and columns referenced in the GROUP BY clause

In the case of SELECT *, be sure to reference all columns produced by the expansion of the * in the GROUP BY clause.

INSERT/UPDATE/DELETE disallowed on DISTINCT operation. (DBERR 2706)

UPDATE, INSERT, and DELETE operations through a view are not allowed if the view definition involves a distinct clause.

Perform the UPDATE, INSERT, or DELETE operation on the base table or re-create the view without the DISTINCT clause.

UPDATE/DELETE disallowed on a cursor containing a subquery. (DBERR 2707)

You attempted to UPDATE or DELETE rows accessed through a cursor which contained a subquery in its definition.

Perform the UPDATE or DELETE only through a cursor which does not contain a subquery.

UPDATE/DELETE disallowed with subquery containing update/delete table. (DBERR 2708)

You attempted to UPDATE or DELETE through a view or with a search condition containing a subquery which references the target table.

Perform the UPDATE or DELETE only through views with search conditions which do not reference the target table in any subqueries.

UPDATE/DELETE disallowed on UNION. (DBERR 2709)

You attempted to UPDATE or DELETE through a cursor containing a UNION.

Perform the UPDATE or DELETE only through cursors not containing UNIONs.

INSERT or FORMAT II INSERT disallowed on a view referencing the insert table in a subquery. (DBERR 2710)

You attempted to insert through a view, where the view contains a subquery which references the same base table the view is based upon. Such an insert is not allowed.

Insert directly through the base table, or use a view not containing subqueries which reference the same table as the view.

Qualifier !.! (column !) is different from input table. (DBERR 2711)

The table name you specified in the select list or WHERE clause is different from the table name specified in the FROM clause of the SELECT statement.

Issue the SELECT statement again, specifying the same table name in both the select list or WHERE clause and the FROM clause. Refer to the ALLBASE/SQL Reference Manual for additional information on the SELECT statement.

Hash key columns may not be updated. (DBERR 2712)

You tried to update the value of a column included in the key for a hash.

DELETE the tuple with the old key column value. Then, INSERT a new tuple with the new key column value.

User ! does not have authority to GENPLAN on table/view !.!.(!) (DBERR 2716)

You do not have run authority to GENPLAN on a specified section.

Contact your database administrator to get the required authority or sign on as a user who does have the required authority.

The specified section !.!(!) is not a SELECT, UPDATE, DELETE or type II INSERT statement. (DBERR 2717)

The specified section you included is not an allowed statement for GENPLAN.

Check the source file to find the right section number.

Optimizer did not generate an access plan for the query. (DBERR 2718)

Internal Error.

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

User ! does not have authority to GENPLAN on table/view !.!. (DBERR 2719)

You do not have the required authority to execute GENPLAN on the named table or view.

Contact your database administrator to obtain the required authority or sign on as a user who does have the required authority.

INSERT/UPDATE/DELETE disallowed on system tables (!.!). (DBERR 2720)

You attempted to INSERT, UPDATE or DELETE to a system table.

Re-issue the statement on a non-system table.

Command ! is not allowed for views (!.!). (DBERR 2724)

You specified a command (ALTER TABLE, UPDATE STATISTICS, LOCK TABLE) that cannot be performed on a view.

No action is necessary. Refer to the ALLBASE/SQL Reference Manual for additional information on these commands and the ALLBASE/SQL Database Administration Guide for additional information on views.

Use DROP VIEW to drop view !.!. (DBERR 2725)

You attempted to drop a view using the DROP TABLE statement.

Use the DROP VIEW statement to drop a view.

Use DROP TABLE to drop table !.!. (DBERR 2726)

You attempted to drop a table using the DROP VIEW statement.

Use the DROP TABLE statement to drop a table.

Column ! does not accept nulls. (DBERR 2730)

You specified the NULL keyword for a non-null column in the INSERT or UPDATE statement.

Issue the command again, specifying a value for all non-null columns.

Reset command not valid for table !.!. (DBERR 2731)

You cannot issue the RESET statement on the specified table.

No action is necessary. The only valid tables for the RESET statement are SYSTEM.COUNTER and SYSTEM.ACCOUNT.

Invalid number of columns in view column list. (DBERR 2732)

The number of columns in the CREATE VIEW statement did not match the number of columns in the SELECT statement for the view.

Issue the command again using the same number of columns in both the CREATE VIEW statement and the SELECT statement.

Invalid savepoint number. (DBERR 2740)

The ROLLBACK WORK statement included a non-existent savepoint.

Issue the command again, specifying a valid savepoint number. Refer to the ALLBASE/SQL Reference Manual for additional information on the ROLLBACK WORK statement.

Archive not begun. (DBERR 2741)

You attempted to COMMIT ARCHIVE without a preceding BEGIN ARCHIVE statement.

Issue the BEGIN ARCHIVE statement first followed by the COMMIT ARCHIVE statement.

Archive already begun. (DBERR 2742)

The BEGIN ARCHIVE statement was issued twice.

No action is necessary.

Archive checkpoint not found. (DBERR 2743)

The checkpoint was not found.

Review the syntax for CHECKPOINT statement.

ROLLBACK WORK TO savepointnumber when you have cursors opened with KEEP CURSOR option. (DBERR 2744)

You opened a cursor with the KEEP CURSOR option and you are trying to use the SAVEPOINT option of the ROLLBACK WORK statement.

Revise the program to open the cursor without the KEEP CURSOR option, or eliminate the TO SAVEPOINT clause.

Procedure cursor !.!(!) has no current result set. (DBERR 2749)

An attempt was made to fetch from a procedure cursor, either without first issuing an ADVANCE statement

or

after an ADVANCE returned an sqlcode of 200 (no more result sets).

Issue an ADVANCE statement after opening the cursor, and before trying to fetch results.

or

Check for an sqlcode of 200 on an ADVANCE statement before attempting to fetch results.

Module !.!(!) has DBEFileSet error. (DBERR 2750)

You tried to use DECLARE CURSOR or to PREPARE a section in a non-existent DBEFileSet.

Check your spelling, and examine the SYSTEM.DBEFILESET view to make sure that the DBEFileSet actually exists. Then issue the command again, specifying a valid DBEFileSet.

Module !.!(!) is a cursor. (DBERR 2752)

You tried to use the EXECUTE statement on a cursor.

The only valid commands for a cursor are OPEN, CLOSE, FETCH, DESCRIBE, and DECLARE CURSOR.

Module !.!(!) is not a cursor. (DBERR 2753)

You tried to OPEN, CLOSE, FETCH, or DESCRIBE a section which was not defined with a DECLARE CURSOR statement.

A cursor must be declared using the DECLARE CURSOR statement before you refer to it in the other cursor commands.

Cursor !. ! (!) is not open. (DBERR 2754)

ALLBASE/SQL automatically rolled back your transaction causing the cursors to be closed

or

the cursor was never opened.

Insure that the cursor was opened.

Module !.!(!) already open. (DBERR 2755)

You attempted to OPEN the same cursor twice.

No action is necessary.

Cursor !.!(!) has no current tuple. (DBERR 2756)

You issued an UPDATE or DELETE statement with a CURRENT OF CURSOR clause without preceding it with a FETCH statement or you terminated the transaction between the FETCH and DELETE or UPDATE statement.

A FETCH statement must precede any DELETE or UPDATE WHERE CURRENT operation within the transaction.

Update column list not in cursor update column list. (DBERR 2757)

You tried to update a column which was not specified when the cursor was declared.

A column must be listed in the DECLARE CURSOR statement before an update operation can be performed on that column.

Update table different from cursor table. (DBERR 2758)

You tried to update a table which was not specified in the DECLARE CURSOR statement.

A table must be listed in the DECLARE CURSOR statement before it can be updated using the UPDATE statement with a CURRENT OF CURSOR clause.

Cursor has no current tuple. (DBERR 2759)

You issued an UPDATE or DELETE statement with a CURRENT OF CURSOR clause when the current tuple had already been deleted.

Modify your application so that no UPDATE or DELETE WHERE CURRENT is attempted once the current tuple has been deleted.

Null value detected and indicator variable not declared OR attempted to put null value into non-null column or result. (DBERR 2760)

A SELECT or FETCH statement had no corresponding indicator variable and a null value was fetched for an item

or

you attempted to put a null value into a non-null column using the INSERT or UPDATE statement by setting the indicator variable to a negative number.

or

You specified NOT NULL for a procedure result and a null value was fetched.

Modify your program to include indicator variables with columns that might contain null values

or

issue the INSERT or UPDATE statement again, specifying only non-null values for columns created with the NOT NULL option.

or

drop the procedure and recreate it, either omitting the NOT NULL option in the WITH RESULT clause, or modifying the procedure SELECT statements so that no null values will be retrieved.

Selectlist has ! items and host variable buffer has !. (DBERR 2762)

The number of select list items in a DECLARE CURSOR or a SELECT statement does not match the number of host variables in the corresponding FETCH or SELECT statement or the number of select list items in the SELECT statement does not match the number of host variables in the SELECT statement.

Modify your program so that the number of variables in the select list or the SELECT statement matches the number of host variables. Refer to the ALLBASE/SQL Reference Manual for additional information on these commands.

DISTINCT within aggregate functions cannot reference multiple column names. (DBERR 2763)

The SELECT statement contains more than one aggregate function containing the DISTINCT option and references more than one column.

Modify your statement so that it references only one column. Refer to the ALLBASE/SQL Reference Manual for additional information on the SELECT statement.

DISTINCT within an aggregate function cannot reference an expression. (DBERR 2764)

The SELECT statement contains an aggregate function containing the DISTINCT option and references a column containing computed values.

Modify your statement so that only raw columns are referenced. Refer to the ALLBASE/SQL Reference Manual for additional information on the SELECT statement.

DDL commands disabled. (DBERR 2765)

The DDL Enabled flag in the DBECon file was set to NO when you attempted to execute DDL (data definition language) commands.

STOP the DBEnvironment, use the SQLUtil ALTDBE command to set the DDL Enabled flag to YES, then START the DBEnvironment and proceed with data definition.

Unable to revalidate section while DDL commands are disabled. (DBERR 2766)

The DDL Enabled flag in the DBECon file was set to NO when ALLBASE/SQL encountered an invalid stored section.

STOP the DBEnvironment, use the SQLUtil ALTDBE command to set the DDL Enabled flag to YES, then START the DBEnvironment and run the application again.

Current tuple does not satisfy the predicate in the cursor definition. (DBERR 2768)

After you fetched the data, the data was updated by another transaction and no longer satisfies your cursor definition.

No action is necessary.

Cursor !.!(!) is not updatable. (DBERR 2769)

You tried to REFETCH or UPDATE using a cursor that is not updatable.

Make sure you declare the cursor FOR UPDATE in the DECLARE CUSOR statement.

INSERT rejected: FORMAT II INSERT cannot insert a table into itself. (DBERR 2770)

The table you specified as the target table in the INSERT statement was the same as one of the tables in the embedded SELECT statement.

Modify your command specifying a different target table or remove the target table from the embedded SELECT statement.