4.2 List of SQLSTATE values
The table below lists the SQLSTATE values that HADB outputs.
If an SQLSTATE value is returned, check the message provided in the Corresponding message column in the following table, and then take the appropriate action.
|
SQLSTATE value |
Summary of the contents |
Corresponding message |
|---|---|---|
|
00000 |
SQL statement execution has finished. |
|
|
The node in which to execute SQL statements is changed. |
||
|
01004 |
Data was truncated in data type conversion processing performed by the ODBC driver. |
|
|
01601 |
Processing of the SQL statement might require a long time because the SQL statement accesses data in all archived chunks. |
|
|
01J11 |
The result set type was changed because the result set type that allows scrolling with updated content is not supported. |
|
|
01J12 |
The concurrent processing type was changed for the result set, because updatable result sets are not supported. |
|
|
01J13 |
Because CLOSE_CURSORS_AT_COMMIT cannot be specified in the result set holdability, the result set holdability has been changed. |
|
|
01S07 |
Data was truncated in data type conversion processing performed by the ODBC driver. |
|
|
01S51 |
Characters that could not be converted during character encoding conversion were replaced with hash marks (#). |
|
|
02000 |
No rows match the conditions. Another possibility is that row fetching has terminated. |
|
|
07003 |
Queries cannot be executed with the CLI function a_rdb_SQLExecDirect(), which performs preprocessing and execution of SQL statements. |
|
|
07005 |
SQL statements other than queries whose SQL statement is preprocessed cannot be executed. |
|
|
07006 |
An error occurred in data type conversion version processing performed by the ODBC driver. |
|
|
08002 |
A connection to the HADB server has already been established. Connection processing cannot be re-executed while there is a connection to the HADB server. |
|
|
08004 |
The HADB server is not running. |
|
|
08605 |
The character encoding of the HADB server and that of the HADB client do not match. |
|
|
08607 |
The sort order of the character string data is incorrect. |
|
|
08608 |
A command is running that cannot be executed concurrently with another command or application. |
|
|
08609 |
The CONNECT statement cannot be executed because the HADB server operation mode is in offline mode. |
|
|
0860A |
The CONNECT statement cannot be executed because a direct connection to a slave node is being established. |
|
|
0860B |
The CONNECT statement cannot be executed because an attempt to establish a connection to an HADB server-dedicated communication port is in progress. |
|
|
0860C |
The HADB client cannot connect to the HADB server because the versions of the HADB client and HADB server are different. |
|
|
0860D |
A connection to the HADB server cannot be established because the client or command belongs to a client group or command group whose maximum number of concurrent connections is zero. |
|
|
0860E |
The CONNECT statement cannot be executed because the HADB server operation mode is maintenance mode. |
|
|
08620 |
No more connections can be established to the HADB server because the number of connections has reached the maximum for simultaneous connections. |
|
|
08622 |
The sort order of the character string data is incorrect. |
|
|
08623 |
The CONNECT statement cannot be executed because the HADB client execution environment is invalid. |
|
|
21502 |
A cardinality violation occurred. |
|
|
22001 |
The input data length is invalid (the input data is longer than the column). |
|
|
The character string returned by scalar function TRANSLATE exceeded the permitted data length for execution results. |
||
|
The specified scalar function is invalid. |
||
|
An error occurred while executing a scalar function. |
||
|
An error occurred in data type conversion version processing performed by the ODBC driver. |
||
|
22003 |
The input data falls outside of the range of values for the column's data type. |
|
|
The input data for a dynamic parameter is invalid. |
||
|
An error occurred while executing a scalar function. |
||
|
The specified scalar function is invalid. |
||
|
An overflow occurred in a numeric data operation. |
||
|
An overflow occurred while a set function or a window function was executing. |
||
|
The value range for a set function argument is invalid. |
||
|
An error occurred in data type conversion version processing performed by the ODBC driver. |
||
|
22007 |
The input data for a dynamic parameter is invalid. |
|
|
An error occurred in data type conversion version processing performed by the ODBC driver. |
||
|
22008 |
An overflow error occurred in datetime data. |
|
|
An error occurred in data type conversion version processing performed by the ODBC driver. |
||
|
22012 |
A division by zero error occurred while a scalar function was executing. |
|
|
A division by zero error occurred during an arithmetic operation. |
||
|
22013 |
A value specified in the window frame value specification for a window frame border is invalid. |
|
|
22018 |
The specified scalar function is invalid. |
|
|
An error occurred while executing a scalar function. |
||
|
An error occurred in data type conversion version processing performed by the ODBC driver. |
||
|
22019 |
The data length of the value expression specified for the escape character is invalid. |
|
|
2201E |
An error occurred while executing a scalar function. |
|
|
An out-of-range value was specified in the LN scalar function. |
||
|
2201F |
An error occurred while executing a scalar function. |
|
|
An out-of-range value was specified in the POWER or SQRT scalar function. |
||
|
22505 |
The input data for a dynamic parameter is invalid. |
|
|
2250A |
The data content of the value expression specified for the escape character is invalid. |
|
|
2250G |
A character string representation used in the scalar function does not match the format specification. |
|
|
The format specification in a scalar function is invalid. |
||
|
A required element is missing from the format specification of the scalar function. |
||
|
2250H |
An error occurred while executing a scalar function. |
|
|
An out-of-range value was specified in a scalar function. |
||
|
2250I |
The data lengths of the arguments specified in the scalar function are different. |
|
|
22510 |
The value specified for row-count or offset in the LIMIT clause is invalid. |
|
|
22521 |
The indicator value of the input data for a dynamic parameter is invalid. |
|
|
22522 |
The specification format of a scalar function is invalid. |
|
|
22523 |
An error occurred during check of the path name of the file that will be the input data of the system-defined function. |
|
|
22524 |
||
|
22525 |
The data format of the file that will be the input data of the system-defined function is invalid. |
|
|
22527 |
An error occurred in the file that will be the input data of the ADB_CSVREAD function. |
|
|
22528 |
||
|
22529 |
||
|
2252A |
An error occurred during check of the path name of the file that will be the input data of the system-defined function. |
|
|
2252B |
||
|
2252C |
||
|
23503 |
An attempt was made to set a null value in a column for which null values cannot be set. |
|
|
23504 |
An attempt was made to update or add data that would have resulted in key values of a unique index being duplicated. |
|
|
24504 |
The cursor has not been opened. |
|
|
24505 |
An attempt was made to open a cursor that is already open. |
|
|
24506 |
Preprocessing was requested for a query that has a cursor open. |
|
|
24511 |
The cursor has not been closed. |
|
|
24512 |
There is a dynamic parameter for which no value is set. |
|
|
24513 |
An error has already occurred in the opened cursor. |
|
|
25006 |
The SQL statement could not be executed because the transaction access mode is read-only. |
|
|
28501 |
The specified password violates the password specification rules. |
|
|
28502 |
The specified authorization identifier or password is invalid. |
|
|
40503 |
No more pages can be created because the DB area file cannot be expanded. |
|
|
40508 |
An attempt was made to access an index that was in unfinished status. |
|
|
4050D |
An attempt was made to access a table that is in non-updateable status due to a suspended command. |
|
|
4050G |
An error occurred during lock processing. |
|
|
4050P |
Processing to reserve a lock timed out. |
|
|
4050Q |
An attempt was made to update or delete a row that is being updated or deleted by another transaction. |
|
|
40518 |
The row length of the work table has exceeded the upper limit. |
|
|
40528 |
An error occurred in processing on a file or directory. |
|
|
40602 |
No global buffer has been assigned to the DB area. |
|
|
40701 |
Processing cannot continue because there are not enough buffer sectors. |
|
|
40704 |
The global buffer is temporarily unavailable. |
|
|
40801 |
No new table or index can be defined in the data DB area because the maximum number of chunks that can be managed by one data DB area was exceeded. Another possibility is that the maximum number of chunks for the table defined in the data DB area cannot be increased. |
|
|
40802 |
The specified chunk ID does not exist in the table. |
|
|
40803 |
The chunk ID of the current chunk cannot be specified in the PURGE CHUNK statement. |
|
|
40804 |
The ALTER TABLE statement cannot be executed because the maximum number of chunks specified in the ALTER TABLE statement is less than the number of chunks that have already been created in the table. |
|
|
40820 |
The number of user log files has reached its upper limit. |
|
|
40900 |
The number of base tables, indexes, viewed tables, or HADB users exceeded the maximum number defined for the system. |
|
|
40910 |
The number of tables or indexes has exceeded the maximum that can be stored in a single DB area. |
|
|
40920 |
The page being recovered for database update processing was accessed during the master node switchover processing. |
|
|
42501 |
The length of a character string literal exceeds 32,000 bytes. |
|
|
42502 |
The length of a binary literal exceeds the maximum allowed value. |
|
|
42505 |
A character string literal is incomplete. |
|
|
42509 |
A binary literal specification is invalid. |
|
|
42510 |
An SQL statement contains an error such as one of the following:
|
|
|
42511 |
The numeric literal that was specified is invalid. |
|
|
42512 |
The specification format of the floating-point numeric literal is invalid. |
|
|
42513 |
A numeric literal that is outside the specification range was specified. |
|
|
42520 |
The length of a name exceeds 100 bytes. Another possibility is that a keyword was specified incorrectly. |
|
|
42529 |
The length of the authorization identifier is outside the range of 1 to 100 bytes. |
|
|
42530 |
An SQL statement contains an error such as one of the following:
|
|
|
42532 |
The following syntax error was found in the identifier specified for the national character set:
|
|
|
42539 |
The specified authorization identifier contains at least one of the following errors:
|
|
|
42550 |
A dynamic parameter is specified at an invalid location. |
|
|
42561 |
The specified predicate is invalid. |
|
|
42572 |
The specified ROW is invalid. |
|
|
42590 |
The length, precision, or scale of a data type is invalid. |
|
|
42591 |
The fractional seconds precision specified for the datetime information acquisition function is invalid. |
|
|
425A0 |
The specified number exceeds the maximum allowed value. |
|
|
425A4 |
||
|
425A6 |
||
|
425A7 |
||
|
425A8 |
||
|
425A9 |
||
|
425AA |
||
|
425AI |
||
|
425B0 |
||
|
425B1 |
||
|
425B2 |
The number of grouping columns specified in a GROUP BY clause exceeds the maximum allowed value. |
|
|
425B3 |
The number of specified sort keys exceeds the maximum allowed value. |
|
|
425B5 |
The specified value exceeds the maximum allowed value. |
|
|
425B6 |
||
|
425B7 |
||
|
425BB |
||
|
425BC |
||
|
425BG |
The number of value expressions specified in a window partition clause exceeds the maximum allowed value. |
|
|
425BJ |
The specified number exceeds the maximum allowed value. |
|
|
425C0 |
The number of columns in the table exceeds the upper limit of 1,000. |
|
|
425C1 |
The specified value exceeds the maximum allowed value. |
|
|
425C2 |
||
|
425C6 |
The number of columns in a multiple-column index exceeds the upper limit of 16. Another possibility is that the number of columns making up the primary key exceeds the upper limit of 16. |
|
|
425CA |
The specified value exceeds the maximum allowed value. |
|
|
425CD |
The number of columns constituting a foreign key exceeds the maximum of 16. |
|
|
425CF |
The specified value exceeds the maximum allowed value. |
|
|
425CG |
||
|
425CH |
||
|
425CK |
The number of specifications exceeds the maximum allowed. |
|
|
425CL |
A delimited identifier that contains left or right parentheses can be specified only in the first query specification in the SELECT statement. However, a delimited identifier that contains left or right parentheses cannot be specified for a query specification in the WITH clause. |
|
|
425CM |
Although NULL is specified in the selection expression in a query specification, an error occurred in the SELECT statement because the conditions of available specifications are not met. |
|
|
425D0 |
No column definition is specified in the CREATE TABLE statement. |
|
|
425D4 |
An option was illegally specified more than once in a table or index definition. |
|
|
425D5 |
A value outside the valid range was specified for a table option in the CREATE TABLE or ALTER TABLE statement, or for an index option in the CREATE INDEX statement. |
|
|
425D7 |
A privilege specified in the GRANT or REVOKE statement is duplicated. |
|
|
425Q0 |
The specification of the maximum-number-of-recursions specification is invalid. |
|
|
42601 |
An extra character string exists after the SQL statement. |
|
|
42602 |
An SQL statement contains a syntax error. |
|
|
42603 |
An SQL statement is incomplete. |
|
|
42703 |
The value specified for labeled duration is invalid. |
|
|
42705 |
The data type or length of a column is invalid. A value expression whose result has a data length of 0 was specified. |
|
|
42710 |
The aggregated argument specified in a set function is invalid. Another possibility is that the argument specified in a window function is invalid. |
|
|
42711 |
A set function is specified in an argument of a set function. |
|
|
42712 |
The data type of an aggregated argument in a set function is invalid. Another possibility is that the data type of an argument in an inverse distribution function is invalid. |
|
|
42713 |
The specified set function is invalid. |
|
|
42714 |
A set function or a window function is specified at an invalid location. |
|
|
42715 |
A subquery is specified at an invalid location. |
|
|
42716 |
The SELECT DISTINCT and DISTINCT set functions are both specified. |
|
|
42717 |
Multiple DISTINCT set functions containing different column names in the arguments are specified. |
|
|
42718 |
Another DISTINCT set function is specified in addition to a DISTINCT set function specified in the value expression of an argument. |
|
|
42720 |
The number of columns to be inserted does not match the number of values to be inserted. |
|
|
42721 |
In a specified set operation, the tables derived from individual query expression bodies do not have the same number of columns. |
|
|
42722 |
Two or more selection expressions have been specified for a retrieval item. |
|
|
42723 |
There is an error in the specified CREATE VIEW statement. The number of column names specified in the column name list differs from the number of columns for the table that is derived from the query expression. |
|
|
42730 |
A name is duplicated within a FROM clause. |
|
|
42731 |
An update column or insertion column is duplicated. |
|
|
42732 |
A column specification is duplicated. |
|
|
42733 |
A query name was specified more than once in a WITH clause. |
|
|
42734 |
A column name is duplicated in a viewed table. |
|
|
42736 |
A column used as a sort key specified in the ORDER BY clause is duplicated. |
|
|
42737 |
The specified viewed table has a view level that cannot be specified in the CREATE VIEW statement. |
|
|
42740 |
The qualifying table specification contains a name that is not valid to specify in an SQL statement. |
|
|
42741 |
The specified table or index has not been defined. |
|
|
42742 |
The specified column does not exist in any table of the SQL statement or query specification. Another possibility is that the name is invalid. |
|
|
The specified column was not found in a table, correlation name, or query in a FROM clause. |
||
|
There are no target candidates for the specified identifier within the valid range. |
||
|
42743 |
The sort item specification number specified in an ORDER BY clause is invalid. |
|
|
A column that is not specified in the selection expression cannot be specified in the ORDER BY clause due to one of the following reasons:
|
||
|
42744 |
The table to which the specified column name belongs cannot be determined. |
|
|
There are two or more corresponding tables in a query with ROW specified. |
||
|
42745 |
A column specified in an ORDER BY clause is found more than once in a table derived as a result of a query. |
|
|
42746 |
The specified SQL statement contains the following error:
|
|
|
42750 |
ROW is specified for a table that is not a FIX table. |
|
|
42767 |
The specification of the chunk ID is invalid. |
|
|
42768 |
||
|
42769 |
||
|
4276B |
||
|
4276C |
||
|
4276D |
||
|
4276E |
||
|
4276F |
||
|
42770 |
A dynamic parameter is specified at an invalid location in a predicate. |
|
|
42771 |
A dynamic parameter is specified at an invalid location in an operation. |
|
|
4277E |
The specification of the system-defined function is invalid. |
|
|
4277F |
||
|
4277G |
||
|
42780 |
A data type that cannot be specified in a datetime operation was specified with an arithmetic operator. |
|
|
Labeled durations can only be specified for the operands of addition and subtraction operations on datetime data. |
||
|
42782 |
The argument specified in the scalar function is invalid. |
|
|
42784 |
The specified CASE expression is invalid. |
|
|
42785 |
The argument specified in the scalar function is invalid. |
|
|
42786 |
The specification of the system-defined function is invalid. |
|
|
42787 |
The datetime format specified in a scalar function is not compatible with the time data. |
|
|
42788 |
The data type of an argument is invalid in the LTRIM, RTRIM, or TRIM scalar function. |
|
|
42789 |
The format specification in a scalar function is invalid. |
|
|
4278A |
||
|
4278B |
||
|
4278C |
||
|
4278D |
||
|
4278E |
The data length of an argument in the REPLACE scalar function is invalid. |
|
|
4278G |
The specification of the labeled duration is invalid. |
|
|
4278H |
||
|
4278I |
||
|
4278J |
The specification method of the scalar function is invalid. |
|
|
4278K |
||
|
4278M |
||
|
4278N |
||
|
4278O |
The specified scalar function is invalid. |
|
|
4278P |
||
|
4278Q |
||
|
4278R |
The length of the regular expression character string specified in the LIKE_REGEX predicate is invalid. |
|
|
4278S |
The specified scalar function LTDECODE is invalid. |
|
|
42793 |
The table to be updated cannot be specified as a table from which data is to be retrieved. |
|
|
427A0 |
The depth of nesting of the operation exceeded 255. Another possibility is that the SQL statement could not be executed because of a restriction on system processing. |
|
|
427A2 |
The number of value expressions specified in an IN predicate has exceeded the upper limit of 30,000. |
|
|
427A3 |
CURRENT_USER_IS_DBA is specified, but this character string is not permitted. |
|
|
427A4 |
The insertion value specified in an INSERT statement is invalid. |
|
|
427A5 |
The null-value sort order specification cannot be specified in the sort specification list. |
|
|
427A6 |
The number of set operations specified in an SQL statement that include EXCEPT or INTERSECT exceeds the maximum of 63 that can be specified. |
|
|
427B2 |
For a query that uses a set operation, a column name qualified in the table specification cannot be specified as a sort key. |
|
|
427B3 |
A viewed table cannot be defined with another viewed table as its underlying table. |
|
|
The TRUNCATE TABLE statement cannot be executed on a viewed table. |
||
|
427B4 |
The PURGE CHUNK statement cannot be executed on a single-chunk table or viewed table. |
|
|
427B5 |
No chunk ID is specified in the PURGE CHUNK statement. |
|
|
427B6 |
For a query that uses a set operation, no value expression can be specified in the ORDER BY clause. |
|
|
427B7 |
No more than one sort key can be specified in this function. |
|
|
427B9 |
The specified inverse distribution function is invalid. |
|
|
427BA |
||
|
427BB |
||
|
427BC |
A column in the table where chunks are to be deleted is specified in the PURGE CHUNK statement. |
|
|
427D3 |
A WITH clause specification is invalid. |
|
|
427G0 |
A window function specification is invalid. |
|
|
427G1 |
||
|
427G2 |
||
|
427G3 |
||
|
427G4 |
||
|
427G5 |
||
|
427H0 |
A window function specification is invalid. |
|
|
427H1 |
||
|
427H2 |
||
|
427H3 |
A window function specification is invalid. |
|
|
427H4 |
The number of window functions specified in the query specification or the ORDER BY clause exceeds 8. |
|
|
427HA |
The value expression in the following location contains no column specification.
|
|
|
427HC |
The sort key specified in an ORDER BY clause is invalid. |
|
|
427HD |
Sort item specification numbers for ROW cannot be specified. |
|
|
427HE |
For a query that specifies SELECT DISTINCT, no value expression can be specified in the ORDER BY clause. |
|
|
427I0 |
If AS column-name is specified in the GROUP BY clause, a value expression containing only column specifications cannot be specified in the GROUP BY clause. |
|
|
427I3 |
The specified LIMIT clause is invalid. |
|
|
427I4 |
||
|
427I5 |
If AS column-name is specified in the GROUP BY clause, the grouping column name cannot be referenced from a subquery in the HAVING clause or selection expression. |
|
|
427I6 |
The specified LIMIT clause is invalid. |
|
|
427I7 |
Table names of table references specified in the outermost query specification cannot be referenced from subqueries in ORDER BY clauses. |
|
|
427I8 |
A FULL OUTER JOIN specification is invalid. |
|
|
427I9 |
The specified multiset value expression is invalid. |
|
|
427IA |
||
|
427J0 |
An argument specified in the ADB_CSVREAD function is invalid. |
|
|
427J1 |
||
|
427J2 |
||
|
427J3 |
||
|
427J4 |
||
|
427J5 |
||
|
427J6 |
||
|
427J7 |
||
|
427J8 |
||
|
427J9 |
||
|
427JA |
The table function column list specified in the table function derived table is invalid. |
|
|
427K0 |
The specification of the table function derived table with the system-defined function specified is invalid. |
|
|
427K1 |
The argument specified in the system-defined function is invalid. |
|
|
427K2 |
||
|
427K5 |
A multiset value constructor by query cannot be specified as an argument of the ADB_AUDITREAD function. |
|
|
427K6 |
There is a problem with the audit trail file path names (that contain special characters) specified as the argument of the ADB_AUDITREAD function. |
|
|
427K7 |
||
|
427L0 |
The numbers of row value constructor elements specified in the row value constructors do not match. |
|
|
427M0 |
The specified row value constructor element is invalid. |
|
|
427M1 |
A dynamic parameter alone cannot be specified in a row value constructor element. |
|
|
427N0 |
The recursive member contains an item that cannot be specified. |
|
|
427N1 |
The data type and data length of the column derived from the anchor member are different from those of the column derived from the recursive member. |
|
|
427N5 |
The specification of the recursive query is invalid. |
|
|
427N6 |
||
|
427N7 |
||
|
427N8 |
||
|
42801 |
The data types of the results of the value expressions specified in a predicate cannot be compared to each other or converted. |
|
|
The data type of a value expression specified in a predicate is not character string data. |
||
|
42802 |
An invalid data type is specified in the operand of an operator. |
|
|
An invalid data type was specified in the first or second operand of a concatenation operation. |
||
|
42803 |
The data type of the update value or insertion value is not a data type that can be converted. |
|
|
42804 |
A set operation specification is invalid. |
|
|
42806 |
The data types of the results of value expressions specified for THEN and ELSE in a CASE expression are not compatible. |
|
|
42807 |
The specified scalar function is invalid. |
|
|
4280F |
A window function specification is invalid. |
|
|
42812 |
The maximum length of the result of an operation exceeds 32,000 bytes. |
|
|
42819 |
The data length of an argument specified in the scalar function exceeds the maximum byte length. |
|
|
42820 |
Permission to access the specified schema or schema object has not been granted. |
|
|
42849 |
A table function derived table with the system-defined function specified cannot be specified. |
|
|
42850 |
No dynamic parameter can be specified in a view definition. |
|
|
42870 |
An attempt was made to perform an operation that cannot be performed on a table. |
|
|
42875 |
The SQL statement specification is invalid. |
|
|
428A3 |
A viewed table cannot be defined with a dictionary table or a system table as its underlying table. |
|
|
428F0 |
An index specification is invalid. |
|
|
428F1 |
||
|
428F5 |
The specified subquery processing method specification is invalid. |
|
|
428T0 |
The specified scalar function CONTAINS contains an error. |
|
|
428T1 |
||
|
428T2 |
A notation-correction-search specification cannot be specified because the character encoding used by the HADB server is Shift-JIS (if the value specified for the environment variable ADBLANG is SJIS). |
|
|
428T3 |
A regular expression specified for a regular expression character string in the LIKE_REGEX predicate is invalid. |
|
|
428T4 |
||
|
428T5 |
||
|
428T6 |
||
|
428T7 |
The synonym dictionary specified in the scalar function CONTAINS does not exist. |
|
|
428T8 |
The synonym dictionary specified in the scalar function CONTAINS does not support a correction search. |
|
|
428T9 |
A synonym search cannot be performed if the multi-node function is used. |
|
|
428TA |
The specified scalar function CONTAINS contains an error. |
|
|
428TB |
||
|
428TC |
||
|
42929 |
A viewed table contains a column for which no derived column name has been set, and the column name specification was omitted. |
|
|
4292A |
This viewed table cannot be accessed because it is invalidated. |
|
|
42932 |
The specified environment variable is invalid. |
|
|
429D9 |
The data type of row-count or offset in the LIMIT clause is invalid. |
|
|
42I01 |
An SQL statement contains an error similar to the following:
|
|
|
42I05 |
The specified schema object does not exist. |
|
|
42I08 |
The authorization identifier or schema name specification is invalid. |
|
|
42I13 |
The table name, index name, or constraint name specified in one of the following SQL statements is already in use:
|
|
|
42I14 |
The following operations cannot be performed for a FIX table:
|
|
|
42I15 |
A column name has been used more than once. |
|
|
42I16 |
A column that cannot be defined for a B-tree index was specified as an indexed column for a B-tree index. |
|
|
42I18 |
An error occurred in an SQL statement because a column name was specified more than once. |
|
|
42I26 |
The schema does not exist. |
|
|
42I29 |
An index with the same structure already exists. |
|
|
42I30 |
A schema with the same name already exists. |
|
|
42I44 |
An SQL statement was executed with RESTRICT specified for the drop behavior, but the SQL statement resulted in an error for one of the following reasons:
|
|
|
42I53 |
A foreign key cannot be defined because the referenced table has no primary key defined for it. |
|
|
42I54 |
The configuration of a foreign key differs from that of the primary key that the foreign key accesses. |
|
|
42I55 |
A foreign key cannot be defined for one of the following reasons:
|
|
|
42I60 |
The null-value exclusion specification (EXCLUDE NULL VALUES) cannot be specified due to one of the following reasons:
|
|
|
42I72 |
A DEFAULT clause specification is invalid. |
|
|
42I75 |
A CREATE INDEX statement, an ALTER TABLE or a CREATE TABLE statement cannot be executed. |
|
|
42I77 |
Multiple referential constraints that access the same primary key cannot be defined from the same column or from the same group of multiple columns (even if the column order is different). |
|
|
42IA6 |
An invalid option is specified in an index definition. |
|
|
42IA7 |
Multiple indexed columns are specified in an index definition. |
|
|
42IA8 |
A column for which a range index cannot be defined is specified as an range-indexed column. |
|
|
42IA9 |
An attempt is made to define a unique index for a multi-chunk table. |
|
|
42IAA |
The specified table option is invalid. |
|
|
42IAB |
The specified option is invalid. |
|
|
42IAC |
A column with the NOT NULL constraint specified cannot be added to a base table to which segments for storing rows are assigned. |
|
|
42IAD |
The maximum number of chunks was not specified in the chunk specification when the base table was defined by using the CREATE TABLE statement. Therefore, the ALTER TABLE statement cannot be used to change the maximum number of chunks. |
|
|
42IAE |
The specified ALTER TABLE statement is invalid. Neither the maximum number of chunks nor the chunk-archive specification is specified. |
|
|
42IAF |
If the chunk specification is specified, a primary key cannot be defined. Conversely, if a primary key is defined, the chunk specification cannot be specified. |
|
|
42IB0 |
The DROP INDEX statement cannot be used to delete the indexes that correspond to the primary key. Alternatively, the DROP INDEX statement cannot be used to delete the range indexes that are automatically defined for archive range columns. |
|
|
42IB2 |
A text index cannot be defined for columns. |
|
|
42IB3 |
The following index option cannot be specified for an index other than a text index:
|
|
|
42IB4 |
Columns of the following data types cannot be specified as archive range columns:
|
|
|
42IB5 |
The length of the path name of the specified archive directory is not in the range from 1 to 400 bytes. |
|
|
42IB6 |
The specified archive directory is not an absolute path. |
|
|
42IB7 |
The notation-correction-search text-index specification (CORRECTIONRULE) cannot be specified because the character encoding used on the HADB server is Shift-JIS (if the value specified for the environment variable ADBLANG is SJIS). |
|
|
42IB8 |
The specified ALTER TABLE statement is invalid. Change of the maximum number of chunks and the chunk-archive specification cannot be specified at the same time. |
|
|
42IB9 |
The chunk-archive specification in the ALTER TABLE statement cannot be specified for an archivable multi-chunk table. |
|
|
42IBA |
The chunk-archive specification in the CREATE TABLE statement or ALTER TABLE statement is invalid. |
|
|
42IBB |
The chunk-archive specification in the ALTER TABLE statement is invalid. |
|
|
42IBC |
The NOT NULL constraint (NOT NULL) is not defined for the column specified for RANGECOLUMN in the chunk-archive specification in the ALTER TABLE statement. |
|
|
42IBD |
The chunk-archive specification in the ALTER TABLE statement cannot be specified for a single-chunk table. |
|
|
42IBE |
The column name cannot be changed by using the ALTER TABLE statement because the current column name is the same as the new column name. |
|
|
42IBF |
The archivable multi-chunk table could not be changed to a regular multi-chunk table because an error occurred in the ALTER TABLE statement. |
|
|
42IC0 |
TEXT WORDCONTEXT is not specified for the index type. Therefore, a text-index delimiter specification cannot be specified. |
|
|
42IC1 |
The table for which you are attempting to define a text index is a column store table. |
|
|
42K01 |
The table to be searched cannot be referenced because you do not have the required privileges. |
|
|
42K02 |
The SQL statement cannot be executed because the user who executed the SQL statement is invalid. |
|
|
42K03 |
The DBA privilege is required to perform the attempted operation. |
|
|
42K05 |
An attempt was made to revoke a privilege that cannot be revoked by that same user. |
|
|
42K06 |
The operation by a GRANT or REVOKE statement could not be performed. |
|
|
42K07 |
A nonexistent authorization identifier is specified. |
|
|
42K10 |
The schema definition privilege cannot be deleted because the HADB user having the authorization identifier specified in the REVOKE statement owns the schema. |
|
|
42K12 |
An attempted operation requires the schema definition privilege. |
|
|
42K14 |
Schema belonging to other HADB users cannot be changed. |
|
|
42K19 |
The HADB user having the authorization identifier specified in the DROP USER statement cannot be deleted. |
|
|
42K26 |
The privilege cannot be revoked because RESTRICT is specified for the drop behavior. |
|
|
42K30 |
An attempt is made to grant privileges that cannot be granted to the same HADB user. |
|
|
42K33 |
The password of an HADB user who has the audit privilege cannot be changed by other HADB users. |
|
|
42K35 |
You do not have the privilege required to perform operations relating to the audit trail facility. |
|
|
42K38 |
The audit target specified in the CREATE AUDIT statement is already defined. |
|
|
42K39 |
The audit target definition specified in the DROP AUDIT statement does not exist. |
|
|
42K43 |
The specified authorization identifier is already in use. |
|
|
5100J |
An error occurred when an SQL statement that uses hash tables was executing. |
|
|
5100K |
An attempt to execute the DELETE statement for the archivable multi-chunk table caused an error because the specified search condition did not meet the execution condition of the DELETE statement. Alternatively, an attempt to execute the UPDATE statement for the archivable multi-chunk table caused an error because the specified search condition did not meet the execution condition of the UPDATE statement. |
|
|
5100L |
The number of recursions in the recursive query exceeds the maximum number of recursions. |
|
|
52004 |
No SQL statements can be executed because the HADB server is being started or terminated. |
|
|
52011 |
The operation relating to the audit trail facility cannot be performed because the audit trail facility is disabled. |
|
|
5201F |
An application program cannot connect to the HADB server on a kernel or OS version that is not supported by HADB. |
|
|
52020 |
The SQL statement cannot be executed because a uniqueness constraint violation occurred on a B-tree index between the time the preprocessing of the SQL statement began and the time the SQL statement was executed. |
|
|
52320 |
The connection to the HADB server was closed. |
|
|
52321 |
Invalid data was received from the HADB server. |
|
|
52322 |
The address of the target host could not be acquired. |
|
|
52324 |
One of the following failures was detected:
|
|
|
52325 |
A security violation occurred in the JDBC driver. |
|
|
52326 |
A timeout occurred while connecting to the HADB server or during data transmission. |
|
|
52328 |
A system call error occurred during communication processing. |
|
|
52330 |
An error occurred in the application program or command because HADB server processing did not terminate when the timeout period expired. |
|
|
52401 |
The SQL statement cannot be executed because another SQL statement or command has locked a resource that the SQL statement needs to execute. |
|
|
52402 |
The dictionary table (base table) cannot be accessed because a transaction is using the dictionary table (base table). |
|
|
52403 |
The specified operation cannot be performed because a locked resource is being used by another operation. |
|
|
52404 |
||
|
53021 |
Columns cannot be added to the target table. |
|
|
53024 |
A definition SQL statement cannot be executed because the table definition information is in use. |
|
|
53026 |
The table definition information for a slave node could not be invalidated. |
|
|
53027 |
The SQL statement cannot be executed because the table is being referenced in the same transaction. |
|
|
53028 |
The SQL statement or the command cannot be executed due to contention of the locked resource. |
|
|
53029 |
The definition SQL statement cannot be executed because a ResultSet object exists. |
|
|
5302A |
A directory that does not exist is specified as an archive directory. |
|
|
5302B |
A directory that cannot be specified as an archive directory is specified. |
|
|
5302C |
A directory for which the HADB administrator does not have read, write, and execution permissions is specified as an active directory. Alternatively, the archive directory path contains a directory for which the HADB administrator does not have execution permission. |
|
|
5302D |
Link destinations for the symbolic link specified in the archive directory cannot be acquired. |
|
|
5302E |
An error occurred in a system call. |
|
|
53030 |
The server message log file is full. |
|
|
53031 |
The client message log file is full. |
|
|
53040 |
A descriptor shortage occurred. |
|
|
53041 |
Allocation of communication port numbers failed. |
|
|
53050 |
An error occurred during operation on the synonym dictionary file. |
|
|
53051 |
Data retrieval by using the text index is not available. Alternatively, the text index cannot be updated. |
|
|
53201 |
A memory shortage occurred in a client library. |
|
|
An attempt to acquire enough memory to execute the SQL statement has failed. |
||
|
54001 |
An argument of a CLI function is invalid. |
|
|
54006 |
An analysis of the client definition has failed. |
|
|
54009 |
Execution of an SQL statement was requested before preprocessing of the SQL statement had terminated normally. |
|
|
54012 |
The following functions cannot be used on statement handles prepared for execution of statements other than DELETE, INSERT, and UPDATE statements:
|
|
|
54013 |
An SQL statement is already executing on the same connection. |
|
|
54014 |
Transactions cannot be started because a read-only transaction is being executed on an HADB server in a multi-node configuration. |
|
|
54016 |
Transactions cannot be started because a read/write transaction or command is being executed on an HADB server in a multi-node configuration. |
|
|
54017 |
The transaction cannot be executed because a command is executing or because another transaction is being executed by an application program. |
|
|
54018 |
An update SQL statement or definition SQL statement cannot be executed because the HADB server operation mode is quiescence mode. |
|
|
54020 |
A retrieval SQL statement resulted in an error. |
|
|
54201 |
An SQL statement cannot be executed because no connection has been established to the HADB server. |
|
|
54202 |
An SQL statement that uses this connection is already being executed. |
|
|
54203 |
The following items cannot be set because no connection has been established:
|
|
|
54204 |
The following items cannot be set because the transaction has already started:
|
|
|
54205 |
The specified character string data sort order is invalid. |
|
|
54206 |
The following items cannot be set because the cursor is already opened:
|
|
|
56001 |
The total length of data specified in a dynamic parameter exceeds 2 gigabytes. Another possibility is that the total length of data in the retrieval result exceeds 2 gigabytes. |
|
|
56006 |
The total memory required to execute the SQL statement exceeds 2 gigabytes. |
|
|
56007 |
The length of a B-tree index key exceeds the maximum value. |
|
|
56009 |
The CREATE TABLE or ALTER TABLE statement cannot be executed because the size of the area required to store a row exceeds the page size. |
|
|
5600B |
The number of indexes that can be defined for a single table has exceeded the upper limit of 32. |
|
|
5600C |
The number of foreign keys that reference a primary key exceeded 255. |
|
|
5600E |
The SQL statement length has exceeded the upper limit of 16,000,000 bytes, or the length is invalid. |
|
|
The length of a CREATE VIEW statement exceeds 64,000 bytes. |
||
|
56020 |
An invalid statement handle is specified. |
|
|
56033 |
The number of statement handles has exceeded the upper limit of 4,095. |
|
|
56034 |
The total data length of dynamic parameters exceeds 32,000,000 bytes. |
|
|
58005 |
The DB area specified in the following SQL statements or the assumed DB area does not exist:
|
|
|
58006 |
The specified or assumed DB area is not a data DB area. |
|
|
58024 |
The data DB area for storing tables or indexes is not specified in the CREATE TABLE or CREATE INDEX statement. |
|
|
5B002 |
Processing of the SQL statement or command was canceled and the transaction was rolled back. |
|
|
5C002 |
A character encoding conversion error occurred. |
|
|
An error occurred in data type conversion version processing performed by the ODBC driver. |
||
|
5C011 |
An internal conflict was found. |
|
|
5C015 |
Invalid data was received from the HADB server. |
|
|
5C034 |
Invalid data was received from an HADB client (including a JDBC driver) or command. |
|
|
5C035 |
An internal conflict was detected in the ODBC driver. |
|
|
5C036 |
The specified input data whose setting was requested is invalid. |
-- |
|
An error occurred in data type conversion version processing performed by the ODBC driver. |
||
|
5C037 |
The specified input data whose setting was requested is invalid. |
-- |
|
An error occurred in data type conversion version processing performed by the ODBC driver. |
||
|
5C038 |
There is an error in the area specified for receiving acquired result data. |
-- |
|
An error occurred in data type conversion version processing performed by the ODBC driver. |
||
|
5C039 |
There is an error in the area specified for receiving acquired result data. |
-- |
|
5C03A |
The transaction was rolled back because an error occurred in one of the statement handles used in the transaction. |
|
|
5C041 |
A data type that is not supported by the ODBC driver was specified in an SQL statement. |
-- |
|
5C051 |
The length of an SQL statement exceeded 16,000,000 characters. |
|
|
5C052 |
The versions of the ODBC driver and the HADB client are different. |
|
|
5D001 |
An error occurred in HADB, and neither the SQLSTATE value nor the message could be obtained. |
|
|
HY001 |
An error occurred in data type conversion version processing performed by the ODBC driver. |
|
|
HY003 |
||
|
HY004 |
||
|
HY009 |
||
|
HY013 |
||
|
HY090 |
||
|
HY104 |
||
|
HYC00 |
||
|
R2411 |
The object was invalidated because its transaction has terminated (including any implicit rollbacks). |
|
|
R2412 |
The type of the table specified by the getTables method argument for the String-type array is invalid. |
|
|
R2413 |
Processing cannot be accepted because the Statement instance is already closed. |
|
|
R2414 |
Conversion of the character encoding failed. |
|
|
R2415 |
An attempt to read from the java.io.Reader or java.io.InputStream has failed. |
|
|
R2416 |
Processing cannot be accepted because the Connection instance is already closed. |
|
|
R2417 |
An attempt was made to execute a method that is not supported. |
|
|
R2418 |
Batch processing cannot be performed because this SQL statement returns a result set. |
|
|
R2419 |
An unsupported argument was specified in the setFetchDirection method. |
|
|
R2420 |
The value of an argument specified in the setFetchSize method is invalid. |
|
|
R2421 |
Processing cannot be accepted because the instance is already closed. |
|
|
R2423 |
Objects of the class specified by the unwrap method of the Wrapper interface cannot be acquired. |
|
|
R2424 |
An attempt to register the JDBC driver with the driver manager has failed. |
|
|
R2425 |
The scroll type value of the specified result set is an invalid scroll type that is not defined by ResultSet. |
|
|
R2426 |
The concurrent processing type value of the specified result set is an invalid concurrent processing type that is not defined by ResultSet. |
|
|
R2427 |
The escape clause of the specified SQL statement is invalid. |
|
|
R2428 |
The specified connection information is invalid. |
|
|
R2429 |
The value of the holdability of the specified result set is an invalid value that is not defined in the ResultSet class. |
|
|
R2430 |
A negative value is specified for the maximum selection row count that is specified with the setMaxRows method or setLargeMaxRows method. |
|
|
R2431 |
The specified SQL statement is a null value or a character string with a length of zero. |
|
|
R2432 |
A negative value is specified for the timeout value that is specified with the setQueryTimeout method. |
|
|
R2433 |
A negative value is specified for the maximum field length that is specified with the setMaxFieldSize method. |
|
|
R2434 |
The specified SQL statement cannot be executed by executeQuery. |
|
|
R2435 |
The specified SQL statement cannot be executed by the executeUpdate method or executeLargeUpdate method. |
|
|
R2436 |
The number of batch registrations exceeded the upper limit of 2,147,483,647. |
|
|
R2437 |
Parameters of this SQL data type cannot be specified. |
|
|
R2438 |
A required parameter has not been specified. |
|
|
R2439 |
The specified parameter is invalid. |
|
|
R2440 |
The value of the parameter index is invalid. |
|
|
R2441 |
The object that was specified with the setObject method cannot be converted to the specified SQL data type. |
|
|
R2442 |
The data cannot be converted to the data type of the table definition because the number of digits of the integer portion of the specified data exceeds the number of digits of the integer portion of the table definition. |
|
|
R2443 |
The data is a value that is outside the range of the data type at the conversion destination, or else it is in a format that cannot be converted. |
|
|
R2444 |
The data type of the dynamic parameter that corresponds to the specified parameter index cannot be used with this setXXX method. |
|
|
R2445 |
The column name specified with the getXXX method of the ResultSet class is invalid. |
|
|
R2446 |
The specified column data cannot be acquired with the getString method of the ResultSet class. |
|
|
R2447 |
The specified column data cannot be acquired with the getBoolean method of the ResultSet class. |
|
|
R2448 |
The specified column data cannot be acquired with the getByte method of the ResultSet class. |
|
|
R2449 |
The specified column data cannot be acquired with the getShort method of the ResultSet class. |
|
|
R2450 |
The specified column data cannot be acquired with the getInt method of the ResultSet class. |
|
|
R2451 |
The specified column data cannot be acquired with the getLong method of the ResultSet class. |
|
|
R2452 |
The specified column data cannot be acquired with the getFloat method of the ResultSet class. |
|
|
R2453 |
The specified column data cannot be acquired with the getDouble method of the ResultSet class. |
|
|
R2454 |
The specified column data cannot be acquired with the getBigDecimal method of the ResultSet class. |
|
|
R2455 |
The specified column data cannot be acquired with the getBytes method of the ResultSet class. |
|
|
R2456 |
The specified column data cannot be acquired with the getDate method of the ResultSet class. |
|
|
R2457 |
The specified column data cannot be acquired with the getTime method of the ResultSet class. |
|
|
R2458 |
The specified column data cannot be acquired with the getTimestamp method of the ResultSet class. |
|
|
R2459 |
The specified column data cannot be acquired with the getAsciiStream method of the ResultSet class. |
|
|
R2460 |
Processing cannot be accepted because the ResultSet instance is already closed. |
|
|
R2461 |
The specified column data cannot be acquired with the getCharacterStream method of the ResultSet class. |
|
|
R2462 |
The column index specified with the getXXX method of the ResultSet class is invalid. |
|
|
R2464 |
Data cannot be acquired with the getXXX method of the ResultSet class used because the data acquired from the database does not match the date data format. |
|
|
R2465 |
Data cannot be acquired with the getXXX method of the ResultSet class used because the data acquired from the database does not match the time data format. |
|
|
R2466 |
Data cannot be acquired with the getXXX method of the ResultSet class used because the data acquired from the database does not match the time stamp data format. |
|
|
R2467 |
Scrolling is not possible because the result set type of this ResultSet object is TYPE_FORWARD_ONLY. |
|
|
R2468 |
Zero was specified with the absolute method. |
|
|
R2469 |
The cursor is not on a valid row. |
|
|
R2470 |
An argument value is invalid. |
|
|
R2471 |
An invalid value is specified for an argument of the setLoginTimeout method. |
|
|
R2472 |
An invalid character string is specified in the argument of the setEncodeLang method. |
|
|
R2473 |
The length of an SQL statement exceeded 16,000,000 characters. |
|
|
R2474 |
The specified column data cannot be acquired with the getBinaryStream method of the ResultSet class. |
|
|
R2475 |
The data of the specified column cannot be converted to a class of the Java data type specified in the getObject method of the ResultSet class. |
|
|
R2476 |
A timeout occurred during execution of an SQL statement because processing to allocate a processing real thread was repeated. |
- Legend:
-
--: There is no corresponding message.
- Note:
-
If the SQLSTATE value that is output is not listed above, see ODBC Programmer's Reference in MSDN library.