 |
» |
|
|
|
|  |  |
- 2420
- MESSAGE
INSERT rejected: Values do not match number of columns. (DBERR 2420) - CAUSE
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. - ACTION
Issue the INSERT statement again, specifying a valid number
of columns. Use the INFO command to get a list of columns in the
table.
- 2421
- MESSAGE
Column number exceeds number of SelectList items. (DBERR 2421) - CAUSE
The ORDER BY clause contained a number greater than the
number of select list items. - ACTION
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.
- 2422
- MESSAGE
Range violation on value !. Valid range is ! - !. (DBERR 2422) - CAUSE
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. - ACTION
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.
- 2423
- MESSAGE
Number of Selects in command exceeds maximum !. (DBERR 2423) - CAUSE
The maximum number of Selects in a command has been exceeded. - ACTION
Issue the command again, specifying the maximum number
or fewer.
- 2424
- MESSAGE
SelectList counts are not equal in UNION command. (DBERR 2424) - CAUSE
The number of columns in the individual select lists
in the UNION command are not the same. - ACTION
Issue the command again with an equal number of columns
in the select lists.
- 2425
- MESSAGE
UNION operation disallowed within a Nested Query. (DBERR 2425) - CAUSE
You tried to include a UNION operation in a nested
query. - ACTION
UNION of two nested queries is allowed but UNION cannot
be within a nested query.
- 2426
- MESSAGE
Tuple size exceeds maximum for UNION command ! bytes. (DBERR 2426) - CAUSE
Your select list size is greater than the maximum currently
allowed for a UNION command. - ACTION
Re-issue the command with a valid tuple size.
- 2428
- MESSAGE
Sort length of UNION exceeds maximum allowed ! bytes. (DBERR 2428) - CAUSE
The UNION command specifies a number of columns whose
total sort tuple length exceeds the maximum allowable. - ACTION
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.
- 2429
- MESSAGE
Sort length of ORDER BY/GROUP BY/DISTINCT/UNION exceeds maximum
allowed ! bytes. (DBERR 2429) - CAUSE
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. - ACTION
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.
- 2430
- MESSAGE
Invalid decimal precision ! - Allowed range is ! - !. (DBERR 2430) - CAUSE
The decimal precision you specified was not within
the valid range. - ACTION
Refer to the ALLBASE/SQL Reference Manual for
valid decimal precision.
- 2431
- MESSAGE
Invalid decimal column - Scale ! exceeds precision !. (DBERR 2431) - CAUSE
The decimal scale was greater than the precision
value. - ACTION
Refer to the ALLBASE/SQL Reference Manual for
valid decimal numbers.
- 2432
- MESSAGE
Invalid float precision !- Allowed range is ! - !. (DBERR 2432) - CAUSE
The float precision you specified was not within
the valid range. - ACTION
Refer to the ALLBASE/SQL Reference Manual for
valid float precision.
- 2433
- MESSAGE
Sort length of sort merge join exceeds maximum allowed ! bytes. (DBERR 2433) - CAUSE
The sort merge join query specifies a number of
columns whose total sort tuple length exceeds the maximum allowable. - ACTION
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.
- 2434
- MESSAGE
Invalid section number. Valid range is ! - !. (DBERR 2434) - CAUSE
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. - ACTION
Re-issue your command, specifying a value within
the valid range.
- 2435
- MESSAGE
Invalid transaction priority. Valid range is ! - !. (DBERR 2435) - CAUSE
You issued a BEGIN WORK with an invalid priority option. - ACTION
Reissue the BEGIN WORK with a priority within the valid
range.
- 2436
- MESSAGE
Invalid decimal parameter - Scale ! exceeds
precision !. (DBERR 2436) - CAUSE
The decimal scale was greater than the precision
value. - ACTION
Refer to the "Data Types" chapter in the ALLBASE/SQL Reference Guide for complete information about valid decimal values.
- 2437
- MESSAGE
Invalid decimal result - Scale ! exceeds precision !. (DBERR 2437) - CAUSE
The scale specified was greater than the precision specified
for a procedure result column. - ACTION
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.
- 2438
- MESSAGE
Length of result ! in procedure !.! exceeds ! bytes. (DBERR 2438) - CAUSE
The number of bytes you specified for a procedure
result column exceeded the maximum allowed. - ACTION
Issue the CREATE PROCEDURE statement again, specifying
a number of bytes no greater than the maximum.
- 2439
- MESSAGE
Length of result ! in procedure !.! below minimum ! bytes. (DBERR 2439) - CAUSE
You tried to create a procedure result column with
a length of 0 bytes. - ACTION
Issue the CREATE PROCEDURE statement again, specifying
a length of at least 1 byte.
- 2440
- MESSAGE
! should be ! to !. Number ! is invalid. (DBERR 2440) - CAUSE
The size you specified for one or more parameters
of the START DBE statement is invalid. - ACTION
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.
- 2449
- MESSAGE
TRANSFER OWNERSHIP OF MODULE is not supported. (DBERR 2449) - CAUSE
You specified the MODULE option of the TRANSFER OWNERSHIP
statement. However, the ownership of modules cannot be transferred. - ACTION
DROP the existing modules and preprocess the program with
the -o option.
- 2450
- MESSAGE
BEGIN WORK MULTI is not supported. (DBERR 2450) - CAUSE
You attempted to use the MULTI option for the BEGIN WORK
statement. - ACTION
You can have only one active transaction at a time.
Issue a COMMIT WORK or ROLLBACK WORK statement before beginning
the second transaction.
- 2452
- MESSAGE
Clustering index not allowed on table on which hash structure has already been defined. (DBERR 2452) - CAUSE
You tried to create a clustering B-tree index on
a table on which a hash structure already existed. - ACTION
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.
- 2453
- MESSAGE
Non-unique hash is not supported. (DBERR 2453) - CAUSE
You tried to create a table with a non-unique hash structure. - ACTION
Issue the CREATE TABLE statement again, including
the UNIQUE keyword with the HASH option.
- 2454
- MESSAGE
Operation not allowed on non-SQL table. (DBERR 2454) - CAUSE
You attempted an operation on a TurboIMAGE table. - ACTION
TurboIMAGE tables are read-only through ALLBASE/SQL.
- 2500
- MESSAGE
Cannot drop a non-empty DBEFileSet. (DBERR 2500) - CAUSE
You attempted to DROP a DBEFileSet which has DBEFiles
associated with it. - ACTION
Before dropping the DBEFileSet, drop the DBEFiles
then remove them. Remember that the DBEFiles must be empty before
they can be dropped.
- 2501
- MESSAGE
DBEFileSet has no DBEFiles. (DBERR 2501) - CAUSE
You created a table in an empty DBEFileSet and then tried
to INSERT into that table. - ACTION
ADD a DBEFile to the DBEFileSet before attempting
an INSERT statement.
- 2502
- MESSAGE
! space exhausted in DBEFileSet !. (DBERR 2502) - CAUSE
This message can have several meanings as follows: All the space is exhausted in a DBEFileset if no expandable
DBEFiles are available. All fixed-length DBEFiles in the DBEFileSet have
run out of space, and all expandable DBEFiles have been fully expanded.
The first parameter is the setting for the DBEFile's TYPE attribute.
Valid settings are INDEX, TABLE, and MIXED. - ACTION
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.
- 2503
- MESSAGE
DBEFile not empty. (DBERR 2503) - CAUSE
You attempted to REMOVE a non-empty DBEFile from
its DBEFileSet. - ACTION
The DBEFile must be empty before it can be removed
from the DBEFileSet.
- 2505
- MESSAGE
DBEFile size must be between ! and ! pages. (DBERR 2505) - CAUSE
The file size you specified in the CREATE DBEFILE statement
was not within the valid range. - ACTION
Issue the CREATE DBEFILE statement again, specifying a
valid file size.
- 2506
- MESSAGE
TempSpace file size limit must be between ! and ! pages. (DBERR 2506) - CAUSE
The file size you specified in the CREATE TEMPSPACE statement
was not within the valid range. - ACTION
Issue the CREATE TEMPSPACE statement again, specifying
a valid file size.
- 2507
- MESSAGE
DBEFile must be empty or new type must be mixed. (DBERR 2507) - CAUSE
You attempted to ALTER a non-empty DBEFile to a
type other than mixed. - ACTION
The type of a non-empty DBEFile can be changed from TABLE
or INDEX to MIXED. No other changes are allowed.
- 2508
- MESSAGE
DBEFileSet has no DBEFile of required DBEFile type. (DBERR 2508) - CAUSE
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. - ACTION
Ask your database administrator to CREATE and ADD the
appropriate DBEFiles.
- 2509
- MESSAGE
Index uniqueness or UNIQUE/PRIMARY KEY constraint violated. (DBERR 2509) - CAUSE
You tried to insert a duplicate key value into a
column used in a unique index or a unique constraint. - ACTION
Issue the INSERT or UPDATE statement again without the
duplicate row.
- 2510
- MESSAGE
Table is read only. (DBERR 2510) - CAUSE
You tried a LOCK or WRITE operation (DROP, DELETE, INSERT,
LOCK TABLE, UPDATE, UPDATE STATISTICS) on a read only table. - ACTION
No action is necessary. These operations cannot
be performed on SYSTEM.CALL, SYSTEM.ACCOUNT, SYSTEM.USER, SYSTEM.COUNTER,
or SYSTEM.TRANSACTION.
- 2511
- MESSAGE
User ! does not exist. (DBERR 2511) - CAUSE
The DBEUserId you specified in the TERMINATE USER or
RESET SYSTEM.ACCOUNT command is not currently connected to the DBEnvironment. - ACTION
Issue the command again, specifying a valid userid.
- 2512
- MESSAGE
Session ID ! does not exist. (DBERR 2512) - CAUSE
You attempted to terminate a session ID that does
not exist, or you do not have the authority to terminate it. - ACTION
Check that a valid session ID was used. If the session
ID is valid, have your DBA issue the statement.
- 2513
- MESSAGE
Number of primary pages must be between ! and !. (DBERR 2513) - CAUSE
You specified a number of primary pages for the
hash in the CREATE TABLE statement which was not within the valid
range. - ACTION
Issue the CREATE TABLE statement again, specifying
a valid number of primary pages.
- 2514
- MESSAGE
Hash key uniqueness or UNIQUE/PRIMARY KEY constraint violated. (DBERR 2514) - CAUSE
You tried to insert a duplicate key value into a
column used in a unique hash structure, which might be supporting
a unique constraint. - ACTION
Issue the INSERT statement again without the duplicate row.
- 2515
- MESSAGE
DBEFile is currently associated with a DBEFileSet. (DBERR 2515) - CAUSE
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. - ACTION
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.
- 2516
- MESSAGE
This table already has a clustering index. (DBERR 2516) - CAUSE
When you use the CREATE INDEX statement, no more than
one index per table can have the clustering attribute. - ACTION
Drop the existing clustering index or create the
new index without the clustering attribute.
- 2518
- MESSAGE
DBEFile in use for hash. (DBERR 2518) - CAUSE
You tried to DROP or ALTER a DBEFile that is allocated for
hash table data. - ACTION
First DROP the hash table. Then, the DBEFile may
be DROPped or ALTERed.
- 2519
- MESSAGE
Exceeded maximum number of DBEFiles for hash space (!). (DBERR 2519) - CAUSE
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. - ACTION
Create additional DBEFiles large enough that the
primary pages for the hash table can be allocated using 16 or fewer DBEFiles.
- 2520
- MESSAGE
Not enough space in DBEFileset for hash primary pages. (DBERR 2520) - CAUSE
There is not enough space in the empty table or
mixed DBEFiles in the DBEFileSet specified for the number of primary
pages specified. - ACTION
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.
- 2521
- MESSAGE
Maximum size for DBEFile expansion exceeds ! pages. (DBERR 2521) - CAUSE
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. - ACTION
Make sure the maximum DBEFile size specified is
within the system limit.
- 2522
- MESSAGE
DBEFile INCREMENT size must be between ! and ! pages. (DBERR 2522) - CAUSE
The size you specified in the INCREMENT clause for DBEFile
expansion is not within the range. - ACTION
Specify a valid INCREMENT size for the corresponding DBEFile.
- 2523
- MESSAGE
Maximum size ! pages for DBEFile expansion is less than the initial size ! pages. (DBERR 2523) - CAUSE
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. - ACTION
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.
- 2524
- MESSAGE
Connection ID ! does not exist. (DBERR 2524) - CAUSE
The Connection ID specified does not exist. - ACTION
Use a valid Connection ID.
- 2525
- MESSAGE
Transaction ID ! does not exist. (DBERR 2525) - CAUSE
The Transaction ID specified does not exist. - ACTION
Use a valid Transaction ID.
- 2526
- MESSAGE
Attempting to terminate current query. (DBERR 2526) - CAUSE
The current query is being terminated. - ACTION
Take appropriate action for this query.
- 2527
- MESSAGE
There is no transaction for Connection ID !. (DBERR 2527) - CAUSE
There was an attempt to terminate a transaction
for the specified Connection ID, but no transaction was in progress. - ACTION
No action is required.
- 2528
- MESSAGE
Attempting to terminate persistent transaction. (DBERR 2528) - CAUSE
There is an attempt to terminate a persistent transaction. - ACTION
The SQLUtil command cannot be used to terminate
a persistent transaction.
- 2529
- MESSAGE
The user termination level does not allow this type of termination. (DBERR 2529) - CAUSE
The user attempted to perform an unauthorized termination. - ACTION
A user can terminate a transaction or query if the
user is the owner or the user has DBA authority. No action required.
- 2530
- MESSAGE
Query was aborted externally. (DBERR 2530) - CAUSE
The query was aborted by an external process. - ACTION
Resume the query at an appropriate time.
- 2600
- MESSAGE
Integer overflow on operation !. (DBERR 2600) - CAUSE
The result of an integer arithmetic operation within
an expression was too big for the hardware to accommodate. - ACTION
Try to modify your expression so that divisions
occur before multiplications or break the expression into multiple
expressions.
- 2601
- MESSAGE
Integer divide by zero. (DBERR 2601) - CAUSE
The result of an arithmetic operation within an
expression caused an integer value to be divided by zero. - ACTION
Look at your data to find where this error occurred
and make any necessary changes to your expression.
- 2602
- MESSAGE
Extended precision overflow on operation !. (DBERR 2602) - CAUSE
The result of a float arithmetic operation within
an expression was too big for the hardware to accommodate. - ACTION
Try to modify your expression so that divisions
occur before multiplications or break the expression into multiple
expressions.
- 2603
- MESSAGE
Extended precision underflow on operation !. (DBERR 2603) - CAUSE
The result of a float arithmetic operation within
an expression was too small for the hardware to accommodate. - ACTION
Try to modify your expression so that multiplications occur
before divisions or break the expression into multiple expressions.
- 2604
- MESSAGE
Extended precision divide by zero. (DBERR 2604) - CAUSE
The result of an arithmetic operation within an
expression caused an extended precision value to be divided by zero. - ACTION
Look at your data to find where this error occurred
and make any necessary changes.
- 2605
- MESSAGE
Packed decimal overflow on operation !. (DBERR 2605) - CAUSE
The result of an intermediate decimal operation
was too big for the hardware to accommodate. - ACTION
Try to modify your expression so that divisions
occur before multiplications or break the expression into multiple
expressions.
- 2606
- MESSAGE
Invalid decimal digit in operation !. (DBERR 2606) - CAUSE
The decimal number you included through the host variable
in a COBOL program was not valid. - ACTION
Correct the decimal so that it is within the range
of 0 through 9 and contains either a + or - sign.
- 2607
- MESSAGE
Packed decimal divide by zero. (DBERR 2607) - CAUSE
The result of an arithmetic operation within an
expression caused a packed decimal value to be divided by zero. - ACTION
Look at your data to find where this error occurred
and make any necessary changes.
- 2609
- MESSAGE
Incompatible data types ! and ! in expression. (DBERR 2609) - CAUSE
You attempted to mix numeric and character data
types in an expression in the select list, the WHERE clause, or
the SET clause. - ACTION
Issue the command again, specifying either numeric
or character data only.
- 2610
- MESSAGE
Operator ! invalid for data type !. (DBERR 2610) - CAUSE
You attempted to perform an arithmetic operation
on char or varchar data, or attempted the LIKE predicate on numeric
data. - ACTION
Issue the command again using only appropriate operators
on data types.
- 2615
- MESSAGE
Datetime value contains a field greater than valid range
allowed. (DBERR 2615) - CAUSE
You tried to insert a datetime value which was not
valid. - ACTION
Verify that all fields of all datetime literals
are within the valid range.
- 2616
- MESSAGE
Datetime value contains a field less than valid range allowed. (DBERR 2616) - CAUSE
You tried to insert a datetime value which was not
valid. - ACTION
Verify that all fields of all datetime literals
are within the valid range.
- 2617
- MESSAGE
Datetime data value does not match default format specification. (DBERR 2617) - CAUSE
You tried to insert a datetime value which did not
meet the default specification criteria of "YYYY-MM-DD HH:MI:SS.FFF." - ACTION
Verify that all fields of all datetime literals
match the default format specification.
- 2618
- MESSAGE
ALLBASE/SQL internal error in datetime conversion routine. (DBERR 2618) - CAUSE
ALLBASE/SQL internal software problem. - ACTION
Contact your HP Service Representative or Response Center.
- 2619
- MESSAGE
Invalid date entered, February 29th invalid for non-leap year. (DBERR 2619) - CAUSE
You tried to insert a datetime value which was not
valid. - ACTION
Enter the correct date.
- 2620
- MESSAGE
Result of DATE/TIME arithmetic exceeds maximum value allowed. (DBERR 2620) - CAUSE
The arithmetic produced a value greater than the maximum
allowed. - ACTION
Verify that the requested arithmetic should produce
a result which exceeds maximum values specified.
- 2621
- MESSAGE
Result of DATE/TIME arithmetic less than minimum value allowed. (DBERR 2621) - CAUSE
The arithmetic produced a value less than the minimum allowed. - ACTION
Verify that the requested arithmetic should produce
a result which is less than the minimum values specified.
- 2622
- MESSAGE
Size of datetime literal less than valid default size. (DBERR 2622) - CAUSE
You tried to insert a datetime value of incorrect
length. - ACTION
Verify that all datetime literals in the query are
of the correct size.
- 2623
- MESSAGE
Date value contains a field greater than valid range allowed. (DBERR 2623) - CAUSE
You tried to insert a date value which was not valid. - ACTION
Verify that all fields of all date literals are
within the valid range.
- 2624
- MESSAGE
Date value contains a field less than valid range allowed. (DBERR 2624) - CAUSE
You tried to insert a date value which was not valid. - ACTION
Verify that all fields of all date literals are
within the valid range.
- 2625
- MESSAGE
Date data value does not match default format
specification. (DBERR 2625) - CAUSE
You tried to insert a date value which did not meet
the default specification criteria. - ACTION
Verify that all datetime literals in the query are
specified in the default specification "YYYY-MM-DD."
- 2626
- MESSAGE
Size of date literal less than valid default size. (DBERR 2626) - CAUSE
You tried to insert a date value of incorrect length. - ACTION
Verify that all date literals in the query are of
the correct size.
- 2627
- MESSAGE
Time value contains a field greater than valid range allowed. (DBERR 2627) - CAUSE
You tried to insert a time value which was not valid. - ACTION
Verify that all fields of all time literals are
within the valid range.
- 2628
- MESSAGE
Time value contains a field less than valid range allowed. (DBERR 2628) - CAUSE
You tried to insert a time value which was not valid. - ACTION
Verify that all fields of all time literals are
within the valid range.
- 2629
- MESSAGE
Time data value does not match default format
specification. (DBERR 2629) - CAUSE
You tried to insert a time value which did not meet
the default specification "HH:MI:SS." - ACTION
Verify that all time literals match the default
format specification.
- 2630
- MESSAGE
Size of time literal less than valid default size. (DBERR 2630) - CAUSE
You tried to insert a time value of incorrect length. - ACTION
Verify that all time literals in the query are of
the correct size.
- 2631
- MESSAGE
Interval value contains a field greater than valid range allowed. (DBERR 2631) - CAUSE
You tried to insert an interval value which was
not valid. - ACTION
Verify that all fields of all interval literals
are within the valid range.
- 2632
- MESSAGE
Interval value contains a field less than valid range allowed. (DBERR 2632) - CAUSE
You tried to insert an interval value which was
not valid. - ACTION
Verify that all fields of all interval literals
are within the valid range.
- 2633
- MESSAGE
Interval data value does not match default format specification. (DBERR 2633) - CAUSE
You tried to insert an interval value which did
not meet the default specification criteria. - ACTION
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.
- 2634
- MESSAGE
Size of interval literal less than valid default size. (DBERR 2634) - CAUSE
You tried to insert an interval value of incorrect
length. - ACTION
Verify that all interval literals in the query are
of the correct size.
- 2635
- MESSAGE
Real precision overflow on operation !. (DBERR 2635) - CAUSE
The result of a real arithmetic operation within
an expression was too big for the hardware to accommodate. - ACTION
Try to modify your expression to convert the real
values in it to floats or to have a target host variable of type
FLOAT.
- 2636
- MESSAGE
Real precision underflow on operation !. (DBERR 2636) - CAUSE
The result of a real arithmetic operation within
an expression was too small for the hardware to accommodate. - ACTION
Try to modify your expression to convert the real
values in it to floats or to have a target host variable of type
FLOAT.
- 2637
- MESSAGE
Format specification exceeds maximum length (! bytes). (DBERR 2637) - CAUSE
You specified a date/time format length which exceeds
the maximum length of 72 bytes. - ACTION
Issue the command again with the length less than
72 bytes.
- 2638
- MESSAGE
End of format specification detected before parsing end of datetime literal. (DBERR 2638) - CAUSE
Datetime literal does not match format specification
given. Extra characters exist in datetime literal after parsing
end of format specification. - ACTION
Ensure the compatibility between the format specification and
datetime literal specified in the datetime input function.
- 2639
- MESSAGE
Invalid format specification in second parameter of datetime function. (DBERR 2639) - CAUSE
A unit within the format specification is not a
valid unit. - ACTION
Re-issue the command with a format specification.
- 2641
- MESSAGE
Redundant fields specified in format specification. (DBERR 2641) - CAUSE
A unit in the format specification was specified
twice, or two units which contain identical units. - ACTION
Re-issue the command with a valid format specification.
- 2642
- MESSAGE
Invalid data type for second parameter of datetime function. (DBERR 2642) - CAUSE
Data type of second parameter is not valid. - ACTION
Please check the documentation for valid format
types.
- 2643
- MESSAGE
Format specification contains an invalid unit for data type !. (DBERR 2643) - CAUSE
A valid unit was specified in the format specification,
but it is not valid for this datetime type. - ACTION
Please check the documentation for valid format
types for this datetime data type.
- 2644
- MESSAGE
Datetime input function cannot parse input parameters. (DBERR 2644) - CAUSE
When parsing datetime literal, invalid data was
detected. - ACTION
Check validity of datetime literal in first parameter
of datetime input function.
- 2645
- MESSAGE
Day of week specified does not match date supplied. (DBERR 2645) - CAUSE
Alphabetic day of week specified incorrect for date
literal specified. - ACTION
Re-issue command with valid datetime literal.
- 2646
- MESSAGE
End of datetime literal detected before parsing end of format specification. (DBERR 2646) - CAUSE
Format specification does not match datetime literal. - ACTION
Re-issue command with correct input to datetime
input function.
- 2647
- MESSAGE
Datetime literal contains a value outside the valid range for a format specified. (DBERR 2647) - CAUSE
A unit in datetime literal is not within boundary
of the unit values allowed. - ACTION
Issue command with correct values for units specified
in format specification.
- 2650
- MESSAGE
Invalid length in VARCHAR. (DBERR 2650) - CAUSE
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. - ACTION
Make sure that all VARCHAR host variables are properly initialized.
- 2651
- MESSAGE
DEFAULT literal type ! is not compatible with the
corresponding column data type !. (DBERR 2651) - CAUSE
The data type of the literal is not compatible with
the one specified for the corresponding column. - ACTION
Define a valid default value for the corresponding
column.
- 2652
- MESSAGE
DEFAULT ! is not compatible with the corresponding column data type !. (DBERR 2652) - CAUSE
You specified a DEFAULT current function, USER,
or NULL, which is not compatible with the one specified for the
corresponding column. - ACTION
Define a valid default value for the corresponding
column.
- 2653
- MESSAGE
Non-supported DEFAULT value type !. (DBERR 2653) - CAUSE
You specified a DEFAULT value which is not a constant,
a current function, USER, or NULL. - ACTION
Define a valid default value for the corresponding
column.
- 2654
- MESSAGE
Data type ! invalid for the starting position of SUBSTRING function. (DBERR 2654) - CAUSE
The StartPosition parameter of the SUBSTRING function is
not an integer constant or expression. - ACTION
Change the StartPosition parameter to an integer constant
or expression.
- 2655
- MESSAGE
Data type ! invalid for the substring length of SUBSTRING function. (DBERR 2655) - CAUSE
The Length parameter of the SUBSTRING function is
not an integer constant or expression. - ACTION
Change the Length parameter to an integer constant
or expression.
- 2656
- MESSAGE
Source string must contain numeric value. (DBERR 2656) - CAUSE
The source character string of the CAST function
contains invalid characters for a numeric expression. - ACTION
Make sure the source character string contains an appropriate
representation of a numeric value with no extraneous characters
added.
- 2657
- MESSAGE
CAST target data type too small. (DBERR 2657) - CAUSE
The size in bytes of the specified target data type
is too small to hold the value being converted. - ACTION
Specify a larger target data type.
- 2658
- MESSAGE
Numeric/Binary conversion must be of equal length. (DBERR 2658) - CAUSE
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. - ACTION
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.
- 2659
- MESSAGE
Date/Binary conversion must be of equal length. (DBERR 2659) - CAUSE
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. - ACTION
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.
- 2660
- MESSAGE
TID/Binary conversion must be of equal length. (DBERR 2660) - CAUSE
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. - ACTION
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.
- 2661
- MESSAGE
Invalid TID format. (DBERR 2661) - CAUSE
The character string being converted to a TID data
type was not properly formatted. - ACTION
The correct syntax for a character string representation
of a TID is: {0:} filenumber:pagenumber:slot - where:
filenumber is the DBEfile number (0-32767) - pagenumber is the page number (0-16777215)
slot is the slot number (0-255)
- 2662
- MESSAGE
Data type ! invalid for source string in TRIM/LTRIN/RTRIM
functions.(DBERR 2662) - CAUSE
The source string which is to be trimmed is not
of type CHAR or VARCHAR. - ACTION
Change the source string parameter to a string expression.
- 2663
- MESSAGE
Data type ! invalid for the starting position parameter
in INSTR function.(DBERR 2663) - CAUSE
The starting position parameter in INSTR function
is not an integer expression. - ACTION
Change the starting postion parameter to an integer expression.
- 2664
- MESSAGE
Data type ! invalid for the number of occurance parameter in INSTR function.(DBERR 2664) - CAUSE
The number of occurance parameter in INSTR function
is not an integer expression. - ACTION
Change the number of occurance parameter in INSTR function
to an integer expression.
- 2665
- MESSAGE
Data type ! invalid for the search string in POSITION/INSTR function.(DBERR 2665) - CAUSE
The search string parameter in POSITION/INSTR is
not an expression of type CHAR, VARCHAR, BINARY, VARBINARY, LONG
BINARY or LONG VARBINARY. - ACTION
Change the search string parameter in POSITION/INSTR to
appropriate type.
- 2700
- MESSAGE
INSERT/UPDATE/DELETE disallowed on a join. (DBERR 2700) - CAUSE
You attempted to INSERT, UPDATE, or DELETE on a multiple
table view. - ACTION
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.
- 2701
- MESSAGE
INSERT/UPDATE disallowed on virtual column (!). (DBERR 2701) - CAUSE
You attempted to INSERT or UPDATE a computed column
in a view. - ACTION
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.
- 2702
- MESSAGE
INSERT/UPDATE/DELETE disallowed on group operation. (DBERR 2702) - CAUSE
You attempted to INSERT, UPDATE, or DELETE rows
via a view which contained a GROUP BY clause in its definition. - ACTION
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.
- 2703
- MESSAGE
INSERT/UPDATE/DELETE disallowed on ORDER BY. (DBERR 2703) - CAUSE
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. - ACTION
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.
- 2705
- MESSAGE
Illegal reference to column ! in group operation. (DBERR 2705) - CAUSE
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. - ACTION
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.
- 2706
- MESSAGE
INSERT/UPDATE/DELETE disallowed on DISTINCT operation. (DBERR 2706) - CAUSE
UPDATE, INSERT, and DELETE operations through a view
are not allowed if the view definition involves a distinct clause. - ACTION
Perform the UPDATE, INSERT, or DELETE operation
on the base table or re-create the view without the DISTINCT clause.
- 2707
- MESSAGE
UPDATE/DELETE disallowed on a cursor containing a subquery. (DBERR 2707) - CAUSE
You attempted to UPDATE or DELETE rows accessed through
a cursor which contained a subquery in its definition. - ACTION
Perform the UPDATE or DELETE only through a cursor which
does not contain a subquery.
- 2708
- MESSAGE
UPDATE/DELETE disallowed with subquery containing
update/delete table. (DBERR 2708) - CAUSE
You attempted to UPDATE or DELETE through a view
or with a search condition containing a subquery which references
the target table. - ACTION
Perform the UPDATE or DELETE only through views with
search conditions which do not reference the target table in any
subqueries.
- 2709
- MESSAGE
UPDATE/DELETE disallowed on UNION. (DBERR 2709) - CAUSE
You attempted to UPDATE or DELETE through a cursor containing
a UNION. - ACTION
Perform the UPDATE or DELETE only through cursors not
containing UNIONs.
- 2710
- MESSAGE
INSERT or FORMAT II INSERT disallowed on a view referencing
the insert table in a subquery. (DBERR 2710) - CAUSE
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. - ACTION
Insert directly through the base table, or use a
view not containing subqueries which reference the same table as the
view.
- 2711
- MESSAGE
Qualifier !.! (column !) is different from input table. (DBERR 2711) - CAUSE
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. - ACTION
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.
- 2712
- MESSAGE
Hash key columns may not be updated. (DBERR
2712) - CAUSE
You tried to update the value of a column included
in the key for a hash. - ACTION
DELETE the tuple with the old key column value.
Then, INSERT a new tuple with the new key column value.
- 2716
- MESSAGE
User ! does not have authority to GENPLAN on table/view !.!.(!) (DBERR 2716) - CAUSE
You do not have run authority to GENPLAN on a specified section. - ACTION
Contact your database administrator to get the required authority
or sign on as a user who does have the required authority.
- 2717
- MESSAGE
The specified section !.!(!) is not a SELECT, UPDATE, DELETE or type II INSERT statement. (DBERR 2717) - CAUSE
The specified section you included is not an allowed statement
for GENPLAN. - ACTION
Check the source file to find the right section
number.
- 2718
- MESSAGE
Optimizer did not generate an access plan for the query. (DBERR 2718) - CAUSE
Internal Error. - ACTION
Record as much information as possible and contact
your HP Service Representative or Response Center.
- 2719
- MESSAGE
User ! does not have authority to GENPLAN on table/view !.!. (DBERR 2719) - CAUSE
You do not have the required authority to execute GENPLAN
on the named table or view. - ACTION
Contact your database administrator to obtain the required
authority or sign on as a user who does have the required authority.
- 2720
- MESSAGE
INSERT/UPDATE/DELETE disallowed on system tables (!.!). (DBERR 2720) - CAUSE
You attempted to INSERT, UPDATE or DELETE to a system
table. - ACTION
Re-issue the statement on a non-system table.
- 2724
- MESSAGE
Command ! is not allowed for views (!.!). (DBERR 2724) - CAUSE
You specified a command (ALTER TABLE, UPDATE STATISTICS,
LOCK TABLE) that cannot be performed on a view. - ACTION
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.
- 2725
- MESSAGE
Use DROP VIEW to drop view !.!. (DBERR 2725) - CAUSE
You attempted to drop a view using the DROP TABLE statement. - ACTION
Use the DROP VIEW statement to drop a view.
- 2726
- MESSAGE
Use DROP TABLE to drop table !.!. (DBERR 2726) - CAUSE
You attempted to drop a table using the DROP VIEW statement. - ACTION
Use the DROP TABLE statement to drop a table.
- 2730
- MESSAGE
Column ! does not accept nulls. (DBERR 2730) - CAUSE
You specified the NULL keyword for a non-null column
in the INSERT or UPDATE statement. - ACTION
Issue the command again, specifying a value for
all non-null columns.
- 2731
- MESSAGE
Reset command not valid for table !.!. (DBERR 2731) - CAUSE
You cannot issue the RESET statement on the specified table. - ACTION
No action is necessary. The only valid tables for
the RESET statement are SYSTEM.COUNTER and SYSTEM.ACCOUNT.
- 2732
- MESSAGE
Invalid number of columns in view column list. (DBERR 2732) - CAUSE
The number of columns in the CREATE VIEW statement did
not match the number of columns in the SELECT statement for the
view. - ACTION
Issue the command again using the same number of columns
in both the CREATE VIEW statement and the SELECT statement.
- 2740
- MESSAGE
Invalid savepoint number. (DBERR 2740) - CAUSE
The ROLLBACK WORK statement included a non-existent
savepoint. - ACTION
Issue the command again, specifying a valid savepoint number.
Refer to the ALLBASE/SQL Reference Manual for
additional information on the ROLLBACK WORK statement.
- 2741
- MESSAGE
Archive not begun. (DBERR 2741) - CAUSE
You attempted to COMMIT ARCHIVE without a preceding
BEGIN ARCHIVE statement. - ACTION
Issue the BEGIN ARCHIVE statement first followed
by the COMMIT ARCHIVE statement.
- 2742
- MESSAGE
Archive already begun. (DBERR 2742) - CAUSE
The BEGIN ARCHIVE statement was issued twice. - ACTION
No action is necessary.
- 2743
- MESSAGE
Archive checkpoint not found. (DBERR 2743) - CAUSE
The checkpoint was not found. - ACTION
Review the syntax for CHECKPOINT statement.
- 2744
- MESSAGE
ROLLBACK WORK TO savepointnumber when you have cursors
opened with KEEP CURSOR option. (DBERR 2744) - CAUSE
You opened a cursor with the KEEP CURSOR option
and you are trying to use the SAVEPOINT option of the ROLLBACK WORK
statement. - ACTION
Revise the program to open the cursor without the
KEEP CURSOR option, or eliminate the TO SAVEPOINT clause.
- 2749
- MESSAGE
Procedure cursor !.!(!) has no current result set. (DBERR 2749) - CAUSE
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). - ACTION
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.
- 2750
- MESSAGE
Module !.!(!) has DBEFileSet error. (DBERR 2750) - CAUSE
You tried to use DECLARE CURSOR or to PREPARE a section
in a non-existent DBEFileSet. - ACTION
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.
- 2752
- MESSAGE
Module !.!(!) is a cursor. (DBERR 2752) - CAUSE
You tried to use the EXECUTE statement on a cursor. - ACTION
The only valid commands for a cursor are OPEN, CLOSE, FETCH,
DESCRIBE, and DECLARE CURSOR.
- 2753
- MESSAGE
Module !.!(!) is not a cursor. (DBERR 2753) - CAUSE
You tried to OPEN, CLOSE, FETCH, or DESCRIBE a section
which was not defined with a DECLARE CURSOR statement. - ACTION
A cursor must be declared using the DECLARE CURSOR statement
before you refer to it in the other cursor commands.
- 2754
- MESSAGE
Cursor !. ! (!) is not open. (DBERR 2754) - CAUSE
ALLBASE/SQL automatically rolled back your transaction causing
the cursors to be closed or the cursor was never opened. - ACTION
Insure that the cursor was opened.
- 2755
- MESSAGE
Module !.!(!) already open. (DBERR 2755) - CAUSE
You attempted to OPEN the same cursor twice. - ACTION
No action is necessary.
- 2756
- MESSAGE
Cursor !.!(!) has no current tuple. (DBERR 2756) - CAUSE
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. - ACTION
A FETCH statement must precede any DELETE or UPDATE
WHERE CURRENT operation within the transaction.
- 2757
- MESSAGE
Update column list not in cursor update column list. (DBERR 2757) - CAUSE
You tried to update a column which was not specified
when the cursor was declared. - ACTION
A column must be listed in the DECLARE CURSOR statement
before an update operation can be performed on that column.
- 2758
- MESSAGE
Update table different from cursor table. (DBERR 2758) - CAUSE
You tried to update a table which was not specified
in the DECLARE CURSOR statement. - ACTION
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.
- 2759
- MESSAGE
Cursor has no current tuple. (DBERR 2759) - CAUSE
You issued an UPDATE or DELETE statement with a CURRENT
OF CURSOR clause when the current tuple had already been deleted. - ACTION
Modify your application so that no UPDATE or DELETE WHERE
CURRENT is attempted once the current tuple has been deleted.
- 2760
- MESSAGE
Null value detected and indicator variable not declared OR attempted
to put null value into non-null column or result. (DBERR 2760) - CAUSE
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. - ACTION
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.
- 2762
- MESSAGE
Selectlist has ! items and host variable buffer has !. (DBERR 2762) - CAUSE
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. - ACTION
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.
- 2763
- MESSAGE
DISTINCT within aggregate functions cannot reference multiple column
names. (DBERR 2763) - CAUSE
The SELECT statement contains more than one aggregate function
containing the DISTINCT option and references more than one column. - ACTION
Modify your statement so that it references only
one column. Refer to the ALLBASE/SQL Reference Manual for
additional information on the SELECT statement.
- 2764
- MESSAGE
DISTINCT within an aggregate function cannot reference an expression. (DBERR 2764) - CAUSE
The SELECT statement contains an aggregate function containing
the DISTINCT option and references a column containing computed
values. - ACTION
Modify your statement so that only raw columns are referenced.
Refer to the ALLBASE/SQL Reference Manual for
additional information on the SELECT statement.
- 2765
- MESSAGE
DDL commands disabled. (DBERR 2765) - CAUSE
The DDL Enabled flag in the DBECon file was set
to NO when you attempted to execute DDL (data definition language)
commands. - ACTION
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.
- 2766
- MESSAGE
Unable to revalidate section while DDL commands are disabled. (DBERR 2766) - CAUSE
The DDL Enabled flag in the DBECon file was set
to NO when ALLBASE/SQL encountered an invalid stored section. - ACTION
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.
- 2768
- MESSAGE
Current tuple does not satisfy the predicate in the
cursor definition. (DBERR 2768) - CAUSE
After you fetched the data, the data was updated
by another transaction and no longer satisfies your cursor definition. - ACTION
No action is necessary.
- 2769
- MESSAGE
Cursor !.!(!) is not updatable. (DBERR 2769) - CAUSE
You tried to REFETCH or UPDATE using a cursor that
is not updatable. - ACTION
Make sure you declare the cursor FOR UPDATE in the DECLARE
CUSOR statement.
- 2770
- MESSAGE
INSERT rejected: FORMAT II INSERT cannot insert a table
into itself. (DBERR 2770) - CAUSE
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. - ACTION
Modify your command specifying a different target
table or remove the target table from the embedded SELECT statement.
- 2771
- MESSAGE
KEEP CURSOR with NOLOCKS is not supported on
NON-UPDATABLE CURSOR. (DBERR 2771) - CAUSE
You specified the KEEP CURSOR WITH NOLOCKS option
for a cursor which was declared as SELECT...ORDER BY or SELECT DISTINCT.
These operations need to build temporary tables, and if KEEP CURSOR
WITH NOLOCKS is in effect, the consistency between permanent and
temporary tables cannot be guaranteed between transactions. - ACTION
Revise the program to open the cursor with the KEEP CURSOR
WITH LOCKS option.
- 2772
- MESSAGE
Cursor !.!(!) containing SUBQUERY is not allowed in the REFETCH command. (DBERR 2772) - CAUSE
You attempted to perform a REFETCH on a cursor containing
a subquery. - ACTION
REFETCH cannot be done on cursors containing subqueries.
Either remove the subquery from the cursor, or do not perform REFETCH
on that cursor.
- 2773
- MESSAGE
Multiple-rows operation is NOT allowed in the REFETCH command. (DBERR 2773) - CAUSE
You specified more than one record in the REFETCH statement. - ACTION
Make sure to specify only one record for the REFETCH statement.
- 2774
- MESSAGE
Escape character in LIKE pattern must be followed by escape character, underscore, or percent. (DBERR 2774) - CAUSE
There is an escape character in a LIKE predicate
pattern that is not followed by an escape character, underscore,
or percent. - ACTION
Change the pattern to a legal pattern.
- 2775
- MESSAGE
Escape character must be a single character. (DBERR 2775) - CAUSE
You specified a multi-character string for the escape pattern,
or passed in a host variable containing more than a single character. - ACTION
Correct the specification of the escape string to
be a single character, or make sure that the host variable is set
to blanks after the escape character.
- 2776
- MESSAGE
Dynamic parameters as both operands of a single binary
operator disallowed. (DBERR 2776) - CAUSE
You specified dynamic parameters for both operands
of an arithmetic or comparison operator. - ACTION
Modify your statement to not specify dynamic parameters for
both operands of the arithmetic or comparison operator.
- 2777
- MESSAGE
Dynamic parameter as the operand of a unary arithmetic operator disallowed. (DBERR 2777) - CAUSE
You specified a dynamic parameter in a NULL predicate
or a minus sign is specified in front of the dynamic parameter. - ACTION
Modify your statement to not contain a dynamic parameter
in a NULL predicate nor a minus sign in front of a dynamic parameter.
- 2778
- MESSAGE
Dynamic parameter in the SELECT list disallowed. (DBERR 2778) - CAUSE
You specified a dynamic parameter in the SELECT
list. - ACTION
Modify your statement to not contain a dynamic parameter
in a SELECT list.
- 2779
- MESSAGE
TID data type is not supported. (DBERR 2779) - CAUSE
You specified a column of TID data type in the CREATE TABLE
or ALTER TABLE statement. There is no TID data type. - ACTION
Check and modify the statement.
- 2780
- MESSAGE
Psuedotable can not be updated. (DBERR 2780) - CAUSE
You attempted to perform an update on a system pseudotable. - ACTION
Check that the correct table name has been specified.
- 2781
- MESSAGE
Illegal reference to TID function in group operation. (DBERR 2781) - CAUSE
Within a single query block, you cannot specify
the GROUP BY clause when using the TID function in the select list. - ACTION
Check and modify the command.
- 2782
- MESSAGE
TID function is not allowed for the pseudotable (!.!). (DBERR 2782) - CAUSE
The parameter in the TID function is a system pseudotable. - ACTION
Check and modify the command.
- 2783
- MESSAGE
TID function is not allowed for the non-updatable view (!.!). (DBERR 2783) - CAUSE
The parameter in the TID function is not an updatable view. - ACTION
Check and modify the command.
- 2784
- MESSAGE
DDL statement not allowed in PREPARE REPEAT command. (DBERR 2784) - CAUSE
Data definition language statements (CREATE TABLE, CREATE
INDEX, DROP TABLE, etc.) are not allowed in a PREPARE command with
the REPEAT option. - ACTION
Do not use the REPEAT option for DDL commands.
- 2785
- MESSAGE
The starting position is invalid for the SUBSTRING function. (DBERR 2785) - CAUSE
The StartPosition parameter of the SUBSTRING function is
less than 1 or greater than the length of the SourceString. - ACTION
Change the StartPosition parameter to a value greater than
0, and less than or equal to the length of the SourceString parameter.
- 2786
- MESSAGE
The substring length is invalid for the SUBSTRING function. (DBERR 2786) - CAUSE
The Length parameter of the SUBSTRING function is
less than 1 or greater than the length of the SourceString parameter. - ACTION
Change the Length parameter to a value greater than
0, and less than or equal to the length of the SourceString parameter.
- 2787
- MESSAGE
Length of item ! in select list exceeds that of corresponding procedure result column. (DBERR 2787) - CAUSE
An item in the select list in a procedure SELECT statement
with no INTO clause has a length greater than that specified for
the corresponding procedure result column in the WITH RESULT clause
of the CREATE PROCEDURE statement. - ACTION
Re-issue the CREATE PROCEDURE statement, either omitting
the WITH RESULT clause, or ensuring that all multiple row result
sets returned from the procedure are compatible with the format
specified.
- 2788
- MESSAGE
USING Clause is required for output dynamic parameters. (DBERR 2788) - CAUSE
You tried to execute a prepared EXECUTE PROCEDURE statement
with output dynamic parameters, but no output variables were provided
in the USING clause of an EXECUTE or CLOSE statement. - ACTION
Issue the EXECUTE or CLOSE statement again with
the USING clause, specifying output variables for output dynamic
parameters in the prepared statement.
- 2790
- MESSAGE
CANNOT use DROP PARTITION on DEFAULT partition. (DBERR 2790) - CAUSE
You attempted to drop the DEFAULT partition. - ACTION
This partition cannot be dropped. Its partition
number can be changed with the START DBE NEWLOG statement.
- 2791
- MESSAGE
Cannot CREATE PARTITION !. (DBERR 2791) - CAUSE
You attempted to create a partition named NONE or DEFAULT.
This partition name cannot be used since it refers to the nonexistent
partition. - ACTION
No partition can be created with this name in the CREATE
PARTITION statement.
- 2792
- MESSAGE
Comment text for LOG COMMENT must have data type CHAR or VARCHAR. (DBERR 2792) - CAUSE
The value for a log comment was not a character
value. - ACTION
Check the type of the value and be sure it is CHAR
or VARCHAR.
- 2793
- MESSAGE
Cannot LOG COMMENT when AUDIT LOG not enabled. (DBERR 2793) - CAUSE
You specified a LOG COMMENT statement in a DBEnvironment
without audit logging or with audit logging disabled. - ACTION
Enable AUDIT LOG for the DBEnvironment or refrain from
issuing LOG COMMENT on the DBEnvironment.
- 2794
- MESSAGE
Cannot open log scan on AUDIT CHECKPOINT only DBEnvironment. (DBERR 2794) - CAUSE
Unable to open the log scan on the AUDIT CHECKPOINT. - ACTION
Enable AUDIT LOG for the DBEnvironment, not for AUDIT
CHECKPOINT.
- 2795
- MESSAGE
Invalid value for the number of occurance parameter in INSTR function.(DBERR 2795) - CAUSE
The number of occurance parameter has a value less
than 1 or greater than the length of SourceString. - ACTION
Change the parameter to a value greater than 0 and
less than or equal to the length of SourceString parameter.
|