KFPA11101-E A
More than 255 nested operations, or implementation restriction exists
- The operation contains more than 255 nesting levels, or an SQL statement cannot be executed due to restrictions on the system processing.
- S: Ignores this SQL statement.
- P: Take one of the following actions:
- Reduce the nesting levels to no more than 255 and re-execute. There are cases in which the nesting levels in the SQL that specifies a named derived table are 255 or less. In such cases, decrease the number of nesting levels in the SQL or in the query that derives the named derived table.
- Either simplify the SQL statement (by reducing the number of tables or columns, etc.) or reduce the number of table indexes the applicable SQL statement references, and then re-execute.
- If a large number of SQL statements that create work tables are being executed in a transaction, revise the SQL statements so that the number of work tables created is 255 or less, and then re-execute the SQL statements. For a description of how to estimate the number of work tables that are created, see the manual HiRDB Version 9 Installation and Design Guide.
KFPA11102-E A
More than aa....aa bytes in character string literal
- One of the following values exceeds the maximum specifiable number (aa....aa):
- Number of bytes specified for a character string literal
- Number of bytes in the result of a concatenation operation between character string literals
- Number of bytes in the result of a scalar function (HEX) for which a literal is specified in its argument
- Number of bytes in the result of a character string literal after it is converted into the conversion target (for assignment or comparison)
- The following maximum specifiable numbers apply:
- When specified in the SQLSTATE value: 5
- When specified in the CREATE TABLE or ALTER TABLE boundary values and storage conditions: 255
- All other cases: 32000
- aa....aa:
{ 5|255|32000 }
- S: Ignores this SQL statement.
- P: Reduce the length of the character string literal to no more than aa....aa bytes and re-execute.
KFPA11103-E A
Invalid floating point numeric literal aa....aa
- The format of a specified floating-point numeric literal is invalid.
- aa....aa: Invalid floating-point numeric literal
- S: Ignores this SQL statement.
- P: Correct the floating-point numeric literal and re-execute.
KFPA11104-E A
Invalid part "aa....aa" in SQL
- The SQL statement contains an error, such as one of the following:
- The SQL statement is followed by a superfluous character string.
- A syntactically invalid character or keyword is specified.
- The first keyword in the SQL statement is invalid.
- A name does not begin with an alphabetic character.
- There is a name of zero length.
- aa....aa: Invalid part of the SQL statement
- If the SQL statement contains a syntactically invalid character, the character is displayed with its hexadecimal representation enclosed in parentheses.
- S: Ignores this SQL statement.
- P: Correct the error and re-execute.
KFPA11105-E A
Invalid token "bb....bb" after token "aa....aa"
- Syntactically, "bb....bb" cannot follow "aa....aa" in an SQL statement.
- aa....aa: Last characters satisfying the syntax rules
- bb....bb: Syntactically invalid characters
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute. Possible errors are as follows:
- The specification contains a syntax error.
- The order of clauses is invalid.
KFPA111106-E A
Incomplete SQL
- An SQL statement is not complete.
- S: Ignores this SQL statement.
- P: Complete the SQL statement and re-execute.
- If you specified Y for pd_sql_simple_comment_use in the system definition and this is a simple comment, check whether the linefeed code that ends the simple comment is missing. If it is missing, add the linefeed code, and then retry the operation.
KFPA11107-E A
More than 30 characters in identifier "aa....aa"
- The name is longer than 30 characters. Another possibility is that an invalid keyword is specified.
- aa....aa: The first 30 characters of the name.
- S: Ignores this SQL statement.
- P: If the name is longer than 30 characters, revise it so that it is 30 characters or less, and then re-execute. Revise any authorization identifier to 8 characters or less. If a keyword is specified incorrectly, revise the SQL statement, and re-execute it.
KFPA11112-E A
Invalid argument of set function "aa....aa"
- One of the following errors exists in an argument of the set function "aa....aa":
- No column was specified in the argument.
- A FLAT specification was specified for an argument in a set function other than MAX or MIN.
- A column other than a repetition column was specified for the FLAT specification in the set function MAX or MIN.
- A set function with FLAT specified in an argument was specified in a GROUP BY clause query in which a value expression other than a column was specified.
- aa....aa: Set function:
{ AVG |COUNT |COUNT_FLOAT |MAX |MIN |SUM }
- S: Ignores this SQL statement.
- P: Specify the argument correctly in the set function and re-execute.
KFPA11113-E A
aa....aa function "bb....bb" is specified in argument of set function, query-no=ccc
- Set function "bb....bb" is specified as an argument of a set function.
- aa....aa: Specified function
Set
- bb....bb: Set function:
{ AVG |COUNT |COUNT_FLOAT |MAX |MIN |SUM }
- ccc: Query number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11114-E A
Invalid specification in predicate "aa....aa", query-no=bbb
- There is an error in the specification of a NULL, LIKE, XLIKE, SIMILAR, BETWEEN, Boolean predicate, or XMLEXISTS predicate.
- A literal, USER value function, CURRENT_DATE value function, CURRENT_TIME value function, CURRENT_TIMESTAMP value function, ? parameter, or embedded variable was specified in a LIKE predicate, in a value expression in an XLIKE predicate, or in the row-value-constructor-1 of a BETWEEN predicate.
- A CURRENT_DATE value function, CURRENT_TIME value function, CURRENT_TIMESTAMP value function, ? parameter, or embedded variable was specified in a value expression in a SIMILAR predicate.
- A row value constructor was specified in the value expression of a NULL, LIKE, XLIKE, SIMILAR, or Boolean predicate.
- An XMLEXISTS predicate was specified somewhere other than in a WHERE clause. Note that the XMLEXISTS predicate cannot be specified in a subquery of a WHERE clause.
- aa....aa: Predicate whose operand is invalid:
{NULL|LIKE|XLIKE|SIMILAR|BETWEEN|BOOL|XMLEXISTS}
- bbb: Number of the query that specified the predicate
- S: Ignores this SQL statement. Alternatively, rolls back if the SQL statement is a definition SQL.
- P: Correct the SQL statement as follows and re-execute:
KFPA11116-E A
Invalid search condition in "HAVING" clause, query-no=aaa
- Structured repetition predicate was specified in the search condition in a HAVING clause
- aaa: Number of the query that specified the predicate
- S: Ignores this SQL statement.
- P: Correct the search condition in the HAVING clause and re-execute.
KFPA11117-E A
Number of aa....aa not equal to number of bb....bb
- The number of aa....aa does not match the number of bb....bb.
- aa....aa
{insert-values|update-values-specified-by-subquery|left-side-row-value-constructor-elements|derived-column-list}
- bb....bb
{insert-columns|update-columns|right-side-row-value-constructor-elements|derived-columns}
- S: Ignores this SQL statement. Rollback occurs in the case of a definition SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11118-E A
Invalid use of update table in update value
- The following error occurred in the use of a table subject to updating:
- When the table to be updated is specified in the FROM clause of a subquery specified in the SET or ADD clause of the UPDATE statement, and the columns of the table to be updated are referenced externally, value expressions with the following attributes cannot be specified in the selection expression of the subquery:
BLOB
BINARY with a maximum length of 32,001 bytes or larger
Repetition column
Abstract data type
- When the UPDATE statement uses a cursor, a subquery that specifies the table to be updated in the FROM clause cannot be specified in the SET clause.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11119-E A
Column "aa....aa" in bb....bb clause must be either group column or within set function, query-no=(ccc,ddd)
- In a query specifying a GROUP BY clause or a set function, the column specification in the SELECT, HAVING, or ORDER BY clause must satisfy either of the following conditions:
- The column specification must be a grouping column.
- The column specification must be specified in the argument of a set function.
- If a value expression other than a column specification is specified in the GROUP BY clause, a grouping column cannot be referenced from a scalar subquery specified in the query's selection expression.
- aa....aa: Name of the column whose specification is invalid
- bb....bb: Name of the clause specifying "aa....aa"
- {SELECT|HAVING|ORDER BY|subquery in SELECT}
- ccc: Number of the innermost query specifying the column
- ddd: Number of the query specifying the clause
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11120-E A
Cannot specify "aa....aa" function in "bb....bb" query-no=(ccc,ddd)
- A set function, SQL/XML set function, or window function is specified at an invalid location.
- aa....aa: {set|SQL/XML set|window|only window}
- bb....bb: Name of the clause or statement in which a set function or window function is specified
- {"WHERE" clause|"SET" clause|"ADD"clause
- |"ON" clause|"GROUP BY" clause|"IF" statement
- |"WHILE" statement|"SET" statement
- |"RETURN" statement|"VALUES" clause
- |"CALL" statement|"WRITE LINE" statement
- |"HAVING" clause|insert statement|subquery|derived table|select list
- | select list with set function|value expression|set operation
- |select list with group by clause|select list with having clause}
- ccc: Query number in which a set function, SQL/XML set function, or window function is specified
- ddd: Query number in which the clause or statement is specified
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11121-E A
Duplicate update items or insert columns
- In an INSERT statement, a column to be inserted cannot be specified more than once.
In an UPDATE statement, a column or attribute cannot be specified more than once as a column to be updated or as an update attribute. An element in a repetition column cannot be specified more than once. - S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11122-E A
More than 255 value expressions in "GROUP BY" clause
- More than 255 value expressions were specified in the GROUP BY clause.
- S: Ignores this SQL statement.
- P: Reduce the number of value expressions in the GROUP BY clause to no more than 255 and re-execute.
KFPA11123-E A
Duplicate columns "aa....aa" in "bb....bb" clause
- The same column cannot be specified more than once in the GROUP BY, ORDER BY, or FOR UPDATE clause, or in a derived column list.
- aa....aa: Name of the column specified more than once, or the sort item specification number
- bb....bb: Name of the clause specifying "aa....aa"
- {GROUP BY|ORDER BY|FOR UPDATE OF|derived column list}
- S: Ignores this SQL statement.
- P: If the specified column name is invalid, correct the column name and re-execute. If the specified column name is correct, delete the invalid specification and re-execute.
KFPA11124-E A
More than 255 columns in "ORDER BY" clause
- More than 255 columns were specified in the ORDER BY clause.
- S: Ignores this SQL statement.
- P: Reduce the number of columns in the ORDER BY clause to no more than 255 and re-execute.
KFPA11125-E A
Invalid integer aa....aa in "ORDER BY" clause
- The following error was detected in the sort item specification number specified in the ORDER BY clause:
- The sort item specification number exceeds the number of derived columns.
- aa....aa: The erroneous sort item specification number
- S: Ignores this SQL statement.
- P: For the sort item specification number, specify the number indicating the location of the derived column in the SELECT clause of the selection expression, and then re-execute.
KFPA11126-E A
"ROW" can not be specified in "ORDER BY" clause using sort item number
- A sort item specification number cannot be specified in the ORDER BY clause of an SQL statement specifying ROW.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11127-E A
Keyword "DISTINCT" already specified in query specification, query-no=aaa
- DISTINCT cannot be specified more than once in one query specification.
- aaa: Number of the query specifying DISTINCT more than one time.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11128-E A
Invalid use of keyword "NULL", query-no=aaa
- One of the following errors was detected in the usage of NULL:
- NULL was specified as a value other than the NULL predicate in a search condition
- NULL was specified in the SELECT clause
- NULL was specified as the object of an arithmetic operation or concatenation operation
- NULL was specified as the argument of a scalar function
- aaa: Number of the query that specified NULL.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11129-E A
More than aa....aa bb....bb
- The number of bb....bb specified in an SQL statement exceeds the maximum number aa....aa.
- aa....aa: Permitted maximum value:
{ 16 |64 |65 |128 |255 |1023 |30000 }
- bb....bb: Specification exceeding the permitted maximum:
- {tables | select columns
- | update columns
- | columns in "INTO" clause
- | variables or parameters
- | columns in "FOR UPDATE OF" clause
- | values in "VALUES" clause
- | view columns
- | "WITH" query columns
- | "java.sql.ResultSet[]" in EXTERNAL NAME clause
- | attributes in type definition
- | data types
- | arguments in function invocation
- | multi-value columns in column name list of ARRAY predicate
- | SQL variables and SQL parameters
- | row value constructor elements
- | derived columns
- | correlation names
- | arguments in XMLQUERY function
- | arguments in XMLEXISTS predicate
- | SQL parameters in C routine}
- S: Ignores this SQL statement.
- P: Reduce the number of bb....bb to no more than aa....aa and re-execute.
KFPA11131-E A
Invalid precision or scale in scalar function "DECIMAL"
- Invalid precision or scale was specified in the DECIMAL scalar function.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11132-E A
Invalid use of aa....aa dd....dd "bb....bb", query-no=ccc
- One of the following was used incorrectly:
- A column, SQL variable, or SQL parameter of the aa....aa type
- An attribute of the aa....aa type
- A function invocation of the aa....aa type, used as a data type for a function return value
- SQL/XML set function, or SQL/XML scalar function
- aa....aa: Incorrectly used data type
{ BLOB |BINARY |abstract |BOOLEAN |XML }
- bb....bb: Name of the incorrectly used column, SQL variable, SQL parameter, attribute, or function
- ccc: Number of the innermost query that specified an incorrectly used column, SQL variable, SQL parameter, attribute, or function
- dd....dd: Type of the incorrectly used name
{ column, SQL variable or SQL parameter | attribute | function invocation | set function }
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11133-E A
Invalid specification of update value for aa....aa column or attribute
- When updating or inserting an abstract data type column or attribute, neither an embedded variable nor the ? parameter can be specified as the insertion value or update value.
- aa....aa: Invalid data type (abstract)
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11134-E A
Invalid use of long data cc....cc "aa....aa", query-no=bbb
- One of the following items was used incorrectly:
- A column of long data, an SQL variable, or an SQL parameter
- An attribute of long data
- A function invocation with a long data data type for its function return value
- Long data refers to any of the following data types:
- CHAR, VARCHAR, MCHAR, MVARCHAR, or BINARY with a definition length of 256 bytes or greater
- NCHAR or NVARCHAR with a definition length of 128 characters or greater
- aa....aa: Name of the incorrectly used column, SQL variable, SQL parameter, attribute, or function
- bbb: Number of the innermost query that specified an incorrectly used column, SQL variable, SQL parameter, attribute, or function
- cc....cc: Type of the incorrectly used name
{ column, SQL variable or SQL parameter
|attribute|function invocation }
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11136-E A
Invalid use of ? parameter in aa....aa statement
- The ? parameter is used in a procedure definition, in a procedure body in a type definition, in a function definition, or in a function body in a type definition modification.
- aa....aa: CREATE PROCEDURE, PROCEDURE definition in CREATE TYPE, CREATE FUNCTION, FUNCTION definition in CREATE TYPE
- S: Ignores this SQL statement
- P: Correct the SQL statement and re-execute.
KFPA11137-E A
More than 255 aa....aa in bb....bb
- The number of items in bb....bb, which was specified in the descriptor displayed for cc....cc, exceeds the maximum number aa....aa.
- aa....aa: { 255 | 30000 }
- bb....bb: { value expressions| row value expressions }
- cc....cc: { "IN" predicate | scalar function "VALUE"| case abbreviation "COALESCE"}
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11138-E A
Invalid use of derived table
- The correlation name for the derived table was not specified. The correlation name for the derived table can be omitted only when the outermost query is specified in the following format:
- SELECT COUNT(*) FROM derived-table
- SELECT COUNT_FLOAT(*) FROM derived-table
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11139-E A
More than 30000 elements in multi-value specification
- The number of elements in a repetition value expression is greater than the maximum allowable value (30000). Repetition value expression refers to ARRAY[element-value, ....].
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Reduce the number of element values, and then rerun the program.
KFPA11140-E A
Invalid national character string literal
- Specified national character string literal contains a syntax error.
- S: Ignores this SQL statement.
- P: Correct the national character string literal in the SQL statement and re-execute.
KFPA11141-E A
More than aa....aa characters in national character string literal
- One of the following numbers is greater than the maximum specifiable number (aa....aa):
- Number of characters specified in a national character string literal
- Number of characters in the result of a concatenation operation between national character string literals
- The following maximum specifiable numbers apply:
- Number when specified in the CREATE TABLE or ALTER TABLE boundary values and storage conditions: 127
- All other cases: 16,000
- aa....aa: 16000 or 127
- S: Ignores this SQL statement.
- P: Correct the national character string literal so that its length does not exceed aa....aa characters, then re-execute.
KFPA11142-E A
Invalid identifier in XDS
- One of the following errors was detected in an identifier being used in the memory database:
- Single- and double-byte characters are mixed together.
- Double-byte space characters are specified.
- S: Ignores this SQL statement.
- P: Correct the identifier and re-execute.
KFPA11144-E A
Invalid aa....aa string literal
- There is a syntax error in the hexadecimal character string literal specification.
- aa....aa:{usage of hex|hex}
- For usage of hex:
- The hexadecimal character string literal is specified in the following locations:
- COMMENT statement
- Plug-in option
- For hex:
- The hexadecimal character length specified in the hexadecimal character string literal is not a multiple of 2.
- A character other than 0-9, a-f, or A-F was specified in the hexadecimal character string literal.
- S: Ignores this SQL statement.
- P:
- When aa....aa is usage of hex:
- Use a character string literal instead of a hexadecimal character string literal.
- When aa....aa is hex:
- Take one of the following actions, and then re-execute:
- In the hexadecimal character string literal, specify a hexadecimal character length that is a multiple of 2.
- Delete any characters other than 0-9, a-f, or A-F that are specified in the hexadecimal character string literal.
KFPA11145-E A
More than 64000 bytes in hex string literal
- The hexadecimal character length specified in the hexadecimal character string literal is more than 64,000 characters.
- S: Ignores this SQL statement.
- P: Reduce the hexadecimal character length of the hexadecimal character literal to a maximum of 64,000 characters.
KFPA11146-E A
More than 255 compound(BEGIN) statements and FOR statement nested
- There are more than 255 nesting levels in the compound statement and FOR statement.
- S: Ignores this SQL statement.
- P: Reduce the nesting level count of the compound statement and FOR statement to 255 or less and re-execute.
KFPA11148-E A
Invalid use of holdable cursor
- The specified holdable cursor is invalid for one of the following reasons:
- A holdable cursor cannot be specified for a single-line retrieval.
- A holdable cursor cannot be specified in a search specifying columns of the abstract data type provided by a plug-in.
- A holdable cursor cannot be specified in a search specifying a function call provided by a plug-in.
- A holdable cursor cannot be specified in a search of a named derived table specified in a function call provided by a plug-in.
- A holdable cursor cannot be specified in a search using a list.
- A holdable cursor cannot be specified in a search of a transaction-specific temporary table (a temporary table that specifies ON COMMIT DELETE ROWS).
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute. For details about plug-in support for holdable cursors, check the values in the PLUGIN_HOLDABLE column in the dictionary table SQL_PLUGINS. For details about the dictionary table SQL_PLUGINS, see the HiRDB Version 9 UAP Development Guide.
KFPA11149-E A
Invalid use of keyword "ROW"
- One of the following errors was detected in the usage of ROW:
- ROW cannot be specified in a query specifying the GROUP BY clause, HAVING clause, or a set function.
- ROW cannot be specified in a subquery (including derived tables in the FROM clause).
- ROW cannot be specified in a query using UNION.
- ROW cannot be specified in a view definition query or in a WITH clause.
- ROW cannot be specified in a derived table of a FOR statement cursor specification.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11154-E A
Invalid use of SQL parameter or SQL variable "aa....aa"
- An identifier was specified in a location where only a value specification is allowed in an SQL statement other than CREATE PROCEDURE, CREATE TRIGGER, CREATE FUNCTION, or CREATE TYPE.
Note that you cannot specify an SQL parameter or SQL variable in an SQL statement other than CREATE PROCEDURE, CREATE TRIGGER, CREATE FUNCTION, or CREATE TYPE. The only identifiers that can be specified as a value specification are SQL parameters and SQL variables. - aa....aa: Name of the specified SQL variable or SQL parameter
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11155-E A
Invalid use of "aa....aa" clause
- A FOR UPDATE OF or FOR READ ONLY clause cannot be specified in any location other than a cursor declaration or a dynamic SELECT statement. A FOR READ ONLY clause cannot be specified in a single-row SELECT statement. In addition, you cannot specify the lock option and FOR UPDATE with NOWAIT specified at the same time.
- aa....aa: Name of the invalid clause:
- {"FOR UPDATE OF" clause|"FOR READ ONLY" clause|"FOR UPDATE" clause with "NOWAIT"}
- S: Ignores this SQL statement.
- P: Correct the SQL statement or update option and re-execute.
KFPA11156-E A
Invalid query for "UPDATE" or "DELETE" statement with cursor
- None of the following can be specified in a query that updates or deletes data using a cursor, or in a query that specifies the FOR UPDATE clause:
- Joining tables
- FROM clause derived table
- Grouping
- Set function
- Set operation
- Duplicate elimination
- Specification, in the FROM clause of a subquery, of a table specified in a FROM clause of the outermost query specification
- Read-only viewed table
- WITHOUT LOCK NOWAIT
- Query name specified in a FROM clause of the outermost query specification in the query expression body that specified a WITH clause
- Result set returned from a procedure
- Window function
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11157-E A
Invalid use of "UPDATE" or "DELETE" statement with cursor
- One of the following errors occurred in the UPDATE or DELETE statement using a cursor:
- The UPDATE or DELETE statement using a statically declared cursor cannot be preprocessed by the PREPARE statement.
- The UPDATE or DELETE statement using a cursor that can be preprocessed cannot be statically executed.
- The cursor is incorrectly declared or is not assigned.
- S: Ignores this SQL statement.
- P: Take one of the following actions:
- If the SQL statement is executed dynamically, revise the SQL statement to an UPDATE or DELETE statement that uses a preprocessable cursor, and re-execute.
- If the SQL statement is executed statically, revise the SQL statement to an UPDATE or DELETE statement that uses a statically declared cursor, and re-execute.
- Revise the cursor declaration or assignment and re-execute.
KFPA11158-E S
Invalid SQL statement for pddef utility
- The specified SQL statement cannot be executed by the database definition utility (pddef).
- S: Ignores this SQL statement.
- P: Specify an SQL statement that can be executed by the database definition utility and re-execute.
KFPA11159-E A
Unable to specify aa....aa in bb....bb SQL
- An ASSIGN LIST statement, DROP LIST statement, or a search using a list cannot be embedded directly in the host program for execution. Also, GET DIAGNOSTICS cannot be dynamically executed.
- aa....aa:
{ ASSIGN LIST|DROP LIST|
query using LIST|GET DIAGNOSTICS }
- bb....bb: {dynamic|static}
- S: Ignores this SQL statement.
- P: Take one of the following actions:
- Specify the ASSIGN LIST statement or DROP LIST statement in the PREPARE statement or EXECUTE IMMEDIATE statement.
- In a PREPARE statement, specify a search that uses a list.
- Do not specify GET DIAGNOSTICS in a PREPARE statement or an EXECUTE IMMEDIATE statement.
KFPA11161-E A
Zero divisor specified
- Zero was specified as the divisor.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11162-E A
Ending label name must be the same name as beginning label name, beginning-label=aa....aa, ending-label=bb....bb
- The beginning label does not match the ending label.
- aa....aa: Specified beginning label
- bb....bb: Specified ending label
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11163-E A
Invalid search condition in IF statement or WHILE statement
- The following error was detected in the search condition specified in the IF or WHILE statement:
- A subquery is specified.
- A structured repetition predicate was specified.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11164-E A
Missing cursor name after "where current of"
- The cursor name or extended cursor name is missing in an UPDATE or DELETE statement that uses a cursor.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11165-E A
Invalid value "aa....aa" of cc....cc "bb....bb"
- The following error exists in the SQL statement:
- There is an error in the value or identifier of the specified compile option.
- aa....aa: Specified compile option, or the value or identifier of the option
- If the option is longer than 30 characters, and then the first 30 characters are displayed. Also, the option becomes ******** if the option value is a null character string.
- bb....bb: Invalid compile option or other option
{ISOLATION|OPTIMIZE LEVEL|ADD OPTIMIZE LEVEL|SUBSTR LENGTH|COLLATING_SEQUENCE|TRAILING_SPACE|NULLABLE_SCHEMA|TABLE|USING_BES|USER|PASSWD}
- cc....cc: Error location:
{compile option|OPTIONS}
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11167-E A
More than 255 WHEN clauses in CASE expression, query_no=aaa
- More than 255 WHEN clauses were specified in one CASE expression or in an outermost CASE expression that included nested CASE expressions.
- aaa: Number of the query that specified a CASE expression
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11168-E A
Invalid search condition in CASE expression, query_no=aaa
- The search condition in a CASE expression contains the following error:
- A structured repetition predicate was specified.
- aaa: Number of the query that specified a CASE expression
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11169-E A
Unable to specify joined table in view definition, "WITH" query or query expression body with "WITH" clause
- A joined table cannot be specified in a view-definition-derived query expression, a derived query expression in a WITH clause, or in a query expression body for a query expression containing a WITH clause specification.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11170-E A
Unable to specify aa....aa in environment using bb....bb character code set
- While Unicode (UTF-8) or the Chinese character encoding GB18030 (CHINESE-GB18030) were being used, one of the following errors was detected:
- A national character literal was used.
- A column with the national character data type was defined.
- While one-byte character codes were being used, one of the following errors was detected:
- A national character or mixed character string literal was used.
- A column with the national character or mixed character data type was defined.
- While a character encoding other than SJIS was being used, the following error was detected:
- An EBCDIK character set specification was used.
- While a character encoding other than Unicode (UTF-8) was being used, the following error was detected:
- A UTF16 character set specification was used.
- aa....aa: {national character|mixed character|national character or mixed character|character set "EBCDIK"|character set "UTF16"}
- bb....bb: {chinese|ujis|utf-8|lang-c|chinese-gb18030|sjis}
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11171-E A
Duplicate value expressions in "GROUP BY" clause
- Only one value expression of the same type can be specified in the GROUP BY clause.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11172-E A
Unable to specify outer reference "aa....aa"."bb....bb" in query with grouping by expression, query-no=ccc
- If a value expression other than the column specification is used in the GROUP BY clause contained in a subquery, a column that makes an external reference cannot be specified in the WHERE clause or ON clause for the same subquery.
- aa....aa: Table identifier or correlation name
- bb....bb: Name of column that makes an external reference
- ccc: Number of the query specifying a column that makes an external reference
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11173-E A
Invalid value expression in "GROUP BY" clause, query-no=aaa
- One of the following errors was detected in the GROUP BY clause:
- A value expression other than a column specification is specified in a view definition or in the GROUP BY clause of a derived query expression containing a WITH clause.
- A value expression other than a column specification is specified in the GROUP BY clause of a subquery contained in a WHERE clause for a query specification in which a value expression other than a column specification is specified in the GROUP BY clause.
- A ? parameter or embedded variable was specified in the value expression in the GROUP BY clause.
- A component specification is specified in a value expression in a GROUP BY clause.
- A subquery is specified in a value expression in a GROUP BY clause.
- aaa: Number of the query specifying an invalid GROUP BY clause
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11174-E A
RETURN statement not specified in function definition
- The RETURN statement is not specified in the function definition.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11175-E A
Unable to specify component specification in derived table
- Component specifications are not allowed in a derived table.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11176-E A
Specify only routine control statement except FOR statement in function definition
- Only routine control SQL statements other than the FOR statement are allowed in a function definition.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11177-E A
Invalid use of "AS" clause or ? parameter or embedded variable for argument in aa....aa
- One of the following errors occurred in the specification of an AS data-type clause, ? parameter, or embedded variable:
- Either a ? parameter or embedded variable was specified in an argument without specifying AS data-type.
- The specified data type cannot be specified in AS data-type.
Function invocation:
A non-predefined data type was specified.
Scalar function (LENGTH, SUBSTR, or POSITION):
A data type other than BLOB or BINARY was specified.
XML constructor function:
A data type other than BINARY was specified.
XMLSERIALIZE function:
A data type other than VARCHAR or BINARY was specified.
XMLPARSE function:
A data type other than the following was specified in AS data-type:
Character string data type (CHAR, VARCHAR)
Mixed character string data type (MCHAR, MVARCHAR)
BINARY type
- AS data-type was specified in an argument other than a ? parameter or an embedded variable.
- A unary operation using a ? parameter or an embedded variable was specified for an argument.
- If aa....aa is an assignment statement, one of the following errors occurred in the specification of the assignment value:
- A ? parameter or embedded variable was specified in the assignment value without specifying AS data-type.
- A data type other than BLOB or BINARY was specified in AS data-type.
- aa....aa: Statement containing the syntax error
- {function invocation
- |scalar function "LENGTH"
- |scalar function "SUBSTR"
- |scalar function "POSITION"
- |assignment statement
- |XML constructor
- |XMLSERIALIZE
- |XMLPARSE }
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11179-E A
Unable to specify aa....aa in search condition of ARRAY predicate, query-no=bbb
- The following specifications are not allowed in a search condition in a structured repetition predicate:
- A structured repetition predicate
- An XMLEXISTS predicate
- A subquery
- A column other than those specified in ARRAY(repetition-column [, repetition-column]....).
- One of the following specifications made in a predicate comparison condition:
- System-defined scalar function, function invocation, and predicate that includes IS_USER_CONTAINED_IN_HDS_GROUP.
- Predicate that does not include a column specification
- aa....aa:
{ ARRAY predicate |XMLEXISTS predicate |subquery
|except columns in column name list of ARRAY predicate
|function invocation |predicate without column }
- bbb: Number of the query specifying a predicate
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11180-E A
Subscript specified for single-value column, SQL variable, or SQL parameter "aa....aa", query-no=bbb
- Subscripts cannot be specified in a non-repetition column, an SQL variable, or the SQL parameter "aa....aa".
- aa....aa: Item for which an incorrect subscript was specified
- bbb: Number of the innermost query specifying "aa....aa".
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11181-E A
Invalid use of multi-value column "aa....aa" without subscript, query-no=bbb
- A repetition column that omitted subscripts is specified at an invalid location.
- aa....aa: Column name of the column from which subscripts are omitted
- bbb: Number of the innermost query specifying "aa....aa".
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11182-E A
Invalid use of multi-value column "aa....aa" with subscript, query-no=bbb
- A repetition column with a subscript specification is specified at an invalid location.
- aa....aa: Column name of the repetition column with a subscript specification
- bbb: Number of the innermost query specifying "aa....aa".
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11183-E A
Invalid use of multi-value column "aa....aa", query-no=bbb
- A repetition column is specified at an invalid location.
- aa....aa: Name of the incorrectly specified column. However, if this incorrectly specified column is a column of a named derived table that was derived from a set function that has a repetition column as an argument, the column name of the base table of the applicable named derived table is displayed.
- bbb: Number of the innermost query specifying "aa....aa".
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11184-E A
Subscript of multi-value column "aa....aa" exceeds maximum number of elements, query-no=bbb
- The subscript specified in a repetition column exceeds the maximum number of elements.
- aa....aa: Column name of the repetition column
- bbb: Number of the innermost query specifying "aa....aa".
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11185-E A
Invalid specification of update or insert value for column "aa....aa"
- The insert or update value contains one of the following errors:
- Insert value:
- A non-NULL simple structure value is specified for a repetition column that omitted subscripts.
- A repetition structure value is specified for a column in a simple structure.
- Update value in a SET clause:
- A non-NULL simple structure value is specified for a repetition column that omitted subscripts.
- A repetition structure value is specified in a component specification, a column of a simple structure, or a repetition column with a subscript specification.
- Update value in ADD clause:
- A simple structure value is specified.
- A subquery is specified for the element value of a repetition column.
- aa....aa: The column name with an insert or update value specification error, or the column name in a component specification
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11186-E A
Invalid subscript for multi-value column "aa....aa", query-no=bbb
- The subscript specified for a repetition column contains an error.
- aa....aa: Column name of the repetition column
- bbb: Number of the innermost query specifying "aa....aa".
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11187-E A
DISTINCT specified for multi-value column, query-no=aaa
- DISTINCT cannot be specified for a repetition column.
- aaa: Number of the innermost query specifying a repetition column
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11188-E A
Invalid query with FLAT specification
- The following error occurred in a query with FLAT specified in the FROM clause:
- A column other than the column specified by FLAT is specified.
- The number of columns specified in FLAT exceeds 16.
- Not all of the indexes included for the columns specified in FLAT are defined. Another possibility is that, for queries that include an RDAREA name specification, the number of partitions of the indexes included for all columns specified in FLAT is different from the number of partitions of the table.
- The columns specified in FLAT do not include any repetition columns.
- A viewed table or query is specified in the FROM clause.
- FLAT is specified in the SELECT clause of INSERT SELECT, a view definition, the WITH clause, a FROM clause derived table, or a subquery.
- The following items are specified:
FOR READ ONLY
FOR UPDATE clause
LIMIT clause
GROUP BY clause that specifies a value expression other than a column specification
Component specification
Set function containing a FLAT specification
Function call
Subquery
Set operation
Table join
Column that specifies a subscript
- The following item is specified in a search condition:
Structured repetition predicate
- S: Ignores this SQL statement.
- P: Take one of the following actions:
- Correct the SQL statement and re-execute.
- If an RDAREA name is specified, make sure that the number of partitions of the defined index is equal to the number of partitions of the table, and then re-execute the SQL statement.
KFPA11189-E A
Invalid subscript for multi-value column "aa....aa"
- The maximum number of elements in the repetition column "aa....aa" specified in the CREATE TABLE or ALTER TABLE statement is invalid.
- aa....aa: Column name of the repetition column
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11191-E A
Subquery specified in ASSIGN LIST statement
- A subquery (excluding subqueries in an IN predicate without a NOT specification that do not make an external reference) is specified in an ASSIGN LIST statement.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11192-E A
Two or more selection items specified in scalar subquery, query-no=aaa
- More than one retrieval item is specified in a scalar subquery.
- aaa: Number of the subquery in which more than one retrieval item is specified
- However, if a set operation is specified in a subquery, this becomes the number of the first specified query specification among the query specifications of the set operation.
- S: Ignores this SQL statement.
- P: Correct the SQL statement so that only one retrieval item is specified and re-execute.
KFPA11194-E A
Unable to specify qualified column name in ORDER BY clause in query using set operation
- A qualified column name has been specified in the ORDER BY clause of a query using a set operation.
- S: Ignores this SQL statement.
- P: Correct the SQL statement as follows and re-execute:
- If AS column-name is specified in the SELECT clause specified in the first query, specify the column name specified in AS column-name.
- If there is no AS column-name specification, delete the table specification.
- Specify a sort item specification number.
- If no sorting is to be performed, delete the ORDER BY clause.
KFPA11195-E A
Derived tables for SET operation must have same number of columns
- The number of derived columns does not match the number specified for a set operation.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11196-E A
Precision exceeds ddd in aa....aa, result data type decimal, column-no=bbbbb, query-no=ccc
- The data type of the execution result of the scalar function VALUE, the result of a CASE expression, the execution result of a set operation, or the result of a function invocation, is the DECIMAL data type. Or, the resulting precision exceeded ddd.
- aa....aa: SQL statement containing the error
{ scalar function |SET operation |CASE expression
|function invocation }
- bbbbb: The column number indicating which element in the derived table exceeded ddd in precision (the value 0 indicates a scalar function, a CASE expression, or a function invocation)
- ccc: Number of the query specifying the error-causing scalar function, CASE expression, set operation, or function invocation
- ddd: Maximum precision
- The maximum precision is determined by the following conditions:
Value of system common definition pd_sql_dec_op_maxprec | Precision of the operands | Maximum precision |
---|
29 or omitted | All 29 digits or fewer | 29 |
Includes operands with 30 digits or more | 38 |
38 | Any | 38 |
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P:
- Correct the decimal data specified in the VALUE scalar function, the CASE expression, or the set operation, and then re-execute.
- For a function invocation, correct the data type in the RETURNS clause in the function definition, and then re-execute.
KFPA11197-E A
Inconvertible data type in SET operation, column-no=aaaaa, query-no=bbb
- A set operation was specified, but the data type of the corresponding column cannot be converted. If the data type of the corresponding column is a character string data type, conversion is not possible when the character sets are different. However, if the second and subsequent corresponding columns in the set operation are the following value expression, conversion is performed based on the character set of the first corresponding column in the set operation:
- aaaaa: Number of the column of the derived table resulting in the error
- bbb: Number of the query resulting in an error
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11198-E A
Invalid specification of SET clause in UPDATE statement
- One of the following error corrections must be made to the UPDATE statement:
- If only one update target item is specified as the assignment target for the SET clause, omit the parentheses enclosing the update target's name.
- If multiple update target items are specified as the assignment targets for the SET clause, enclose all the update target names in parentheses. In this case, specify a subquery for the assignment source.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11201-E A
Invalid item specification, authorization identifier aa....aa, table identifier aa....aa, table identifier, correlation name, query name, statement label or routine identifier "bb....bb", query-no=ccc
- In the SQL statement, the table specification that qualifies a column name is not a valid name. Or, a qualifier of the SQL parameter or the SQL variable is not a valid name specified in the SQL statement.
The invalid qualifier is aa....aa.bb....bb or "bb....bb". - aa....aa: Authorization identifier specified in the table specification
- bb....bb: Table identifier, correlation name, query name, statement label name, or routine name
- ccc: Number of the innermost query specifying the invalid qualifier
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11202-E A
Column, SQL variable, or SQL parameter "aa....aa" not found in any tables, query names, statement label, or routines, query-no=bbb
- Column "aa....aa" cannot be found in any table of the SQL statement or query, or in a query name. Or, the SQL variable or SQL parameter "aa....aa" is not declared in the routine.
- aa....aa: SQL variable, SQL parameter, or column name that could not be found in the SQL statement
- bbb: Number of the query specifying the column, SQL variable, or SQL parameter.
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement, and then re-execute.
KFPA11203-E A
Column "aa....aa" ambiguous, query-no=bbb
- Because column "aa....aa" was found in more than one table in this query or in more than one query name, the table or query name column corresponding to column "aa....aa" cannot be determined.
- aa....aa: Name of the column that was found more than once in the query
- bbb: Number of the query specifying the column
- S: Ignores this SQL statement.
- P: Modify the column name with the correct table name, correlation name, or query name, and then re-execute.
KFPA11204-E A
aa....aa bb....bb."cc....cc" not found in system
- aa....aa bb....bb."cc....cc" was not found in the HiRDB system.
In a data manipulation SQL statement that includes a WITH clause, if aa....aa is Table, table bb....bb."cc....cc" was not found in the HiRDB system, or query name cc....cc was not found in the WITH clause. - aa....aa: {Table|Index|Trigger|Sequence}
- bb....bb: Authorization identifier
- cc....cc:
- When aa....aa is Table: Table identifier, query name
- When aa....aa is Index: Index identifier
- When aa....aa is Trigger: Trigger identifier
- When aa....aa is Sequence: Sequence generator identifier
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11205-E A
Column "aa....aa" not found in table bb....bb."cc....cc"
- Column aa....aa was not found in table bb....bb."cc....cc", in the correlation name of a derived table of the FROM clause, or in query name "cc....cc" in a query of the WITH clause.
- aa....aa: Column name
- bb....bb: Authorization identifier
- cc....cc: Table identifier (for a derived table, the correlation name) or query name
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
- If the column indicated in aa....aa is a reserved column, reserved columns cannot be specified in this SQL statement. Modify the SQL statement so that it does not specify a reserved column, and then retry the operation.
KFPA11206-E A
Invalid aa....aa type
- One of the following errors was detected in the table specification:
- DROP TABLE cannot be used to delete a viewed table definition.
- DROP VIEW cannot be used to delete a base table definition.
- aa....aa: Table
- S: Ignores this SQL statement.
- P: When executing DROP TABLE, specify a base table, and when executing DROP VIEW, specify a viewed table, and then retry the operation.
KFPA11207-E A
cc....cc not found in table aa....aa."bb....bb"
- No cc....cc is defined for table aa....aa."bb....bb".
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc:
{ CLUSTER KEY |PRIMARY KEY |PRIMARY CLUSTER KEY }
- S: Ignores this SQL statement.
- P: Delete this SQL statement.
KFPA11208-E A
Sort column "aa....aa" must be selected column
- Column "aa....aa" specified in the ORDER BY clause is not specified in the SELECT clause of the outermost query.
- aa....aa: Name of the sort column
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11209-E A
Column cannot be updated
- An attempt was made to update a column that cannot be updated. The following columns cannot be updated:
- Column specifying a storage condition
- Column specifying a cluster key
- Column of a table with the WITHOUT ROLLBACK specification that specifies the index
- S: Invalidates this transaction.
- P: Correct the SQL statement and re-execute.
KFPA11210-E A
"NOT NULL" constraint violation
- An attempt was made to set the NULL value in a column where the NULL value cannot be set, or in an argument passed to a Java stored procedure.
- A NULL value cannot be set in a column that has the NOT NULL constraint.
- A NULL value cannot be set in a table column or ROW that has the FIX attribute.
- A NULL value cannot be set in a cluster key or for configuring a primary key.
- If a Java stored procedure is defined where a NULL value data type cannot be set as the argument for a Java method specified as an external routine, a NULL value cannot be set for the argument used when the Java stored procedure is called.
- S: Ignores this SQL statement.
- P: Set a value other than the NULL value in the column that cannot accept NULL values or in the argument of the Java stored procedure, and then re-execute. Or, redefine the Java stored procedure by changing the argument of the Java method to a data type that can be set to a NULL value, and re-execute.
KFPA11211-E A
Duplicate identifier "aa....aa" in "FROM" clause, query-no=bbb
- Name "aa....aa" is duplicated in the FROM clause. The same correlation name cannot be used for more than one table. Or, the correlation name cannot be the same as the table identifier or query name.
- aa....aa: Name
- bbb: Number of the query specifying a duplicate name
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11212-E A
"NULL" predicate cannot be specified in column "aa....aa" with "NOT NULL", query-no=bbb
- The NULL predicate was specified for a column for which the null value cannot be specified:
- A NULL predicate cannot be specified for a column that has the NOT NULL constraint.
- A NULL predicate cannot be specified for a column or ROW that has the FIX attribute.
- A NULL predicate cannot be specified for a column configured as a cluster key.
- aa....aa: Name of the column for which the invalid NULL predicate was specified
- bbb: Number of the innermost query specifying the invalid column
- S: Ignores this SQL statement.
- P: Correct the search condition and re-execute.
KFPA11213-E A
"ROW" specification ambiguous
- Because there is more than one applicable table in a query specifying ROW, the table corresponding to the ROW specification cannot be determined.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11214-E A
Unable to specify "ROW",due to aa....aa
- Cannot specify ROW due to reason aa....aa.
- aa....aa: The reason ROW cannot be specified
- non-"FIX" attribute table: The table does not have the FIX attribute.
- column character set specification: There is no character set specification column in the table.
- endian mismatch: The endian of the client and server do not match.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
- In the case of an endian mismatch between client and server, see the following table regarding the compatibility of the endian of various clients and servers:
Client | Server |
---|
HP-UX | Solaris | AIX | Linux | Windows |
---|
HP-UX | Y | Y | Y | N | N |
Solaris | Y | Y | Y | N | N |
AIX | Y | Y | Y | N | N |
Linux | N | N | N | Y | Y |
Windows | N | N | N | Y | Y |
- Legend:
- Y: Endian does match.
- N: Endian does not match.
KFPA11215-E A
Invalid update VALUE for "ROW" specification
- When specifying ROW and inserting or updating data, specify an embedded variable, ? parameter, SQL variable, or SQL parameter was specified as the update value.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11216-E A
"ROW" cannot be specified for inner table
- ROW cannot be specified for an inner table specified for an outer join of a joined table.
- S: Ignores this SQL statement; executes a rollback in the case of a definition SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11217-E A
Invalid use of aa....aa
- There is an error in the specification of SQLCODE, SQLCOUNT, SQLCODE_OF_LAST_CONDITION, or SQLERRM_OF_LAST_CONDITION.
These values can only be used in a condition in an IF or WHILE statement, in an assignment value in an assignment (SET) statement, in a return value in a RETURN statement, or in a value expression in a WRITE LINE statement. - aa....aa: { SQLCODE | SQLCOUNT
- | SQLCODE_OF_LAST_CONDITION
- | SQLERRM_OF_LAST_CONDITION }
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11218-E A
Duplicate column "aa....aa" in derived table
- A duplicate column, "aa....aa", is present in the derived table of the FROM clause.
- aa....aa: Duplicate column name
- S: Ignores this SQL statement. However, if this SQL statement is a definition SQL statement, it is rolled back.
- P: Correct the SQL statement and re-execute.
KFPA11220-E A
Sort column "aa....aa" found more than once in derived table
- Column "aa....aa" specified in the ORDER BY clause was detected more than once in the table derived as the result of a query.
- aa....aa: Column name specified in the ORDER BY clause
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11223-E A
Invalid type, aa....aa must be specified
- An invalid data type is specified.
If aa....aa is abstract data, a subtype cannot be defined by specifying a plug-in-provided data type in the under clause. - aa....aa: Type of the data type that needs to be specified
- abstract data: Abstract data type
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11224-E A
aa....aa type "bb....bb"."cc....cc" not found in system
- The user-defined type "bb....bb" or "cc....cc" of the type aa....aa is not in the HiRDB system.
- aa....aa: Data type
{Data |Index}
- bb....bb: Authorization identifier (owner of the type)
- cc....cc: Data type identifier or index type identifier
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11227-E A
Column "aa....aa" in "ON" condition not found in any tables, query-no=bbb
- The column name "aa....aa" specified in the ON condition is not found in any of the following tables:
- Table joined in a joined table containing the ON condition
- Table that can make an external reference
- aa....aa: Column name
- bbb: Query number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11228-E A
Attribute "aa....aa" not found in data type "bb....bb"."cc....cc"
- The attribute "aa....aa" is not in the data type "bb....bb"."cc....cc".
- aa....aa: Attribute name
- bb....bb: Authorization identifier (owner of the user-defined type)
- cc....cc: Data type identifier
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFP11231-E A
SQL variable "aa....aa" already defined
- The specified SQL variable "aa....aa" is already defined.
- aa....aa: SQL variable
- S: Ignores this SQL statement and executes rollback.
- P: Correct the SQL statement and re-execute.
KFPA11232-E A
Cursor "aa....aa" already defined
- The specified cursor is already defined.
- aa....aa: Cursor name
- S: Ignores this SQL statement and executes rollback.
- P: Correct the SQL statement and re-execute.
KFPA11233-E A
DECLARE CURSOR statement missing for cursor "aa....aa"
- The specified cursor "aa....aa" is not declared as a cursor.
- aa....aa: Cursor name
- S: Ignores this SQL statement and executes rollback.
- P: Correct the SQL statement and re-execute.
KFPA11234-E A
Invalid statement label "aa....aa" in LEAVE statement
- One of the following errors was found in statement label "aa....aa" of the LEAVE statement.
- The statement label specified in the LEAVE statement was not found.
- The statement label specified in the LEAVE statement is not a statement label of a compound statement that includes that LEAVE statement, or a statement label of a WHILE statement.
- A LEAVE statement that omits the label name is not included in the compound statement or WHILE statement.
- A LEAVE statement to exit handler operation was specified while the handler was running.
- A FOR statement loop variable name, which cannot be specified.
- aa....aa: Statement label (******** when the label name is omitted)
- S: Ignores this SQL statement and executes rollback.
- P: Correct the SQL statement and re-execute.
KFPA11235-E A
Number of call parameters not equal to number of SQL parameters
- The number of arguments specified in the CALL statement does not match the number of SQL parameters of the procedure to be called.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11236-E A
Invalid use of SQL parameter or column "aa....aa", due to in/out parameter mode or qualification by old row value correlation
- One of the following usage errors was found in SQL parameter "aa....aa" that the SQL parameter or old correlation name qualified:
- An input parameter or column qualified by an old correlation name was specified in a FETCH statement, in the INTO clause of a single-row SELECT statement, or in the assignment target of an assignment statement.
- An argument definition of a routine subject to the CALL statement specifies an input parameter or column qualified by the old correlation name in the OUT or INOUT argument.
- An output parameter was specified in a location other than the FETCH statement, the INTO clause in a single-row SELECT statement, the assignment target in an assignment statement, or the value expression in a WRITE LINE statement.
- An output parameter was specified in the IN argument of the argument definition for a routine that is subject to the CALL statement.
- aa....aa: SQL parameter
- S: Ignores this SQL statement and executes rollback.
- P: Correct the SQL statement and re-execute.
KFPA11237-E A
Unable to specified column "aa....aa", query-no=bbb
- Column "aa....aa" is specified in a specification-disabled location.
A specification-disabled location is either of the following: - Pattern character string or escape character in the LIKE predicate
- Pattern character string or escape character in the SIMILAR predicate
- The right-hand value of the IN predicate
- aa....aa: Column that was specified incorrectly
- bbb: Number of the query incorrectly specifying the column
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P:
- Correct the SQL statement and re-execute.
- If the same column name as the SQL variable or SQL parameter exists in the SQL statements table, qualify the SQL variable or SQL parameter with a statement label and procedure name.
KFPA11238-E A
Invalid parameter mode of argument in call statement for SQL parameter definition of procedure
- The argument specification (IN, OUT, INOUT) specified in the CALL statement does not match the SQL parameter specification (IN, OUT, INOUT) of the procedure to be called.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11240-E A
Duplicate statement label or loop variable "aa....aa" appeared in the scope of statement label or loop variable
- The same statement label or loop variable is specified more than once in statement labels or loop variables contained in a compound statement or in a WHILE or FOR statement.
- aa....aa: Statement label name or loop variable name
- S: Ignores this SQL statement and executes rollback.
- P: Correct the SQL statement and re-execute.
KFPA11241-E A
Invalid table specification, as qualiifier, authorization identifier aa....aa, table identifier or correlation name or query name "bb....bb", query-no=ccc
- The specified column name or table specification that qualifies * or ROW is not the valid name specified in the SQL statement.
The invalid qualifier is aa....aa.bb....bb or "bb....bb". - aa....aa: Authorization identifier specified in the table specification
- bb....bb: Table identifier, correlation name, or query name
- ccc: Number of the innermost query specifying the invalid qualifier
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11242-E A
Column "aa....aa" not found in any tables or query names, query-no=bbb
- Column "aa....aa" cannot be found in any SQL statement, table with a query specification, or query name.
- aa....aa: Name of the column that is not in the SQL statement, query specification table, or query name
- bbb: Number of the query specifying a column name not listed in the table
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11243-E A
Table aa....aa."bb....bb" with multi-value column in joined table
- The following tables cannot be specified in a joined table:
- Tables containing a repetition column
- Tables derived from a table containing a repetition column
- aa....aa: Authorization identifier for a table containing a repetition column, or for a table derived from a table containing a repetition column
- bb....bb: Table identifier for a table containing a repetition column, or for a table derived from a table containing a repetition column
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11245-E A
Invalid part "aa....aa" in EXTERNAL NAME
- One of the following errors was found in the external routine name:
- In the case of an external Java stored routine:
- An extraneous character string was detected at the end.
- A letter or keyword that is syntactically invalid was detected.
- A JAR file name or class name does not begin with an alphabetic character.
- A JAR file name exceeds 255 bytes.
- A class name, including the package name, exceeds 255 bytes.
- A method name exceeds 255 bytes.
- In the case of an external C stored routine:
- An extraneous character string was detected at the end.
- A letter that is syntactically invalid was detected.
- An external function identifier begins with a number.
- aa....aa: Area with an invalid external routine name. If a character that is syntactically invalid was detected, that character and its hexadecimal representation will be shown in parentheses.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11246-E A
Incomplete EXTERNAL NAME
- The external routine name is incomplete.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11247-E A
Invalid Java method argument "aa....aa" in EXTERNAL NAME
- One of the following errors was found in the Java method argument of the external routine name:
- Another data type was specified following the java.sql.ResultSet type.
- The java.sql.ResultSet type was not specified as an array.
- A multi-dimensional array was specified for the java.sql.ResultSet type.
- The byte type was not specified for an array.
- A multi-dimensional array was specified for the byte type.
- A multi-dimensional array was specified for a data type that is not the byte type.
- The java.sql.ResultSet type was specified in CREATE FUNCTION.
- aa....aa: Argument of the Java method containing the error
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11248-E A
Invalid Java method return data type "aa....aa" in EXTERNAL NAME
- One of the following errors was found in the Java method return portion of the external routine name:
- The java.sql.ResultSet type was specified.
- An array was specified for a data type that is not the byte type.
- The byte type was not specified for an array
- A multi-dimensional array was specified for the byte type.
- aa....aa: Java method return portion containing the error
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11249-E A
Invalid specification of style in PARAMETER STYLE
- One of the following errors was detected in the parameter style:
- JAVA was specified for the LANGUAGE clause, but a parameter style other than JAVA was specified for the PARAMETER STYLE clause.
- SQL was specified for the LANGUAGE clause.
- C was specified for the LANGUAGE clause, but a parameter style other than RDSQL was specified for the PARAMETER STYLE clause.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11250-E A
Invalid number of DYNAMIC RESULT SETS
- One of the following errors has occurred:
- The number of result sets specified in the DYNAMIC RESULT SETS clause was a negative value or exceeded the maximum value.
- The number of result sets specified in the DYNAMIC RESULT SETS clause was smaller than the number of result sets specified in the Java signature with external routine specification.
- A cursor that specifies WITH RETURN was declared in an SQL procedure, and 0 was specified in the DYNAMIC RESULT SETS clause, or the DYNAMIC RESULT SETS clause was not specified.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11251-E A
Invalid item specification, authorization identifier aa....aa, statement label or routine identifier or loop variable "bb....bb", query-no=ccc
- The qualifier specification for the SQL parameter or an SQL variable is invalid in SQL statements, or a column is specified in an incorrect location.
The invalid qualifier is aa....aa.bb....bb or "bb....bb". - aa....aa: The authorization identifier specified in the item specification
- bb....bb: Statement label name, routine name, loop variable name, or table identifier
- ccc: Number of the innermost query specifying an invalid qualifier
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11252-E A
SQL variable or SQL parameter "aa....aa" not found in any statement label or routines, query-no=bbb
- Either the SQL variable or the SQL parameter "aa....aa" is not declared in the routine, or a column name is specified in an incorrect location.
- aa....aa: The SQL variable, SQL parameter, or column name that is not in the routine
- bbb: Number of the innermost query specifying an SQL variable, SQL parameter, or column name not found in the routine
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11254-E A
Invalid specification aa....aa-th argument in CALL statement, reason=parameter mode "bb....bb"
- One of the following errors was found in the aa....aath argument of the CALL statement.
- The argument is a value expression, but a parameter mode other than IN was specified.
- The argument is a value expression, but the call procedure was a parameter mode other than IN.
- aa....aa: Argument number containing the error
- bb....bb: Parameter mode of the CALL statement argument, or parameter mode of the calling procedure
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11255-E A
SQL variable "aa....aa" not found in statement label or loop variable "bb....bb"
- SQL variable "aa....aa" is not in statement label or loop variable "bb....bb".
- aa....aa: SQL variable that does not exist
- bb....bb: Statement label name or loop variable name
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11256-E A
SQL parameter "aa....aa" not found in routine bb....bb."cc....cc"
- SQL parameter "aa....aa" is not in routine bb....bb."cc....cc".
- aa....aa: SQL parameter that does not exist
- bb....bb: Authorization identifier
- cc....cc: Routine name
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11259-E A
Unable to specify invocation of aa....aa "bb....bb"."cc....cc" in definition of dd....dd with same name
- When bb....bb is the authorization identifier of a routine being defined:
- You cannot specify a call to a routine inside a routine definition when the routine being called and the routine being defined match in the following respects:
- When aa....aa is function:
- If the name of a called function specified in the body of function is qualified with an authorization identifier, when the called function and the function being defined share the same authorization identifier, routine identifier, and number of arguments
- If the name of a called function specified in the body of function is not qualified with an authorization identifier, when the called function and the function being defined share the same routine identifier and number of arguments
- When aa....aa is procedure:
- If a procedure name in a call statement in the body of function is qualified with an authorization identifier, when the called procedure and the procedure being defined share the same authorization identifier and routine identifier
- If a procedure name in a call statement in the body of function is not qualified with an authorization identifier, when the called procedure and the procedure being defined share the same routine identifier
- When bb....bb is PUBLIC:
- You cannot specify a call to a routine inside a public routine definition when the routine being called and the routine being defined match in the following respects:
- When aa....aa is function:
- If the name of a called function specified in the body of function is qualified with PUBLIC, when the called function and the public function being defined share the same routine identifier and number of arguments
- If the name of a called function specified in the body of function is not qualified with an authorization identifier, when the called function and the public function being defined share the same routine identifier and number of arguments
- When aa....aa is procedure:
- If a procedure name in a call statement in the body of function is qualified with PUBLIC, when the called procedure and the public routine being defined share the same authorization identifier and routine identifier
- If a procedure name in a call statement in the body of function is not qualified with an authorization identifier, when the called procedure and the public routine being defined share the same routine identifier
- aa....aa: {function|procedure}
- bb....bb: {authorization identifier|PUBLIC}
- cc....cc: Routine identifier
- dd....dd:
{ function |procedure }
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11260-E A
Attribute "aa....aa" not defined in abstract data bb....bb "cc....cc"
- "aa....aa" is not defined as an attribute of "cc....cc", which is a column of the abstract data type, an SQL variable, an SQL parameter, or an attribute.
- aa....aa: Name of the undefined attribute
- bb....bb:
{ column, SQL variable or SQL parameter |attribute }
- cc....cc: Name of the column, SQL variable, SQL parameter, or attribute for which "aa....aa" is specified as an attribute
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11262-E A
aa....aa "bb....bb" not defined as abstract data
- The column bb....bb, the SQL variable, the SQL parameter, or the attribute that is a qualifier in a component specification is not defined as an abstract data type.
- aa....aa:
{ column, SQL variable or SQL parameter |attribute }
- bb....bb: Name of the column, SQL variable, SQL parameter, or attribute
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11263-E A
Unable to access attribute "aa....aa" because of encapsulation level bb....bb
- When bb....bb is PRIVATE:
- Because the encapsulation level for the attribute "aa....aa" is PRIVATE, this attribute can be accessed only in the CREATE TYPE statement that defines it.
- When bb....bb is PROTECTED:
- Because the encapsulation level for the attribute "aa....aa" is PROTECTED, this attribute can be accessed only in the CREATE TYPE statement that defines it, or in a subtype CREATE TYPE statement.
- aa....aa: Name of the attribute
- bb....bb: Encapsulation level
{ PRIVATE |PROTECTED }
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11266-E A
Unable to specify component specification in argument of set function
- Component specifications cannot be specified in an argument in a set function.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11267-E A
Unable to specify component specification in "SELECT" clause in INSERT statement
- Component specifications cannot be specified in the SELECT clause of an INSERT statement (except for a SELECT clause in a subquery).
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11273-E A
Invalid use of WRITE specification
- One of the following errors was found in the usage of the WRITE specification:
- Duplicate locking cannot be specified for a query in which a WRITE specification is specified.
- A WRITE specification cannot be used as a sort key.
- When a BLOB column is specified for the output BLOB value of a WRITE specification, the same column cannot be specified by itself in the selection expression or in the output BLOB value of another WRITE specification.
- When the output BLOB value of a WRITE specification is not a column, FOR READ ONLY cannot be specified for the query.
- A WRITE specification cannot be specified in a routine.
- A set operation cannot be specified for a query in which a WRITE specification is specified.
- A WRITE specification cannot be specified in the selection expression of a query specification of an INSERT statement.
- A WRITE specification cannot be specified in the selection expression of a subquery (including the derived table of a FROM clause).
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11274-E A
Invalid use of GET_JAVA_STORED_ROUTINE_SOURCE specification
- One of the following errors was detected in the use of a GET_JAVA_STORED_ROUTINE_SOURCE specification:
- Duplicate locking cannot be specified in a query in which a GET_JAVA_STORED_ROUTINE_SOURCE specification is specified.
- A GET_JAVA_STORED_ROUTINE_SOURCE specification cannot be specified as a sort key.
- When a GET_JAVA_STORED_ROUTINE_SOURCE specification is specified, FOR READ ONLY cannot be specified in the query.
- A set operation cannot be specified for a query in which a GET_JAVA_STORED_ROUTINE_SOURCE specification is specified.
- A GET_JAVA_STORED_ROUTINE_SOURCE specification cannot be specified for the selection expression of a query specification of an INSERT statement.
- A GET_JAVA_STORED_ROUTINE_SOURCE specification cannot be specified for a selection expression inside a subquery (including the derived table of a FROM clause).
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11276-E A
Unable to specify outer reference column of abstract data type
- An abstract data type column that makes an external reference cannot be specified.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11277-E A
Unable to specify outer reference column of BLOB data type in argument of function invocation
- BLOB columns that make an external reference cannot be specified in an argument for a user-defined function.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11280-E A
PLUGIN not installed for abstract data type "aa....aa"."bb....bb"
- A plug-in for the abstract data type "aa....aa"."bb....bb" is not installed.
- aa....aa: Authorization identifier
- bb....bb: Name of the abstract data type
- S: Ignores this SQL statement.
- P: Ask the HiRDB administrator to install the required plug-in.
- Action
- Install the required plug-in.
KFPA11281-E A
PLUGIN "aa....aa" not installed
- The plug-in "aa....aa" is not installed.
- aa....aa: Name of the plug-in
- S: Ignores this SQL statement.
- P: Ask the HiRDB administrator to install the required plug-in.
- Action
- Install the required plug-in.
KFPA11282-E A
Receiving function for inter-function value passing can be specified only in "SELECT" or "SET" clause
- The receiving function for inter-function value passing can be specified only in an update value in the SELECT or SET clause (it cannot be specified in a routine control statement).
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11283-E A
Sending function for inter-function value passing can be specified only in "WHERE" clause or "ON" condition in query specification without view or "WITH" clause
- The sending function for inter-function value passing can be specified only in a WHERE clause or an ON search condition (it cannot be specified in the routine control statement). However, if you specify the sending function for inter-function value passing in the ON search conditions of a joined table specifying an outer join, you cannot specify a column of the outer table in the first argument.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11284-E A
Sending function for inter-function value passing cannot be specified in "OR" condition
- The sending function for inter-function value passing can be specified in the OR condition only when the index can be used (when specified following a NOT condition, an OR condition is converted into an AND condition and an AND condition is converted into an OR condition).
The index can be used when all of the following conditions are met: - A plug-in index is defined in the first argument of the sending function for inter-function value passing.
- The first argument of the sending function for inter-function value passing is a column specification in a base table that does not make an external reference.
- Arguments including the following expressions are not specified in arguments other than the first argument of the sending function for inter-function value passing:
- Column specifications other than those that make an external reference
- Component specification in a column
- A predicate including IS FALSE, IS UNKNOWN, or NOT was not specified in the sending function for inter-function value passing.
- No sending function for inter-function value passing was specified in CAST.
- When the FROM clause specifies more than one table, the table column that differs from the first argument of the sending function for inter-function value passing was not specified in the search conditions of the OR operand.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11285-E A
Function for inter-function value passing cannot be specified in "CASE" expression or scalar function "VALUE"
- The receiving or sending function for inter-function value passing cannot be specified in a CASE expression or the scalar function VALUE.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11286-E A
Receiving function for inter-function value passing without sending function
- The receiving function for inter-function value passing cannot be specified unless there is a corresponding sending function for inter-function value passing in the same query specification. For details about the corresponding send function for passing inter-function values, see the plug-in manual. If a table is being searched via a list, the cause is that the receive function for passing inter-function values does not correspond to the inter-function values collected from the list.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute. For a table search via a list, the plug-in version is old, which may cause the receive function for passing inter-function values not to correspond to the inter-function values collected from the list. In this case, contact the HiRDB administrator.
- Action
- For a table search via a list, obtain the plug-in version, and refer to the manual that corresponds to that version. Check that the receive function for passing inter-function values corresponds to the inter-function values collected from the list, and upgrade the plug-in version if necessary.
KFPA11287-E A
Invalid specification of first argument in receiving function for inter-function value passing
- The first argument in the receiving function for inter-function value passing is invalid. The first argument must satisfy the following conditions:
- Its data type must be an abstract data type.
- It must be specified in a column specification, an SQL parameter, or an SQL variable.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11288-E A
Unable to specify receiving function for inter-function value passing except in set function in query with grouping or set function
- In a query specifying a GROUP BY clause, a HAVING clause, or a set function, a receiving function for inter-function value passing cannot be specified in locations other than an argument for a set function.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11289-E A
More than one sending function for inter-function value passing with same first arguments
- Two or more receiving functions for inter-function value passing with identical first arguments cannot be specified.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11291-E A
No available index for ARRAY predicate
- An index for the evaluation of a structured repetition predicate is missing.
For queries that include an RDAREA name specification, the structured repetition predicate cannot be evaluated because the number of partitions of the index for the structured repetition predicate is different from the number of partitions of the table. - S: Ignores this SQL statement.
- P: Take one of the following actions:
- Correct the SQL statement, or revise the index definition, and then retry the operation.
- When an RDAREA name is specified, make sure that the number of partitions of the defined index is equal to the number of partitions of the table, and then re-execute the SQL statement.
KFPA11292-E A
Unable to specify ARRAY predicate in operand of boolean operator "NOT"
- A structured repetition predicate cannot be negated by using the NOT operator.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11294-E A
Unable to specify ARRAY predicate with columns of aa....aa of outer join in bb....bb, query-no=ccc
- A structured repetition predicate cannot be specified for the following columns:
- Column in an outer table in an ON search condition of a query specification that includes an outer join
- Column in an inner table in a WHERE clause of a query specification that includes an outer join
- aa....aa: Table type:
- inner table: Inner table
- outer table: Outer table
- bb....bb: Condition type:
- ON condition: In an ON search condition
- WHERE clause: In a WHERE clause
- ccc: Query number in which the predicate is specified
- S: Ignores the SQL statement and continues processing. Rollback occurs in the case of a definition SQL statement.
- P: Correct the SQL statement as explained below and re-execute:
- When specifying a structured repetition predicate for a column of an outer table of a joined table in a query specification that includes an outer join, specify the predicate in a WHERE clause.
- When specifying a structured repetition predicate for a column of an inner table of a joined table in a query specification that includes an outer join, specify the predicate in an ON search condition.
KFPA11295-E A
Unable to aa....aa rebalancing table bb....bb."cc....cc" with unique constraint
- When table bb....bb."cc....cc" is being rebalanced and an index with UNIQUE specified is being defined for the table, aa....aa cannot be executed for that table.
- aa....aa:
{ INSERT INTO|UPDATE }
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Ignores this SQL statement.
- P: Re-execute the SQL statement after the rebalancing has finished.
KFPA11296-E A
Unable to aa....aa shared table without LOCK TABLE IN EXCLUSIVE MODE
- Without executing the LOCK statement with the IN EXCLUSIVE MODE specification, the following SQL statements cannot be executed for a shared table:
- INSERT statement
- UPDATE statement accompanying index updates
- UPDATE statement specifying DEFAULT in the update value for a TIMESTAMP column with the USING BES specification defined in the DEFAULT clause
- DELETE statement
- aa....aa: {INSERT | UPDATE | DELETE}
- S: Ignores this SQL statement.
- P: Execute the LOCK statement with the IN EXCLUSIVE MODE specification on the table corresponding to the INSERT, UPDATE, or DELETE statement, and re-execute the SQL statement.
KFPA11299-E A
Duplicate LIST name "aa....aa" in ASSIGN LIST statement
- List name "aa....aa" is already specified in the ASSIGN LIST statement. The same name cannot be specified more than once in an ASSIGN LIST statement.
- aa....aa: Duplicated list name
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11301-E A
Inconvertible data type of input variable aa....aa
- The data type of input variable aaaaa cannot be converted. Or, the input variable has an inconvertible structure (a simple structure or a repetition structure).
- aa....aa: Sequence number of input variable
- S: Ignores this SQL statement.
- P: Change the input variable into a convertible data type with the correct structure, and then re-execute.
KFPA11302-E A
Input data too large for column or assignment target aa....aa
- One of the following errors was detected:
- The input data is outside the range of values permitted for the data type of the column.
- The number of elements in the input data is greater than the maximum number of elements for a repetition column.
- In a call-out of a user-defined function or system-defined scalar function, the input arguments exceed the range of values permitted for the data type of the parameter.
- The argument of the input variable for the scalar function VALUE exceeds the range of values permitted for the data type.
- aa....aa: One of the following characters:
- Sequential number of the in variable variable
When independently specifying an input variable or when independently specifying an input variable in an argument for the scalar function VALUE
- One-byte space
In all other cases
- S: Ignores this SQL statement.
- P: If the input data is invalid, correct it and re-execute.
KFPA11303-E A
Inconvertible data type of output variable aaaaa
- The data type of output variable aaaaa cannot be converted. Or, the output variable has an inconvertible structure (a simple structure or a repetition structure).
- aaaaa: Sequence number of the output variable
- S: Ignores this SQL statement.
- P: Change the output variable into a convertible data type with the correct structure, and then re-execute.
KFPA11304-E A
Output data too large for variable aa....aa
- The data length to be output exceeds the value permitted for the variable attribute.
- aa....aa: Sequential number of the invalid output variable
- S: Ignores this SQL statement.
- P: Change the attribute of the variable and re-execute.
KFPA11305-E A
Indicator must be specified for null value in variable aa....aa
- Because no indicator variable was specified, null-value output data cannot be returned.
- aa....aa: Sequential number of the invalid output variable
- S: Terminates processing.
- P: Specify an indicator variable and re-execute the UAP.
KFPA11306-E A
Invalid data aa....aa variable bbbbb
- An error was detected in the following data (data to be set to national character string data type might have a length that is an odd number of bytes, or there might be data that cannot be converted into the target character set).
- When aa....aa is in input:
Data in the bbbbbth input variable
- When aa....aa is to output:
Data to be set in the bbbbbth output variable
Data to be set in the bbbbbth SQL parameter whose parameter mode is OUT or INOUT in an external routine
Data to be set in the bbbbbth SQL parameter (if bbbbb is *****) in an external routine
- aa....aa: Variable type:
{ in input |to output }
- bbbbb: One of the following:
- Serial number of an input variable or output variable
- Serial number of an SQL parameter whose parameter mode is OUT or INOUT.
***** is displayed for the return value of a function.
- S: Ignores this SQL statement.
- P: Correct the data and re-execute the SQL.
KFPA11307-E A
No RDAREA for specified divided Key VALUEs
- The RDAREA for storing the specified values was not specified in the table definition.
- S: Ignores this SQL statement.
- P: Modify the specification so that the specified values satisfy the storage condition. Or, re-evaluate the specified storage condition.
KFPA11308-E A
Unexpected request, SQLNAME or TYPE option necessary in PREPARE
- The DESCRIBE statement or the DESCRIBE TYPE statement cannot be executed for the following reasons:
- In the PREPARE statement, the receipt (Column Name Descriptor Area (SQLCNDA)) of either a column name or an attribute name is specified in either the DESCRIBE or DESCRIBE TYPE statement without the specification of the WITH SQLNAME OPTION.
- In the PREPARE statement, the receipt (Type Name Descriptor Area (SQLTNDA)) of a data type name of a user-defined type is specified in the DESCRIBE statement without the specification of the WITH TYPE OPTION.
- In the PREPARE statement, the DESCRIBE TYPE statement is specified without the specification of the WITH ALL TYPE OPTION.
- S: Ignores this SQL statement.
- P:
- In the PREPARE statement, specify the WITH SQLNAME OPTION and re-execute. Or, re-execute without specifying the Column Name Descriptor Area (SQLCNDA) in either the DESCRIBE or DESCRIBE TYPE statement.
- In the PREPARE statement, specify the WITH TYPE OPTION and re-execute. Or, re-execute without specifying the Type Name Descriptor Area (SQLTNDA) in either the DESCRIBE or DESCRIBE TYPE statement.
- In the PREPARE statement, specify the WITH ALL TYPE OPTION and re-execute. Or, re-execute without specifying the Type Name Descriptor Area in the DESCRIBE TYPE statement.
KFPA11310-E A
Invalid number of variables
- The value of either SQLN or SQLD specified in the SQL descriptor area is invalid.
- S: Ignores this SQL statement.
- P: Correct the value specified for either SQLN or SQLD to satisfy the conditions 0
SQLD
30,000 and SQLD
SQLN
30,000 and re-execute.
KFPA11311-E A
Invalid data type or length of variable aa....aa bb....bb
- Embedded variable aa....aa or parameter variable declaration is invalid. Or, the maximum number of elements, the data type, or the length of the aa....aath variable specified in the SQL descriptor area is invalid.
- aa....aa: Sequence number of variable#
- #
- When specifying an embedded variable or ? parameter as an argument of a CALL statement, the sequence number output in aa....aa might be different from the order of the variables specified in the CALL statement. This is to keep the sequence numbers separate for variables whose input/output mode is IN and variables whose input/output mode is OUT.
- bb....bb: Additional information
- Any of the following information:
- (input) cc....cc (argument):
- The cc....ccth input argument of the CALL statement or CALL COMMAND statement is incorrect.
- (output) cc....cc (argument):
- The cc....ccth output argument of the CALL statement or CALL COMMAND statement is incorrect.
- (into):
- aa....aa is the sequence number of the variable specified in into.
- (using):
- aa....aa is the sequence number of the variable specified in using.
- S: Ignores this SQL statement.
- P: Correct the embedded variable or parameter variable declaration and re-execute. Or, correct the maximum number of elements, the data type, or the length of the aa....aa variable specified in the SQL descriptor area and re-execute. In addition, if UTF-8 or CHINESE-GB18030 is used as the character encoding, specify a data type other than national character string data for the embedded variable, and then retry the operation.
KFPA11312-E A
Sum of aa....aa variable length exceeds 2GB
- The total length of variable aa....aa exceeds 2 GB.
- aa....aa: Variable resulting in the error:
- INPUT: Input variable
- OUTPUT: Output variable
- S: Ignores this SQL statement.
- P: Correct what is specified in the SQL descriptor area so that the total length of the input and output variables is less than 2 GB, and then re-execute the SQL statement. For details about how to calculate the total length of the input and output variables, see Outbound message length (when executing other SQL code) and Inbound message length (when executing other SQL code) under Estimating the memory size of a client library in the HiRDB Version 9 UAP Development Guide.
KFPA11313-E A
Number of variables not equal to number of parameters
- One of the following errors occurred:
- The number of embedded variables specified in the DECLARE CURSOR statement is not the same as the number of embedded variables specified in the OPEN statement.
- The number of ? parameters in the SQL code that is pre-processed in a PREPARE statement or EXECUTE IMMEDIATE statement is not the same as the number of embedded variables that give values to those ? parameters, or the number specified for SQLD in the SQL descriptor area.
- A ? parameter, rather than an embedded variable, was specified in that SQL code that is not pre-processed in a PREPARE statement or EXECUTE IMMEDIATE statement, or a mixture of embedded variables and ? parameters was specified.
- S: Ignores this SQL statement.
- P: Depending on the error, take one of the following actions:
- Correct the SQL statement so that the number of embedded variables specified in the DECLARE CURSOR statement is the same as the number of embedded variables in the OPEN statement, and then retry the operation.
- Correct the SQL statement or program so that the number of ? parameters in the SQL code that is pre-processed in a PREPARE statement or EXECUTE IMMEDIATE statement is the same as the number of embedded variables that give values to those ? parameters or number specified for SQLD in the SQL descriptor area, and then retry the operation.
- Change the ? parameters to embedded variables in the SQL code that is not pre-processed in a PREPARE statement or EXECUTE IMMEDIATE statement, and then retry the operation.
KFPA11314-E A
Invalid data type name specified in DESCRIBE TYPE
- A data type name (owner name and data type identifier) not associated with the SQL statement preprocessed by the PREPARE statement was specified in the DESCRIBE TYPE statement. Only data type names of the user-defined type can be specified in selection item in the SQL statement preprocessed by the PREPARE statement.
- S: Ignores this SQL statement.
- P: Correct the specified data type name specification and re-execute.
KFPA11315-E A
Unable to use multi value columns on this client library or application
- An attempt was made to reference or update a repetition column by using a version of a client library that does not support repetition columns.
- S: Continues processing.
- P: When not using a repetition column, revise the UAP so that the value 1 is explicitly assigned to the SQLXDIM of the SQL descriptor area. When using a repetition column, use a version of a client library that supports repetition columns, and then re-execute the preprocessing and execution steps.
KFPA11316-E R+A
Invalid number of elements of array variable
- The size specified for an array is 0, a negative value, or is greater than the maximum value.
- S: Ignores this SQL statement.
- P: Correct the program so that the dynamic size value specified in the FETCH or INSERT statement that uses the array is a value less than the maximum value, and re-execute.
KFPA11317-E E+L+P
An error occurred during XDS start or termination processing in XDS. information = aaa
- An error occurred during XDS start or termination processing.
- aaa: Maintenance information
- S: Terminates abnormally.
- O: If an error message was output immediately prior to this error message, then refer to that message to eliminate the cause of the error. If no error message was output prior to this message, save the contents of this message and any core file that was output. Then contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPA11318-E E+L+P
XDS aborted because an error occurred in XDS. information = aa....aa
- An error was detected in XDS, therefore XDS was stopped.
- aa....aa: Maintenance information
- S: Terminates abnormally.
- O: If an error message was output immediately prior to this error message, then refer to that message to eliminate the cause of the error. If no error message was output prior to this message, save the contents of this message and any core file that was output. Then contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPA11321-E A
Sequence generator limit exceeded, sequence generator=aa....aa."bb....bb"
- The sequence generator aa....aa."bb....bb", which was specified as NO CYCLE, exceeded the maximum value or fell below the minimum value.
- aa....aa: Authorization identifier
- bb....bb: Sequence generator identifier
- S: Ignores this SQL statement.
- P: After deleting the sequence generator once, define the sequence generator again.
KFPA11326-E A
Length, precision, or number of elements of input variable "aa....aa" conflicts with SQLDA
- The data in input variable "aa....aa" contradicts the specification in an embedded variable, parameter variable declaration, or SQL Data Area:
- If the input variable is variable-length data, its length either exceeds the maximum value or is 0 or less.
- If the input variable is decimal data, either the data format is invalid or the precision is invalid.
- If the input variable is a repetition column, either the number of elements is greater than the maximum allowable number or is less than or equal to 0.
- aa....aa: Sequence number of input variable
- S: Ignores this SQL statement.
- P: Correct the input data, variable declaration, or specification in the SQL Data Area and re-execute.
KFPA11329-E A
Invalid SQL for query in "aa....aa"
- One of the following errors has occurred:
- An SQL statement using the cursor is invalid for the query specified in the cursor declaration.
- For a query specified by a cursor allocation, an SQL statement using the cursor is incorrect.
- A query specifying a table can be executed only by the UPDATE or DELETE statement for the table.
- aa....aa: {DECLARE CURSOR|ALLOCATE CURSOR}
- S: Ignores this SQL statement.
- P: Correct the SQL statement, recompile the module, then execute it.
KFPA11330-E A
CURSOR not opened or not positioned on any ROW
- One of the following errors was detected:
- The cursor has not been opened.
- Row retrieval was not executed.
The row cannot be updated or deleted using the cursor.
- S: Ignores this SQL statement.
- P: Define the cursor, open it, modify the UAP so that the row can be updated or deleted, then re-execute.
KFPA11331-E A
Specified table different from that in cursor specification
- The table specified in the cursor specification is not the same as the table specified in this SQL statement. Therefore, the UPDATE or DELETE statement cannot be executed using the cursor.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11332-E A
Fetch of all ROWs completed, or an error occurred during fetch
- Because row fetch was completed or an error occurred during row fetch processing, the cursor specified in the UPDATE or DELETE statement cannot be executed.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11340-E A
Invalid address for variable aaaaa in SQLDATA or SQLIND
- The value specified in SQLDATA or SQLIND in the SQL descriptor area is invalid or has not been set. Another possibility is that an address for an embedded variable or indicator variable in the SQL statement is incorrect.
- aaaaa: Sequence number of variable
- S: Ignores this SQL statement.
- P: Set the variable correctly and re-execute.
KFPA11342-E A
Insufficient data area in client, size=aa....aa
- Retrieval result cannot be transferred to the client, because the output buffer is too small.
- aa....aa: Length (in bytes) of the data area requested by the client
- The size of the data area includes the length of the SQL descriptor area.
- S: Ignores this SQL statement.
- P:
- Check the type of embedded variable that receives the retrieval result to make sure that it correctly corresponds to the data type of the column.
- If the SQL descriptor area is used directly, check if the value of SQLLEN is set correctly based on the data type of the corresponding column.
- If an indicator variable is used, check if the length of the receive area is correct.
- If a Column Name Descriptor Area (SQLCNDA) or Type Name Descriptor Area (SQLTNDA) is used, check that the length of the receive area is correct.
KFPA11343-E A
Invalid condition number in "GET DIAGNOSTICS" statement
- The following values cannot be specified as a condition number:
- Value smaller than zero
- Value greater than the number of errors in the diagnostic area
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11351-E A
Unable to specify column or value expression for update value of ADD clause in UPDATE statement with cursor
- The following items cannot be specified as an update value in the ADD clause of the UPDATE statement using a cursor:
- Columns
- Scalar operations
- Component specifications
- Function invocations
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11355-E A
Unable to FETCH from LIST using arrays
- A FETCH that uses an array cannot be used for a search via a list.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11356-E A
File "aa....aa" bb....bb error occurred in processing for WRITE specification, code=cc....cc
- An error occurred during a file operation for the processing of a WRITE specification.
- aa....aa: Name of the file in which the error occurred:
- If the file name consists of no more than 126 bytes, the entire file name is displayed; if it exceeds 126 bytes, the excess is truncated, and 2 bytes of periods (..) are displayed following the first 126 bytes.
- bb....bb: Operation in which the error occurred:
- OPEN: Error occurred in open system call in BLOB data file
- CLOSE: Error occurred in close system call in BLOB data file
- WRITE: Error occurred in write system call in BLOB data file
- cc....cc: Detail codes for system-related errors
- -20000: Output file exists.
- Other than the above: see 4.2 Detail codes for system-related errors.
- S: Ignores this SQL statement.
- P:
- When cc....cc is -20000:
- Overwriting denied (a value of 2 or 6) was specified in the file output options. Check for an error in the file output options, eliminate the cause of the error, and then re-execute the SQL statement.
- Other than above:
- Eliminate the cause of the error and re-execute the SQL statement.
KFPA11358-E A
RDAREA aa....aa freezed
- RDAREA aa....aa is in frozen update status.
- aa....aa: Name of the RDAREA
- S: Ignores this SQL statement.
- Action
- To handle a frozen area:
- Check to be sure your work flow did not incorrectly issue a request to update an RDAREA in frozen update status.
- Use the pddbfrz -d command to release the frozen update status of the RDAREA, and re-execute. In such cases, perform maintenance on the RDAREA, and then back up the entire RDAREA.
KFPA11359-E A
Unable to delete row in delete prohibition period
- The process cannot delete a row in the falsification prevented table during the deletion prevented period.
- S:
- Deleting using the cursor:
The process continues without deleting the row indicated by the cursor.
- In all other cases:
The process ignores this SQL statement and rolls back.
- P: Correct the deletion conditions and re-execute.
KFPA11360-E A
Invalid format specification in scalar function "aa....aa", pos=bbb, query-no=ccc, format="dd....dd"
- The format specified by the scalar function "aa....aa" is invalid.
- aa....aa: Name of the scalar function that specified the invalid format:
{VARCHAR_FORMAT|DATE|TIME|TIMESTAMP_FORMAT}
- bbb: Location where the error was detected (byte bbb)
- ccc: Query number
- dd....dd: Invalid format:
- "dd....dd" displays a hash mark (#) at byte 100 when the format exceeds 100 bytes.
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Check the available format elements, correct the format, and re-execute.
KFPA11361-E A
Character representation unmatch specified format in scalar function "aa....aa", pos=bbb, query-no=ccc, format="dd....dd"
- The character string representation in scalar function "aa....aa" does not match the specified format.
- aa....aa: Scalar function specifying a value expression that does not match the format
{DATE|TIME|TIMESTAMP_FORMAT}
- bbb: Location of character string representation that does not match the specified format (byte bbb of the format)
- ccc: Query number
- dd....dd:
- Specified format:
- "dd....dd" displays a hash mark (#) at byte 100 when the format exceeds 100 bytes. Also, when the query specifies a value expression not using a literal and specifies the format using a literal, the following character strings indicate format elements other than the character strings and the delimiting characters:
- Year: YYYY
- Month: MM
- Abbreviations for month: MON, Mon, mon#
- Name of a month: MONTH, Month, month#
- Day: DD
- Hour: HH
- Minute: MI
- Second: SS
- Fractional second: NN....N (the specified number of digits)
- #: Follows the upper case or lower case convention described in the format (in the first or second character).
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Either make the specified format and the character string match or correct the format and re-execute.
KFPA11362-E A
No format element aa....aa in format specification in scalar function "bb....bb", query-no=ccc
- The format specified by scalar function "bb....bb" does not contain the required format element aa....aa.
- aa....aa: The missing format element:
{DD|HH|MI|MM, MON or MONTH|SS|YYYY}
- bb....bb: Scalar function:
{DATE|TIME|TIMESTAMP_FORMAT}
- ccc: Query number
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Check the correlation between the scalar function and the required format elements, add the required format elements, and re-execute.
KFPA11364-E A
Invalid LOCATOR specified, pos=aaaaa
- An invalid locator was specified.
- aaaaa: Sequence number of the embedded variable or ? parameter
- S: Performs one of the following processing functions:
- For the FREE LOCATOR statement
Invalidates all valid locators.
- For all else
Ignores this SQL statement.
- P: Correct the SQL statement to specify a valid locator, and re-execute.
KFPA11366-E A
Indicator must be specified for null value assigned to LOCATOR in variable aa....aa
- The data value assigned to the locator is a null value, and there is no indicator variable.
- aa....aa: Sequence number of the embedded variable or ? parameter
- S: Ignores this SQL statement.
- P: Specify an indicator variable in the locator, and re-execute the UAP.
KFPA11367-E A
Unable to update non null valued column with "UPDATE ONLY FROM NULL"
- Because the value stored in the column with UPDATE ONLY FROM NULL specified is not a null value, this column cannot be updated.
- S: Ignores this SQL statement.
- P: Correct the UAP so that it does not update a column that contains a non-null value that is specified with UPDATE ONLY FROM NULL, and re-execute.
KFPA11381-E A
Overflow in converting floating point numeric, type=aa....aa
- Overflow occurred during conversion of data to floating-point data.
- aa....aa: Error cause:
{INPUT|OUTPUT}
- S: Ignores this SQL statement.
- P: Change the data type so that overflow does not occur.
KFPA11382-E A
Invalid use of "CURRENT OF" clause
- CURRENT OF cursor-name or extended cursor name was specified during batch retrieval.
- S: Ignores this SQL statement.
- P: Correct the SQL statement so that CURRENT OF cursor-name or an extended cursor name is not specified. Or, correct the environment definition so that batch retrieval is not executed.
KFPA11385-E E+L+P
A timeout was detected during command sending or receiving processing in XDS. wait time = aa....aa
- After data was sent to request command processing, a timeout was detected before the message was received.
- aa....aa: Timeout time (unit: minutes)
- S: Terminates processing.
- O: If you can specify the cutoff time for command processing, change the cutoff time and re-execute. If this message is displayed repeatedly, contact the HiRDB administrator.
- Action
- If this message is output repeatedly, contact the customer support center.
KFPA11401-E A
Inconvertible data type in "aa....aa" predicate, query-no=bbb
- The data types specified in the operands on both sides of predicate aa....aa are not valid for comparison or conversion. Even if the operands on both sides of predicate aa....aa are character string data types, they cannot be compared or converted if they are coded in different character sets. However, the following value expressions can be converted to the character set of the comparison target, and then, compared:
- Character string literals
- Embedded variables
- ? parameters
- aa....aa: Predicate specifying the invalid data types:
- {COMPARISON|IN|LIKE|BETWEEN|XLIKE|SIMILAR}
- bbb: Number of the query specifying the predicate
- S: Ignores this SQL statement.
- P: Correct the predicate and re-execute.
KFPA11402-E A
Argument of "AVG" or "SUM" must be numeric, query-no=aaa
- The argument of a set function (AVG or SUM) is not numeric data.
- aaa: Number of the query specifying a set function
- S: Ignores this SQL statement.
- P: Correct the set function and re-execute.
KFPA11403-E A
Unable to specify "aa....aa"."bb....bb" in SET function "cc....cc", query-no=ddd
- If arguments of a set function specify values other than columns, they must not include rows that make an external reference.
- aa....aa: Table identifier or correlation name
- bb....bb: Name of column that makes an external reference
- cc....cc: Name of the set function
- ddd: Query number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11404-E A
Input data too long for column or assignment target aa....aa
- One of the following errors was detected:
- A column of the input data is longer than the defined column.
- The assignment value data in the SET statement is longer than the assignment destination.
- In a call-out of a user-defined function or system-defined scalar function, the argument is too long for the parameter.
- An argument is longer than the data in the result of the scalar function VALUE.
- The default value specified in the DEFAULT clause of the SQL variable declaration is too long for the SQL variable.
- The input data is too long for the AS data type specification.
- aa....aa: One of the following characters:
- Sequential number of the in variable variable
When independently specifying an input variable or when independently specifying an input variable in an argument for the scalar function VALUE
- One-byte space
In all other cases
- S: Ignores this SQL statement.
- P: Correct the input data and re-execute.
KFPA11405-E A
Numeric literal out of range
- Specified numeric literal is outside the following permitted value range:
- Integer literal:
- -2,147,483,648 to 2,147,483,647
- Decimal literal#:
1038 to
(1039 - 1)
- Floating point numeric literal:
4.9
10-324 to
1.7
10308
- Integer literal specified for a labeled duration:
- YEAR(S): -9,998 to +9,998
- MONTH(S): -119,987 to +119,987
- DAY(S): -3,652,058 to +3,652,058
- HOUR(S): -23 to +23
- MINUTE(S): -1,439 to +1,439
- SECOND(S): -86,399 to +86,399
- Integer literal specified as the row count in the LIMIT clause: -1 to +2,147,483,647
- Integer literal specified as the offset in the LIMIT clause: 0 to +2,147,483,647
- #: The maximum number of specifiable digits is 38 (including the number of leading zeros).
- S: Ignores this SQL statement.
- P: Correct the specification of the numeric literal and re-execute.
KFPA11406-E A
Arithmetic operation cannot be specified for string, binary, timestamp, abstract, or Boolean data, query-no=aaa
- Arithmetic operations cannot be specified for national character string data, large object data (BLOB), binary data (BINARY), timestamp data, abstract data, or Boolean data (BOOLEAN).
In addition, if character string data or mixed character string data is specified, the following restrictions apply: - Arithmetic operations cannot be specified for the following value expressions if they result in character string data:
- USER value function
- SQLERRM_OF_LAST_CONDITION
- When specifying arithmetic operations involving character string data or mixed character string data in the following locations, only character string literals or mixed character string literals can be specified:
- Selection expression
- Argument of a set function
- Argument of a user-defined function (including system-defined scalar functions)
- GROUP BY clause
- Value expression in a VALUES clause for a partitioning column
- Value expression in the VALUES clause of an INSERT statement, or in the SET clause of the UPDATE statement, referenced by a new values correlation name
- Value expression in the SET clause of the UPDATE statement referenced by an old values correlation name
- aaa: Number of the query specifying character string data, national character string data, mixed character string data, large object data, binary data, timestamp data, abstract data, or Boolean data.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11407-E A
aa....aa predicate can be specified for string data only, query-no=bbb
- The LIKE, XLIKE, or SIMILAR predicate cannot be specified in any of the following data types:
- Numeric data
- Date data
- Date interval data
- Time data
- Time interval data
- Timestamp data
- Large object data
- Binary data (however, binary data with a maximum length of 32,000 bytes can be specified in a LIKE or SIMILAR predicate)
- aa....aa: error-containing predicate {LIKE |XLIKE |SIMILAR}
- bbb: The query number in which an invalid LIKE, XLIKE, or SIMILAR predicate is specified
- S: Ignores this SQL statement.
- P: Revise the LIKE, XLIKE, or SIMILAR predicate, and re-execute.
KFPA11408-E A
Inconvertible data type for update or insert value
- The data type of the specified update or insertion value cannot be converted.
When an insertion or update is performed on a character string data type, the insert or update value must use the same character set as the target of the insertion or update. However, if an embedded variable, ? parameter, or character string literal is specified as the update value, it is automatically converted to the character set of the update target.
When an insertion or update is performed on an abstract data type, the insert or update value must be the same abstract data type as the target of the insertion or update, or a subtype of the target of the insertion or update. - S: Ignores this SQL statement.
- P: Correct the update or insert value and re-execute.
KFPA11409-E A
Unable to specify character string data of more than 4,036 bytes in aa....aa in XDS
- Character type data of 4,037 bytes or more was specified in an invalid location of the memory database allocation table in SQL.
- aa....aa:
- "COMPARISON" predicate
- "SELECT" clause
- "ORDER BY" clause
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11410-E A
Invalid numeric literal aa....aa
- Specified numeric literal contains a syntax error.
- aa....aa: Erroneous numeric literal
- S: Ignores this SQL statement.
- P: Correct the numeric literal and re-execute.
KFPA11411-E A
Inconvertible data type in concatenation operation, query-no=aaa
- The data types specified in the operands on both sides of a concatenation operation are not valid for comparison or conversion. Even if the operands on both sides of the concatenation operation are character string data types, conversion is not possible when the character sets are different. However, the following value expression can be converted to the character set of the other operand:
- aaa: Number of the query specifying a nonconvertible data type in a data type of a concatenation operation
- S: Ignores this SQL statement.
- P: Correct the specification of the concatenation operation and re-execute.
KFPA11412-E A
Concatenation operation can be specified for string data except large object, query-no=aaa
- The following data types cannot be specified for concatenation operations:
- Date data
- Year-to-day data
- Time data
- Hour-to-second data
- Timestamp data
- Large object data (BLOB)
- Abstract data
- Logical data (BOOLEAN)
- However, the concatenation operation of large object data (BLOB) cannot be specified in the update value of the UPDATE statement.
- aaa: Number of the query specifying an invalid data type
- S: Ignores this SQL statement.
- P: Correct the specification of the concatenation operation and re-execute.
KFPA11413-E A
Invalid operation specified in date/time arithmetic operation, query-no=aaa
- A data type not permitted for a date or time operation was used in an arithmetic operation (such as date data plus date data or year-to-day data minus integer data). Or, a monomial operation is used for date data, time data, or labeled duration.
- aaa: Number of the query specifying an invalid date or time operation
- S: Ignores this SQL statement.
- P: Correct the specification of the arithmetic operation and re-execute.
KFPA11414-E A
Invalid use of labeled duration, query-no=aaa
- A labeled duration can be specified only for an addition or subtraction operation on date or time data.
- aaa: Query number specifying the invalid labeled duration
- S: Ignores this SQL statement.
- P: Correct the specification of the labeled duration and re-execute.
KFPA11415-E A
aa....aa can be specified for integer or smallint data only, query-no=bbb
- Only INTEGER or SMALLINT data types can be specified for aa....aa.
- aa....aa: The value expression or predicate that caused an error
- {Labeled duration|Row count in "LIMIT" clause}
- bbb: Query number
- S: Ignores this SQL statement.
- P: For a labeled duration, correct the specified value expression and re-execute. For LIMIT, correct the specified row count or offset, and re-execute.
KFPA11416-E A
Invalid character representation for data type aa....aa
- One of the following errors was detected in the character string representation that the data type aa....aa indicates:
- A character other than a numeral or hyphen (-) was used in the character string representation of the date data.
- Three or more hyphens (-) were used in the character string representation of the date data or the time data.
- The character string representation of the date data or the time data does not meet one of the following conditions:
0001
year
9999
01
month
12
01
day
last day of month
- A character other than a numeral or colon (:) was used in the character string representation of the timestamp data.
- Three or more colons (:) were used in the character string representation of the timestamp data.
- The character string representation of the time data or the timestamp data does not meet one of the following conditions:
00
hour
23
00
minute
59
00
second
59
- A character other than a numeral, hyphen (-), colon (:), space, or period (.) was used in the character string representation of the timestamp data.
- Two or more spaces or periods (.) were used in the character string representation of the timestamp data.
- The character string representation of the timestamp data does not meet the following condition:
000000
fractional second
999999
- A digit count other than 0, 2, 4, or 6 was specified for the fractional second precision in the character string representation of the timestamp data.
- A character other than a sign (+ or -) or a numeral was used in the character representation of the integer.
- A character other than a sign (+ or -), a decimal point (.) or a numeral was used in the decimal character representation.
- No decimal was used in the decimal character representation.
- A character other than a sign (+ or -), a numeral, E, or e was used in the floating-point character string representation.
- Neither E nor e was used in the floating-point character string representation.
- aa....aa: Data in which an invalid character string representation is specified
{TIME|DATE|TIMESTAMP|INTEGER|DECIMAL|FLOAT}
- S: Ignores this SQL statement.
- P: Correct the data with character string representation and re-execute.
KFPA11417-E A
Value specifications cannot be specified for both operands of compare operation or left-hand side operand in predicate "IN", query-no=aaa
- A ? parameter cannot be specified in both operands of a comparison predicate. Another possibility is that a value (literal, USER, CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, ? parameter) cannot be specified in both operands of a comparison predicate or in the left operand of the IN predicate.
- aaa: Number of the query specifying the comparison predicate or the IN predicate
- S: Ignores this SQL statement.
- P: Correct the specification of the comparison predicate or the IN predicate and re-execute.
KFPA11418-E A
Parameter cannot be specified in "SELECT" clause, query-no=aaa
- The ? parameter or embedded variable cannot be specified in the SELECT clause.
- aaa: Number of the query in which the ? parameter or embedded variable is specified
- S: Ignores this SQL statement.
- P: Correct the SELECT clause and re-execute.
KFPA11419-E A
Parameters cannot be specified for both operands of arithmetic operation or concatenation operation, query-no=aaa
- The ? parameter cannot be specified in both operands of an arithmetic or concatenation operation.
- aaa: Number of the query specifying the arithmetic operation or concatenation operation
- S: Ignores this SQL statement.
- P: Correct the specification of the arithmetic or concatenation operation and re-execute.
KFPA11420-E A
Result string of aa....aa too long or result type invalid, query-no=bbb
- One of the following errors was detected:
- The character string length of the result of value expression aa....aa exceeded one of the following maximums:
CHAR, VARCHAR, MCHAR, or MVARCHAR: 32,000 bytes
NCHAR or NVARCHAR: 16,000 characters
BINARY: 32,000 bytes
- Because the character string length of the result of value expression aa....aa exceeded one of the following maximums, this result cannot be specified in the value expression of a HEX scalar function.
CHAR, VARCHAR, MCHAR, and MVARCHAR: 16,000 bytes
NCHAR and NVARCHAR: 8,000 characters
BINARY: 16,000 bytes
- The result of the value expression aa....aa cannot be specified in a value expression in the scalar function HEX because it is one of the following data types:
BOOLEAN
BLOB
- Because the value expression result of aa....aa is one of the following data types, the result cannot be specified in the value expression of a predicate or set function. However, the BOOLEAN type can be specified in a Boolean predicate.
BOOLEAN
BLOB
BINARY 32,001 bytes or larger
- Because the data type of the value expression result of aa....aa is BLOB or is BINARY and is 32,001 bytes or larger, the result cannot be specified in a CALL statement, function call, or system definition scalar function argument.
- aa....aa: Name of operation
{ concatenation |scalar function "SUBSTR"
|scalar function "HEX" |scalar function "UPPER"
|scalar function "LOWER" |scalar function "VALUE"
|scalar function "IS_USER_CONTAINED_IN HDS_GROUP"
|scalar function "BIT_AND_TEST"
|scalar function "TRIM"
|simple CASE |searched CASE |case abbreviation
|cast specification | scalar subquery }
- bbb: Query number specifying aa....aa
- S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11421-E A
Invalid operation specified for arithmetic operation or concatenation operation, query-no=aaa
- A concatenation operation was specified in an arithmetic operation. Or, an arithmetic operation was specified in a concatenation operation.
- aaa: Number of the query specifying the invalid concatenation operation or arithmetic operation
- S: Ignores this SQL statement.
- P: Correct the concatenation or arithmetic operation and re-execute.
KFPA11422-E A
Variable or parameter cannot be specified for concatenation operation or date/time arithmetic operation, query-no=aaa
- An embedded variable or ? parameter cannot be specified for the following operations:
- Concatenation operation
- Date or time operation
- aaa: Number of the query specifying an embedded variable or the ? parameter
- S: Ignores this SQL statement.
- P: Correct the concatenation operation or time operation specifying the embedded variable or ? parameter and re-execute.
KFPA11424-E A
Invalid aa....aa in bb....bb predicate
- The value expression aa....aa specified in the LIKE, XLIKE, or SIMILAR predicate contains an error.
- aa....aa: Invalid SQL statement specification:
- {PATTERN |ESCAPE CHARACTER}
- PATTERN:
- If bb....bb is either LIKE or XLIKE, the character following the escape character in the pattern character string cannot be an underscore (_), percent sign (%), or an escape character.
- If bb....bb is SIMILAR, the pattern character string is specified incorrectly. For a description of conditions in which pattern character strings can be invalid, see the section on the SIMILAR predicate in the manual HiRDB Version 9 SQL Reference.
- ESCAPE CHARACTER:
- The length of the escape character is not one character.
- bb....bb: Predicate containing an error
- {LIKE |XLIKE |SIMILAR}
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11425-E A
Invalid data type for operand aaa in scalar function "bb....bb", query-no=ccc
- The data type of the value expression or type expression specified at aaa is invalid in scalar function bb....bb. If bb....bb is TRIM and aaa is 1, the TRIM character might be two or more characters.
- aaa: Number assigned to the invalid value expression
- bb....bb: Name of the scalar function:
{ ABS |CHARACTER |DATE |DAY |DAYS |DECIMAL
|DIGITS |FLOAT |HEX |HOUR |INTEGER |LENGTH
|LOWER |MINUTE |MOD |MONTH |SECOND |SUBSTR
|TIME |TIMESTAMP |UPPER |VALUE |YEAR
|VARCHAR_FORMAT |TIMESTAMP_FORMAT
|IS_USER_CONTAINED_IN_HDS_GROUP|BIT_AND_TEST
| MICROSECOND | POSITION | TRIM }
- ccc: Query number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11426-E A
Operand aaa incompatible with first operand in bb....bb, query-no=ccc
- The data types of the first value expression and the aaath value expression of a scalar function (VALUE, BIT_AND_TEST, POSITION, TRIM) or a CASE abbreviation (NULLIF, COALESCE) are not compatible. Even when the first value expression and the aaath value expression are character string data types, the data types might not be compatible if the character sets are different. However, if either the first value expression or the aaath value expression are one the following value expressions, it is converted to the character set of the corresponding value expression:
- Scalar function VALUE, CASE abbreviation COALESCE:
If the aaath value expression is a character string literal, it is converted to the character set of the first value expression.
- Scalar function POSITION:
If the first value expression is a character string literal, it is converted to the character set of the second value expression.
- Scalar function BIT_AND_TEST, CASE abbreviation NULLIF:
If the first value expression is a character string literal, it is converted to the character set of the second value expression. Conversely, if the second value expression is a character string literal, it is converted to the character set of the first value expression.
- Scalar function TRIM:
If the first value expression (the TRIM character) is a character string literal, it is converted to the character set of the second value expression (the TRIM source).
- aaa: Number assigned to the value expression whose data type is not compatible with the data type of the first value expression
- bb....bb: Erroneous function or expression:
{scalar function "VALUE"|scalar function "BIT_AND_TEST"
|scalar function "POSITION"
|scalar function "TRIM"
|case abbreviation "NULLIF"|case abbreviation "COALESCE"}
- ccc: Query number
- S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11427-E A
Operand a out of range in scalar function "bb....bb", query-no=ccc
- Value expression a in scalar function "bb....bb" does not satisfy the following conditions:
- Scalar function SUBSTR
- 1
value-expression-2
length of value-expression-1 - 0
value-expression-3
length of value-expression-1 - value-expression-2 + 1
- Note that 0 cannot be specified if a literal is specified in a.
- Scalar function POSITION
- 1
value-expression-3
length-of-value-expression-2
- a: Number assigned to the value expression:
{2|3}
- bb....bb: Scalar function name {SUBSTR|POSITION}
- ccc: Query number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11428-E A
Variable or parameter cannot be specified in aa....aa, query-no=bbb
- One of the following errors was detected in a scalar function (VALUE, HEX, or BIT_AND_TEST), in an embedded variable stored in the CASE expression, or the ? parameter.
- An embedded variable or ? parameter was specified in the first operand of the scalar function (VALUE).
- An embedded variable or ? parameter was specified as the value expression of the scalar function (HEX).
- An embedded variable or the ? parameter was specified in both operands of the scalar operation (BIT_AND_TEST).
- An embedded variable or ? parameter was specified in the first operand of the CASE abbreviation (COALESCE).
- An embedded variable or ? parameter was specified in both operands of the CASE abbreviation (NULLIF).
- An embedded variable or ? parameter was specified in the first WHEN clause of the simple CASE expression.
- An embedded variable or ? parameter was specified in the THEN or ELSE clause of the simple CASE expression or searched CASE expression.
- An embedded variable or ? parameter was specified in the CASE clause of the simple CASE expression.
- aa....aa: Erroneous function or expression:
{ scalar function "VALUE" |scalar function "HEX"
|case abbreviation "COALESCE"
|case abbreviation "NULLIF"
|simple CASE |searched CASE
|scalar function "BIT_AND_TEST" }
- bbb: Query number
- S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11430-E A
Invalid data type specified in select list
- A data type of a selection expression is invalid.
Invalid data type: - S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11431-E A
aa....aa error occurred, code=bbbb
- An error occurred during execution of an internal system function.
- aa....aa: Name of the internal function resulting in the error
- bbbb: Detail error code
- S: Ignores this SQL statement.
- P: Contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPA11440-E A
Inconvertible data type in assignment statement
- The data types of the assignment destination and assignment value in the SET statement are not convertible.
For the character string data type, the source and the destination of an assignment must use the same character set. However, if the assignment value is a character string literal, it is automatically converted to the character set of the assignment target, even if the character sets are different.
For an abstract data type, either the source and the destination of an assignment must have the same abstract data type, or the abstract data type for the source must be a subtype of that target. - S: Ignores this SQL statement and executes rollback.
- P: Correct the SQL statement and re-execute.
KFPA11441-E A
Invalid use of data type in "SELECT" clause, select-list-no=aaaaa, query-no=bbb
- When the literal, operation, component specification, or function invocation result specified in a selection expression is one of the following data types, you cannot query a table derived by specifying the FOR READ ONLY clause, duplicate elimination, or a set operation:
- BLOB
- BINARY (larger than 32,000 bytes)
- Abstract data type
- BOOLEAN
- In the selection expression of the derived table of a FROM clause, the following data type operators cannot be specified in the operational result.
- BLOB
- BINARY with a maximum length of 32,001 bytes or more
- aaaaa: The number in the selection expression with an invalid data type or data length
- bbb: Query number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11442-E A
Invalid use of BLOB in scalar function "LENGTH", query-no=aa
- Usage of the LENGTH scalar function with a BLOB data column specified is incorrect. The LENGTH scalar function with a BLOB data column specified can be specified only in a selection expression or update value as a single-unit LENGTH function.
- aa: Number of the query specifying an invalid LENGTH function
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11443-E A
Inconvertible data type of target specification "aa....aa" in FETCH or SELECT statement
- The target specification for the FETCH statement or the single-row SELECT statement is not a convertible data type.
For a character string data type, one of the following conditions must be satisfied (except in the case of an embedded variable): - The FETCH statement and the target specification for the FETCH statement must use the same character set.
- The single-row SELECT statement and the target specification for the single-row SELECT statement must use the same character set.
- For an abstract data type, one of the following conditions must be satisfied:
- The FETCH statement and the target specification for the FETCH statement must be of the same abstract data type.
- The single-row SELECT statement and the target specification for the single-row SELECT statement must be of the same abstract data type.
- The abstract data type of the FETCH statement must be a subtype of the abstract data type of the target specification for the FETCH statement.
- The abstract data type of the single-row SELECT statement must be a subtype of the abstract data type of the target specification for the single-row SELECT statement.
- aa....aa: Name of the target
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11444-E A
Invalid data type for operand aaa in bb....bb, query-no=ccc
- The data type or format specified in a CASE expression is invalid for the following reason:
- The result of the value expression is the BLOB type, BINARY type of 32,001 bytes or larger, abstract data type, or BOOLEAN type.
- This error was detected in the following value expression:
- Value expression aaa in the CASE abbreviation
- Value expression in CASE aaa, WHEN aaa, or THEN aaa, or ELSE aaa of the simple CASE expression
- Value expression in THEN aaa or ELSE aaa of the searched CASE expression
- aaa: Number of the operand containing the erroneous value expression or the number of the erroneous value expression
- bb....bb: Erroneous CASE expression or the operand of the erroneous CASE expression:
{ case abbreviation "COALESCE"
|case abbreviation "NULLIF"
|"CASE" in simple CASE |"WHEN" in simple CASE
|"THEN" in simple CASE |"ELSE" in simple CASE
|"THEN" in searched CASE |"ELSE" in searched CASE }
- ccc: Query number
- S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11445-E A
Variables or parameters cannot be specified in argument of set function "aa....aa", query-no=bbb
- An embedded variable, SQL parameter, or ? parameter cannot be specified in the argument of a set function.
- aa....aa: Name of the set function specifying an embedded variable or ? parameter in its argument
- bbb: Query number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11446-E A
CASE operand is incompatible with WHEN operand aaa in simple CASE, query-no=bbb
- The data type of a CASE value expression in a simple CASE expression is not compatible with the data type of the aaath WHEN value expression. Even if the CASE value expression in a simple CASE expression and the aaath WHEN value expression are character string data types, the data types might not be compatible if the character set are different. However, if the WHEN value expression is the following, it is converted to the character set of the CASE expression:
- aaa: Number of value expression in WHEN that does not match the data type of the value expression in CASE
- bbb: Query number
- S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11447-E A
THEN operand aaa is incompatible with THEN or ELSE operand bbb in simple CASE or searched CASE, query-no=ccc
- The data type of the value expression in THEN aaa does not match the data type of the value expression in THEN bbb or ELSE bbb in a simple CASE expression or searched CASE expression.
- aaa: Number of the value expression to become the basis for checking data type compatibility
- bbb: Number of the value expression whose data type does not match the data type of value expression aaa
- ccc: Query number
- S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11448-E A
At least one THEN operand in simple CASE or searched CASE must be value expression, query-no=aaa
- NULL was specified in all THEN operands. In a simple CASE expression or searched CASE expression, a value expression must be specified in at least one THEN operand.
- aaa: Query number
- S: Ignores this SQL statement; executes rollback in the case of a definition SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11449-E A
Cardinality violation in single row select
- The result of a single-row SELECT statement is two or more rows.
- S: Ignores this SQL statement.
- P: Either specify a query whose selection result becomes one row or less or use the cursor for selection.
KFPA11450-E A
Cardinality violation at aaa-th subquery.Two or more rows found
- The result of a subquery of one of the following types consists of at least two rows:
- Scalar subquery specified with a comparison predicate or the SET clause of an UPDATE statement
- Row subquery
- aaa: Position from the beginning of the subquery that resulted in the base error. However, when a set operation is specified in a subquery, this is the number of the first specified query in the set operation query specification. Also, if the cause of the error is the contents of the viewed table definition, this is the number of the query that specified the viewed table.
- S: Ignores this SQL statement.
- P: Correct the SQL statement so that the subquery result is one row or less and re-execute.
KFPA11451-E A
aa....aa constraint "bb....bb" violation at cc....cc
- There is a violation of a referential constraint or a check constraint.
- aa....aa: Type of constraint
- {Referential|Check}
- bb....bb: Name of the constraint involved in the constraint violation
- cc....cc: SQL statement involved in the constraint violation
- {INSERT | UPDATE | DELETE}
- aa....aa: Referential (referential constraint violation)
- For a primary key update of a referenced table, the value of the primary key configuration column before update and the value of the row that holds the equivalent foreign key configuration column are in the referencing table.
- For a primary key deletion of a referenced table, the value of the primary key configuration column of the row to be deleted and the value of the row that holds the equivalent foreign key configuration column are in the referencing table.
- For a foreign key insertion of a referencing table, the value of the primary key configuration column of the row to be inserted and the value of the row that holds the equivalent foreign key configuration column are not in the referencing table.
- For a foreign key update of a referencing table, the value of the primary key configuration column after the update and the value of the row that holds the equivalent foreign key configuration column are not in the referencing table.
- The same primary key has already been referenced within a table, and there are multiple definitions of referential constraints that include the ON UPDATE CASCADE specification in the specified referential constraint operation.
- aa....aa: Check (check constraint violation)
- The update value or the insert value does not satisfy the conditions defined for the check constraint.
- The same primary key has already been referenced within a table, and there are multiple definitions of referential constraints that include the ON UPDATE CASCADE specification in the specified referential constraint operation.
- S: Ignores this SQL statement. If this is a definition SQL statement, it is rolled back.
- P:
- aa....aa: Referential
- If an UPDATE statement is for a referenced table, take one of the following actions:
Change the update conditions.
Delete from the referencing table the row that holds the foreign key value that is equivalent to the value of the primary key before update, or update the value of the foreign key of the referencing table to the value of another primary key in the referenced table.
- If a DELETE statement is for a referenced table, take one of the following actions:
Change the deletion conditions.
Delete from the referencing table the row that holds the foreign key value that is equivalent to the value of the primary key to be deleted, or update the value of the foreign key of the referencing table to the value of another primary key in the referenced table.
- If an INSERT statement is for a referenced table, take one of the following actions:
Change the value of the foreign key to be inserted to an appropriate value.
Add to the referenced table the row that holds the insert value of the foreign key of the referencing table as the primary key.
- If an UPDATE statement is for a referenced table, take one of the following actions:
Change the update conditions.
Change the update value of the foreign key to an appropriate value.
Add to the referenced table the row that holds the update value of the foreign key of the referencing table as the primary key.
- If an error occurs after taking the above actions, change the specification to one referential constraint that includes the ON UPDATE CASCADE specification in the referential constraint operation, which references the same primary key, and re-define the table.
- aa....aa: Check
- Correct the update or insertion value to satisfy the conditions of the check constraint definition.
- If an error occurs even after taking the above action, change the specification to one referential constraint that includes the ON UPDATE CASCADE specification in the referential constraint operation, which references the same primary key, and re-define the table.
KFPA11453-E A
CAST error occurred, reason=aa....aa, query-no=bbb
- The method of specifying CAST or the data content is invalid.
- aa....aa: Error cause
- COMBINATION:
- An error occurred when combining the data type and data length of the value expression result with the data type and data length after conversion. This applies to the character set as well as the data type. For details about which data type conversions are possible, see the manual HiRDB Version 9 SQL Reference.
- Examples: CAST(TIME-type AS INT)
- CAST(MCHAR-type AS CHAR(1) CHARACTER SET EBCDIK)
- FORMAT:
- The format of a character string literal in the conversion source data is invalid.
- (Example) CAST('ABC' AS INT)
- VALUE:
- A value in the conversion source data is invalid.
- (Example) CAST('1999-99-99' AS DATE)
- TRUNCATION:
- Characters were truncated.
- (Example) CAST(DATE-type AS CHAR(1))
- OVERFLOW:
- An overflow occurred.
- (Example) CAST(99999 AS DEC(1,1))
- INVALID CAST OPERAND:
- An invalid specification exists in the conversion source.
- (Example) CAST(BLOB-type AS data-type)
- DATA TYPE:
- A data type that cannot be used is specified as a conversion data type.
- (Example) CAST(C1 AS BLOB)
- bbb: Number of the query specifying CAST specification that caused the error.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11455-E A
Unable to specify aa....aa in view definition or in "WITH" query
- If a CASE expression is specified in a selection expression in the outermost query of a view definition, or in a derived query expression for a query in a WITH clause, a repetition column cannot be specified in its search condition.
- aa....aa: multi-value column in search condition of CASE expression
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11456-E A
Outer reference specified for column derived from set function with argument of operation
- When a set function in which an operation is an argument is specified in either a selection expression for a view definition or a selection expression in a derived query expression for a query in a WITH clause, the applicable column cannot be specified in a subquery as an outer reference column.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11458-E A
Duplicate query name "aa....aa" in "WITH" clause
- Query name "aa....aa" is duplicated in the WITH clause. The same query name cannot be specified more than once in the WITH clause.
- aa....aa: Duplicated query name
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11459-E A
Duplicate column name "aa....aa" in derived table "bb....bb" in view definition or "WITH" query
- The column name "aa....aa" in the query name "bb....bb" in the viewed table or the WITH clause is duplicated. A column name can be specified only once in a viewed table or in a query name in a WITH clause.
- aa....aa: Duplicate column name
- bb....bb: Name of the viewed table or the query name containing duplicate column names
- S: Ignores this SQL statement.
- P:
- If a column name is specified, correct the column name to eliminate duplication.
- If a column name is omitted, the column name in the query selection expression must be duplicated, resulting in duplicate column names in the viewed table or in the query in the WITH clause. In this case, explicitly specify a unique column name.
KFPA11460-E A
No name for derived column in view definition or "WITH" query
- If a table derived by a view definition or a derived query expression in a WITH clause contains an unnamed column, a column name cannot be omitted from the name of the viewed table or the query name.
- S: Ignores this SQL statement.
- P: Specify a column name.
KFPA11461-E A
Unable to derive internal table for view or "WITH" query having long data column or abstract data column or multi-value column
- A query to create an internal derived table cannot be specified for a named derived table specified in one of the following selection expressions:
- BLOB
- BINARY 32,001 bytes or larger
- Abstract data type
- Repetition column
- The conditions for creating an internal derived table are as follows:
- In a query for a named derived table, derived by specifying SELECT DISTINCT, the named derived table is included in a subquery or directly includes one of the following:
- GROUP BY clause, HAVING clause, or set function
- SELECT DISTINCT
- Table join (including outer join and inner join)
- A value expression other than a column specification is specified in the selection expression.
- None of the columns of the named derived table specified in the FROM clause is specified singularly in the selection expression.
- NEXT VALUE expression
- A query for a named derived table, derived by specifying a GROUP BY clause, HAVING clause, or a set function, directly includes one of the following:
- GROUP BY clause, HAVING clause, or set function
- Table join (including outer join and inner join)
- Window function
- NEXT VALUE expression
- One of the following is directly included in the query for a named derived table specified by a selection expression that is a value expression other than a column specification:
- GROUP BY clause, HAVING clause, or set function
- Window function
- Joined table
- A query on a named derived table derived by directly specifying a set function with DISTINCT contains one of the following:
- GROUP BY clause, HAVING clause, or set function
- SELECT DISTINCT
- Window function
- A query for a named derived table derived by specifying a table join (including outer join and inner join) directly includes a table join (including outer join and inner join), and one of the specified table joins specifies a joined table.
- A query on a named derived table derived by directly specifying a scalar subquery as a selection expression contains one of the following:
- SELECT DISTINCT
- GROUP BY clause, HAVING clause, or set function
- Table join (including outer join and inner join)
- A value expression other than a column specification specified in a selection expression
- A scalar subquery specified in a selection expression
- The same column derived from a value expression containing a subquery, specified more than once in the selection expression for a named derived table
- A column derived from a value expression containing a subquery, specified as an external reference column in the selection expression for a named derived table
- A viewed table defined before HiRDB version 07-02
- A query for a named derived table derived from a set operation, which satisfies one of the following conditions:
- One of the operators of the set operation includes an internal derived table query, a query that specifies a derived table, or a query that specifies a subquery in a selection expression.
- One of the operators of the set operation and the query for the named derived table satisfy one of the conditions of 1 through 6 above.
- A query for a named derived table derived from a set operation that includes clauses other than UNION ALL, which directly includes one of the following:
- GROUP BY clause, HAVING clause, or a set function
- SELECT DISTINCT
- Table join (including external or internal joins)
- WHERE clause
- Subquery
- Value expression other than a column specification in a selection expression
- In a selection expression, the columns of a named derived table specified in the FROM clause are not specified once each
- NEXT VALUE expression
- A query for a named derived table derived from a set operation that includes only UNION ALL, which directly includes one of the following:
- GROUP BY clause, HAVING clause, or a set function
- Window function
- WHERE clause or subquery (however, a subquery, a set operation operator, or an INSERT statement query only)
- Function call or system definition scalar function
- Component specification
- WRITE specification
- GET_JAVA_STORED_ROUTINE_SOURCE specification
- Sort specification with items not in the selection expression
- Subquery for a named derived table derived from a set operation specified in the FROM clause
- Subquery that specifies a derived table
- Subquery specified in a value expression other than a column specification in the GROUP BY clause
- A data type of an SQL variable specified in a selection expression or an SQL parameter that is one of the following:
BLOB type
BINARY type 32,001 bytes or larger
Abstract data type
BOOLEAN type
- The query specification specified for the table-joining of named derived tables derived by a set operation consisting solely of UNION ALL specifies one of the following:
- A named derived table in a table reference other than at the leftmost outer table for an outer join
- The FROM clause specifying a named derived table, which specifies a comma join (that is, specifies a different table reference than the joined table for which a derived table is specified)
- A subquery or a derived table
- A query specification contained either in a subquery or in the operation term for a set operation
- A set operation term that derives named derived tables and contains one of the following:
Table join
GROUP BY clause, HAVING clause, or a set function
SELECT DISTINCT
A value expression in a selection expression other than a column specification
A query that creates an inner derived table
A query specifying a derived table
- A named derived table derived by specifying a set operation (in addition to a named derived table)
- One of the following, in the table reference to a joined table specifying a named derived table:
A named derived table derived by specifying the joining of tables
A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
A named derived table derived by specifying SELECT DISTINCT
A named derived table derived by specifying a value expression other than a column specification in a selection expression
A named derived table derived by specifying a query that creates an inner derived table
A named derived table derived by specifying a subquery
- The total number of tables obtained by the following expression is greater than 65:
Total number of tables = a + b
c + d
a: Total number of tables from which named derived tables are derived
b: Number of set operations from which named derived tables are derived + 1
c: Total number of tables specified on the right side of an outer join
d: If a query other than a query for which a named derived table is specified is also specified, the total number of tables specified in the query
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11463-E A
Unable to specify long, large object, abstract, or boolean data in "bb....bb" clause, query-no=aaa
- A value expression with a result of abstract data, BOOLEAN data, BLOB data, or BINARY data with a maximum length of 32,001 bytes or larger cannot be specified in a GROUP BY clause value expression or an ORDER BY clause sort key.
- aaa: Query number
- bb....bb:
{GROUP BY|ORDER BY}
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11465-E A
Data type must be BOOLEAN in "BOOLEAN" predicate, query-no=aaa
- A non-BOOLEAN data type cannot be specified in a logical predicate.
- aaa: Query number for the logical predicate specifying an invalid data type
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11467-E A
Unable to specify aa....aa in view definition or in "WITH" query
- The following items cannot be specified in a view definition, or in a query specification in a WITH clause:
- WRITE specification
- GET_JAVA_STORED_ROUTINE_SOURCE specification
- XML constructor function
- SQL/XML scalar function
- SQL/XML predicate
- SQL/XML set function
- aa....aa:
- { WRITE specification
- | GET_JAVA_STORED_ROUTINE_SOURCE specification
- | XML constructor
- | XMLQUERY
- | XMLSERIALIZE
- | XMLPARSE
- | XMLAGG
- | XMLEXISTS }
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11468-E A
Inconvertible data type in "RETURN" statement with "RETURNS" clause
- The data types in the RETURN statement and the RETURNS clause are not convertible.
For a character string data type, the RETURNS clause and RETURN statement must use the same character set. However, if the value expression in the RETURN statement is a literal, the value expression is automatically converted to the character set of the RETURNS clause.
For an abstract data type, either the abstract data type for the RETURNS clause and the RETURN statement must be the same, or the abstract data type for the RETURN statement must be a subtype of that in the RETURNS clause. - S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11469-E A
Return data in "RETURN" statement too long for "RETURNS" clause
- The length of the return value data in the RETURN statement is too long for the RETURNS clause.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11470-E A
Unable to specify aa....aa in column-name list of ARRAY predicate, query-no=bbb
- The column specification for the structured repetition predicate contains one of the following errors:
- The specified repetition columns do not belong to the same table or are not columns derived from the same table.
- A repetition column is an outer reference column.
- The same column is specified as a repetition column.
- A non-repetition column, an SQL variable, or an SQL parameter is specified.
- aa....aa:
{ columns in different tables |outer reference column
|same columns |single-value column,
SQL variable or SQL parameter
|derived columns from different tables }
- bbb: Number of the query specifying the predicate
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11471-E A
Unable to specify columns in different tables in OR condition includes ARRAY predicate
- The following columns (excluding outer reference columns) cannot be specified in the search condition of the OR operand that includes a structured repetition predicate:
- Columns from different tables
- Columns derived from different tables
- Different tables also includes tables that have the same base table but different correlation names.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11472-E A
Unable to specify both DISTINCT for selected row or distinct view and set operation in view definition or "WITH" query
- The following items cannot be specified in a query specification that is the object of a set operation when a view definition is specified, or when a set operation (UNION ALL) is specified in a derived query expression for a query in a WITH clause:
- SELECT DISTINCT
- Viewed tables defined by specifying SELECT DISTINCT in the outermost query specification
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11473-E A
Unable to specify "aa....aa" in query for table derived from set operation
- The following items cannot be specified in a query for a table that is derived by specifying a set operation (UNION ALL):
- A GROUP BY clause, a HAVING clause, or a set operation
- Joining of tables
- Set operations
- Subqueries specifying a joined table
- Subqueries specifying a value expression other than a column specification in a GROUP BY clause
- Queries specifying, in a sort key, a column that is not included in a column specification
- Function invocations
- Component specifications
- aa....aa:
{ grouping or set function |join |set operation
|subquery with joined table
|subquery with grouping by expression
|sorting by unselected column
|function invocation |component specification }
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11474-E A
Unable to specify table derived from "bb....bb" in "aa....aa"
- One of the following errors was detected:
- A table derived by specifying a set operation (UNION ALL) cannot be specified in the FROM clause of the following types of query specification:
- Query specification of an INSERT statement
- Subquery
- Derived query expression in a view definition
- Derived query expression of a query that uses a WITH clause
- A table derived by specifying a joined table cannot be specified in the FROM clause of the following types of query specification:
- Derived query expression in a view definition
- Derived query expression of a query that uses a WITH clause
- A table derived by specifying a joined table for the query, which is the target of a set operation (UNION ALL), cannot be specified in the FROM clause of a query that specifies a subquery.
- aa....aa:
{ subquery |INSERT statement |view definition
|"WITH" query |query in "FROM" clause
|query with subquery }
- bb....bb:
{ set operation |joined table
|set operation with joined table }
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11475-E A
Invalid a-th operand in bb....bb
- The ath operand in the bb....bb specification is invalid:
- A value expression that is not allowed was specified.
- A data type that is not allowed was specified.
- a: Operand number containing the error
- bb....bb: Name of the specification containing the error:
{ WRITE specification |WRITE LINE statement |GET_JAVA_STORED_ROUTINE_SOURCE }
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11476-E A
Error occurred during execution of system defined scalar function in aa....aa, query-no=bbb, detail="cc....cc"
- An error occurred during execution of a system-defined scalar function.
- aa....aa: Name of the clause or statement that specified the function:
{ "WHERE" clause |"SET" clause |"ADD" clause
|"SELECT" clause |"ON" condition |"GROUP BY" clause
|"HAVING" clause |"ORDER BY"clause |"IF" statement
|"WHILE" statement |"SET" statement |"RETURN" statement
|"VALUES" statement |"CALL" statement
|"WRITE LINE" statement |triggered action condition }
- bbb: Query number that specified the clause or statement
- cc....cc: Error detail message
- S: Ignores this SQL statement.
- P: Take action appropriate to the error detail message:
Error detail message (cc....cc) | Function name | Explanation | Action to be taken |
---|
Invalid value of 1st argument for function function-name | ADD_INTERNAL DATETIME DAYNAME DAYOFWEEK DAYOFYEAR INTERVAL_DATETIMES ISDIGITS LAST_DAY MONTHNAME MONTHS_BETWEEN NEXT_DAY STRTONUM YEARSBETWEEN TRUNCYEAR ROUNDMONTH QUARTER HALF WEEK WEEKOFMONTH CENTURY MIDNIGHTSECONDES STRTONUM | Argument 1 value is invalid. | Modify the SQL by considering the following:
- If a date, time, or date and time character string expression is specified for the argument, is the format correct?
- If a numerical value character string expression is specified for the argument, is the format correct?
- If the data type of the argument is variable-length character string, is the length appropriate?
For details about specifying this argument, see the description of the relevant scalar function in the manual HiRDB Version 9 SQL Reference. |
Invalid value of 2nd argument for function function-name | DATETIME INTERVAL_DATETIMES LTRIM MONTHS_BETWEEN NEXT_DAY NUMEDIT REPLACE REPLACE_LONG ROUND RTRIM TRUNC YEARSBETWEEN INSERTSTR INSERTSTR_LONG LEFTSTR RIGHTSTR TRUNCYEAR ROUNDMONTH QUARTER HALF | Argument 2 value is invalid. |
Invalid value of 3rd argument for function function-name | REPLACE REPLACE_LONG ROUND INSERTSTR INSERTSTR_LONG POSSTR TRUNCYEAR QUARTER HALF | Argument 3 value is invalid. |
Invalid value of 4th argument for function function-name | POSSTR TRANSL TRANSL_LONG | Argument 4 value is invalid. |
Result data too long for returned data type in function function-name | REPLACE REPLACE_LONG INSERTSTR INSERTSTR_LONG TRANSL TRANSL_LONG | Results length exceeded the maximum permissible length for the results data type. | Ensure that the results length does not exceed the maximum permissible length for the results data type. For details about the length of the results data type, see the description of the relevant scalar function in the manual HiRDB Version 9 SQL Reference. |
Domain error in function function-name | ACOS ASIN LN LOG10 SQRT | Value outside the definition range of the function was passed. | Ensure that a value outside the definition range of the function is not passed. For details about the definition range of the function, see the description of the relevant scalar function in the manual HiRDB Version 9 SQL Reference. |
Division by zero in function function-name | POWER | Division by 0 occurred. | Ensure that division by 0 does not occur. For details about conditions that cause this error, see the description of the relevant scalar function in the manual HiRDB Version 9 SQL Reference. |
Overflow error in function function-name | ADD_INTERNAL CEIL COSH DEGREES EXP FLOOR GREATEST LEAST NEXT_DAY NUMEDIT POWER ROUND ROUNDMONTH SINH STRTONUM TAN TRUNCYEAR | Overflow occurred. | Ensure that the function results can be expressed in the results data type. |
KFPA11477-E A
Data type of aa....aa-th argument in CALL statement inconvertible with parameter data type "bb....bb"
- The data type of the aa....aath argument in the CALL statement and the data type bb....bb of the aa....aath parameter of the called procedure are not convertible data types.
Even when both have character string data types, conversion is not possible when the character sets are different. However, if the aa....aath argument of the CALL statement is one of the following value expressions, it is converted to the character set of the aa....aath parameter of the procedure being called: - Character string literal
- Embedded variable
- ? parameter
- aa....aa: Argument number of the inconvertible data type
- bb....bb: Data type of the parameter to the procedure:
- {INTEGER|SMALLINT|DECIMAL(m,n)|FLOAT|SMALLFLT
- |CHARACTER(l)|CHARACTER(l) CHARACTER SET EBCDIK
- |CHARACTER(l) CHARACTER SET UTF16
- |VARCHAR(l)|VARCHAR(l) CHARACTER SET EBCDIK
- |VARCHAR(l) CHARACTER SET UTF16
- |NCHAR(l)
- |NVARCHAR(l)|MCHAR(l)|MVARCHAR(l)|DATE
- |TIME|TIMESTAMP(p)
- |INTERVAL YEAR TO DAY
- |INTERVAL HOUR TO SECOND
- |BLOB(l)|BINARY(l)|ABSTRACT DATA TYPE}
- m and n indicate the DECIMAL precision and scaling, respectively. l indicates the character string length. p indicates the precision in seconds.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11479-E A
Invalid concatenation operation for "aa....aa" in UPDATE statement
- One of the following errors was detected when updating a BLOB string or BINARY string whose length is 32,001 bytes or more using a concatenation operation:
- An item other than a column was specified in the first operation item of the concatenation operation.
- An item other than the ? parameter, SQL variable, or SQL parameter was specified in the second operation item of the concatenation operation.
- The column to be updated differs from the column in the first operation item of the concatenation operation.
- A concatenation operation was specified for the result of the concatenation operation.
- A BLOB column specified in the search condition of a check constraint or a BINARY column with a maximum length of 32,001 bytes or larger is specified as the column to be updated.
- aa....aa: {BLOB|BINARY}
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA11487-E A
Status of dynamic result set invalid
- An object was returned as an invalid dynamic results set for the following reason:
- The object returned as a dynamic results set from a method defined as a Java stored procedure is not the object for which a results set was determined by the query.
- S: Invalidates the transaction.
- P: Specify an object that performs a query as the object to be returned as a dynamic results set from the method defined as a Java stored procedure. (Use the SQL statement specified by JDBC's prepareStatement method as the SELECT statement.). Also execute a query of this object (execute JDBC's executeQuery method).
KFPA11488-E A
Duplicate dynamic result set
- The object returned as a dynamic results set from a method defined as a Java stored procedure is specified by multiple parameters.
- S: Invalidates the transaction.
- P: Correct so that the object returned as a dynamic results set from the method defined as a Java stored procedure is not set by multiple parameters.
KFPA11489-E A
System function aa....aa error, code=bb....bb, in copying cc....cc file "dd....dd" to "ee....ee" for ff....ff
- An error occurred in a system function during registration, re-registration, or deletion of a JAR file or C library file.
- aa....aa: System function name
- bb....bb: Detail codes for system-related errors
- See 4.2 Detail codes for system-related errors.
- cc....cc: File type
- JAR: JAR file
- CLIB: C library file
- dd....dd: Name of file (only the first 80 characters if the name exceeds 80 characters)
- ee....ee: Temporary file name
- ff....ff: Type of file operation{ install | replace | remove }
- S: Invalidates the transaction.
- P: Remove the error cause and re-execute the transaction.
KFPA11490-E A
aa....aa bb....bb "cc....cc" failed, because dd....dd
- An attempt to register, re-register, or delete a JAR file or C library file failed.
- aa....aa: Type of file operation { INSTALL | REPLACE | REMOVE }
- bb....bb: File type
- JAR: JAR file
- CLIB: C library file
- cc....cc: Name of file (only the first 80 characters if the name exceeds 80 characters)
- dd....dd: Reason
- transaction already begin:
- The transaction has already started.
- JAR file already installed:
- The JAR file is already installed.
- JAR file not found:
- The JAR file cannot be found in the JAR file storage directory.
- JAR file synchronization failed:
- An error occurred in the pdjarsync command.
- C library file already installed:
- The C library file is already installed.
- C library file not found:
- The C library file cannot be found in the C library file storage directory.
- C library file synchronization failed:
- An error occurred in the pdclibsync command.
- S: Invalidates the transaction.
- P:
- When dd....dd is transaction already begin:
Before registration, re-registration, or deletion, commit all transactions (perform a COMMIT or ROLLBACK).
- When dd....dd is JAR file already installed:
If you want to overwrite the existing JAR file, execute REPLACE JAR.
- When dd....dd is JAR file not found:
Correct the specified JAR file name and re-execute.
- When dd....dd is JAR file synchronization failed:
Use the pdjarsync command to display a list of JAR files, and then check the contents. If necessary, re-execute registration, re-registration, or deletion with the pdjarsync command.
- When dd....dd is C library file already installed:
If you want to overwrite the existing C library file, execute REPLACE CLIB.
- When dd....dd is C library file not found:
Correct the specified C library file name and re-execute.
- When dd....dd is C library file synchronization failed:
Use the pdclibsync command to display a list of C library files, and then check the contents. If necessary, re-execute registration, re-registration, or deletion with the pdclibsync command.
KFPA11491-E A
Error occurred on JavaVM, message=aa....aa
- An error occurred in the Java Virtual Machine.
- aa....aa: Error detail and type:
- INIT
- Error occurred during startup.
- exception or error message
- Error occurred at a time other than during startup. If the number of characters exceeds 208, a hash mark (#) is displayed as the 208th character.
- ******
- Error occurred in the Java Virtual Machine.
- S: Ignores this SQL statement.
- P: Re-execute the Java stored procedure or Java stored function. If the same error occurs again, contact the HiRDB administrator.
- O:
- When aa....aa is INIT
Ensure that the following system definition operands are correct:
pd_java_option, pd_java_archive_directory, pd_java_classpath, pd_java_libpath, pd_java_stdout_file, pd_java_runtimepath
- When aa....aa is exception or error message
Refer to the JDK documentation and take appropriate action.
- When aa....aa is ******
Restart the HiRDB server.
KFPA11492-E A
Exception raised, in java method=cc....cc for ROUTINE aa....aa."bb....bb", message=dd....dd
- An exception error occurred during execution of a Java method defined as a Java stored procedure or Java stored function.
- aa....aa: Owner name
- bb....bb: Name of Java stored procedure or Java stored function
- cc....cc: Java method name (if the name exceeds 64 characters, a hash mark (#) is displayed as the 64th character)
- dd....dd: One of the following (if the item exceeds 65 characters, a hash mark (#) is displayed as the 65th character):
- Detailed message that is set for the exception error object caused by the Java method
- Class name of the exception error object (this is displayed when no detailed message has been set)
- S: Ignores this SQL statement.
- P: Take one of the following actions:
- Re-create the Java method by referring to the exception error message.
- Eliminate the cause of the exception error by referring to standard output or standard error from the Java method, which is output to the file specified in the pd_java_stdout_file system definition operand.
- O: Specify the pd_java_stdout_file operand to make it possible to obtain standard output or standard error from the Java method.
KFPA11493-E A
Unable to execute aa....aa for ROUTINE bb....bb."cc....cc", reason_code=dd, message=ee....ee
- For reason dd, unable to execute the Java method or C function for a stored procedure or stored function defined as cc....cc and owned by bb....bb.
- aa....aa: Implementation language of the external routine: {Java method|C function}
- bb....bb: Owner name
- cc....cc: Name of stored procedure or stored function
- dd: Reason code
- When aa....aa is Java method:
- 02: Specified method was not found.
- 03: Class loading failed.
- 04: Specified method caused a security violation exception.
- 05: JAR file I/O processing failed.
- 06: Specified JAR file was not found.
- 07: Specified class was not found.
- 08: Specified method has no static qualifier.
- 09: Return value type specified by EXTERNAL NAME in the definition of the Java stored procedure or Java stored function is different from the return value type of the Java method.
- When aa....aa is C function:
- 02: Specified C function was not found.
- 05: I/O failure in the C library file for the external C stored routine.
- 06: C library file for the external C stored routine was not found.
- ee....ee: Message (if it exceeds 109 characters, the first 108 characters are shown and a hash mark (#) is displayed in the 109th character)
- When aa....aa is Java method:
Reason code | Message |
---|
02, 04, 08 | Method name |
03, 07 | Class name |
05, 06, 09 | JAR file name |
- When aa....aa is C function:
Reason code | Message |
---|
02 | C function name |
05, 06 | C library file name |
- S: Ignores this SQL statement.
- P: Take one of the following corrective actions:
- Review and, if necessary, revise the specification of the external routine where the stored procedure or stored function is defined according to the tables below.
- When aa....aa is Java method:
Reason code | Action |
---|
02, 04 | Check the specification of the method name. |
03, 07 | Check the specification of the class name. |
05, 06 | Check the specification of the JAR file name. |
08 | Check the Java class source file to make sure that the method has a static qualifier. |
09 | Make sure that the return value type matches the return value type of the Java method. |
- When aa....aa is C function:
Reason code | Action |
---|
02 | Check the external function identifier or C library file name. |
05, 06 | Check the specification of the C library file name. |
- Make sure that the specified JAR file or C library file is registered correctly.
- Make sure that the specified C function exists in the C library file that is specified when the stored procedure or stored function is defined.
KFPA11494-E A
Unable to use JAVA procedure or function
- Java stored procedure or Java stored function cannot be used for the following reason:
- The HiRDB being used is not a POSIX library version.
- S: Ignores this SQL statement. The transaction is invalidated in the case of a definition SQL statement.
- Action
- To use Java stored procedures or Java stored functions, execute the pdsetup -l command.
KFPA11495-E A
Unable to execute SQL in function aa....aa."bb....bb" (cc....cc)
- A database manipulation SQL statement is being executed from the aa....aa."bb....bb" function.
- aa....aa: Owner name
- bb....bb: Function name
- cc....cc: Identifying name
- S: Ignores this SQL statement.
- P:
- Correct so that the SQL statement is not executed from the aa....aa."bb....bb" function, and then re-execute.
- If the function body is a Java method, correct so that the Java method does not manipulate the database, and then re-execute.
KFPA11497-E A
aa....aa in RDAREA name specification
- One of the following errors occurred in the specified RDAREA name.
- The specification contains a syntax error.
- The same RDAREA name is specified more than once.
- An RDAREA storing the table is not supported.
- aa....aa: {Syntax error|Duplicate RDAREA names|Invalid RDAREA for table}
- S: Ignores this SQL statement.
- P: Correct the error and re-execute.
KFPA11500-E A
Unable to open holdable cursor
- A holdable cursor cannot be opened for the following reason:
- The maximum number of simultaneously open holdable cursors during non-runtime of the LOCK statement with UNTIL DISCONNECT specified that is specified in the pd_max_open_holdable_cursors operand of the server common definition, back-end server definition, dictionary server definition, or single server definition, was exceeded.
- S: Ignores this SQL statement.
- P: Correct the UAP or SQL and re-execute.
- Action
- Revise the maximum number of simultaneously open holdable cursors during non-runtime of a LOCK statement with UNTIL DISCONNECT specified that is specified in the pd_max_open_holdable_cursors operand of the server common definition, back-end server definition, dictionary server definition, or single server definition. If necessary, change the specified value and re-start HiRDB.
KFPA11501-E A
Cursor not opened
- The cursor specified in the FETCH or CLOSE statement has not been opened.
- S: Ignores this SQL statement.
- P: Modify the UAP so that the cursor is opened before fetching a row and then is closed, then re-execute.
KFPA11502-E A
Cursor already opened
- An attempt was made to open an already open cursor.
- S: Ignores this SQL statement.
- P: Modify the UAP so that the cursor is closed before reopening it, then re-execute.
KFPA11504-E A
Invalid data type specified in routine definition
- One of the following errors was detected in a data type specification in the routine definition:
- The data type of the parameter of the routine that specifies Java in the LANGUAGE clause is not convertible to the data type specified in the EXTERNAL NAME clause.
- The data type of the RETURN clause of the routine that specifies Java in the LANGUAGE clause is not convertible to the data type specified in the EXTERNAL NAME clause.
- The number of data types for the parameter of the routine that specifies Java in the LANGUAGE clause is different from the number of data types specified in the EXTERNAL NAME clause.
- void is not specified as the returns type name in the EXTERNAL NAME clause of the procedure that specifies Java in the LANGUAGE clause.
- BLOB type, BINARY type, or an abstract data type (including XML type) was specified in a parameter of the routine that specifies C in the LANGUAGE clause.
- BLOB type, BINARY type, or an abstract data type (including XML type) was specified in the RETURNS clause of the routine that specifies C in the LANGUAGE clause.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11505-E A
aa....aa requested for query with opened cursor
- Preprocessing or preprocessing invalidation was requested for a query while a cursor was open. Or, preprocessing or preprocessing invalidation was requested for a query open for reference by another cursor.
- aa....aa: The SQL statement that requested execution
- PREPARE: Preprocessing has been requested.
- DEALLOCATE PREPARE: Preprocessing invalidation has been requested.
- S: Ignores this SQL statement.
- P: Revise the UAP so that the cursor is closed before preprocessing or preprocessing invalidation, and re-execute. Or, revise the UAP so that another cursor that is referencing is closed before preprocessing or preprocessing invalidation, and re-execute.
KFPA11506-E A
Invalid request for executing of query
- A query for which preprocessing was executed with the PREPARE statement cannot be executed by the EXECUTE statement. Or, a query cannot be executed by the EXECUTE IMMEDIATE statement.
- S: Ignores this SQL statement.
- P: Modify the UAP so that the SQL statements are executed in the following order, then re-execute:
- Cursor declaration or cursor assignment
- OPEN statement
- FETCH statement
- CLOSE statement
KFPA11507-E A
aa....aa cursor for SQL except query
- aa....aa: {Declare|Allocate}
- aa....aa is Declare:
- There is a cursor declaration (DECLARE CURSOR) for an SQL statement that is not a query.
- aa....aa is Allocate:
- There is a cursor assignment (ALLOCATE CURSOR) for an SQL statement that is not a query.
- S: Ignores this SQL statement.
- P:
- aa....aa is Declare:
- Revise the UAP to change the SQL statement that declares a cursor into a query, or delete the cursor declaration from the non-query SQL statement, and re-execute.
- aa....aa is Allocate:
- Revise the UAP to change the SQL statement that assigns a cursor into a query, or delete the cursor declaration from the non-query SQL statement, and re-execute.
KFPA11508-E A
Invalid use of "aa....aa" statement
- An attempt was made to execute an SQL statement other than CALL or one row SELECT with an EXECUTE or EXECUTE IMMEDIATE statement that has an INTO clause.
- aa....aa: {EXECUTE | EXECUTE IMMEDIATE}
- S: Ignores this SQL statement.
- P: Revise the usage of the EXECUTE or EXECUTE IMMEDIATE statement, and re-execute. If an SQL statement other than CALL or a one row SELECT statement is executed by the EXECUTE or EXECUTE IMMEDIATE statement, revise it into an EXECUTE or EXECUTE IMMEDIATE statement without INTO, and re-execute.
KFPA11511-E A
Unmatched RDAREA status or generation number between number "aa" of "bbbbb" RDAREA "cc....cc" and number "dd" of table RDAREA "ee....ee"
- The statuses of RDAREA "cc....cc" for storing "bbbbb" and RDAREA "ee....ee" for storing tables do not match. Or, generation aa and generation "dd" do not match.
- aa: Generation number of the RDAREA for user LOB or the RDAREA for index storage
- bbbbb: Storage data type of the RDAREA:
- {INDEX|LOB}
- cc....cc: Name of the original RDAREA for the user LOB or the name of the original RDAREA for storing indexes
- dd: Generation number of the RDAREA for storing tables
- ee....ee: Name of the original RDAREA for storing tables
- S: Ignores the transaction.
- O: Contact the HiRDB administrator.
- Actions
- Perform one of the following actions to solve the problem:
- If the generations of the RDAREA for storing tables and the RDAREA for user LOB, or the RDAREA for storing indexes, do not match during the current access:
Execute the pddbchg command and match up the generation numbers of the RDAREA for user LOB or the RDAREA for storing indexes and the RDAREA for storing tables.
- If the replica RDAREA of the specified generation is not created in the applicable RDAREA:
Execute the pdmod command to create a replica RDAREA.
- If the generation numbers of the RDAREA for storing tables and the RDAREA for user LOB do not match:
The statuses of the RDAREA for displaying tables and the RDAREA for user LOB do not match. Execute the pddbchg command and change the status of the RDAREA for storing tables and the RDAREA for user LOB to the current status or another status.
KFPA11512-E A
Invalid request for executing of SQL except query
- A non-query SQL statement for which preprocessing was executed with the PREPARE statement cannot be executed by the OPEN, FETCH, or CLOSE statement.
- S: Ignores this SQL statement.
- P: Modify the UAP so that the SQL statement is executed with the EXECUTE statement, then re-execute. If the specified cursor is invalid, correct the cursor name and re-execute.
KFPA11513-E A
Unable to execute definition SQL due to aa....aa bb....bb. "cc....cc" using replicated RDAREA dd....dd
- The following definition SQLs cannot be executed because the RDAREA for storing tables or indexes is using the inner replica function:
- ALTER TABLE
- CREATE INDEX
- DROP INDEX
- DROP SCHEMA
- DROP TABLE
- aa....aa: {TABLE|INDEX}
- bb....bb: Authorization identifier
- cc....cc: Table identifier when aa....aa is TABLE, or index identifier when aa....aa is INDEX
- dd....dd: The RDAREA name
- S: Ignores this SQL statement.
- P: Cancel application of the inner replica function and re-execute.
KFPA11514-E A
Unable to execute "SET SESSION AUTHORIZATION" statement, due to aa....aa
- The user cannot be changed for one of the following reasons:
- Transaction has already started.
- A holdable cursor is open.
- A lock is applied using the LOCK statement with the UNTIL DISCONNECT specification.
- This is not executed first in a transaction.
- The statement is inside a stored procedure.
- aa....aa: One of the following:
{ ACTIVE TRANSACTION |HOLDABLE CURSOR
|LOCK WITH UNTIL DISCONNECT
|DISTRIBUTED DATABASE ACCESS |NON-FIRST EXECUTION
|STORED PROCEDURE }
- S: Ignores this SQL statement.
- P: Correct the UAP and re-execute.
KFPA11528-E A
aa....aa bb....bb.cc....cc(dd....dd) not executable due to invalid SQL OBJECT
- The SQL object is invalid; the routine bb....bb.cc....cc could not be executed.
- aa....aa: Routine type
{ Procedure |Function }
- bb....bb: Authorization identifier
- cc....cc: Routine identifier
- dd....dd: Special name
- S: Ignores this SQL statement or invalidates the transaction.
- P: Resolve the cause of the error that makes the SQL object invalid, redefine the procedure, and then retry the operation. The possible causes are:
- Table, index, or definition changes
- A change to the specification of the pd_rpl_func_control operand in the system common definition
- Recovery of the data dictionary LOB RDAREA for object storage
KFPA11529-E A
aa....aa bb....bb.cc....cc invokable for specified arguments not found in system
- The procedure specified in any of the following SQL statements was not found in the HiRDB system, or a callable routine did not exist:
- DROP PROCEDURE
- DROP FUNCTION
- ALTER PROCEDURE
- CALL statement
- Function invocation (user-defined function, system-defined function)
- The CALL statement or function invocations cannot call encapsulated routines.
A routine cannot be called if the number of arguments in the CALL statement and the function invocation does not match the number of parameters in the routine. A function cannot be called that has as a corresponding parameter a data type that is higher in priority than the data type of the argument.
For rules about determining the function to be called, see the manual HiRDB Version 9 SQL Reference.
For a CALL statement, a routine cannot be called if the data types of the arguments of the statement are incompatible with the data types of the parameters of the routine. Even if the argument and parameter are character string data types, the data types are incompatible if the character sets are different. - aa....aa: Routine type
{ Procedure |Function }
- bb....bb: Authorization identifier
- cc....cc: Routine identifier
- S: Ignores this SQL statement or invalidates the transaction.
- P:
- Execution of a CALL statement or a function invocation (user-defined function):
- Check that there are no errors in any of the specifications listed as follows:
- Authorization identifier
- Routine identifier
- Number of arguments
- Data types of arguments (including the character sets in the case of the character string data type)
- If there are no errors, redefine the procedure by using CREATE PROCEDURE or CREATE FUNCTION, as appropriate, and then re-execute.
- If there is an encapsulation level error in part of the routine definition, use CREATE TYPE to redefine the routine, and then re-execute.
- Function invocation (system-defined function):
- Check that the following specifications are correct:
- Authorization identifier
- Routine identifier
- Argument count
- Data types of arguments (including the character sets in the case of the character string data type)
- During execution of DROP PROCEDURE:
- Check that there are no errors in the specified authorization identifier or the routine identifier.
- During execution of ALTER PROCEDURE:
- Check that there are no errors in the specified authorization identifier or the routine identifier. If there are no errors, use CREATE PROCEDURE to redefine the procedure.
- During execution of DROP FUNCTION:
- Check that there are no errors in the specified values listed below. If there are no errors, no action is required.
- Authorization identifier
- Routine identifier
- Number of arguments
- Data types of arguments (including the character sets in the case of the character string data type)
KFPA11530-E A
SQL OBJECT not executable aa....aa, size=bb....bb
- The specified SQL object cannot be executed because the transfer size of that SQL object exceeds 1 MB.
- aa....aa: Reason the SQL object cannot be executed:
- TRANSFER MAX SIZE: Transfer size of SQL object exceeds the maximum.
- bb....bb: Transfer size that exceeds 1 MB
- S: Invalidates the transaction.
- P: Correct the SQL so that the SQL object transfer size is within 1 MB and re-execute.
KFPA11531-E A
SQL OBJECT CACHE currently full, server=aa....aa, info=bb....bb
- The buffer for the SQL object is full; the SQL object cannot be executed.
- aa....aa: Name of the server that has a buffer space shortage
- bb....bb: Information about shortage resources
{ Numeric value, "SQL OBJECT MANAGEMENT", "ACTIVE LIST" }
- S: Does not execute the SQL object, or invalidates the transaction.
- P: Notify the HiRDB administrator to increase the value of pd_sql_object_cache_size. Or, based on shortage resources information, take the following actions:
- If resources information is a numeric value:
- Revise the SQL so that the SQL object length is less than the SQL object buffer size. (When calling a procedure or a function, re-create the procedure or the function to reduce its SQL object length.)
- If resources information is "SQL OBJECT MANAGEMENT":
- Reduce the number of UAPs that are concurrently executed. Alternatively, reduce the number of SQL statements, procedures, or functions that are executed per transaction.
- If resources information is ACTIVE LIST:
- Reduce the number of SQL statements, procedures, or functions that are executed per transaction. Or, increase the value of pd_max_access_tables.
- Action
- Estimate the required size for the SQL object buffer, and then increase the pd_sql_object_cache_size value for the affected server or system.
KFPA11537-E A
Unable to execute specified ROUTINE due to invalid SQL OBJECT
- The specified routine does not contain the information necessary for delayed batch creation of a plug-in index. Therefore, the delayed batch creation of the plug-in index cannot be performed.
- S: Invalidates the transaction.
- P: If the delayed batch creation of a plug-in index is not required, specify PDPLGIXMK=NO in the client environment definition.
- Action
- If the delayed batch creation of a plug-in index is required, execute either ALTER ROUTINE or ALTER PROCEDURE on all routines that update the plug-in index.
KFPA11546-E A
Unable to assign LIST due to executing "pdmod"
- List creation or retrieval cannot be executed because the RDAREA storing the base table from which the list to be created is being initialized by the database structure modification utility.
- S: Ignores this SQL statement.
- O: Re-execute after the processing by the database structure modification utility has finished.
KFPA11547-E A
Unable to define view from "SQL_USERS"
- A viewed table cannot be defined using the SQL_USERS table of the dictionary table as a base.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11548-E A
Unable to execute aa....aa:no bb....bb privilege for cc....cc dd....dd.ee....ee
- One of the following errors has occurred:
- There is no dd....dd privilege for cc....cc dd....dd.ee....ee; SQL statement aa....aa could not be executed.
- If the optimizing information collection utility (pdgetcst) is being used, the user does not have SELECT privilege for the table to be processed.
- aa....aa: SQL statement to be executed
- {SELECT|INSERT|UPDATE|DELETE|ASSIGN|DROP LIST|PREPARE/EXECUTE|PURGE TABLE|LOCK TABLE|CREATE VIEW}
- bb....bb: Required access privilege
- {SELECT|INSERT|UPDATE|DELETE|USAGE}
- If the user attempted to execute LOCK TABLE with EXCLUSIVE specified and does not have DELETE, INSERT, or UPDATE privilege, UPDATE is displayed for bb....bb.
- cc....cc: TABLE, or SEQUENCE
- dd....dd: Authorization identifier
- ee....ee:
- When cc....cc is TABLE: Table identifier
- When cc....cc is SEQUENCE: Sequence generator identifier
- S: Ignores this SQL statement.
- P: Acquire the required access privilege and re-execute.
- O: If the optimizing information collection utility (pdgetcst) is being executed, make sure the user has the SELECT privilege for the table that is to be processed.
KFPA11549-E A
Invalid authorization identifier aa....aa
- PUBLIC, MASTER, HiRDB, or ALL is specified as the authorization identifier. The following are examples of incorrect use of the authorization identifier:
- An attempt was made to connect to the HiRDB server by specifying one of these character strings as the authorization identifier.
- An attempt was made to create (or delete) a base table or viewed table identified by an authorization identifier consisting of one of these character strings.
- An attempt was made to delete a table identified by an authorization identifier consisting of one of these character strings.
- An attempt was made to update a table identified by an authorization identifier consisting of one of these character strings.
- An attempt was made to create (or delete) a procedure of a function identified by an authorization identifier consisting of one of these character strings.
- An attempt was made to re-create a procedure of a function identified by an authorization identifier consisting of one of these character strings.
- An attempt was made to create (or delete) a data type or index type identified by an authorization identifier consisting of one of these character strings.
- An attempt was made to update a data type or index type identified by an authorization identifier consisting of one of these character strings.
- An attempt was made to search a table whose authorization identifier is HiRDB.
- One of these character strings was specified as the user's authorization identifier to define a privilege (GRANT) or revoke a privilege (REVOKE).
- aa....aa: PUBLIC, MASTER, HiRDB, or ALL
- S: Ignores this SQL statement.
- P: Correct the authorization identifier and re-execute.
KFPA11550-E A
Unable to access MASTER.aa....aa without DBA or Auditor privilege
- Only users with DBA privileges or auditor privileges can access dictionary table aa....aa.
- aa....aa: Table identifier of the dictionary table to be accessed
- S: Ignores this SQL statement.
- P: Check the table identifier of the dictionary to be accessed for an error. If there is an error, correct the error and re-execute. If there is no error, contact the HiRDB administrator and request DBA privileges or auditor privileges as necessary.
KFPA11551-E A
Unable to execute aa....aa due to lack of privilege for table bb....bb."cc....cc"
- The SQL statement indicated by aa....aa cannot be executed because the executor is not the table owner.
Or, a privilege that has not been granted to the executor cannot be granted to other users. - aa....aa: SQL statement that cannot be executed:
- grant table access privilege: Grant access privilege for a table.
- revoke table access privilege: Revoke access privilege for a table.
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Ignores this SQL statement.
- Action
- In the case of a GRANT or REVOKE statement, execute this SQL statement for a table the user owns. In addition, correct the SQL statement so that only the SELECT privilege is added to the read-only viewed table.
KFPA11552-E A
Unable to execute "aa....aa" due to lack of privilege
- SQL statement aa....aa cannot be executed, because the user does not have the DBA privilege.
Or, the SQL statement displayed in "aa....aa" cannot be executed because the password of the DBA privilege holder is not registered in HiRDB. - aa....aa: SQL statement that cannot be executed:
- GRANT DBA
- GRANT CONNECT
- GRANT RDAREA
- GRANT SCHEMA
- REVOKE DBA
- REVOKE CONNECT
- REVOKE RDAREA
- REVOKE SCHEMA
- S: Ignores this SQL statement.
- P:
- To execute this SQL statement, acquire the DBA privilege and re-execute.
- Or, register the password of the DBA privilege holder in HiRDB and then execute this SQL statement.
KFPA11553-E A
Unable to execute function IS_USER_CONTAINED_IN_HDS_GROUP
- The IS_USER_CONTAINED_IN_HDS_GROUP scalar function cannot be executed. Following are possible explanations for this error:
- When specifying columns in a value expression, columns other than dictionary table columns cannot be specified.
- Multiple table columns were specified in the value expression. When performing an OR operation for the predicate in which this scalar function is specified, you cannot specify multiple table columns in the OR operation. Here, an AND operation negated by NOT is also considered to be an OR operation.
- This scalar function cannot be specified in a search that uses a list.
- This scalar function cannot be specified in a selection expression or HAVING clause.
- When specifying this scalar function as the ON search condition for a joined table with an outer join, columns of the outer table cannot be specified in the value expression.
- When a joined table with an outer join is specified in a FROM clause and this scalar function is specified in a WHERE clause, columns of the inner table with an outer join cannot be specified.
- The following cannot be specified when no dictionary table column is specified in the value expression:
- Multiple tables in the FROM clause
- ORDER BY
- DISTINCT
- GROUP BY
- Set function
- FOR UPDATE
- FOR READ ONLY
- More than one dictionary table was specified in the FROM clause.
- S: Ignores this SQL statement.
- P: Determine the reason for the error; if applicable, correct the SQL statement and re-execute.
KFPA11554-E A
Unable to grant privilege to yourself
- The user cannot grant a privilege to himself/herself.
- S: Ignores this SQL statement.
- Action
- Change the user's authorization identifier specified in the TO clause and re-execute.
KFPA11555-E A
Unable to revoke privilege from yourself
- The user cannot revoke his/her own privilege.
- S: Ignores this SQL statement.
- Action
- Change the user's authorization identifier specified in the FROM clause and re-execute.
KFPA11556-E A
Unable to execute aa....aa table access privilege bb....bb table owner
- The list of authorization identifiers specified in the GRANT statement (privilege definition) or REVOKE statement (privilege revocation) contains the table owner's authorization identifier.
- aa....aa: Erroneous SQL statement:
{ GRANT |REVOKE }
- bb....bb: Erroneous specification in SQL statement:
{ TO |FROM }
- S: Ignores this SQL statement.
- Action
- A table owner cannot grant a privilege to himself/herself or revoke his/her own privilege. Therefore, delete the table owner's authorization identifier from the TO or FROM clause and re-execute.
KFPA11558-E A
pdvrup command not executed
- An attempt was made to upgrade the HiRDB version, but a UAP or utility could not be executed because the pdvrup command had not been executed.
- S: Causes an error for this SQL statement.
- O: Execute the pdvrup command.
KFPA11559-E A
Unable to grant privilege to unauthorized user aa....aa
- The schema definition privilege cannot be granted to a user who does not have the CONNECT privilege.
- aa....aa:
- Authorization identifier of the user who does not have the CONNECT privilege
- S: Ignores this SQL statement.
- Action
- Check if the specified authorization identifier aa....aa is correct. If it is not correct, correct it and re-execute the SQL statement.
- If the authorization identifier is correct, grant CONNECT privileges to authorization identifier aa....aa and re-execute.
KFPA11560-E A
Invalid password for authorization identifier aa....aa
- The specified password is not the correct password for authorization identifier aa....aa.
When using the Directory Server linkage facility, the specified password either differs from the password registered in the Directory Server, or the password has expired. If this message is output when accessing the table, either the password attribute in the user information on the Directory Server has been modified since the user previously connected to HiRDB, or the password has expired. - aa....aa: Authorization identifier for which an invalid password was specified
- S: Ignores this SQL statement.
- However, if a utility is being executed, processing is terminated.
- P:
- When this message is output during an attempt to connect to HiRDB, specify the correct password and re-execute.
- In the Windows edition of HiRDB
- When executing a utility with -u authorization-identifier specified, note the following point:
- To enter a password as a response, there is no need to enclose the character string in backslashes (\). Enclosing it in backslashes is correct for the command line entry, but it is not necessary in the response format.
KFPA11561-E A
Specified authorization identifier aa....aa has no connect privilege
- Specified authorization identifier aa....aa does not have the CONNECT privilege.
- aa....aa: Authorization identifier without the CONNECT privilege
- S: Ignores this SQL statement; however, if a utility is being executed, processing is terminated.
- Action
- Ask a user who has the DBA privilege to grant you the CONNECT privilege, and re-execute.
- Also, when a utility in which -u authorization-identifier is specified is executed, also check the following:
- If -u was omitted, as well as the PDUSER environment variable, the user ID entered at the time of logging in is assumed as the authorization identifier. Check this user ID for any error.
- When an authorization identifier or password is entered in lower case letters to specify a utility or command option, it must be enclosed in double quotes. In this case, to ensure that the shell or other interpreter does not remove the quotes before passing the specified value to the utility, attach \ or '.
- Examples
- pddbst -u \"hitachi\" -p \"hitachi\"
- pddbst -u '"hitachi"' -p '"hitachi"
KFPA11562-E A
Unable to bb....bb connect privilege due to aa....aa
- The CONNECT privilege cannot be revoked due to aa....aa.
- aa....aa:
- DBA privilege: DBA privilege
- schema: Schema
- bb....bb: revoke
- S: Ignores this SQL statement.
- Action
- Delete the DBA privilege or schema privilege and re-execute.
KFPA11563-E A
Unable to execute SQL before CONNECT
- An SQL statement was executed before executing the CONNECT statement.
- S: Terminates processing.
- P: Check the program for an error in the SQL statement issuance order, correct the error, then re-execute.
- If there is no error in the order in which SQL statements are issued, it is possible that the HiRDB server was disconnected during the execution of the SQL statement before the message was output. Determine whether an error message was returned during the execution of the SQL statement before the message was output.
KFPA11564-E A
Invalid authorization identifier aa....aa
- Authorization identifier aa....aa contains a syntax error. Or, the length of the authorization identifier exceeds 8 characters.
If the specified authorization identifier contains a non-display character, aa....aa may not be displayed correctly. - aa....aa: Authorization identifier containing a syntactical error or authorization identifier that is longer than 8 characters
- S: Ignores this SQL statement.
- P:
- Correct the authorization identifier and re-execute.
- In the Windows edition of HiRDB
- When executing a utility with a -u authorization-identifier specified, note the following point:
- If -u was omitted as well as the PDUSER environment variable at the utility prompt, the user ID entered at the time of logging into Windows is assumed as the authorization identifier. Check this user ID for any error.
KFPA11565-E A
aa....aa bbbb call parameter cc....cc
- When cc....cc is SQLIASDA or sqliasda:
- When bbbb is OPEN or OPNR: In the OPEN statement of the query containing the input ? parameter, the embedded variable or SQL descriptor area that sets the input ? parameter was not specified.
- When bbbb is AUX or AUXO: In the EXECUTE statement of the SQL containing the input ? parameter, the embedded variable or SQL descriptor area that sets the input ? parameter was not specified.
- When bbbb is AUXI: In the EXECUTE IMMEDIATE statement of the SQL containing the input ? parameter, the embedded variable or SQL descriptor area that sets the input ? parameter was not specified.
- When bbbb is OPN2, AUI2, AUI3 or CALL: ? parameters rather than embedded variables were specified in SQL that is not pre-processed in a PREPARE statement or EXECUTE IMMEDIATE statement.
- When cc....cc is SQLIASDA2:
- When bbbb is AUX or AUXI: In the EXECUTE statement or EXECUTE IMMEDIATE statement of the SQL containing the input ? parameter, the embedded variable or SQL descriptor area for receiving the output ? parameter was not specified.
- When bbbb is CALL: ? parameters rather than embedded variables were specified in SQL that is not pre-processed in a PREPARE statement or EXECUTE IMMEDIATE statement.
- aa....aa: Invalid
- bbbb: Operation code (4 characters):
- cc....cc: SQLIASDA, sqliasda, or SQLIASDA2
- S: Ignores this request.
- P: Perform the following action, and then re-execute the UAP:
- When cc....cc is SQLIASDA or sqliasda:
Take one of the following actions depending on the value of the operation code (bbbb):
Operation code (bbbb) | Action |
---|
OPEN, OPNR, AUX, AUXI, or AUXO | Specify the embedded variable or SQL descriptor area name that sets the input ? parameter in the OPEN statement, EXECUTE statement or EXECUTE IMMEDIATE statement. |
OPN2, AUI2, AUI3, or CALL | Specify an embedded variable rather than a ? parameter. |
Other than the above | Contact the customer support center. |
- When cc....cc is SQLIASDA2:
Take one of the following actions depending on the value of the operation code (bbbb):
Operation code (bbbb) | Action |
---|
AUX or AUXI | Specify the embedded variable or SQL descriptor area name for receiving the output ? parameter or search results. |
CALL | Specify an embedded variable rather than a ? parameter. |
Other than the above | Contact the customer support center. |
KFPA11569-E A
Directory server error occurred on aa....aa, func=bb....bb errno=cc....cc, dd....dd
- During aa....aa processing, an error was returned from the HiRDB LDAP Option API used by the Directory Server linkage facility.
- aa....aa: Name of process in which the error occurred
- bb....bb: API name when the error occurred
- cc....cc: Detailed error code
- 10: User is not registered.
- 11: Duplicate user names are registered on the Sun Java System Directory Server.
- 20: The role name is not registered.
- 21: Duplicate role names are registered on the Sun Java System Directory Server.
- 30: The specified user does not belong to the specified role.
- 40: There is no HiRDB LDAP Option environment definition file.
- 41: There are no access privileges to the HiRDB LDAP Option environment definition file.
- 42: Failed to open or close the HiRDB LDAP Option environment definition file (for details, see message KFPD00027-E).
- 43: Error occurred when reading the HiRDB LDAP Option environment definition file (for details, see message KFPD00027-E).
- 44: Operand required in the HiRDB LDAP Option environment definition was not specified.
- 50: There is no Runtime library in the specified path.
- 51: An error occurred when loading the Runtime library (for details, see message KFPD00027-E).
- 60: Insufficient memory.
- 90: The value (maximum wait time) of the NETWORKTIMELIMIT operand of the HiRDB LDAP Option environment definition was exceeded.
- 92: An unexpected error occurred.
- 99: Other error (for details, see message KFPD00027-E).
- dd....dd: Role name
- When bb....bb is p_f_dic_ismatchrulebyid, the role name for where the error occurred is output.
roleid=role-name
- Blank in all other cases.
- S: Ignores this SQL statement.
- P: Take the following action according to the detailed error code. Also, see message KFPD00027-E.
- Action
- When the API name is ldp_xxxxxx, see the Sun Java System Directory Server documents, and take the action appropriate for the detailed error code.
- For detailed error code 42, 43, 51, 60 or 99, follow the instructions in message KFPD00027-E.
- Contact the customer support center when the detailed error code is 92.
KFPA11570-E A
More than 1600 authorization identifiers in "aa....aa" statement
- More than 1600 authorization identifiers were specified in the GRANT statement (privilege definition) or REVOKE statement (privilege revocation) (maximum of 1600 authorization identifiers can be specified).
- aa....aa: Invalid SQL statement:
{ GRANT |REVOKE }
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11571-E A
Password not specified for aa....aa
- No password was specified for the authorization identifier to which DBA privilege is to be granted. Or, an attempt was made without specifying the correct password to change the password for the authorization identifier to which DBA privilege has been granted.
- aa....aa: Authorization identifier for which no password was specified or that is to be changed
- S: Ignores this SQL statement.
- P: Specify the password and re-execute.
KFPA11572-E A
Duplicate access privilege "aaaaaa" in "bb....bb" statement
- A duplicate access privilege was specified in the GRANT or REVOKE statement.
- aaaaaa: Duplicate access privilege:
{ SELECT |UPDATE |INSERT |DELETE }
- bb....bb: SQL statement to be executed:
{ GRANT |REVOKE }
- S: Ignores this SQL statement.
- P: Delete the duplicate access privilege and re-execute.
KFPA11573-E A
Privilege error
- For the reasons given below, none of the following actions can be performed on another user: creating a schema, deleting a schema, re-creating a procedure, or re-creating a trigger SQL object.
- The executing user does not have the DBA privilege.
- The user who is to create a schema does not have the DBA or CONNECT privilege.
- The password of the DBA privilege holder is not registered in HiRDB.
- S: Ignores this SQL statement.
- Action
- Take one of the following actions:
- Have a user with DBA privilege grant the DBA privilege, and re-execute the SQL statement.
- Grant the DBA or CONNECT privilege to the user who will create a schema, and re-execute the SQL statement.
- Register the password of the DBA privilege holder in HiRDB.
KFPA11574-E A
Duplicate RDAREA "aa....aa"
- One of the following errors was detected:
- The same RDAREA name is specified more than once in the primary key definition, cluster key definition, table storage RDAREA, LOB column storage RDAREA, or LOB attribute storage RDAREA in CREATE TABLE or ALTER TABLE.
- The same RDAREA name is specified more than once in CREATE INDEX.
- An attempt was made with ALTER TABLE to add the RDAREA in which this table is already stored.
- aa....aa: Duplicate RDAREA name
- S: Ignores this statement.
- P: Delete or correct the duplicate RDAREA name and re-execute. Or, for ALTER TABLE, specify another RDAREA name and re-execute.
KFPA11576-E A
Unable to revoke RDAREA use privilege for "aa....aa" due to bb....bb cc....cc."dd....dd"
- The RDAREA usage privilege cannot be revoked, because the specified RDAREA contains a table, index, or sequence generator.
- aa....aa: RDAREA name
- bb....bb:
- cc....cc: Authorization identifier of the table, index, or sequence generator in the RDAREA
- dd....dd: Table identifier, index identifier, or sequence generator identifier in the RDAREA
- S: Ignores this SQL statement.
- P: Delete the table, index, or sequence generator in the RDAREA, and then retry the operation.
KFPA11577-E A
Unable to revoke schema privilege due to table/routine/sequence existence
- The schema definition privilege cannot be revoked because a table, routine, or sequence generator exists in the schema.
- S: Ignores this SQL statement.
- P: Delete the table, routine, sequence generator, or schema, and then retry the operation.
KFPA11578-E A
Unable to have two attributes(public,private) for RDAREA "aa....aa"
- An attempt was made with GRANT RDAREA to change an RDAREA to be both a public and a private user RDAREA.
- aa....aa: Name of the RDAREA resulting in the error
- S: Ignores this SQL statement.
- Action
- To change a public user RDAREA to a private user RDAREA, execute REVOKE RDAREA RDAREA-name FROM PUBLIC and re-execute.
- To change a private user RDAREA to a public user RDAREA, execute REVOKE RDAREA RDAREA-name FROM authorization-identifier and re-execute.
KFPA11579-E A
Unable to create aa....aa without schema privilege
- The schema cannot be defined because the user does not have schema definition privileges.
- aa....aa: Invalid SQL statement ( schema )
- S: Ignores this SQL statement.
- P: Ask a user with the DBA privilege to grant the schema definition privilege to this user, then re-execute.
KFPA11580-E A
Unable to drop aa....aa."bb....bb"
- The routine aa....aa."bb....bb" defined in the create type statement, cannot be deleted by itself.
- aa....aa: Authorization identifier
- bb....bb: Routine identifier
- S: Ignores this SQL statement.
- P: If there is an error in the specification of the routine, correct the specification and re-execute. Or, execute the SQL that deletes the abstract data type definition that includes the specified routine.
KFPA11583-E A
Specified ROUTINE aa....aa."bb....bb" not available for index
- A plug-in index cannot be applied to the routine aa....aa."bb....bb". Functions to which a plug-in index can be applied are those that are installed in a plug-in for which SCAN TYPE is specified in the operation qualifier for the plug-in IDL.
- aa....aa: Authorization identifier
- bb....bb: Routine identifier
- S: Ignores this SQL statement.
- P: Correct the specification of the applied function (FOR clause), and re-execute the index definition statement.
KFPA11584-E A
aa....aa "bb....bb" not available for index
- The aa....aa "bb....bb" specified as an object of indexing does not match the index type.
- aa....aa: Type of the target item
{ COLUMN }
- bb....bb: Column or attribute name
- S: Ignores this SQL statement.
- P: Either change the target column specification or the specification for the index type to be used. Revise the SQL statement so that the target column and the index type are correctly associated, and then re-execute.
KFPA11585-E A
More than 16 RDAREAs in "aa....aa" RDAREA statement
- More than 16 RDAREA names were specified in the GRANT RDAREA or REVOKE RDAREA statement (a maximum of 16 RDAREA names can be specified).
- aa....aa: Invalid SQL statement:
{ GRANT |REVOKE }
- S: Ignores this SQL statement.
- Action
- Correct the SQL statement and re-execute.
KFPA11590-E A
Number of specified authorization identifiers not equal to number of password in "GRANT" statement
- The number of authorization identifiers specified in the GRANT statement does not match the number of passwords.
- S: Ignores this SQL statement.
- Action
- Correct the SQL statement and re-execute.
KFPA11591-E A
Unable to specify "NULL" for "FIX" table
- NULL cannot be specified in the column definition for a table for which FIX is specified.
- S: Ignores this SQL statement.
- Action
- Either delete the FIX specification or delete the NULL specification from the column definition, then re-execute.
KFPA11592-E A
Unable to specify "NULL" for cluster key column or primary key column
- NULL cannot be specified in the column definition for a column for which the single-column or multicolumn uniqueness constraint is specified.
- S: Ignores this SQL statement.
- Action
- Delete the column for which NULL was specified from the single-column or multicolumn uniqueness constraint definition or delete the NULL specification from the column definition, then re-execute.
KFPA11595-E A
Duplicate parameter name "aa....aa"
- Duplicate parameter names are specified in CREATE PROCEDURE, CREATE FUNCTION, or CREATE TYPE.
- aa....aa: Duplicated parameter name
- S: Invalidates this transaction.
- P: Change the parameter name and re-execute.
KFPA11596-E A
No RDAREA for routine definition
- A data dictionary LOB RDAREA is not defined; therefore, the following SQL statements cannot be executed:
- ALTER PROCEDURE
- ALTER ROUTINE
- ALTER TRIGGER
- CALL statement
- CREATE FUNCTION
- CREATE PROCEDURE
- CREATE TRIGGER
- CREATE TYPE
- DROP FUNCTION
- DROP PROCEDURE
- Function invocation
- S: Ignores this SQL statement.
- P: Allocate a data dictionary LOB RDAREA with the database initialization utility (pdinit) or the database structure modification utility (pdmod) and re-execute the SQL.
KFPA11597-E A
Unable to alter table for "aa....aa" column
- In ALTER TABLE, columns for which data type aa....aa is specified cannot be deleted.
- aa....aa:
- BLOB
- abstract data (abstract data type)
- S: Ignores this SQL statement.
- P: To modify the definition of the table, delete the table with DROP TABLE, then create a new table with CREATE TABLE.
KFPA11599-E A
Specified RDAREA not for "LOB"
- The specified RDAREA is not user LOB RDAREA.
- S: Ignores this SQL statement.
- P: Specify a user LOB RDAREA and re-execute.
KFPA11600-E A
Routine aa....aa."bb....bb" already specified for another index
- Another plug-in index is already applied to the routine aa....aa."bb....bb".
- aa....aa: Authorization identifier
- bb....bb: Routine identifier
- S: Ignores this SQL statement.
- P: Either change the specification for the applied function or specify the target function, delete the defined index, and then re-execute.
KFPA11601-E A
Duplicate aa....aa bb....bb."cc....cc"
- One of the following errors occurred:
- When bb....bb is something other than ********:
- The table identifier, index identifier, routine identifier, trigger identifier, constraint name, data type identifier, or sequence generator specified in one of the following SQL statements is already defined:
- ALTER TABLE
- ALTER INDEX
- CREATE FUNCTION
- CREATE INDEX
- CREATE PROCEDURE
- CREATE PUBLIC FUNCTION
- CREATE PUBLIC PROCEDURE
- CREATE PUBLIC VIEW
- CREATE SEQUENCE
- CREATE TABLE
- CREATE TRIGGER
- CREATE TYPE
- CREATE VIEW
- When bb....bb is ********:
- The same routine identifier as the routine identifier specified in one of the following SQL statements is already defined by a public procedure:
- CREATE PROCEDURE
- CREATE TYPE
- The same routine identifier as the routine identifier specified in the following SQL statement is already defined by a procedure:
- aa....aa: SQL statement that was executed
- {constraint|datatype|index|routine|sequence|table|trigger}
- bb....bb: Authorization identifier, or ********
- cc....cc: Table identifier, index identifier, routine identifier, trigger identifier, constraint name, data type identifier, or sequence generator identifier
- S: Ignores this SQL statement.
- P: Change the table identifier, index identifier, routine identifier, trigger identifier, constraint name, data type identifier, or sequence generator identifier, and then retry the operation.
KFPA11602-E A
Over 30000 columns in table
- The total number of columns for a table exceeded the maximum (30,000).
- S: Ignores this SQL statement.
- P: If there is an error in the specified SQL statement, correct the error and re-execute. Alternatively, redesign the table so that the number of columns does not exceed 30,000.
KFPA11603-E A
Duplicate key value detected in unique index while creating index
- An attempt was made to create an index with UNIQUE specified, but a duplicate column value was found in the table data.
- S: Disables this transaction.
- P: Correct the duplicate column value in the table and re-create the index with UNIQUE specified. Or, delete the UNIQUE specification, if possible, and create the index by the batch method.
KFPA11604-E A
Invalid length, precision or scale in column definition, column= aa....aa "bb....bb" cc....cc
- The data type length, precision, or scaling factor specified in one of the following locations contains an error:
- In a column, SQL parameter, SQL variable, or attribute definition
- In a function specification in DROP FUNCTION
- In the RETURNS clause of CREATE FUNCTION
- In the AS clause in an argument in a function invocation
- The AS clause of a CAST specification
- CURRENT_TIMESTAMP value function
- AS clause for the ? parameter or embedded variable
- In the AS clause in a substructure specification in CREATE INDEX
- In the AS clause in an argument in an XML constructor function
- In the AS clause in an argument in an SQL/XML scalar function
- Details of the errors in the data type length, precision, or scaling factor are as follows:
- If the data type is DECIMAL:
- The condition 1
precision
38, 0
scaling-factor
38 is not met. - The condition precision
scaling-factor is not met.
- If the data type is CHAR, MCHAR:
- The condition 1
data-type-length
30,000 is not met.
- If the data type is CHAR and the character set name is UTF16 in the character set specification:
- The condition 1
data-type-length
30,000 is not met. - The data length is not a multiple of 2.
- If the data type is VARCHAR, MVARCHAR:
- The condition 1
data-type-length
32,000 is not met.
- If the data type is VARCHAR and the character set name is UTF16 in the character set specification:
- The condition 1
data-type-length
32,000 is not met. - The data length is not a multiple of 2.
- If the data type is NCHAR:
- The condition 1
data-type-length
15,000 is not met.
- If the data type is NVARCHAR:
- The condition 1
data-type-length
16,000 is not met.
- If the data type is BLOB:
- The condition 1
data-type-length
2,147,483,647 is not met. - If G is specified as the data length unit, the condition 1
specified length
2 is not met. - If M is specified as the data length unit, the condition 1
specified length
2,048 is not met. - If K is specified as the data length unit, the condition 1
specified length
2,097,152 is not met.
- If the data type is BINARY:
- The condition 1
data-type-length
2,147,483,647 is not met.
- If the data type is TIMESTAMP, or the CURRENT_TIMESTAMP value function is used:
- The number of digits of fractional seconds is not 0, 2, 4, or 6.
- aa....aa: See below.
- bb....bb: See below.
- cc....cc: See below.
- S: Ignores this SQL statement.
- P:
- Correct the length, precision, or scale and re-execute.
- Following is the correspondence between the invalid data type specification locations and items aa....aa, "bb....bb", and cc....cc:
Data type specification location | aa....aa | "bb....bb" | cc....cc |
---|
Column definition | definition of column | Column name | -- |
SQL parameter declaration | declaration of SQL parameter | SQL parameter name | -- |
SQL variable declaration | declaration of SQL variable | SQL variable name | -- |
Attribute definition | definition of attribute | Attribute name | -- |
In a DROP FUNCTION function specification | function specification | Function name | (nth argument) |
RETURNS clause of the function body | RETURNS clause in function definition | Function name | -- |
AS clause in an argument for the function invocation | function invocation | Function name | (nth argument) |
AS clause of a CAST specification | AS clause in CAST specification | ******** | -- |
CURRENT_TIMESTAMP | CURRENT_TIMESTAMP | ******** | -- |
AS clause specified for the ? parameter or embedded variable | AS clause for ? parameter or embedded variable | ******** | -- |
AS clause in a substructure specification in CREATE INDEX | AS clause in CREATE INDEX statement | ******** | (nth partial structure specification, where n is the substructure specification number) |
AS clause in the argument of an XML constructor function | AS clause in XML constructor | Function name | -- |
AS clause in the argument of an SQL/XML scalar function | AS clause in SQL/XML scalar function | Function name | -- |
- Legend:
- --: Not applicable
KFPA11605-E A
Unable to specify "SUPPRESS" for "FIX" table
- SUPPRESS cannot be specified for a table with the FIX attribute.
- S: Ignores this SQL statement.
- P: Delete the specification of SUPPRESS or the specification of FIX, then re-execute.
KFPA11607-E A
Unable to use definition SQL on other user's aa....aa
- The following processing cannot be executed:
- Creation of a base table, viewed table, or index owned by another user
- Deletion of a base table, viewed table, or index owned by another user
- Modification to the definition of a base table or index owned by another user
- Addition of a comment to a base table or viewed table owned by another user
- Creation or deletion of a procedure owned by another user
- Specification to assign to memory, or release from memory, a base table owned by another user
- Creation or deletion of a function owned by another user
- Creation or deletion of a data type owned by another user
- Creation or deletion of an index type owned by another user
- Modification of a data type owned by another user
- Modification of an index type owned by another user
- Definition or deletion of a trigger owned by another user
- Creation or deletion of a sequence generator owned by another user
- In the Windows edition of HiRDB, this message is also output if the authorization identifier specified in a table in a definition SQL is different from the authorization identifier that was used for connecting. In the case of a utility, such as the database definition utility (pddef), that does not require entry of an authorization identifier for connection, check the PDUSER value of the client environment definition (hirdb.ini). The entire PDUSER value must be enclosed in apostrophes (') in the environment definition (hirdb.ini).
- Example
PDUSER='"root"/"root"'
- aa....aa: {table|index|procedure|trigger|function|datatype|indextype|sequence}
- S: Ignores this SQL statement.
- P: Make sure that the execution user and the owner are the same, and then retry the operation.
KFPA11608-E A
Unable to create table/index/sequence without privilege for specified RDAREA "aa....aa"
- The user does not have RDAREA usage privileges for the specified RDAREA. As a result, the table, index, or sequence generator cannot be created.
- aa....aa: RDAREA name
- S: Ignores this SQL statement.
- P: Either specify the RDAREA for which you have usage privilege, or have the RDAREA usage privilege granted for the RDAREA, and then re-execute.
KFPA11609-E A
Unable to define aa....aa column in "FIX" table
- A column aa....aa cannot be defined for a table with a FIX attribute.
- aa....aa:
- variable length: variable length
- user data type: user-defined data type
- multi-value: repetition column
- S: Ignores this SQL statement.
- P:
- In the case of CREATE TABLE, change the specification for a variable-length column, a user-defined type column, or a repetition column. Or, delete the specification for the FIX attribute, and then re-execute.
- In the case of ALTER TABLE, re-execute the SQL statement without specifying a variable-length column, user-defined column, or repetition column.
KFPA11610-E A
No more available public user RDAREA
- A table or sequence generator cannot be defined, because there is no available public user RDAREA, or there is an available public user RDAREA, but it cannot be used for one of the reasons listed below.
- For a table definition:
- In HiRDB/Parallel Server, an unshared RDAREA is required when defining an unshared table, and a shared RDAREA is required when defining a shared table. In HiRDB/Single Server, an unshared RDAREA is required when defining both unshared tables and shared tables.
- The number of tables defined per RDAREA has reached the maximum (500).
- If a primary key or a cluster key is specified, the number of indexes defined per RDAREA has reached the maximum (500).
- For a table with the FIX attribute, the page length is not sufficient for the specified row length.
- The RDAREA is in shutdown status.
- A table using the rebalancing facility is defined (applicable only for defining unshared tables).
- If a cluster key or primary key is specified, the key length of the index relative to the RDAREA page length has exceeded the maximum length. It is calculated as follows:
key-length
MIN((page-length-of-RDAREA-for-index-storage
2) - 1,242, 4,036)
For details about how to calculate key lengths, see the description of CREATE INDEX in the manual HiRDB Version 9 SQL Reference.
- For a sequence generator definition:
- The total number of tables and sequence generators defined per RDAREA has reached the maximum (500).
- The RDAREA is in shutdown status.
- The RDAREA is using the inner replica facility.
- S: Ignores this SQL statement.
- P: Define a public RDAREA that can be used, and then re-execute. Or, specify a private user RDAREA that can be used, and then re-execute. A usable RDAREA is an RDAREA that does not match the conditions of the previously described unusable RDAREA.
KFPA11611-E A
Unable to aa....aa bb....bb
- Hash function change or RDAREA addition is not possible because the table is not a hash partitioned table.
- aa....aa: Processing to be executed
{ change |add }
- bb....bb: Operation target {HASH|RDAREA}
- S: Ignores this SQL statement.
- P: Delete this SQL statement.
KFPA11612-E A
Duplicate column name "aa....aa"
- A column with the same name cannot be defined more than once for the same table.
- aa....aa: Column name resulting in the error
- S: Ignores this SQL statement.
- P: Correct the SQL statement so that the column name is not duplicated and re-execute.
KFPA11613-E A
Unable to aa....aa for not empty table
- Operation aa....aa cannot be performed on a table containing data.
- aa....aa: Invalid specification:
- add column: Addition of a column that has the NOT NULL constraint or DEFAULT clause specification, or addition of a column in a FIX table
- add rdarea:
- Addition of an RDAREA to a table with FIX hash partitioning that does not use the rebalancing facility
- change no split:
- Change in the no-split option
- change split:
- Change in the no-split option
- change set default:
- Set or change the default
- change drop default:
- Delete the default
- change cluster key:
- Modification of the cluster key attribute
- change hash:
- Modification of the hash function for a table with FIX hash partitioning
- drop column:
- Deletion of a column
- change insert only:
- Change of a non-falsification-prevented table to a falsification-prevented table
- S: Ignores this SQL statement.
- P: Specify a table containing no data and re-execute. Or, with the PURGE TABLE statement, delete all data from the table and re-execute (create a backup copy before executing the PURGE TABLE statement in case an error occurs).
KFPA11614-E A
Unable to bb....bb on column "aa....aa"
- When bb....bb is create index or define foreign key:
- A column with one of the following data types cannot be specified for an index, primary key, cluster key, or foreign key component column:
- BLOB
- User-defined type
- BINARY
- When bb....bb is create partial structure index:
- Only an XML type column can be specified for a column comprising a substructure index.
- aa....aa: Name of the column with the invalid data type
- bb....bb: {create index|define foreign key|create partial structure index}
- S: Ignores this SQL statement.
- P: Delete this SQL statement.
KFPA11615-E A
Unable to create multi column index on column "aa....aa"
- A column with one of the following data types cannot be specified for a multicolumn index, multicolumn primary key, or multicolumn cluster key:
- aa....aa: Name of the column with the invalid data type
- S: Ignores this SQL statement.
- P: Delete this SQL statement.
KFPA11616-E A
Index key length is too long
- The index key exceeds the maximum length. Calculate the key length as follows:
key-length
MIN((page-length-of-RDAREA-for-index-storage
2) - 1242, 4036)
For details about how to calculate key lengths, see the description of CREATE INDEX in the manual HiRDB Version 9 SQL Reference. - S: Ignores this SQL statement.
- P: For a single-column index, delete this SQL statement because it cannot be executed. For a multicolumn index, correct the key length to not exceed maximum and re-execute.
KFPA11617-E A
More than 16 columns specified for index
- The number of CREATE INDEX columns or the number of values comprising the exception key value exceeded the maximum specifiable number of 16.
- S: Ignores this SQL statement.
- P: Correct the number of columns comprising an index or the number of values that comprise exclusion key values to less than or equal to 16 and re-execute.
KFPA11619-E A
Duplicate column name "aa....aa" in constructed index columns
- The column name specified by CREATE INDEX , the column name comprising the primary key, or the column name comprising the cluster key is duplicated.
- aa....aa: Duplicated column name
- S: Ignores this SQL statement.
- P: Correct the SQL statement so that the names of the index component columns are not duplicated, then re-execute.
KFPA11620-E A
Unable to specify "aa....aa" for flexible HASH partitioning table
- UNIQUE or PRIMARY KEY cannot be specified for a table with flexible hash partitioning or a matrix partitioning table using flexible hash partitioning.
- aa....aa:
- UNIQUE: Unique
- PRIMARY KEY: Primary key
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute the job.
KFPA11621-E A
Unable to define unique index for multi-value column "aa....aa"
- An index with a UNIQUE specification cannot be defined on the repetition column "aa....aa".
- aa....aa: Name of the repetition column
- S: Ignores this SQL statement.
- P: Correct the SQL statement or delete the SQL statement and re-execute.
KFPA11622-E A
Invalid HASH function name "aa....aa"
- One of the following errors was found in the hash function specification:
- The specified hash function name could not be found.
- The column length of the hash partitioning key is shorter that the key length of the specified hash function.
Following are the hash functions and the key length of each:
- HASH3: 2 bytes or more
- HASH4: 4 bytes or more
- HASH5: 3 bytes or more
- HASHC: 2 bytes or more
- HASHD: 4 bytes or more
- HASHE: 3 bytes or more
- The hash function of tables not using the rebalancing facility cannot be changed to HASHA, HASHB, HASHC, HASHD, HASHE, or HASHF.
- The hash function for tables using the rebalancing facility cannot be changed to HASH1, HASH2, HASH3, HASH4, HASH5, HASH6, HASH0 or HASHZ.
- HASHA, HASHB, HASHC, HASHD, HASHE, or HASHF cannot be specified in a table hash function defining a cluster key or primary key.
- The SEGMENT REUSE option cannot be specified (the SEGMENT REUSE NO option can be specified) in a table specifying HASHA, HASHB, HASHC, HASHD, HASHE, or HASHF.
- If HASH0 or HASHZ was specified, one of the following errors occurred:
An incorrect data type was specified for the partitioning key. For details about data types that can be specified, see hash-function-name under CREATE TABLE (Define table) in the manual HiRDB Version 9 SQL Reference.
Multiple columns were specified for the partitioning key.
- aa....aa: Hash function name
- Following are the hash function names and their minimum key lengths:
- HASH3: 2 bytes
- HASH4: 4 bytes
- HASH5: 3 bytes
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute the job.
KFPA11625-E A
Unable to define "aa....aa" on multi-value column
- The table restriction definition "aa....aa" cannot be specified for a repetition column.
- aa....aa:
- CLUSTER KEY: cluster key
- PRIMARY KEY: Primary key
- FOREIGN KEY: Foreign key
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11626-E A
Unable to specify "aa....aa" for bb....bb
- aa....aa cannot be specified for bb....bb.
- aa....aa: {FOR RESERVED|INTO}
- bb....bb: {except "FIX" table|INSERT ONLY table}
- S: Ignores this SQL statement.
- P:
- When bb....bb is except "FIX" table:
- Correct the SQL statement so that aa....aa is specified for a FIX attribute table and re-execute.
- When bb....bb is INSERT ONLY table:
- Correct the SQL statement so that a reserved column is added to a table other than a falsification prevented table, and then retry the operation.
KFPA11628-E A
Unable to define aa....aa for multi-value column
- When defining a table or modifying a table definition, aa....aa cannot be specified for a repetition column.
- aa....aa: {"NOT NULL" constraint|character set}
- "NOT NULL" constraint: NOT NULL constraint
- character set: Character set
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11631-E A
Unable to aaaaaa "bb....bb" column
- When "bb....bb" is not abstract data, aaaaaa cannot process "bb....bb".
If "bb....bb" is an abstract data type, the processing aaaaaa cannot be performed on the tables that include "bb....bb". - aaaaaa: Processing that cannot be executed:
{ change |drop }
- bb....bb: Type of column:
- CLUSTER KEY: Column comprising the cluster key
- FOREIGN KEY: Column comprising the foreign key
- PRIMARY KEY: Column comprising the primary key
- PARTITION KEY: Column comprising the partition key
- REFERENCED PRIMARY KEY: Column comprising the primary key of a referenced table
- TRIGGER: Column in the trigger definition that is qualified and referenced by the old or new correlation name values
- CHECK: Check constraint definition
- abstract data: abstract data type
- S: Ignores this SQL statement.
- P: Delete this SQL statement.
KFPA11632-E A
Unable to drop column from aa....aa
- If there is no reserved column in the table, the column cannot be deleted because there is only one column in the table.
If there is a reserved column in the table, the column cannot be deleted because there is only one non-reserved column in the table. - aa....aa: {single column table|single column table except reserved column}
- S: Ignores this SQL statement.
- P: Execute the DROP TABLE statement, not the ALTER TABLE statement.
KFPA11633-E A
Column for divided key must be "NOT NULL"
- The storage condition column, boundary-value partitioning column, or hash partitioning key column does not have the NOT NULL constraint.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11634-E A
More than aaaa partitions or bbbb RDAREA specifications in storage for cc....cc
- The number of partitions for cc....cc storage exceeds aaaa. Or, the specifications of RDAREA names for cc....cc storage exceed bbbb.
- aaaa:
{1024|4096}
- bbbb:
4096
- cc....cc: Storage processing type:
{ TABLE |COLUMN |CLUSTER KEY |PRIMARY KEY |INDEX }
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11636-E A
More than 15000 constants in partitioning condition
- The total number of literals specified for the table storage conditions exceeds 15,000.
- S: Ignores this SQL statement.
- P: Correct the SQL statement so that specification of literals for the storage condition does not exceed 15,000 and re-execute.
KFPA11637-E A
More than 30000 SQL parameters defined in aa....aa definition
- The number of SQL parameters defined in aa....aa is greater than 30,000.
- aa....aa:
{ FUNCTION |PROCEDURE }
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11638-E A
Unable to specify self-join for view or "WITH" query which derives internal table
- In a query specification for creating an internal derived table, joining of the same table is specified.
The conditions for creating an internal derived table are as follows: - In a query for a named derived table, derived by specifying SELECT DISTINCT, the named derived table is included in a subquery or directly includes one of the following:
- GROUP BY clause, HAVING clause, or set function
- SELECT DISTINCT
- Table join (including outer join and inner join)
- Value expression other than a column specification was specified in the selection expression
- None of the columns of the named derived table specified in the FROM clause is specified singularly in the selection expression.
- NEXT VALUE expression
- A query for a named derived table, derived by specifying a GROUP BY clause, HAVING clause, or a set function, directly includes one of the following:
- GROUP BY clause, HAVING clause, or set function
- Table join (including outer join and inner join)
- Window function
- NEXT VALUE expression
- A query for a named derived table, derived by specifying a value expression other than a column specification as the selection expression, directly includes one of the following:
- GROUP BY clause, HAVING clause, or set function
- Window function
- Joined table
- A query for a named derived table, derived by specifying a set function with DISTINCT, directly includes one of the following:
- GROUP BY clause, HAVING clause, or set function
- SELECT DISTINCT
- Window function
- A query for a named derived table, derived by specifying a table join (including both outer joins and inner joins), directly includes a table join (including both outer joins and inner joins) and one of the specified table join operations specifies a table join.
- A query for a named derived table, derived by specifying a scalar subquery in the selection expression, directly includes one of the following:
- SELECT DISTINCT
- GROUP BY clause, HAVING clause, or set function
- Table join (including both outer joins and inner joins)
- A value expression other than a column specification in a selection expression
- A scalar subquery specified in a selection expression
- The same column, derived from a value expression containing a subquery, specified more than once in the selection expression for a named derived table
- A column, derived from a value expression containing a subquery, specified as an external reference column in the selection expression for a named derived table
- A viewed table defined before HiRDB version 07-02
- A query for a named derived table, derived from a set operation, which satisfies one of the following:
- One of the operators of the set operation includes an internal derived table query, a query that specifies a derived table, or a query that specifies a subquery in a selection expression.
- One of the operators of the set operation and the query for the named derived table satisfy one of the conditions of 1 through 6 above
- A query for a named derived table, derived from a set operation that includes other than UNION ALL, which directly includes one of the following:
- GROUP BY clause, HAVING clause, or set function
- SELECT DISTINCT
- Table join (including both outer joins and inner joins)
- WHERE clause
- Subquery
- Value expression, other than a column specification, in a selection expression
- Selection expression in which the columns of a named derived table specified in the FROM clause are not each specified once
- NEXT VALUE expression
- A query for a named derived table derived from a set operation that includes only UNION ALL, which directly includes one of the following:
- GROUP BY clause, HAVING clause, or a set function
- Window function
- WHERE clause or subquery (however, only a subquery, a set operation operator, or an INSERT statement query)
- Function call or system definition scalar function
- Component specification
- WRITE specification
- GET_JAVA_STORED_ROUTINE_SOURCE specification
- Sort specification with items not in the selection expression
- Subquery for a named derived table derived from a set operation specified in the FROM clause
- Subquery that specifies a derived table
- Subquery specified in a value expression other than a column specification in the GROUP BY clause
- The data type of an SQL variable specified in a selection expression or an SQL parameter is one of the following:
BLOB type
BINARY type 32,001 bytes or larger
Abstract data type
BOOLEAN type
- The query specification specified for the table-joining of named derived tables derived by a set operation consisting solely of UNION ALL specifies one of the following:
- A named derived table in a table reference other than at the leftmost outer table for an outer join
- The FROM clause specifying a named derived table, which specifies a comma join (that is, specifies a different table reference than the joined table for which a derived table is specified)
- A subquery or a derived table
- A query specification contained either in a subquery or in the operation term for a set operation
- A set operation term that derives named derived tables and contains one of the following:
Table join
GROUP BY clause, HAVING clause, or a set function
SELECT DISTINCT
A value expression in a selection expression other than a column specification
A query that creates an inner derived table
A query specifying a derived table
- A named derived table derived by specifying a set operation (in addition to a named derived table)
- One of the following, in the table reference to a joined table specifying a named derived table:
A named derived table derived by specifying the joining of tables
A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
A named derived table derived by specifying SELECT DISTINCT
A named derived table derived by specifying a value expression other than a column specification in a selection expression
A named derived table derived by specifying a query that creates an inner derived table
A named derived table derived by specifying a subquery
- The total number of tables obtained by the following expression is greater than 65:
Total number of tables = a + b
c + d
a: Total number of tables from which named derived tables are derived
b: Number of set operations from which named derived tables are derived + 1
c: Total number of tables specified on the right side of an outer join
d: If a query other than a query for which a named derived table is specified is also specified, the total number of tables specified in the query
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11639-E A
Distinct view specified in "FROM" clause of subquery in view definition, in "WITH" query, or in query with grouping by expression
- A derived query in the view definition or the WITH clause or a query specifying a value expression (except for column specifications) in the GROUP BY clause specifies a named derived table that was derived by specifying a duplication elimination in the subquery's FROM clause.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11640-E A
Outer reference specified for column derived from "aa....aa" in view or "WITH" query
- Outer reference was specified for one of the following columns:
- A column in a viewed table defined from COUNT(*) or COUNT_FLOAT(*)
- A column derived from the COUNT(*) or COUNT_FLOAT(*) specified in a selection expression in a derived query expression in the WITH clause
- aa....aa: Set function: {COUNT(*) | COUNT_FLOAT(*)}
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11641-E A
Unable to specify derived table in joined table
- A named derived table derived under the following condition cannot be specified in a joined table:
- A named derived table was derived by specifying a set operation
- Also, a viewed table cannot be specified in a derived query expression joined table if the viewed table or the base table comprising the viewed table is defined as follows:
- With subquery specified
- By specifying the joining of tables, SELECT DISTINCT, a GROUP BY clause, or a HAVING clause
- Viewed table defined by specifying a value expression other than a column specification in the SELECT clause.
- S: Ignores this SQL statement
- P: Correct the SQL statement and re-execute.
KFPA11642-E A
Grouping specified for derived table having derived column in view definition, in "WITH" query, or in query with grouping by expression
- A GROUP BY clause, a HAVING clause, or a set function is specified in a view definition query, in a derived query in the WITH clause query, or in a value expression (except when a column specifies a value expression) in the GROUP BY clause for a named derived table with columns derived by a value expression other than a column specification.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11643-E A
Join specified for group view in view definition, in "WITH" query, or in query with grouping by expression
- A table join is specified in a query specifying a value expression (except when a column specifies a value expression) in a view definition, in a derived query for a query in the WITH clause, or in the GROUP BY clause for a named derived table that was derived by specifying a GROUP BY clause, a HAVING clause, or a set function.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11644-E A
Grouping specified for group view in view definition, in "WITH" query, or in query with grouping by expression
- One of the following specifications was made in a query specifying a value expression (except when a column specifies a value expression) in a view definition, or in a derived query expression in the WITH clause for a named derived table that was derived by a query specifying a GROUP BY clause, a HAVING clause, or a set function:
- GROUP BY clause
- HAVING clause
- Set function
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11645-E A
Constant or value expression in "SELECT" clause specified for distinct view in view definition or "WITH" query
- A value expression other than a column specification was specified in a view definition or the SELECT clause in a derived query expression in a query in the WITH clause for a viewed table specifying a duplication elimination (DISTINCT).
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11646-E A
Join specified for distinct view in view definition or "WITH" query
- A viewed table specifying duplication elimination (DISTINCT) was searched by specifying the joining of tables in either a view definition or a derived query expression in a query in the WITH clause.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11647-E A
Distinct specified for distinct view in view definition, in "WITH" query, or in query with grouping by expression
- A value expression other than a column specification was specified in a view definition, a derived query expression in a query in the WITH clause, or in the GROUP BY clause for a named derived table that was derived by specifying a duplication elimination (DISTINCT).
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11648-E A
Unable to derive internal table in query or in where subquery with grouping by expression
- A query specification for creating an internal derived table cannot be specified in the following:
- A query in which a value expression other than a column specification is specified in a GROUP BY clause
- A subquery of a WHERE clause of a query in which a value expression other than a column specification is specified in a GROUP BY clause
- The conditions for creating an internal derived table are as follows:
- In a query in a named derived table that was derived by specifying SELECT DISTINCT, the named derived table is either included in a subquery or directly includes one of the following:
- GROUP BY clause, HAVING clause, or set function
- SELECT DISTINCT
- Table join (including outer join and inner join)
- Specification of a value expression other than a column specification in the selection expression
- None of the columns of the named derived table specified in the FROM clause is specified singularly in the selection expression.
- A query for a named derived table, derived by specifying a GROUP BY clause, HAVING clause, or a set function, directly includes one of the following:
- GROUP BY clause
- HAVING clause
- Set function
- Table join (including outer join and inner join)
- A query for a named derived table, derived by specifying a value expression other than a column specification as a selection expression, directly includes one of the following:
- GROUP BY clause
- HAVING clause
- Set function
- Joined table
- A query for a named derived table, derived by specifying a set function with DISTINCT specification, directly includes SELECT DISTINCT specification.
- A query for a named derived table, derived by specifying a joined table, directly includes one of the following:
- Table join (including outer join and inner join)
- Subquery
- A query for a named derived table, derived by specifying table join or a subquery, directly includes a joined table specification.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11649-E A
Grouping specified for distinct view in view definition, in "WITH" query, or in query with grouping by expression
- A query specified by a value expression (except when the value expression is a column specification) in a view definition, a derived query expression in a query in the WITH clause, or in the GROUP BY clause, for a named derived table that was derived by specifying a duplication elimination (DISTINCT), directly specifies one of the following:
- GROUP BY clause
- HAVING clause
- Set function
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11650-E A
Number of view columns or "WITH" query columns not equal to number of select columns
- The number of items to be retrieved in the SELECT clause does not match the following value:
- Number of columns comprising the viewed table
- Number of columns in the table specified in the query name of the WITH clause
- S: Ignores this SQL statement.
- P: Check that the number of columns comprising the viewed table or the number of columns in the table derived as the query name matches the number of items subject to retrieval in the SELECT clause, then re-execute.
KFPA11651-E A
Unable to specify aa....aa in view definition
- The following items cannot be specified in a view definition:
- ? parameters or embedded variables
- Structured repetition predicates
- IN (RDAREA-name-specification)
- aa....aa:
{ ? parameter or embedded variable |ARRAY predicate |RDAREA name specification}
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11652-E A
Specified RDAREA "aa....aa" not defined
- The RDAREA specified in one of the following SQL statements was not found:
- ALTER TABLE
- CREATE INDEX
- CREATE SEQUENCE
- CREATE TABLE
- GRANT RDAREA
- aa....aa: RDAREA name
- S: Ignores this SQL statement.
- P: Either specify a defined user RDAREA or correct the RDAREA name and re-execute.
KFPA11653-E A
Specified RDAREA aa....aa bb....bb
- One of the following errors was detected:
- When bb....bb is not for user:
- The user cannot use aa....aa.
- When bb....bb is replicated rdarea:
- aa....aa is a replicated RDAREA.
- When bb....bb is used by inner replica facility:
- The following resources cannot be created in RDAREA aa....aa, which uses the inner replica facility:
- Falsification prevented table
- Sequence generator
- When bb....bb is RDAREA for temporary table:
- aa....aa is a temporary table RDAREA.
- For these reasons, the following SQL statements cannot be executed:
- ALTER TABLE
- CREATE INDEX
- CREATE SEQUENCE
- CREATE TABLE
- GRANT RDAREA
- DROP INDEX
- DROP TABLE
- DROP SCHEMA
- REVOKE RDAREA
- aa....aa: RDAREA-name
- bb....bb: {not for user|replicated rdarea|used by inner replica facility|RDAREA for temporary table}
- S: Ignores this SQL statement.
- P:
- bb....bb is not for user:
- Specify the user RDAREA and re-execute.
- bb....bb is replicated rdarea:
- Specify the original RDAREA and re-execute.
- bb....bb is used by inner replica facility:
- Specify an RDAREA not applying the inner replica facility and re-execute. Alternatively, cancel application of the inner replica facility and re-execute.
- When bb....bb is RDAREA for temporary table:
- Specify a user RDAREA that is not a temporary table RDAREA, and then retry the operation.
KFPA11654-E A
Number of aa....aa exceeds bbb
- When aa....aa is tables and sequences:
- The total number of tables and sequence generators in the RDAREA exceeded the maximum.
- The maximum total number of tables and sequence generators that can be specified in an RDAREA is 500.
- When aa....aa is indexes:
- The number of indexes in the RDAREA exceeded the maximum.
- The maximum number of indexes that can be specified in an RDAREA is 500.
- aa....aa: One of the following is displayed:
- tables and sequences
- indexes
- bbb: 500
- S: Ignores this SQL statement.
- P: Specify another RDAREA and re-execute.
KFPA11656-E A
No schema for aa....aa
- Because a schema is missing, the following SQL statements cannot be executed:
- ALTER PROCEDURE
- ALTER ROUTINE
- CREATE FUNCTION
- CREATE INDEX
- CREATE PROCEDURE
- CREATE SEQUENCE
- CREATE TABLE
- CREATE TRIGGER
- CREATE TYPE
- CREATE VIEW
- DROP SCHEMA
- aa....aa: Authorization identifier of the user without the schema
- S: Ignores this SQL statement.
- P: To execute CREATE TABLE, CREATE INDEX, CREATE PROCEDURE, CREATE TYPE, CREATE FUNCTION, CREATE TRIGGER, CREATE VIEW, or CREATE SEQUENCE, use the CREATE SCHEMA statement to create a schema before executing the desired statement. In the case of DROP SCHEMA, ALTER PROCEDURE, and ALTER ROUTINE, they do not have to be executed because no schema was defined.
KFPA11657-E A
Too small page size aa....aa for row length bb....bb
- The page length of a specified RDAREA is insufficient.
- aa....aa: Page length of the specified RDAREA
- bb....bb: Row length (in bytes)
- For national character data, the specified value times 2 is displayed in the message as the row length.
- S: Ignores this SQL statement.
- P: Either specify an RDAREA satisfying the condition shown below or reduce the row length, then re-execute:
- Condition:
- Note
![[Figure]](figure/zueng011.gif)
means that the value is to be rounded down.
KFPA11658-E A
Unable to specify "ALL" as table identifier
- ALL cannot be used as a table identifier.
- S: Ignores this SQL statement.
- P: Correct the table identifier and re-execute.
KFPA11659-E A
Invalid data type or data length
- The data type or data length specified in the CHANGE clause is invalid for one of the following reasons:
- An attempt was made to reduce the data length.
- An attempt was made to change the length of fixed-length data.
- An attempt was made to change an unchangeable data type.
- An attempt was made to change the data type of a column that has a character set specification.
- A character set was specified for a character string data type after it was changed.
- For a column whose character set is UTF16, an attempt was made to change the data length to a value that is not a multiple of 2.
- S: Ignores this SQL statement.
- P: Correct the error and re-execute.
KFPA11660-E A
Unable to aa....aa on the bb....bb
- One of the following errors was detected in the table manipulation:
- Index creation, trigger creation, or table definition change cannot be performed on a viewed table.
- Table definition change cannot be performed on an audit trail table.
- Index creation or table definition change cannot be performed on a temporary table.
- aa....aa: One of the following items is displayed:
- alter table
- create index
- create trigger
- alter index
- bb....bb: One of the following items is displayed:
- view
- table
- audit trail table
- temporary table
- S: Ignores this SQL statement.
- P: Delete this SQL statement.
KFPA11661-E A
Identical structure index aa....aa."bb....bb" already exists
- Index aa....aa."bb....bb" is already defined in HiRDB.
For a substructure index, substructure index aa....aa."bb....bb", whose key is the same substructure of the same column, is already defined in HiRDB. - aa....aa: Authorization identifier
- bb....bb: Index identifier
- S: Ignores this SQL statement.
- P: Delete this SQL statement.
KFPA11662-E A
Unable to cc....cc because of key length of index aa....aa."bb....bb" too long
- Cannot cc....cc because the key length of index aa....aa."bb....bb" exceeded the maximum specifiable length. Calculate the correct key length in the following formula:
key-length
MIN ((page-length-of-index-storage-RDAREA
2) - 1242, 4037)
For details about how to calculate key lengths, see the description of CREATE INDEX in the manual HiRDB Version 9 SQL Reference. - aa....aa: Authorization identifier
- bb....bb: Index identifier
- cc....cc: {change data length|add rdarea}
- S: Ignores this SQL statement.
- P:
- When cc....cc is change data length:
To prevent the key length of the index key from exceeding the maximum length, either modify ALTER TABLE or delete the index, and then re-execute.
- When cc....cc is add rdarea:
Change the RDAREA storing the index.
KFPA11664-E A
Specified aa....aa bb....bb already exists
- The specified schema has already been defined.
- aa....aa: Schema
- bb....bb: Authorization identifier
- S: Ignores this SQL statement.
- P: Delete this SQL statement.
KFPA11665-E A
No available parameter found for "ALTER TABLE"
- The contents (the maximum number of elements in a repetition column, the data type, the data size, the WITH DEFAULT, or the no-split option specification) specified in the CHANGE clause of ALTER TABLE have not changed from the previous contents.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11667-E A
Invalid maximum number of elements for "ALTER TABLE"
- The maximum number of elements specified in the CHANGE clause of ALTER TABLE contains one of the following errors:
- An attempt was made to reduce the maximum number of elements.
- An attempt was made to change a repetition column into a non-repetition column or a non-repetition column into a repetition column.
- The symbol * was not specified, even when the maximum number of elements was not changed.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11669-E A
Invalid table name in view definition
- The name of a base table for a viewed table or the name of the viewed table is invalid. Or, the name of a base table for a viewed table is the same as the name of the viewed table.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11670-E A
Update specified for aa....aa
- A problem occurred during update processing of a read-only viewed table, falsification-prevented table, or audit trail table, as indicated by aa....aa.
- aa....aa: {read only view|INSERT ONLY table|view table derived from INSERT ONLY table|UPDATE ONLY FROM NULL column|AUDIT TRAIL TABLE}
- read only view:
- An INSERT, UPDATE, or DELETE statement was executed on a read-only viewed table.
- INSERT ONLY table or view table derived from INSERT ONLY table:
- UPDATE was executed on a column for which update is not permitted on a falsification-prevented table or a viewed table using a falsification-prevented table as its base table.
- UPDATE was executed specifying ROW for a falsification-prevented table or a viewed table using a falsification-prevented table as its base table.
- A DELETE statement is being executed on a falsification-prevented duration for which a deletion-prevented duration is not specified, or on a viewed table having a falsification-prevented duration as a base table.
- UPDATE ONLY FROM NULL column:
- UPDATE (element update, add, or delete) was executed with a subscript for a repetition column with the UPDATE ONLY FROM NULL attribute.
- UPDATE was executed using a component specification for an abstract data type column with the UPDATE ONLY FROM NULL attribute.
- AUDIT TRAIL TABLE:
- The INSERT or UPDATE statement was executed for an audit trail table.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11671-E A
As a result of changing data length, invalid use of variable length column occurred in view definition
- The following columns in a view definition cannot be changed to BINARY with a length of 32,001 bytes or larger:
- A column specified in a comparison predicate, quantified predicate, IN predicate, BETWEEN predicate, NULL predicate, LIKE predicate, or SIMILAR predicate
- A column specified in a subquery in a comparison predicate, quantified predicate, or IN predicate
- A base table column specified in duplication elimination
- A column specified in a selection expression in a query that a set operation is to be performed on
- A base table column specified in a grouping or set function
- A column specified to define a viewed table developed as an internal derived table in a query specification that satisfies one of the conditions to create an internal derived table
- The conditions for creating an internal derived table are as follows:
- In a query for a named derived table, derived by specifying SELECT DISTINCT, the named derived table is included in a subquery or directly includes one of the following:
- GROUP BY clause, HAVING clause, or set function
- SELECT DISTINCT
- Table join (including outer join and inner join)
- A value expression other than a column specification specified in the selection expression
- None of the columns of the named derived table specified in the FROM clause is specified singly in the selection expression
- NEXT VALUE expression
- A query for a named derived table, derived by specifying a GROUP BY clause, HAVING clause, or set function, directly includes one of the following:
- GROUP BY clause, HAVING clause, or set function
- Table join (including outer join and inner join)
- Window function
- NEXT VALUE expression
- One of the following is directly included in the query for a named derived table specified by a selection expression that is a value expression other than a column specification:
- GROUP BY clause, HAVING clause, or set function
- Window function
- Joined table
- A query on a named derived table derived by directly specifying a set function with DISTINCT contains one of the following:
- GROUP BY clause, HAVING clause, or set function
- SELECT DISTINCT
- Window function
- A query for a named derived table derived by specifying a table join (including outer join and inner join) directly includes a table join (including outer join and inner join), and one of the specified table joins specifies a joined table.
- A query on a named derived table derived by directly specifying a scalar subquery as a selection expression contains one of the following:
- SELECT DISTINCT
- GROUP BY clause, HAVING clause, or set function
- Table join (including outer join and inner join)
- A value expression other than a column specification specified in a selection expression
- A scalar subquery specified in a selection expression
- The same column derived from a value expression containing a subquery, specified more than once in the selection expression for a named derived table
- A column derived from a value expression containing a subquery, specified as an external reference column in the selection expression for a named derived table
- A viewed table defined before HiRDB version 07-02
- A query for a named derived table derived from a set operation, which satisfies one of the following:
- One of the operators of the set operation includes an internal derived table query, a query that specifies a derived table, or a query that specifies a subquery in a selection expression.
- One of the operators of the set operation and the query for the named derived table satisfy one of the conditions of 1 through 6 above.
- A query for a named derived table derived from a set operation that includes other than UNION ALL, which directly includes one of the following:
- GROUP BY clause, HAVING clause, or a set function
- SELECT DISTINCT
- Table join (including external or internal joins)
- WHERE clause
- Subquery
- Value expression other than a column specification in a selection expression
- In a selection expression, the columns of a named derived table specified in the FROM clause are not specified once each
- NEXT VALUE expression
- A query for a named derived table derived from a set operation that includes only UNION ALL, which directly includes one of the following:
- GROUP BY clause, HAVING clause, or a set function
- Window function
- WHERE clause or subquery (however, only a subquery, a set operation operator, or an INSERT statement query)
- Function call or system definition scalar function
- Component specification
- WRITE specification
- GET_JAVA_STORED_ROUTINE_SOURCE specification
- Sort specification with items not in the selection expression
- Subquery for a named derived table derived from a set operation specified in the FROM clause
- Subquery that specifies a derived table
- Subquery specified in a value expression other than a column specification in the GROUP BY clause
- The data type of an SQL variable specified in a selection expression or an SQL parameter is one of the following:
BLOB type
BINARY type 32,001 bytes or larger
Abstract data type
BOOLEAN type
- The query specification specified for the table-joining of named derived tables derived by a set operation consisting solely of UNION ALL specifies one of the following:
- A named derived table in a table reference other than at the leftmost outer table for an outer join
- The FROM clause specifying a named derived table, which specifies a comma join (that is, specifies a different table reference than the joined table for which a derived table is specified)
- A subquery or a derived table
- A query specification contained either in a subquery or in the operation term for a set operation
- A set operation term that derives named derived tables and contains one of the following:
Table join
GROUP BY clause, HAVING clause, or a set function
SELECT DISTINCT
A value expression in a selection expression other than a column specification
A query that creates an inner derived table
A query specifying a derived table
- A named derived table derived by specifying a set operation (in addition to a named derived table)
- One of the following, in the table reference to a joined table specifying a named derived table:
A named derived table derived by specifying the joining of tables
A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
A named derived table derived by specifying SELECT DISTINCT
A named derived table derived by specifying a value expression other than a column specification in a selection expression
A named derived table derived by specifying a query that creates an inner derived table
A named derived table derived by specifying a subquery
- The total number of tables obtained by the following expression is greater than 65:
Total number of tables = a + b
c + d
a: Total number of tables from which named derived tables are derived
b: Number of set operations from which named derived tables are derived + 1
c: Total number of tables specified on the right side of an outer join
d: If a query other than a query for which a named derived table is specified is also specified, the total number of tables specified in the query
- S: Ignores this SQL statement.
- P: Correct the SQL statement or delete the viewed table, and then re-execute.
KFPA11672-E A
Each column of distinct view can be specified only once in "SELECT" clause in view definition, or in "WITH" query
- One or more columns comprising the viewed table were not specified once each in the view definition or SELECT clause in the derived query expression in the WITH clause for a viewed table defined by specifying duplication elimination (DISTINCT).
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11673-E A
Duplicate "aa....aa" in "bb....bb" statement
- "aa....aa" was specified more than once in "bb....bb".
- aa....aa: Item specified two or more times
- {CLUSTER KEY|PRIMARY KEY|PCTFREE|SUPPRESS
- |LOCK ROW/PAGE|WITHOUT ROLLBACK|UNBALANCED SPLIT
- |EMPTY|EXCEPT VALUES|INDEXLOCK|ISOLATION LEVEL
- |OPTIMIZE LEVEL|ADD OPTIMIZE LEVEL|SUBSTR LENGTH
- |OPTIONS SCHEMA|OPTIONS TABLE
- |OPTIONS COLLATING_SEQUENCE|OPTIONS TRAILING_SPACE
- |OPTIONS NULLABLE|OPTIONS USING_BES|OPTIONS_USER
- |OPTIONS PASSWD|SEGMENT REUSE|INSERT ONLY|NOT NULL
- |CONNECT|PASSWORD|AS DATA TYPE|START WITH
- |INCREMENT BY|MAXVALUE|MINVALUE|CYCLE|LOG INTERVAL
- |FOR RESERVED}
- bb....bb: Specified statement
- {CREATE TABLE|CREATE INDEX|CREATE PROCEDURE
- |CREATE FUNCTION|PROCEDURE definition in CREATE TYPE
- |FUNCTION definition in CREATE TYPE|ALTER TABLE
- |ALTER PROCEDURE|ALTER ROUTINE|CREATE TRIGGER
- |ALTER TRIGGER|CREATE CONNECTION SECURITY
- |DROP CONNECTION SECURITY|CREATE SEQUENCE}
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11674-E A
Unable to specify more than 16 columns for "aa....aa"
- The number of columns in aa....aa exceeds the maximum (16).
- aa....aa: {CLUSTER KEY|HASH KEY|PRIMARY KEY|FOREIGN KEY}
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11676-E A
"aa....aa" cannot be specified in ALTER TABLE statement
- "aa....aa" cannot be specified in the ALTER TABLE statement for a column to be added or modified.
- aa....aa: Nature of error:
{ CLUSTER KEY |NOT NULL }
- Note that the NOT NULL constraint can be specified in the ADD clause.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11677-E A
Unable to purge aa....aa
- The PURGE TABLE statement cannot be executed on a viewed table, falsification prevented table, or memory database allocation table.
- aa....aa: {viewed table|INSERT ONLY table|memory table}
- S: Ignores this SQL statement.
- P: In the case of a viewed table, use the DELETE statement to delete the rows. In the case of a falsification prevented table, use the DELETE statement to delete only the rows that have exceeded the deletion prevented duration. In the case of a memory database allocation table, execute the PURGE TABLE statement after releasing the memory database allocation.
KFPA11678-E A
No Column-definition in "CREATE TABLE" statement
- There is no column definition in the CREATE TABLE statement.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11680-E A
Unable to aa....aa LIST due to executing same user bb....bb
- A user having the same authorization identifier bb....bb is accessing the list; therefore, operation aa....aa cannot be performed on the list.
- aa....aa: List processing:
{ assign |select |drop }
- bb....bb: Authorization identifier
- S: Ignores this SQL statement.
- P: Re-execute the SQL statement after the active transaction has terminated.
KFPA11681-E A
Unable to specify reserved column on aa....aa column
- A reserved column cannot be specified on configuration column aa....aa.
- aa....aa: Type of configuration column
- {cluster key|primary key|foreign key|divided key|index}
- S: Ignores this SQL statement.
- P: Correct the SQL statement so that a reserved column is not specified on aa....aa, and then retry the operation.
KFPA11682-E A
Unable to change definition reserved column "aa....aa"
- The data type of the reserved column cannot be changed.
- aa....aa: Name of reserved column
- S: Ignores this SQL statement.
- P: Correcting the SQL statement so that the data type of the reserved column indicated in aa....aa is not changed, and then retry the operation.
KFPA11683-E A
Unable to specify unsupported data type for reserved column
- An unsupported data type was specified for the reserved column. In a reserved column, you must specify a data type whose default character set is CHAR.
- S: Ignores this SQL statement.
- P: Correct the data type of the reserved column so that the default character set is CHAR, and then retry the operation.
KFPA11684-E A
Unable to add column for table with reserved column
- Unable to add a column to a table with a reserved column.
- S: Ignores this SQL statement.
- P: Add the column by excising it from a reserved column, or delete the reserved column, and then add the column.
KFPA11685-E A
Unable to create table with only reserved column
- You cannot define a table with only reserved columns.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA11690-E A
Unable to drop referenced table
- A referenced table with a referential constraint cannot be dropped.
- S: Ignores this SQL statement.
- P: Drop all referencing tables, and then re-execute.
KFPA11692-E A
Unable to execute due to cc....cc aa....aa."bb....bb" in use
- This SQL statement or operation command cannot be executed because another user is using cc....cc aa....aa."bb....bb".
- aa....aa: Authorization identifier
- bb....bb: Table identifier, or sequence generator identifier
- cc....cc:
- table: Table
- sequence: Sequence generator
- S: Ignores this SQL statement.
- P: Re-execute the SQL statement after the other user has finished using the cc....cc.
- Action
- Check the SQL being executed for an error. If there is no error, execute the SQL statement or operation command after the other user finishes using the cc....cc. The command pdls -d lck -a can be used to determine whether the cc....cc is being used by another user.
KFPA11693-E A
Unable to define same columns construction for primary key and cluster key
- A cluster key clause and a primary key clause with the same column structure cannot be specified simultaneously.
- S: Ignores this SQL statement.
- P: To define a cluster key and a primary key with the same column structure, define them in a PRIMARY CLUSTER KEY clause.
KFPA11694-E A
Unable to change cluster key because of invalid key attribute
- One of the following errors was detected in attempting to change attributes of a cluster key:
- An attempt was made to change to UNIQUE a cluster key for which UNIQUE was already specified, or an attempt was made to change from UNIQUE a cluster key for which UNIQUE was not specified.
- An attempt was made to change a flexible hash partitioning table or a matrix partitioning table using flexible hash partitioning to UNIQUE.
- S: Ignores this SQL statement.
- P: Delete this SQL statement.
KFPA11695-E A
Unable to specify "WITH DEFAULT" for reserved column
- WITH DEFAULT cannot be specified for a reserved column.
- S: Ignores this SQL statement.
- P: If you are defining a table or adding a column, re-execute the SQL statement after correcting it so that it does not specify WITH DEFAULT.
- If you are changing a table definition change, delete this SQL statement.
KFPA11696-E A
Unable to specify "aa....aa" column,reason=bb....bb
- The column indicated in aa....aa cannot be specified due to the reason indicated in bb....bb.
- aa....aa: Column name
- bb....bb: Cause of error
- invalid data length:
- The column cannot be excised because the data length of the column indicated in aa....aa is greater than the data length of the reserved column.
- duplicate column name:
- The same name as the reserved column cannot be specified because the data length of the column indicated in aa....aa is not equal to the data length of the reserved column.
- not reserved column:
- The column cannot be excised because the column indicated in aa....aa is not a reserved column.
- S: Ignores this SQL statement.
- P: Take corrective action as described in the following table:
Cause of error (bb....bb) | Action |
---|
invalid data length | Correct the SQL statement so that the data length of the column indicated in aa....aa does not exceed the data length of the reserved column, and then re-execute it. |
duplicate column name | Correct the SQL statement after changing the column indicated in aa....aa to a name different from the reserved column, and then re-execute it. |
not reserved column | Correct the SQL statement after changing it so that a reserved column is specified, and then re-execute it. |
KFPA11697-E A
Unable to specify "WITH DEFAULT" except for "NOT NULL"
- When defining a table or modifying a table definition, "WITH DEFAULT" cannot be specified for a column without the "NOT NULL" value restriction.
- S: Ignores this SQL statement.
- P: Specify "NOT NULL" and re-execute.
KFPA11698-E A
Unable to specify "bb....bb" for "aa....aa" column
- The item "bb....bb" cannot be specified for a column that comprises "aa....aa".
- aa....aa: abstract data (abstract data type)
- bb....bb: NOT NULL
- S: Ignores this SQL statement.
- P: Delete this SQL statement.
KFPA11699-E A
Unable to specify "WITH DEFAULT" because of column already "WITH DEFAULT"
- WITH DEFAULT has already been specified for the specified column.
- S: Ignores this SQL statement.
- P: Delete this SQL statement.
KFPA11702-E A
Unable to create unique index, because unique key not include all partitioning key columns
- An index with the UNIQUE specification could not be defined for one of the following reasons:
- In a table that is row-partitioned among multiple back-end servers, not all the columns specified as table-partitioning keys are included in the columns comprising the index.
- In a rebalancing table with FIX hash partitioning at a single server or at only one back-end server, not all the columns specified as table-partitioning keys are included in the columns comprising the index.
- S: Ignores this SQL statement.
- P: Correct so that all columns specified as table-partitioning keys are included in the columns comprising the index (in any sequence), and re-execute the SQL statement.
KFPA11703-E A
Unable to partition table more than 4097 servers
- A table cannot be defined to be partitioned into more than 4,097 back-end servers.
- S: Ignores this SQL statement.
- P: Set the number of back-end servers for partitioning to no more than 4,096 and re-execute.
KFPA11704-E A
Unable to specify aa....aa for bb....bb
- aa....aa cannot be specified for bb....bb.
- When bb....bb is "FIX" table:
- Cannot specify a data type BLOB statement or BINARY statement for a FIX attribute table.
- When bb....bb is attribute name:
- A character set cannot be specified for an attribute name in a type definition.
- aa....aa: {"BLOB"|"BINARY"|long data|character set}
- bb....bb: {"FIX" table|attribute name}
- S: Ignores this SQL statement.
- P:
- When bb....bb is "FIX" table:
- Do not specify the BLOB or BINARY data type statement, or delete the FIX attribute specification, and then retry the operation.
- When bb....bb is attribute name:
- Revise the specification of the data type, and then retry the operation.
KFPA11705-E A
Invalid option "aa....aa" number cc....cc in "bb....bb" statement
- The value of option "aa....aa" in statement "bb....bb" exceeds the permitted maximum.
- aa....aa: Name of erroneous option:
{ PCTFREE |SEGMENT REUSE }
- bb....bb: Name of erroneous SQL statement:
{ CREATE TABLE |CREATE INDEX |ALTER TABLE }
- cc....cc: Erroneous value
- S: Ignores this SQL statement.
- P: Change the option specification and re-execute.
KFPA11706-E A
Number of defined indexes on table aa....aa."bb....bb" exceeds 255
- The number of indexes specified for a table exceeded the maximum (255).
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Ignores this SQL statement.
- P: If this SQL statement needs to be executed, delete the index. If this SQL statement need not be executed, delete it.
KFPA11707-E A
Invalid "LOB" RDAREA for table partitions
- One of the items listed below is not consistent with the table storage RDAREA specification, either because it has the same name as the table storage RDAREA name, or ALTER TABLE ADD RDAREA was used to specify a table storage RDAREA that is already in use by the target table.
- LOB column storage RDAREA
- LOB attribute storage RDAREA
- S: Ignores this SQL statement.
- P: If the same name as the table storage RDAREA was specified, make sure that the LOB column storage RDAREA or LOB attribute storage RDAREA is in the same location as the table storage RDAREA, and then retry the operation.
KFPA11708-E A
Not specified "LOB" RDAREA "aa....aa" in same server as table RDAREA
- The specified LOB RDAREA is not on the same server as the table storage RDAREA.
- aa....aa: LOB RDAREA name
- S: Ignores this SQL statement.
- P: Specify a LOB RDAREA on the same server as the corresponding table storage RDAREA.
KFPA11709-E A
Specified RDAREA "aa....aa" already used
- The specified LOB RDAREA is already being used for another table.
- aa....aa: LOB RDAREA name
- S: Ignores this SQL statement.
- P: Specify a LOB RDAREA that is not being used for another table.
KFPA11710-E A
Specific name for aa....aa."bb....bb" conflict with another routine
- The specific name for the routine aa....aa."bb....bb" is in conflict with another routine.
- aa....aa: Authorization identifier
- bb....bb: Routine identifier
- S: Ignores this SQL statement.
- P: Correct the routine identifier and re-execute.
KFPA11711-E A
Invalid update in execution of query with cursor
- One of the following errors was detected:
- An attempt was made to update, delete, or insert data in a table being retrieved using a cursor that was declared or assigned without specifying the FOR UPDATE clause.
- An attempt was made to delete or insert data in a table being retrieved using a cursor that was declared or assigned with FOR UPDATE OF specified.
- An attempt was made to update a column for which FOR UPDATE OF is not specified in a table being retrieved using a cursor that was declared or assigned with FOR UPDATE OF specified.
- An attempt was made to update or delete data using a cursor that was declared or assigned with FOR READ ONLY specified.
- S: Ignores this SQL statement.
- P: Correct the UAP and re-execute.
KFPA11712-E A
Duplicate attribute name "aa....aa"
- The name of an attribute comprising a data type must be unique for all the abstract data types that are in an inheritance relationship.
- aa....aa: Attribute name that is duplicated
- S: Ignores this SQL statement.
- P: Correct the attribute name so that it is unique and re-execute.
KFPA11713-E A
Unable to aa....aa work file due to insufficient HiRDB file system area bb....bb
- During internal processing to create a work table file, a space shortage occurred in the HiRDB file system area specified in pdwork of the server definition.
- aa....aa: Type of operation on the work table HiRDB file:
- create: Creation of work table HiRDB file
- expand: Expansion of work table HiRDB file
- bb....bb: Name of the HiRDB file system area resulting in the space shortage
- If the path name of the HiRDB file system area exceeds 117 characters, the last 117 characters of the HiRDB file system area path name are output.
- S: Invalidates this transaction.
- P: Contact the HiRDB administrator.
- Action
- When creating a work table HiRDB file (create):
- Add a HiRDB file system area using the pdwork operand of the server definition. Or, increase the size of the HiRDB file system area specified in the pdwork operand and start the server.
- When expanding a work table HiRDB file (expand):
- Increase the size of the HiRDB file system area specified in the server definition pdwork operand and start the server.
KFPA11714-E A
Number of "aa....aa" exceeds bb....bb
- The value of "aa....aa" exceeds the system maximum value bb....bb.
- aa....aa: Applicable item
{ ADT LEVEL (number of generations of abstract data types) }
- bb....bb: System maximum value
{ 30000 }
- S: Ignores this SQL statement.
- P: This problem cannot be resolved due to a system limitation. This SQL statement cannot be executed. If the problem is with the SQL statement, correct the error and re-execute.
KFPA11716-E A
Unable to change definition of column specified in aa....aa operand in view definition
- The data type or definition length of a column in a base table specified in one of the following items in the view definition cannot be changed:
- Concatenation operation
- Scalar function
- CASE function
- CAST specification
- Function invocation
- If one of the following facilities is specified in a view definition statement, the data type and definition length of columns used by the view definition cannot be changed.
- Row subquery
- Scalar subquery that specified a set operation
- Table subquery that specified a set operation
- A table subquery with two or more results columns, other than with the EXISTS predicate
- Scalar subquery of a selection expression
- Scalar subquery in the left side row value constructor of a comparison predicate, IN predicate, or quantified predicate
- Scalar subquery in a BETWEEN predicate, LIKE predicate, XLIKE predicate, and SIMILAR predicate
- aa....aa: Nature of error:
{ concatenation |scalar function |CASE expression
|function invocation |CAST specification subquery }
- S: Ignores this SQL statement.
- P: Correct the SQL statement or delete the viewed table, then re-execute.
KFPA11717-E A
Unable to rename aa....aa name on "bb....bb" due to cc....cc
- The name of the table, column, or index cannot be changed for the following reason:
- A viewed table has been created based on the table to be changed.
- A trigger is defined in the table to be changed.
- A check constraint is defined in the table to be changed.
- The column to be changed is used in the search condition of a check constraint.
- A referential constraint (foreign key) is defined in the table to be changed.
- The column to be changed is comprised of a foreign key.
- The table to be changed is a referenced table of a referential constraint.
- The column to be changed is comprised of the primary key of a referenced table of a referential constraint.
- The table to be changed, or the table on which the index to be changed is defined, is specified in a stored procedure or trigger SQL statement.
- An attempt was made to change a column name of a viewed table.
- An attempt was made to change the column name specified by the trigger execution event.
- An attempt was made to change the name of the column referred to using the old or new values correlation name in the search conditions of the trigger operation.
- An attempt was made to change the name of the column referred to using the old or new values correlation name in the trigger SQL statement.
- An attempt was made to change the table name or column name of the falsification prevented table.
- aa....aa: Item to be changed:
- COLUMN: Column name
- TABLE: Table name
- INDEX: Index name
- bb....bb: The table, viewed table, or index
- cc....cc: Error:
- used on view: View is defined
- used on trigger: Trigger is defined.
- check constraint: Check constraint is defined.
- check column: Column name used in a check constraint search condition.
- referential constraint: Referential constraint (foreign key) is defined.
- foreign key column: Name of a column comprised of a foreign key.
- referenced table: Referenced table of a referential constraint.
- referenced primary key: Column comprised of the primary key of a referenced table of a referential constraint.
- used on stored procedure: Used by a stored procedure or a trigger SQL statement.
- view's column: Column name to be changed is a column name in a viewed table
- trigger column: Column name to be changed was defined in the trigger event.
- triggered action condition: Column name to be changed referred to an old or new correlation name in the search condition of a trigger operation.
- triggered SQL statement: Column name to be changed referred to an old or new correlation name in the trigger SQL statement.
- INSERT ONLY table: Table to be changed is a falsification prevented table.
- S: Ignores this SQL statement.
- P:
- cc....cc is used on stored procedure or used on view:
- Delete the viewed table, stored procedure, or trigger that uses the table to be changed or on which the index to be changed is defined, and then re-execute the ALTER TABLE or ALTER INDEX statement. Then, re-create the viewed table, stored procedure, or trigger.
- cc....cc is view's column
- Execute DROP VIEW, then execute CREATE VIEW using a different column name, then change the column name.
- cc....cc is used on trigger:
- Drop the trigger defined for the table to be changed, and re-execute ALTER TABLE. Then re-create the trigger.
- cc....cc is check constraint:
- Revise the table name, and re-execute.
- cc....cc is check column:
- Revise the column name, and re-execute.
- cc....cc is referential constraint:
- Revise the table name, and re-execute.
- cc....cc is foreign key column:
- Revise the column name, and re-execute.
- cc....cc is referenced table:
- Revise the table name, and re-execute.
- cc....cc is referenced primary key:
- Revise the column name, and re-execute.
- cc....cc is trigger column, triggered action condition, or triggered SQL statement:
- Delete the trigger using the column that attempted to change the column name and re-execute ALTER TABLE. Then re-create the trigger.
- cc....cc is an INSERT ONLY table:
- The falsification prevented table cannot change the table name or alias. Review the table name and re-execute.
KFPA11718-E A
Invalid use of column suppress specification
- One of the following errors was detected in the definition of column data restriction:
- Specified for a FIX table
- Specified for a column whose data type is not CHAR, MCHAR, or NCHAR
- The column suppress specification is specified for a repetition column.
- S: Ignores this SQL statement and terminates the transaction.
- P: Correct the SQL statement and re-execute.
KFPA11720-E L+A
Error occurred in HiRDB/client, inf1=aa....aa, inf2=bbbb
- Internal conflict occurred in the client library of the HiRDB system.
The error may be due to either of the following factors: - The host specified in the pdstart command and the host specified in PDHOST on one hand and the client-side system on the other hand are in a condition that prevents them from communicating with each other on the network
- The communications load is high
- If an X/Open-compliant UAP is executed under the OLTP environment, a transaction was not started by using the tx_begin function.
- aa....aa: Name of the source file in which the error was detected
- bbbb: Location of the error (line number)
- S: Terminates processing.
- Action
- Make a backup of the client error log file where the error was output and contact the customer support center.
- If this message is output, the connection with the HiRDB server was disrupted. To execute the UAP, re-execute it beginning with the CONNECT statement.
KFPA11722-E A
Communication error occurred, reason=aa....aa
- SQL processing was interrupted by a communication error.
- aa....aa: Nature of error:
- INVALID DATA: Invalid data was received from the server.
- SERVER PROCESS DOWN: Server process was shut down.
- S: Terminates processing and releases connection with the server.
- P: Contact the HiRDB administrator.
- Action
- Contact the customer support center, and be prepared to provide the contents of the client error log files (pderr1.trc, pderr2.trc). If in XDS was output, also provide the XDS logs (pdxdslog1, pdxdslog2) to the customer support center.
- If this message is output, the connection with the HiRDB server was disrupted. To execute the UAP, re-execute it beginning with the CONNECT statement.
- SERVER PROCESS DOWN:
- Check the cause of the server process shutdown, correct the error, and then re-execute the UAP.
- If the high-speed connection facility (PDSERVICEPORT in the client environment definition) is used, the value specified for PDSERVICEPORT might be invalid. Check if message KFPS00860-W was output during HiRDB startup, or if the value of PDSERVICEPORT is the same as the value of the scheduler port number (the -s option of the pd_service_port, pd_scd_port, or pdunit operand in the system definition). If applicable, correct the value of the PDSERVICEPORT specification, and then re-execute the UAP.
KFPA11723-E L+A
Communication error occurred [ in XDS], reason=aa....aa
- A communication error occurred between the HiRDB system or the HiRDB server. Or, the HiRDB system or HiRDB server is down.
If an error occurred in XDS, in XDS is displayed in the message text. - aa....aa: Character string indicating the nature of the error:
- CLIENT MEMORY:
- A memory shortage occurred in the client library.
- FES(SDS) CLOSE:
- The server (SDS for HiRDB/Single Server, FES for HiRDB/Parallel Server) is engaged in termination processing.
- FES(SDS) NOT UP:
- The server (SDS for HiRDB/Single Server, FES for HiRDB/Parallel Server) is not running, is undergoing startup processing, or is running as a log application site.
- HiRDB BUSY:
- Connection cannot be established because HiRDB (server) is BUSY.
- HiRDB DATA ERROR:
- Communication data from the HiRDB system or HiRDB server is invalid.
- HiRDB INITIALIZE:
- The HiRDB system or HiRDB server is now initializing.
- HiRDB NOT UP:
- The HiRDB system or the HiRDB server is not running, or the Listen queue on the HiRDB server side is insufficient.
- HiRDB SYSTEM ERROR:
- A system error was detected in the HiRDB system or the HiRDB server.
- HiRDB MEMORY:
- Memory on the HiRDB system or HiRDB server is low.
- INIT ERROR:
- An error occurred in the initialization process of the communication.
- INVALID SERVER TYPE:
- The HiRDB (server) server type differs from the PDSRVTYPE (client environment definition).
- NETWORK:
- A network failure occurred, or the HiRDB server abnormally terminated and disconnected itself from the network.
- INSUFFICIENT NETWORK PORT:
- An attempt to allocate a communication port number failed.
- S: Terminates processing.
- O:
- Check the error log file (created in the current directory or under the directory specified in the PDCLTPATH operand) that the HiRDB client outputs for the cause of the failure, eliminate the cause, and then retry the operation. If this message is output, the connection with the HiRDB server was disrupted. You might have to re-execute the command beginning with the CONNECT statement.
- If this message (aa....aa is HiRDB NOT UP) continues to be output when the UAP starts, even though the connection target HiRDB has started, review the value specified for the connection destination. The information below describes how to specify the connection destination.
- When using an XDS client:
- Embedded application:
See Specifying a connection destination under Connection from an XDS Client in the HiRDB Version 9 UAP Development Guide.
- Windows-edition ODBC 3.5 driver-compliant application:
See ODBC-compliant application programs under Connection from an XDS Client in the HiRDB Version 9 UAP Development Guide.
- Linux-edition ODBC 3.5 driver-compliant application:
See ODBC-compliant application programs under Connection from an XDS Client in the HiRDB Version 9 UAP Development Guide.
- Type 4 JDBC driver-compliant application:
See Connection to XDS using the getConnection method under Connection from an XDS Client in the HiRDB Version 9 UAP Development Guide.
- When using a client of the server providing the primary facilities:
- Embedded application:
See Environment variables and connection types for HiRDB servers in the HiRDB Version 9 UAP Development Guide.
- Windows-edition ODBC 2.0 driver-compliant application:
See Installing the ODBC 2.0 driver in the HiRDB Version 9 UAP Development Guide.
- Windows-edition ODBC 3.5 driver-compliant application:
See Installing the ODBC 3.5 driver and setting the environment variables in the HiRDB Version 9 UAP Development Guide.
- Linux-edition ODBC 3.5 driver-compliant application:
See Installing the ODBC 3.5 driver and setting the environment variables in the HiRDB Version 9 UAP Development Guide.
- Type 2 JDBC driver-compliant application:
See Database connection using the DriverManager in the HiRDB Version 9 UAP Development Guide.
- Type 4 JDBC driver-compliant application:
See Database connection using the DriverManager class in the HiRDB Version 9 UAP Development Guide.
- ADO .NET 1.1-compliant application:
See HiRDBConnection in the HiRDB Version 9 UAP Development Guide.
- ADO .NET 2.0-compliant application:
See HiRDBConnection in the HiRDB Version 9 UAP Development Guide.
- OLE DB-compliant application:
See Connection properties in the HiRDB Version 9 UAP Development Guide.
- SQLJ-compliant application:
See Description of connection to and disconnection from a HiRDB server in the HiRDB Version 9 UAP Development Guide.
- If the values in the client environment definition are correct and message KFPZ02444-E (func=connect and the value indicated for errno is either ETIMEDOUT or ECONNREFUSED) is output to the error log file, it is possible that there are too many connection requests for the HiRDB server. Wait for a while, and then retry the operation. For details about the actions to take, see Listen queue specified values in the HiRDB Version 9 Installation and Design Guide.
- If the connection destination HiRDB is using Real Time SAN Replication with the log-only synchronous method and aa....aa is FES(SDS) NOT UP, it is possible that the HiRDB is running as a log application site. If this is the case, ask the HiRDB administrator about the condition. If necessary, change the connection destination to an application site HiRDB, and then re-execute the command.
- If in XDS was output, report the nature of the error to the HiRDB administrator, correct the error, and then retry the operation.
- P:
- When aa....aa is HiRDB BUSY:
- Wait for a while, and then retry the operation. If the same message is issued again, contact the HiRDB administrator.
- When aa....aa is something other than HiRDB BUSY:
- Report the nature of the error to the HiRDB administrator, correct the error, and then retry the operation.
- Action
- When using an XDS client or a client of the server providing the primary facilities:
- If aa....aa is INIT ERROR or NETWORK and message KFPZ02444-E (func=bind or connect and the value indicated for errno is EADDRNOTAVAIL, EADDRINUSE, or ENOBUFS) is output to the error log file, there might not be enough ports automatically allocated by the OS on the client side. For details about corrective actions, see the administrator actions for message KFPS00349-E.
- If there is an attempt to connect to multiple FES groups and all connections fail, in the following cases the contents of the last error that occurred are returned:
You are using an XDS client, and multiple FES groups are specified in PDFESGRP in the XDS environment definition.
You are using a client of the server providing the primary facilities, and multiple FES groups are specified in PDFESGRP in the client environment definition.
Use the error log files and the troubleshooting information collected by the server to determine the cause of the error that occurred in the connection to each FES group.
If the number of users connected to the HiRDB server exceeds the maximum number of concurrent connections, a connection error is returned but the troubleshooting information collected by the server cannot be used to determine whether the maximum number of concurrent connections has been exceeded. Instead, use the command pdls -d act to check the number of connected users.
For details about corrective actions when maximum number of concurrent connections has been exceeded, see the administrator actions for message KFPA11932-E.
- When using an XDS client:
- If aa....aa is INSUFFICIENT NETWORK PORT, there might not be enough ports automatically allocated by the OS on the connection destination server side. For details about corrective actions, see the administrator actions for message KFPS00349-E.
- If in XDS was output, determine the cause of the error from the error log files (pderr1.trc, pderr2.trc) and XDS log (pdxdslog1, pdxdslog2), eliminate the cause of the error, and then retry the operation.
To specify the values for the connection destinations, revise the XDS environment definition. For details about the XDS environment definition, see XDS environment definition in the HiRDB Version 9 Memory Database Installation and Operation Guide.
KFPA11724-E L+A
Environment definition error, variable=aa....aa, reason=bb....bb, identifier="cc....cc"
- An environment variable is invalid.
- aa....aa: Name of invalid environment variable
- If the environment variable begins with PDPLUGIN, either the length of the plug-in environment variable is excessive or there are too many environment variables to be stored in the buffer.
- bb....bb: Reason for the error:
- INVALID CHAR: An invalid character was detected.
- NET ENVIRONMENT: Specification does not match the network environment.
- NO VALUE: A specification value is missing.
- OUT OF RANGE: Specified value is outside the permitted range.
- NOT ENVIRONMENT GROUP: The environment variable group specified in the registry does not exist.
- INVALID IDENTIFIER: The identifier is invalid.
- cc....cc:
- Invalid identifier (first 30 bytes only if the identifier is longer than 30 bytes)
- This is displayed if the cause is INVALID IDENTIFIER; it is not displayed in all other cases.
- S: Terminates processing.
- P: Correct the specification of the environment variable and re-execute.
KFPA11725-E L+A
Other SQL executing cannot execute next SQL
- The next SQL statement is executed before the execution of the previous SQL statement was completed. Or, for a multi-threaded UAP, the same connection handle is being used by multiple threads, or the SQL statement is executing without a connection handle.
- S: Terminates processing.
- O: Wait for the processing of the first SQL to terminate, and then re-execute the next SQL.
KFPA11727-E L+A
Unable to execute SQL, for termination process HiRDB
- An SQL statement cannot be executed, because the HiRDB system or server is engaged in termination processing.
- S: Terminates processing.
- P: Check that the HiRDB system or server is active, and re-execute the UAP.
KFPA11728-E L+A
Error occurred in HiRDB, reason=aa....aa
- The HiRDB system or server made an error control return.
- aa....aa: Character string indicating the reason:
- FALSE:
- Locking of a resource failed.
- NO FES(SDS):
- Either an available server (single server (SDS) or front-end server (FES)) does not exist or an attempt was made to connect to a log application site.
- SHUTDOWN:
- The HiRDB system is engaged in shutdown processing.
- S: Terminates processing.
- P: If the reason code is FALSE
- Retry the command.
- If the reason code is either NO FES(SDS) or SHUTDOWN
- Confirm that the HiRDB has started, and then re-execute the UAP. If this message is output, the connection with the HiRDB server was disrupted. It may be necessary to re-execute the UAP beginning with the CONNECT statement.
- If the HiRDB is running in NO FES(SDS) as a log application site, specify a transaction execution site as a connection destination, and re-execute the UAP.
KFPA11729-E A
Insufficient memory on aa....aa, size=bbbbb
- There is not enough memory to execute an SQL statement.
- aa....aa: Character string indicating the type of area that was to be allocated:
- DYNAMIC_SHMPOOL: Dynamic shared memory
- PROCESS: Process private area
- STATIC_SHMPOOL: Static shared memory
- bbbbb: Size of the area that was to be allocated (in bytes)
- S: Terminates processing.
- Action
- Allocate the memory required for execution and re-execute.
KFPA11731-E L+A
System call error, func=aa....aa, errno=bbb
- System call aa....aa resulted in an error.
- aa....aa: Name of the system call resulting in the error
- bbb: Error number returned from the system call
- S: Terminates processing.
- P: Check the meaning of the error indicator value, eliminate the cause of the error by referencing errno.h and the applicable OS manual, then re-execute.
KFPA11732-E A
Time over, no response from HiRDB[ in XDS][,WAITTIME=aaaaa]
- Because the HiRDB server was shut down or HiRDB server processing was not completed within the timer monitoring interval, a query cannot be sent to the HiRDB server.
The [,WAITTIME=aaaaa] message can be output when the Type 4 JDBC driver is being used.
If an error occurred in XDS, in XDS is displayed in the message text. - aaaaa: The client's maximum wait time
- The timer monitoring interval that is output is as follows:
- If there is a connection to the HiRDB server:
The value of PDCONNECTWAITTIME in the client environment definition
- If the CALL COMMAND statement was executed:
The value of PDCALCMDWAITTIME in the client environment definition
- Other than above
The value of PDCWAITTIME in the client environment definition, or the value of Statement#setQueryTimeout
- S: Terminates processing.
- O:
- When using a client of the server providing the primary facilities:
- This error can occur if an invalid IP address (an address that cannot be accessed from the HiRDB server) or a host name is specified in PDCLTRCVADDR. From the host containing an FES (SDS) for the HiRDB server, check whether the IP address specified in the PDCLTRCVADDR variable can be transmitted using the ping command. This error can also occur if the address associated with the host name specified in PDCLTRCVADDR is different for the host containing the HiRDB server and the host containing the UAP. Make sure that the address associated with the host name assigned to PDCLTRCVADDR is correct.
- When using an XDS client or a client of the server providing the primary facilities:
- If this error occurs while attempting a connection and the automatic reconnect facility is used, check the KFPA11723-E message, which is output to the error log file, to find and eliminate the cause of the communication error with the HiRDB server, and then retry the operation.
- P: If the HiRDB server is stopped, make sure that the HiRDB server has started, and then retry the operation.
- If the HiRDB server is not stopped, increase the timer monitoring interval and re-execute the UAP. The value used for the timer monitoring interval is as follows:
- If there is a connection to the HiRDB server
- The value of PDCONNECTWAITTIME in the client environment definition
- If the CALL COMMAND statement was executed:
- The value of PDCALCMDWAITTIME in the client environment definition
- Other than above
- The value of PDCWAITTIME in the client environment definition, or the value of Statement#setQueryTimeout
- If this message is output, the connection with the HiRDB server was disrupted. You might have to re-execute the UAP beginning with the CONNECT statement.
- Action
- If in XDS was output, revise the values specified in the XDS environment definition. For details about the XDS environment definition, see XDS environment definition in the HiRDB Version 9 Memory Database Installation and Operation Guide.
KFPA11733-E L+A
Error occurred in HiRDB, inf1=aa....aa, inf2=bbbb
- Invalid data was received from the HiRDB server.
- aa....aa: Name of source file in which the error was detected
- bbbb: Location where the error was detected (line number)
- S: Terminates processing.
- Action
- When the client error log file is output, back up the client error log file, eliminate the cause of the error on the server, and then contact the customer support center.
KFPA11734-E L
Unable to get IPaddr of FES(SDS) host, hostname=aa....aa
- The IP address of the host name where the HiRDB/Single Server (SDS) or the HiRDB/Parallel Server (FES) is located cannot be obtained.
- aa....aa: Name of the host whose IP address was to be obtained
- S: Terminates processing.
- P: Refer to the contents of the hosts file at the host where the UAP was executed, add the definition of the host name displayed in the message, and then re-execute the UAP.
KFPA11735-E L
aa....aa canceled
- SQL execution was canceled due to a cancellation request received from the UAP, and the transaction was invalidated.
- aa....aa:
- FES(SDS): When using a client of the server providing the primary facilities
- Transaction: When using an XDS client
- S: Terminates processing.
- O: Because the requested processing has been canceled, re-execute the UAP if necessary.
- P: Modify the program to re-execute the SQL code for the transaction that was invalidated.
KFPA11736-E A
aa....aa bb....bb."cc....cc" not convert to 64-bit
- The specified aa....aa bb....bb."cc....cc" is not compatible with the 64-bit mode.
- aa....aa: Type:
- View: Viewed table
- Routine: Routine
- Trigger: Trigger
- bb....bb: Authorization identifier
- cc....cc: Table identifier, routine identifier, or trigger identifier
- S: Ignores this SQL statement.
- Action
- Use the pdobjconv command to make the viewed table or the routine 64-bit mode compatible. Then, re-execute the UAP statement.
KFPA11737-E A
RDAREA for specified aa....aa already removed, server=bb....bb
- The RDAREA at server bb....bb for storage of aa....aa, as specified by the SQL statement, has already been deleted by the database structure modification utility (pdmod).
- aa....aa: LIST (list)
- bb....bb: Server name
- S: Ignores this SQL statement.
- P: First delete the list specified by the SQL statement, then re-create the list and re-execute.
KFPA11738-E A
No RDAREA for aa....aa, server=bb....bb
- The SQL statement cannot be executed because no RDAREA for aa....aa exists at server bb....bb.
Or, the SQL statement cannot be executed because all RDAREAs for aa....aa at server bb....bb are on shutdown status. - aa....aa: LIST (list)
- bb....bb: Server name
- S: Ignores this SQL statement.
- P:
- Use the database structure modification utility (pdmod) to allocate an RDAREA, and then re-execute the SQL statement.
- Or, release the RDAREAs from shutdown status by removing the error cause, and then re-execute the SQL statement.
- If this message is output, the connection with the HiRDB server was disrupted. It may be necessary to re-execute the UAP beginning with the CONNECT statement.
KFPA11740-E A
Unable to execute SQL for definition due to cc....cc aa....aa."bb....bb"
- The routine aa....aa."bb....bb" is part of an SQL object that uses the resource to be deleted or changed. Therefore, the following definition SQL statements that invalidate SQL objects cannot be executed. Another possibility is that the following definition SQL statements could not be executed because the routine aa....aa."bb....bb" in the SQL object that uses the resource to be deleted or changed is being executed:
ALLOCATE MEMORY TABLE (set table to memory database allocation)
ALTER INDEX (change index definition)
ALTER PROCEDURE (change procedure)
ALTER ROUTINE (change routine)
ALTER TABLE (change the table definition)
ALTER TRIGGER (change trigger)
CREATE FUNCTION (define a function)
CREATE INDEX (define an index)
CREATE TABLE (define a table)
CREATE TRIGGER (define a trigger)
CREATE TYPE (define data type (subtype))
DROP DATA TYPE (delete data type)
DROP FUNCTION (delete function)
DROP INDEX (delete index)
DROP PROCEDURE (delete procedure)
DROP SCHEMA (delete schema)
DROP SEQUENCE (delete sequence generator)
DROP TABLE (delete table)
DROP TRIGGER (delete trigger)
DROP VIEW (delete view)
REVOKE access privilege (delete access privilege)
- The viewed table aa....aa."bb....bb" that uses the resource to be deleted exists. Therefore, the following definition SQL statements cannot be executed:
DROP FUNCTION (delete function)
DROP DATA TYPE (delete data type)
DROP SCHEMA (delete schema)
- The trigger aa....aa."bb....bb", used in the search conditions of a trigger operation, exists for the deleted function. Therefore, the following definition SQL statements cannot be executed:
DROP FUNCTION (delete function)
DROP SCHEMA (delete schema)
- Among the resources invalidated by the definition SQL, there is a viewed table aa....aa."bb....bb" that uses a resource that has an abstract data type parameter or return value. Therefore, the following definition SQL statements cannot be executed:
CREATE FUNCTION (define function)
CREATE TYPE (define data type (subtype))
DROP DATA TYPE (delete data type)
DROP FUNCTION (delete function)
- aa....aa: Authorization identifier
- bb....bb: Routing identifier, table identifier, or trigger identifier
- cc....cc: {ROUTINE|TABLE|TRIGGER}
- S: Invalidates this transaction.
- P:
- cc....cc is ROUTINE
- If you can delete the SQL object, specify WITH PROGRAM and re-execute. If a routine is being executed, terminate the routine before re-executing.
- cc....cc is TABLE
- Re-execute after deleting viewed table aa....aa."bb....bb".
- cc....cc is TRIGGER
- Delete trigger aa....aa."bb....bb" and then re-execute. Alternatively, if you can invalidate a trigger for the DROP FUNCTION, specify WITH PROGRAM and re-execute.
KFPA11741-E A
Unable to drop datatype due to used by aa....aa bb....bb."cc....cc"
- The specified data type is used by bb....bb."cc....cc" of aa....aa. Therefore, it cannot be deleted.
- aa....aa: Resource using the data type
- {TABLE, INDEX, DATATYPE, INDEXTYPE}
- bb....bb: Authorization identifier (owner of the resource being used)
- cc....cc: Name of the resource being used
- S: Ignores this SQL statement.
- P: Check whether the definition of the resource being used can be deleted. If it can be deleted, delete the definition and re-execute this SQL statement.
KFPA11743-E A
Foreign key aa....aa."bb....bb" mismatch primary key code=cc(dd....dd)
- Foreign key aa....aa."bb....bb" does not match the primary key that the foreign key references.
- aa....aa: Authorization identifier
- bb....bb: Constraint name
- cc: Reason code
- dd....dd: Additional error information
- S: Ignores this SQL statement.
- P: The reason codes and the additional error information are listed below. Eliminate the cause of the error, and re-execute the SQL statement.
Reason code (cc) | Additional error information (dd....dd) | Explanation |
---|
01 | number of columns | The number of columns that comprise the foreign key and the primary key are different. |
02 | data types | The data types of the columns that correspond to the foreign key and the primary key are different. |
03 | data length | The data lengths of the columns that correspond to the foreign key and the primary key are different. |
04 | character set | The character sets of the columns corresponding to the foreign key and primary key are different. |
KFPA11744-E A
Unable to define referential constraint aa....aa."bb....bb" for ee....ee."ff....ff" code=cc(dd....dd)
- Unable to define referential constraint aa....aa."bb....bb" for referenced table ee....ee."ff....ff", for the reason shown in cc.
- aa....aa: Authorization identifier
- bb....bb: Constraint name
- cc: Reason code
- dd....dd: Additional error information
- ee....ee: Authorization identifier
- ff....ff: Table identifier
- S: Ignores this SQL statement.
- P: The reason codes and the additional error information are listed below. Eliminate the cause of the error, and re-execute the SQL statement.
Reason code (cc) | Additional error information (dd....dd) | Explanation |
---|
01 | view | A table that is not a permanent base table cannot be specified in a referenced table. |
02 | Primary key not defined | No primary key has been defined for the referenced table. |
03 | WITHOUT ROLLBACK table | In a referenced table, a table with the WITHOUT ROLLBACK specification cannot be specified. |
04 | own table | One's own table cannot be specified in a referenced table. |
05 | another user's table | The table of another user cannot be specified in a referenced table. |
KFPA11745-E A
Unable to specify partitioning key on column "aa....aa"
- A partitioning key cannot be specified on the following columns:
- CHAR, VARCHAR, MCHAR, or MVARCHAR with a definition length of 256 bytes or more
- NCHAR or NVARCHAR with a definition length of 128 characters or more
- For single column partitioning, a column that is not the first column comprising the cluster key
For multicolumn partitioning or matrix partitioning, a column for which the sequence of columns specified in the partitioning key is different from the sequence of columns specified in the cluster key
- BLOB
- A column duplicated in a multicolumn partition or the partitioning key of a matrix partition
- Repetition column
- BINARY
- TIMESTAMP with fractional second precision greater than 0
- Column that specifies CURRENT_TIMESTAMP USING BES as the default value
- Abstract data type
- aa....aa: Column name where the error occurred
- S: Ignores this SQL statement.
- P: Specify an allowed column as the partitioning key, and then retry the operation.
- If a cluster key is specified, specify the columns in the cluster key in the same sequence as the columns specified in the partitioning key, starting from the beginning and including all of the columns, and then retry the operation.
KFPA11746-E A
Incompatible data type specified at partitioning condition aaaa for column "bb....bb"
- One of the following errors was detected in the condition value of storage condition aaaa specified in the "bb....bb" column:
- The data type of the condition value cannot be converted into the data type of the column specified in the storage condition.
- The data length of the condition value exceeds the data length of the column specified in the storage condition.
- The condition value is logically invalid.
- The condition value data is invalid.
- The data length of the condition value converted in the character set specification exceeds the data length of the column specified in the partitioning condition.
- A non-convertible condition value was specified for the character set of the column specifying the storage condition.
- aaaa: Sequential number of the storage condition
- bb....bb: Column name specifying the storage condition value that caused the error
- S: Ignores this SQL statement.
- P: Revise the partitioning storage condition, and then retry the operation.
KFPA11747-E A
Invalid partitioning condition aaaa for column "bb....bb"
- One of the following errors was detected in storage condition aaaa specified in partitioning key "bb....bb".
- When the storage conditions were evaluated in the specified order, there was no row to store according to storage condition aaaa.
- A storage condition was specified in more than one column.
- The length of a character strings in the storage condition is 0.
- aaaa: Sequential number of the storage condition
- bb....bb: The column name specifying the storage condition value that caused the error (******** is displayed when the column name specifying the partitioning condition cannot be determined)
- S: Ignores this SQL statement.
- P: Correct the value specified as the storage condition and re-execute.
KFPA11748-E A
Number of defined foreign keys referencing primary key in a table exceeds 255,table=aa....aa."bb....bb"
- The number of foreign keys that reference the primary key of referenced table aa....aa."bb....bb" exceeds the maximum number (255).
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Ignores this SQL statement.
- P: Drop the table that defines the foreign key, and then re-execute the SQL statement.
KFPA11749-E A
Duplicate column name "aa....aa" in foreign key bb....bb."cc....cc"
- Column name "aa....aa" is duplicated in foreign key bb....bb."cc....cc".
- aa....aa: Column name that comprises the foreign key
- bb....bb: Authorization identifier
- cc....cc: Constraint name
- S: Ignores this SQL statement.
- P: Revise the column names that comprise the foreign key to remove duplicates, and then re-execute.
KFPA11750-E A
Invalid ALLOCATE clause for column "aa....aa"
- An error was detected in the ALLOCATE clause specified in the "aa....aa" column.
If the column data is an abstract data type, you have to specify an RDAREA for storing each LOB for all BLOB attributes included in the abstract data type. Or, the BLOB attribute is defined in the super type of the specified abstract data type. - aa....aa: Column name specifying the ALLOCATE clause
- S: Ignores this SQL statement.
- P: Correct the ALLOCATE clause of the SQL statement and re-execute. However, if the BLOB attribute is defined in the super type of the specified abstract data type, this SQL statement cannot be executed.
KFPA11751-E A
Unable to specify aa....aa in ALTER TABLE statement,reason=bb....bb
- For the reason indicated in bb....bb, aa....aa cannot be specified in ALTER TABLE.
- aa....aa: Processing that cannot be executed
- CHANGE SEGMENT REUSE OPTION
- bb....bb: Cause of error
- not segment reuse table
- The table does not use the free space reusage facility.
- S: Ignores this SQL statement.
- P: When executing the SQL statement, make sure that the reuse option value is specified for a table that uses the free space reusage facility.
KFPA11752-E L+A
Already connected
- The CONNECT statement was already issued. The CONNECT statement cannot be issued again after connecting to the HiRDB system.
- S: Terminates the process.
- P: Re-evaluate the program and check for errors in the order the SQL statements were issued. If necessary, either delete this CONNECT statement or add a DISCONNECT statement in front of this CONNECT statement.
KFPA11753-E A
Invalid option specified for column "aa....aa"
- An error was detected in the option specification of column "aa....aa".
- The with default option cannot be specified in an abstract data type column.
- PLUGIN cannot be specified for columns other than abstract data type columns provided by the plug-in developer.
- aa....aa: Column name with an invalid option specified
- S: Ignores this SQL statement.
- P: Correct the specification of the column definition in the SQL statement and re-execute.
KFPA11754-E A
Duplicate routine name aa....aa."bb....bb"
- The routine name specified by the FOR clause in the CREATE INDEX statement was duplicated.
- aa....aa: Authorization identifier
- bb....bb: Routine identifier
- S: Ignores the SQL statement.
- P: Correct the routine name and re-execute.
KFPA11756-E L+A
No available pages in RDAREA, RDAREA=aa....aa
- A page shortage occurred in the RDAREA.
- aa....aa: Name of the RDAREA with insufficient free space
- S: Ignores this transaction.
- Action
- Perform one of the following actions, and then re-execute the SQL statement in this transaction:
- RDAREA expansion
Expand the capacity of the RDAREA with insufficient space using the pdmod utility.
- Table reorganization or batch index creation
Reorganize the table stored in the applicable RDAREA using the pdrorg utility. Alternatively, execute batch index creation.
- Release the free page
Use the pddbst utility to analyze the status of the applicable RDAREA and execute the pdreclaim utility on an index when necessary. Also, if variable length character string type, BINARY type, or abstract data type data with a definition length of 256 bytes or more or branching lines of a repetition column is stored, execute the pdreclaim utility on a table if necessary.
- If this message is output during execution of pdload or pdrorg, execute one of the following processing functions, and then re-execute the command.
- RDAREA extension
Use the database structure modification utility to expand the size of the insufficient RDAREA.
- Change the storage format of variable length character column data
For tables with VARCHAR, NVARCHAR, or MVARCHAR columns with a defined length of 256 or more bytes, if the no split option can be specified, redefine the table using CREATE TABLE. The number of pages required for data storage can be deleted.
- Change the percentage of unused space or percentage of empty pages (action when the RDAREA cannot be expanded immediately)
Change using one of the following methods:
Reduce the value specified in the PCTFREE operand specified in CREATE TABLE and CREATE INDEX, and then redefine the table or index.
Specify the tblfree or idxfree operand in the option control statement of the database load utility (pdload) or the database reorganization utility (pdrorg), and change the specified value to a value less that the value specified in the PCTFREE operand.
KFPA11758-E A
Invalid "EXCEPT VALUES" for aa....aa
- One of the following errors was detected in the exception key value for the specified index:
- NULL was specified as a value comprising an exception key value in the column of a NOT NULL constraint.
- An exception key value was specified in the index of a repetition column.
- aa....aa: CREATE INDEX
- S: Ignores this SQL statement.
- P: Correct this SQL statement, and then re-execute it.
KFPA11761-E A
PLUGIN for aa....aa."bb....bb" not registered
- This SQL cannot be executed because a plug-in is not registered.
Plug-ins must be registered in the index type specified by the plug-in index definition. - aa....aa: Authorization identifier
- bb....bb: Data type or index type identifier
- S: Ignores this SQL statement.
- P: Register the plug-in, and then re-execute.
KFPA11764-E A
Number of index columns unequals to number of "EXCEPT VALUES" columns
- The number of columns comprising the index and the number of values comprising the exception key value do not match.
- S: Ignores this SQL statement.
- P: Set the number of columns comprising the index and the number of values comprising the exception key value to the same value.
KFPA11766-E A
Unable to define aa....aa cc....cc "bb....bb" for specified data type
- aa....aa cannot be defined in column "bb....bb".
- The following columns cannot be specified when aa....aa is multi-value:
- BLOB column
- Abstract data type column
- BINARY type column
- The following columns cannot be specified when aa....aa is no-split or split:
- Columns other than VARCHAR, MVARCHAR, or NVARCHAR
- The following columns cannot be specified when aa....aa is collating-sequence:
- CHAR, VARCHAR, MCHAR, MVARCHAR, NCHAR or NVARCHAR
- The following columns cannot be specified when aa....aa is trailing-space:
- VARCHAR, MVARCHAR, or NVARCHAR
- If aa....aa is recovery, the following columns cannot be specified:
- BLOB and non-BLOB attribute columns
- If aa....aa is with default, the following columns cannot be specified:
- Columns of the abstract data type
- aa....aa:
- multi-value: A repetition column
- no-split: A column with the no-split option specified
- split: A column without the no-split option specified
- collating-sequence: A column with the COLLATING-SEQUENCE option specified
- trailing-space: A column with the TRAILING-SPACE option specified
- recovery: Columns with a RECOVERY specification
- with default: Columns with a WITH DEFAULT clause specification
- bb....bb: Column name
- cc....cc:
- column: The column name
- attribute: The attribute
- S: Ignores this SQL statement.
- P: Correct the SQL statement then re-execute.
KFPA11769-E A
Unable to lock aa....aa table
- When aa....aa is system:
LOCK statements cannot be executed on a system table or on a viewed table that is based on a system table.
- When aa....aa is memory:
LOCK statements cannot be executed on a memory database allocation table.
- aa....aa: {system|memory}
- S: Ignores this SQL statement.
- P: If aa....aa is system, do not execute a LOCK statement on a system table or on a viewed table that is based on a system table. If aa....aa is memory, do not execute a LOCK statement, or execute it on a table after releasing the memory database allocation.
KFPA11770-I A
aaaa [bb....bb cc....cc] currently in use, resource id=dd....dd
- An SQL statement cannot be executed because the resource indicated by resource ID dd....dd is in use by another transaction.
Unless the SQL statement has a NO WAIT specification (including a NOWAIT specified in a FOR UPDATE clause), this message is output when the wait time timeout is reached. - aaaa: Resource type alias
- bb....bb: Resource name 1
- cc....cc: Resource name 2
- dd....dd: Resource information
- For details on resource type names, resource names, and resource information, see the HiRDB Version 9 System Operation Guide. In HiRDB/Parallel Server, resource name 1 is always ****.
- S:
- For an SQL statement with a NO WAIT specification (including a NOWAIT specified in a FOR UPDATE clause), ignores this SQL statement.
- For an SQL statement with a WITH ROLLBACK specification, rolls back and invalidates the transaction.
- O:
- Re-execute. For details, see the explanation of measures for deadlocks and timeouts in the HiRDB Version 9 System Operation Guide.
- If a shared table is used with a HiRDB/Parallel Server, verify that an updatable back-end server is active. If not, re-start the server, and then retry the operation.
KFPA11771-E A
Not specified index RDAREA in same server as table RDAREA
- The specified index storage RDAREA was not found on the server. The index storage RDAREA includes an RDAREA for storing cluster key indexes and an RDAREA for storing a primary key index.
- S: Ignores this SQL statement.
- P: Specify the index storage RDAREA on the server containing the table storage RDAREA and re-execute the SQL statement.
KFPA11773-E A
Invalid specification of base tables for LIST
- One of the following errors was detected in the specification of the tables on which to base the list to be created:
- A viewed table was specified
- A shared table was specified
- A table created with WITHOUT ROLLBACK was specified
- A table that contains a column that specifies a character set was specified
- A memory database allocation table was specified
- A temporary table was specified
- S: Ignores this SQL statement.
- P: Correct the specification of the tables on which to base the list.
KFPA11774-E A
Base tables for LIST conflict
- A base table for a list used for performing a set operation in the ASSIGN LIST statement differs from the base tables of the other list.
- S: Ignores this SQL statement.
- P: Correct the specified list name if there is an error, and then re-execute the SQL statement.
KFPA11775-E A
Unable to define function "aa....aa"."bb....bb" because of same signature as system function
- The specified function "aa....aa"."bb....bb" cannot be defined because it has the same name and SQL parameter configuration as a function provided by the system.
- aa....aa: Authorization identifier
- bb....bb: Routine identifier
- S: Ignores this SQL statement.
- P: Change the routine identifier and re-execute this SQL statement.
KFPA11776-E A
Invalid specification in ASSIGN LIST statement
- One of the following errors occurred in the ASSIGN LIST statement.
- An arithmetic operation, date operation, concatenation operation scalar function, CASE expression, CAST specification, or component specification is specified in a search condition.
- A column in a search condition is qualified by a table name or a correlation name.
- A column is specified on both sides of the comparison operator in a search condition.
- A column is specified in value expression 2 or 3 of the BETWEEN predicate in a search condition.
- A literal, or a USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP value function is specified on both sides of the comparison operator in a search condition.
- A literal, or a USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP value function is specified on the left side of the IN predicate in a search condition.
- A literal, or a USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP value function is specified in value expression 1 of the BETWEEN predicate in a search condition.
- A literal, or a USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP value function is specified on the left side of the LIKE predicate or XLIKE predicate in a search condition.
- A literal, or a USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP value function is specified on the left side of the SIMILAR predicate in a search condition.
- A user-defined function other than a plug-in function for packaging logic that uses an index is specified.
- No ANY subscript is specified in the repetition column in a search condition.
- A predicate for a repetition column is negated by NOT.
- A condition expression specifying ANDNOT is negated by NOT.
- An IS FALSE or IS UNKNOWN Boolean predicate is specified.
- An IN predicate specifying a subquery is negated by NOT.
- A Boolean predicate is negated by NOT.
- Two or more send functions for passing inter-function values that can store inter-function values were specified in a list.
- Set operations cannot be performed on a list that stores inter-function values (for details on set operations on lists that store inter-function values, see the HiRDB Version 9 UAP Development Guide).
- An XMLQUERY function, XMLSERIALIZE function, XMLPARSE function, or an XMLEXISTS predicate without an XML query context item for a column specification was specified.
- S: This SQL statement is ignored.
- P: Correct the SQL statement, and then re-execute it.
KFPA11777-E A
Unable to execute due to aa....aa bb....bb."cc....cc" in use
- During pre-processing of the SQL statement, the resource indicated in the message was being used by another user. For this reason, the SQL statement cannot be executed.
- aa....aa: Type of resource being used
- type: Abstract data type
- routine: Routine
- bb....bb: Authorization identifier
- If the type of resource being used is a routine, ******** is output because the authorization identifier cannot be determined.
- cc....cc: Data type identifier, or routine identifier
- S: Ignores this SQL statement.
- P: After the pre-processing of the SQL statement is completed, re-execute the SQL statement.
KFPA11778-E A
Invalid specification in query with LIST
- One of the following errors occurred in the specification in a query using a list.
- A set function was specified in the SELECT clause of the outermost query.
- A window function is specified in the SELECT clause in the outermost query.
- A subquery was specified in the SELECT clause of the outermost query.
- ROW was specified in the SELECT clause of the outermost query.
- Table-specification.* was specified in the SELECT clause of the outermost query.
- A column specification with a table qualifier was specified in the SELECT clause of the outermost query.
- A column name with a qualifier was specified in the ORDER BY clause.
- For a list that does not store inter-function values, a receive function for passing inter-function values was specified in a projection column.
- More receive functions for passing inter-function values were specified in the projection column than the number of inter-function values that were stored in the list.
- S: Ignores this SQL statement.
- P: Correct the SELECT statement using the list and re-execute.
KFPA11780-E A
No appropriate index on table aa....aa."bb....bb"
- One of the following indexes must be defined in table aa....aa."bb....bb" when the ASSIGN LIST statement is executed:
- The column specified in the search condition requires an index (excluding an index that has an exception key value).
- When a structured repetition predicate is specified in the search condition, an index is required that includes the column specified in the search condition in the structured repetition predicate of the configuration column.
- When an XMLEXISTS predicate is specified in the search condition, the index cannot be used if the index's usage conditions are not satisfied. For details about the usage conditions of indexes, see the HiRDB Version 9 Installation and Design Guide.
- When no search condition is specified, an index (except an index with an exceptional key value, or a plug-in index) is required on the columns (except a repetition column) of the table.
- When using an index that includes repetition columns and other columns in a configuration column and evaluating the predicate for a column that is not a repetition column, an index can be used if a condition is specified in one of the columns in the repetition column.
- A single column index is required in the column of the IN predicate specifying a subquery.
- One of the following indexes must be defined in the column of an IN predicate that specifies a subquery. Case (b) applies only when the SQL optimization mode is set to optimizing mode 2 based on cost.
(a) Single column index
(b) Multicolumn index starting at the column in the IN predicate specifying a query:
Even when the column in the IN predicate that specifies a subquery is not the beginning of a multicolumn index, a comparison predicate (=), NULL predicate (IS-NULL) or IN predicate (IN) with a value specified for the right side, must be specified in the index configuration column in front of this column. However, this excludes indexes that include a repetition column in the index configuration column. For an IN predicate (IN) with a value specified for the right side, the number of values specified must meet one of the following conditions:
When there is one IN column, there are no more than 5 values specified.
When there are two or more IN columns, the total number of values specified in each column must be 5 or less.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Ignores this SQL statement.
- P: Create the required index, and then re-execute the ASSIGN LIST statement.
KFPA11781-E A
Authorization identifier unable to specified for LIST
- An authorization identifier cannot be specified for a list.
- S: Ignores this SQL statement.
- P: Delete the authorization identifier specified for the list and re-execute the SQL statement.
KFPA11782-E A
Column qualified with table specification in ASSIGN LIST statement
- A column name in the search condition of an ASSIGN LIST statement cannot be qualified with a table name or correlation name.
- S: Ignores this SQL statement.
- P: Correct so that the column name is not qualified with a table name or correlation name, and re-execute.
KFPA11783-E A
LIST aa....aa not found in system
- The specified list aa....aa does not exist.
- aa....aa: List name
- S: Ignores this SQL statement.
- P:
- Correct the list name if it is incorrect, and re-execute.
- If the list name is correct, create the list, and then retry the operation.
KFPA11785-E A
List already dropped or altered
- The SQL statement cannot be executed because the list referenced in the SQL statement has already been deleted or re-created.
- S: Ignores this SQL statement.
- P: Change the sequence of this SQL statement so that it will be executed before the list being referenced is deleted or re-created. If there is no need to change the sequence, perform pre-processing again and re-execute.
KFPA11787-E A
Unable to execute "aa....aa" due to existence of bb....bb's LIST "cc....cc" based on the table
- "aa....aa" cannot be executed because of an operation on the base table of list "cc....cc" owned by bb....bb.
- aa....aa
{ DROP TABLE |ALTER TABLE |DROP SCHEMA }
- bb....bb: Authorization identifier
- cc....cc: List name
- S: Ignores this SQL statement.
- P: Delete all lists based on the table in question, and then retry the operation.
KFPA11791-E A
Number of RDAREAs not equal to that of table partitions
- The specified number of index-storage RDAREAs is invalid.
- In the case of a partitioning key index, specify the same number of index-storage RDAREAs as the number of RDAREAs for storing the row-partitioned table.
- In the case of a non-partitioning key index, specify the same number of index-storage RDAREAs as the number of RDAREAs for storing the row-partitioned table. Or, specify the same number of index-storage RDAREAs as the number of back-end servers.
- If TYPE is specified (format 2), specify the same number of index-storage RDAREAs as the number of table-storage RDAREAs.
- For matrix partitioning tables, specify the same number of index storage RDAREAs as RDAREAs storing matrix partitioning tables.
- Or, an error was detected in the number of RDAREAs storing columns specifying the BLOB type or LOB columns with LOB attributes.
- S: Ignores this SQL statement.
- P: Match the specified number of index-storage RDAREAs or the number of LOB column storage RDAREAs and re-execute.
KFPA11793-E A
Invalid RDAREA "aa....aa" for index
- Index-storage RDAREA aa....aa with partitioning specified does not correspond to an RDAREA with boundary-value partitioning or hash partitioning.
- aa....aa: Name of the invalid index-storage RDAREA
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute the job.
KFPA11795-E A
Number of partitioning aa....aa exceed bbbb
- The number of duplicates-exclusion RDAREAs that can be specified during table or index partitioning has exceeded the maximum.
- aa....aa: Processing subject
{ table |index }
- bbbb: Maximum number of duplicates-exclusion RDAREAs { 1024 | 4096 }
- S: Ignores this SQL statement.
- P: Correct so that the number of duplicates-exclusion RDAREAs does not exceed the maximum and re-execute.
KFPA11796-E A
Unable to specify same RDAREA "aa....aa"
- RDAREA that is the same as the previous storage RDAREA cannot be specified.
- aa....aa: Table storage RDAREA
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute the job.
KFPA11797-E A
Invalid specification for "WITHOUT ROLLBACK" table
- The WITHOUT ROLLBACK option cannot be specified for any of the following tables:
- Non-FIX tables
- Tables containing a BLOB
- Tables with a LOCK PAGE specification
- Tables defining a foreign key
- The following items cannot be specified for a table for which the WITHOUT ROLLBACK option is specified:
- CHANGE LOCK PAGE option of ALTER TABLE
- S: Invalidates the transaction.
- P: If the executed SQL statement is CREATE TABLE, correct the SQL statement and re-execute. If the executed SQL statement is ALTER TABLE, delete the SQL statement.
KFPA11798-E A
Invalid usage of DEFAULT clause for column or SQL variable "aa....aa", code=bb
- The DEFAULT clause specification is invalid in the following cases:
- During table definition
- During table definition update (during DEFAULT clause setting or DEFAULT clause deletion)
- During SQL variable declaration in routine definition
- aa....aa: Alias
- bb: Reason code
- The meanings of the reason codes are as follows:
Reason code | Meaning |
---|
01 | The DEFAULT clause and WITH DEFAULT cannot be specified simultaneously. |
02 | The DEFAULT clause cannot be specified for a repetition column. |
04 | The DEFAULT clause cannot be specified for a reserved column. |
06 | One of the following values, that cannot be specified as the DEFAULT clause, was specified:
- A value that cannot be converted into the data type of the specified column or SQL variable
- A value greater than the definition length of the specified column or SQL variable
- A value whose upper valid digit becomes invalid
- A value that exceeds the definition length of the column as a result of conversion due to the character set specification
- A value that cannot be converted into the character set of the specified column
|
07 | The USER value function cannot be specified in a column or SQL variable with a data type other than CHAR, MCHAR, VARCHAR, or MVARCHAR. |
08 | The CURRENT_DATE value function cannot be specified in a column or SQL variable with a data type other than DATE or CHAR(10). |
09 | The CURRENT_TIME value function cannot be specified in a column or SQL variable with a data type other than TIME or CHAR(8). |
10 | NULL cannot be specified in a column with the NOT NULL constraint. |
12 | A DEFAULT clause cannot be specified for columns or SQL variables of the following data types:
- BLOB
- Abstract data type
- BINARY 32,001 bytes or larger
|
14 | The CURRENT_TIMESTAMP value function cannot be specified in a column or SQL variable with a data type other than TIMESTAMP, CHAR(19), CHAR(22), CHAR(24), or CHAR(26). |
15 | The following cannot be specified in a DEFAULT clause when a character set is defined on the column:
- CURRENT_TIME value function
- CURRENT_DATE value function
- CURRENT_TIMESTAMP value function
|
31 | DROP DEFAULT cannot be specified for a column for which no DEFAULT clause was specified. |
32 | WITH DEFAULT cannot be specified for a column for which a DEFAULT clause was specified. |
33 | The following cannot be specified in a DEFAULT clause which is also specifying the character set:
- CURRENT_TIME value function
- CURRENT_DATE value function
- CURRENT_TIMESTAMP value function
|
34 | A DEFAULT clause cannot be specified for an insert history maintenance column in a falsification prevented table where a deletion prevented duration has been specified. |
- S: Ignores this SQL statement.
- P: Correct the SQL statement, and then re-execute (for reason code 31 or 32, delete the SQL statement).
KFPA11800-E A
Zero divisor in arithmetic operation for aa....aa data type
- Division by zero error occurred during an arithmetic operation on data type aa....aa.
- aa....aa: Data type resulting in the division by zero error:
{ INTEGER |DECIMAL |SMALLFLT |FLOAT
|INTERVAL YEAR TO DAY
|INTERVAL HOUR TO SECOND |SMALLINT }
- S: Ignores this SQL statement.
- P: Modify the arithmetic expression so that division by zero does not occur, then re-execute.
KFPA11801-E A
Overflow in aa....aa for bb....bb data type
- Overflow occurred during operation aa....aa on data type bb....bb.
- aa....aa: Type of operation resulting in the overflow:
{ addition |subtraction |division |multiplication
|sign inversion |scalar function "INTEGER"
|scalar function "DECIMAL" |scalar function "DAYS"
|scalar function "DATE" |correction
|scalar function "ABS" |scalar function "MOD"
|java routine | c routine}
- bb....bb: Data type resulting in the overflow
{ integer |smallint |decimal |smallflt |float
|date |interval year to day |time
|interval hour to second }
- S: Ignores this SQL statement.
- P: Modify the arithmetic expression so that overflow does not occur, then re-execute.
- Action
- In either of the following circumstances, overflow might be avoidable if 38 is specified in the operand pd_sql_dec_op_maxprec:
- The type of operation resulting in the overflow is scalar function DECIMAL and the data type resulting in the overflow is FLOAT.
- The type of operation resulting in the overflow is scalar function MOD and the data type resulting in the overflow is DECIMAL.
KFPA11802-E A
Overflow in aa....aa FUNCTION "bb....bb" for cc....cc data type
- An overflow occurred during the processing of the set or window function bb....bb whose other data type is cc....cc.
- If SUM or AVG is displayed as the function, overflow occurred while adding the data subject to processing.
- If COUNT is displayed as the function, the number of data items subject to processing exceeded 2,147,483,647.
- If COUNT_FLOAT is displayed as the function, the number of data items subject to processing exceeded the range that can be represented in a floating-point number#.
- aa....aa: specified function:
{ SET |WINDOW }
- bb....bb: the type of the set or window function:
{ SUM |AVG |COUNT | COUNT_FLOAT }
- cc....cc: Data type resulting in the overflow:
{ integer |smallint |decimal |smallflt |float }
- S: Ignores this SQL statement.
- P: Eliminate the cause of the error, such as by reducing the number of data items subject to processing, then re-execute.
- #: The range of floating-point numeric values depends on the hardware representation.
- Action
- If overflow occurred while adding the data subject to processing using the set function SUM or AVG and the data type resulting in the overflow is DECIMAL, overflow might be avoidable if 38 is specified in the operand pd_sql_dec_op_maxprec.
KFPA11803-E A
Duplicate key value in unique index id=aa....aa
- An attempt was made to add a duplicated column value to an index with UNIQUE specified or with a primary key. Or, an attempt was made to update a column value to a duplicated value.
- aa....aa: Index number
- S: Ignores this SQL statement.
- P: Correct the duplicated column value and re-execute the SQL statement.
- Search the dictionary table if you want to identify the index name from the index number.
KFPA11804-E A
Invalid operation code aaaa
- RPC interface from the client is invalid:
- Specified operation code is invalid.
- Specified system type is invalid.
- aaaa: Operation code
- S: Ignores this request.
- P: Check the UAP preprocess, compilation, or linkage for an error. If there is no error, contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPA11805-E A
Invalid section number
- Section number is outside the range 1 to 4095.
- S: Ignores this request.
- P: Check the UAP preprocess, compilation, or linkage for an error. If there is no error, contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPA11806-E A
Current number of elements exceeds aa....aa, columnid=bb....bb
- The number of elements in the column added by the ADD clause in the UPDATE statement is greater than the maximum allowable number of elements.
- aa....aa: Maximum number of elements
- bb....bb: The column number that indicates which column caused the error
- S: Invalidates this transaction.
- Action
- Use the ALTER TABLE statement to increase the maximum number of elements and re-execute.
KFPA11807-E A
Invalid update option
- Update option is invalid for DECLARE CURSOR.
- S: Ignores this request.
- P: Check the UAP preprocess, compilation, or linkage for an error. If there is no error, contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPA11808-E A
Row length for work list bbbbbbb exceeds maximum list row length aaaaa
- Row length bbbbbbb is greater than maximum length aaaaa that can be stored as a work table.
- aaaaa: Maximum length of row that can be stored
- bbbbbbb: Length of row that was to be stored
- S: Invalidates this transaction.
- P: Re-evaluate the number of columns and column size specified in the SELECT statement and specify a value that is no greater than the maximum length of the work table.
KFPA11809-I A
Row length bb....bb exceeds aa....aa in RDAREA cc....cc
- Storage length bb....bb for the row for which INSERT or UPDATE SET is specified, or for which a data load was attempted, exceeds maximum row length aa....aa.
- aa....aa: Maximum length of row that can be stored
- bb....bb: Length of row that was to be stored
- cc....cc: RDAREA name
- S: Invalidates this transaction.
- Action
- When issued by an operation on a non-FIX temporary table
- Take one of the following actions, and then re-execute the operation:
- When the client environment variable PDTMPTBLRDAREA is specified:
Change the page length of all the temporary table RDAREAs specified in PDTMPTBLRDAREA to a value greater than bb....bb.
- When the client environment variable PDTMPTBLRDAREA is not specified, or an XDS client is used:
Change the page length of all the temporary table RDAREAs with attributes shared between SQL sessions to a value greater than bb....bb.
- When issued by the SQL statement
- Unload the table, redefine the table in an RDAREA with a page length longer than bb....bb, and then reload the table.
- When issued by the database load utility (pdload)
- Use the database structure modification utility (pdmod) to change the page length of the RDAREA to a value greater than bb....bb, and then re-execute the command.
KFPA11810-E A
Duplicate key value detected in unique index while loading index index id=aa....aa
- This message is output in either of the following circumstances:
- A duplicated key value was detected while loading an index for which UNIQUE is specified or an index for the primary key.
- A non-FIX table was unloaded in binary format, and then an attempt was made to load the data into a FIX table.
- aa....aa: Index identifier
- S: Invalidates this transaction.
- P:
- When a duplicated key value was detected:
- Delete the index, correct the duplicated key value, and then execute CREATE INDEX. If CLUSTER KEY or PRIMARY KEY is specified for the table, restore the RDAREA from a backup that was made before execution of the pdload command, correct the duplicated column values in the input data, and then re-execute the pdload command.
- When a non-FIX table was unloaded in binary format, and an attempt was made to load the data into a FIX table:
- When a non-FIX table is unloaded in binary format, the data cannot be loaded into a FIX table. However, depending on the data type, invalid input data might have gone undetected and been improperly loaded, resulting in this duplicate key value error message being output. In that case, check and correct the conditions under which the data is loaded, and then retry the operation.
KFPA11811-E A
MASTER DIRECTORY RDAREA full
- The master directory RDAREA does not have enough space for an RDAREA, table, index, or viewed table to be defined.
- S: Invalidates the processing and terminates abnormally.
- Action
- Expand the master directory RDAREA with the database structure modification utility. Or, delete unneeded tables or indexes and re-execute.
KFPA11812-E A
Number of aa....aa exceeds bbbb in RDAREA "cc....cc"dd....dd
- The definition information for the specified table and sequence generator, or index definition information, exceeds the maximum bbbb that can be defined in RDAREA cc....cc.
Or, the number of list definitions exceeds the maximum bbbb that can be defined in a list RDAREA where the list definitions are not on hold (server name dd....dd). - aa....aa: Type of definition information:
- TABLE and SEQUENCE: Table and sequence generator
- INDEX: Index
- LIST: List
- bbbb: Maximum number of definitions
- cc....cc: RDAREA name
- ******* is displayed in the case of a list RDAREA.
- dd....dd: Server name
- The following is displayed in the case of a list RDAREA:
- server=server-name
- S: Invalidates this processing.
- P: Take one of the following actions:
- When the attempt was to define a table and sequence generator or index
Either define the table and sequence generator, or index, in another RDAREA, or delete the table and sequence generator, or the index, from the applicable RDAREA.
- When the attempt was to define a list:
Delete unneeded lists that have been defined in the applicable server. If the same error occurs, even after unneeded lists have been deleted, contact the HiRDB administrator.
- Action
- When the attempt was to define a list:
Use the database structure modification utility (pdmod) to add a list RDAREA to the applicable server. If the list RDAREA is shut down, release it from shutdown status by correcting the error.
If the number of lists that can be created in the list RDAREA is insufficient, the KFPA11812-E error may occur temporarily when the following occurs:
After a server process terminates, the same user reconnects to the client and executes an ASSIGN LIST statement before completion of the recovery process called for by the return of the KFPA11812-E error.
KFPA11813-E A
SQL cannot be executed because aa....aa in XDS
- This SQL statement cannot be executed because the work table and index cannot be defined.
- aa....aa: Cause of the error
- the row length is too long: The row length exceeds the page length.
- the index key length is too long: The index key length exceeds the maximum length.
- the number of columns exceeds 3000: The number of columns exceeds 3,000.
- S: Ignores this SQL statement.
- P:
- If aa....aa is the row length is too long:
- Either correct the SQL statement so that the row length of the work table decreases, or increase the page length of the work table DB area, and then re-execute. For details about how to calculate row lengths, see the common rules for CREATE TABLE in the manual HiRDB Version 9 SQL Reference.
- If aa....aa is the index key length is too long:
- Either correct the SQL statement so that the key length of the work table index column decreases, or increase the page length of the work table DB area, and then re-execute.
- For details about how to calculate key lengths, see the description of CREATE INDEX in the manual HiRDB Version 9 SQL Reference.
- If aa....aa is the number of columns exceeds 3000:
- P: Correct the SQL statement so that the work table number of columns decreases, and then re-execute.
- For details about the work table and index configuration columns, see HiRDB Version 9 UAP Development Guide.
KFPA11814-E A
DATA DIRECTORY RDAREA full
- The data directory RDAREA does not have enough space for storing the management information about a table partitioned by values or an index.
- S: Invalidates the processing and terminates abnormally.
- Action
- Expand the data directory RDAREA with the database structure modification utility. Or, delete an unneeded index or table stored in a partition in a different RDAREA and re-execute.
KFPA11815-E A
aa....aaID not found in DIRECTORY data, RDAREA="bb....bb", ID=cc....cc
- No definition information for the table, index, list, or sequence generator to be processed was found in RDAREA bb....bb.
- aa....aa: Table, index, list, or sequence generator type:
- {TABLE|INDEX|LIST|SEQUENCE}
- bb....bb: RDAREA name
- cc....cc: Table, index, list number, or sequence generator
- S: Terminates abnormally.
- P: Take one of the following actions:
- Table, index, or sequence generator
Ensure that the procedure for RDAREA "bb....bb" is correct and restore the RDAREA.
- List
Re-create the list specified by the SQL statement.
KFPA11821-E A
More than aa....aa or invalid length in SQL
- The length of an SQL statement exceeds aa....aa bytes. Or, the length is invalid.
- aa....aa: Length of SQL statement
- S: Ignores this request.
- P: Correct the length of the SQL statement and re-execute.
KFPA11822-E A
Unable to access table due to check pending status, tableID=aa....aa, RDAREA="bb....bb", constraint type=ccccccc
- The table denoted by aa....aa is unavailable for retrieval or updating because it is in check pending status.
- aa....aa: Table number for the table in check pending status
- bb....bb: Name of the RDAREA storing a table in check pending status
- ccccccc: Type of constraint defined in the table
- REF: Reference constraint
- CHK: Check constraint
- REF: CHK: Reference and check constraints
- S: Ignores this SQL statement.
- Action
- Use the integrity check (pdconstck) to reset check pending status. For the procedure for resetting check pending status, see the manual HiRDB Version 9 Installation and Design Guide.
KFPA11823-E A
Unable to execute SQL for definition "aa....aa".bb....bb used by pdrbal
- The following SQL statements cannot be executed because the rebalancing utility is being executed:
- ALTER TABLE
- CREATE INDEX (you cannot define an index for which the number of index-storage RDAREAs does not match the number of table-storage RDAREAs)
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Ignores this SQL statement.
- P: When execution of the rebalancing utility terminates, re-execute the SQL statement.
KFPA11824-E A+L
aa....aa file access error occurred,file name=bb....bb, func=cc....cc, errno=dddd
- Loading of environment variable group file, JAR file, or C library file bb....bb failed.
- aa....aa:
- Environment group: environment variable group file
- JAR: JAR file
- CLIB: C library file
- bb....bb: Name of file (the last 100 bytes only if the file name is longer than 100 bytes)
- cc....cc: Name of function in which error occurred:
- fopen: Open processing
- open: Open processing
- fgets: Read processing
- read: Read processing
- stat: Status acquisition processing
- getcwd: Current directory acquisition processing
- dddd: Error code (errno)
- S: Terminates processing.
- P: Correct the error based on the error code, and then re-execute the operation.
KFPA11827-E A
No available LOB DIRECTORY in RDAREA, RDAREA=aa....aa
- The number of data items in the LOB RDAREA exceeded the management value for the RDAREA.
- aa....aa: Applicable RDAREA name
- S: Ignores this SQL statement.
- Action
- Re-estimate the required size of the applicable RDAREA and expand it. When estimating the required RDAREA size, remember to take into account rows of data length 0. For details about estimating the required RDAREA size, see the HiRDB Version 9 Installation and Design Guide.
KFPA11828-E A
Unable to set non null value at BLOB attribute of sub type because its allocation is not defined, column no=aa....aa, type id=bb....bb, attribute no=cc....cc
- Values of the abstract data type including the BLOB attribute for which a LOB RDAREA name was not specified during table definition cannot be stored in a column of abstract data type or in an attribute of abstract data type.
- aa....aa: The column number indicating which column in the table to be updated caused the error
- bb....bb: Type ID of the abstract data type that includes the BLOB attribute that cannot be stored
- cc....cc: The attribute number that indicates which attribute in the abstract data type is the BLOB attribute that cannot be stored
- S: Invalidates this transaction.
- P: Do not specify a value of the abstract data type including the BLOB attribute for which a LOB RDAREA name was not specified during table definition as an insert value or an update value for the column or attribute that caused the error. Review the data type of the table definition for the column that caused the error.
KFPA11845-E A
Invalid use of RDAREA "aa....aa" errno=b
- One of the following errors was detected:
- When errno=1
Because the specified user RDAREA stores a rebalancing table, it cannot store other tables or indexes.
- When errno=2
Because the specified user RDAREA already stores other tables or indexes, it cannot store a rebalancing table.
- When errno=3
When an index for a rebalancing table is defined, specification of an index-storage RDAREA cannot be omitted.
- aa....aa: RDAREA name
- b: Error code
- S: Ignores this SQL statement.
- P:
- When errno=1 or 2
Change the specified RDAREA name and re-execute the SQL.
- When errno=3
Specify an RDAREA for the index and re-execute the SQL.
KFPA11850-E A
aa....aa was modified after first blocked fetch
- The contents of an SQL descriptor area or character set descriptor area were changed by a FETCH statement during a batch search.
- aa....aa: Name of area that was changed
- SQLDA: SQL descriptor area
- SQLCSNA: Character set descriptor area
- S: Ignores this SQL statement.
- P: Correct the SQL statement so that the contents of the SQL descriptor area or character set descriptor area are not changed.
KFPA11855-E A
Unable to execute remote access SQL. REASON=aa....aa
- Remote access is disabled due to the reason indicated by aa....aa.
- aa....aa: Detailed reason
- MAX RDNODE:
- The maximum number of distributed servers that can be connected simultaneously exceeds the maximum value.
- CHARACTER SET NOT SUPPORTED:
- The current character codes used at the local system are not appropriate for remote access.
- DF NOT SUPPORTED:
- A distributed database facility cannot be used with this HiRDB.
- S: Ignores this SQL statement.
- P: Take one of the following actions:
- MAX RDNODE
- Ensure that the number of distributed servers to be connected simultaneously does not exceed the maximum value. In the HiRDB distributed client facility, a UAP is permitted to connect to only one distributed server at a time.
- CHARACTER SET NOT SUPPORTED
- Do not execute remote access.
- DF NOT SUPPORTED
- Do not perform remote access.
- Action
- CHARACTER SET NOT SUPPORTED or DF NOT SUPPORTED:
The distributed database facility cannot be used in HiRDB Version 9 or later. Check whether the pd_node_name operand is specified in the single-server definition or front-end server definition. If it is specified, delete the pd_node_name operand.
KFPA11875-E A
Specified index already created
- An attempt was made to execute batch index creation for an existing index.
- S: Ignores batch index creation for the specified index and resumes processing.
- Action
- There is no need to execute batch index creation.
KFPA11876-E A
Unable to assign index information file due to not defined "pd_plugin_ixmk_dir", server name=aa....aa
- Although the delayed batch creation of a plug-in index is specified, the name of the directory in which the index information file or HiRDB file system area is to be created is not specified in the pd_plugin_ixmk_dir operand in the server definition aa....aa. Therefore, the index information file cannot be created.
- aa....aa: Server name
- S: Invalidates this transaction.
- P: If the delayed batch creation of a plug-in index is not needed, specify PDPLGIXMK=NO in the client environment definition.
- Action
- If the delayed batch creation of a plug-in index is needed, specify the name of the directory in which the index information file or HiRDB file system area is to be created in the pd_plugin_ixmk_dir operand in the server definition aa....aa.
KFPA11877-E A
Unable to assign index information file due to no such directory, server name=aa....aa, directory name=bb....bb
- The directory in which the index information file or HiRDB file system area (bb....bb) is to be created, specified in the pd_plugin_ixmk_dir operand in the server definition aa....aa, has not been created. Therefore, the index information file cannot be created.
- aa....aa: Server name
- bb....bb: Name of the directory in which the index information file or HiRDB file system area is to be created, as specified in the pd_plugin_ixmk_dir operand
- S: Invalidates this transaction.
- P: If the delayed batch creation of a plug-in index is not needed, specify PDPLGIXMK=NO in the client environment definition.
- Action
- If the delayed batch creation of a plug-in index is needed, create the index information file directory or HiRDB file system area specified in the pd_plugin_ixmk_dir operand in the server definition aa....aa. Alternatively, specify the name of the directory in which the index information file is to be created in the pd_plugin_ixmk_dir operand in the server definition aa....aa.
KFPA11878-E A
Index information file not available, file=aa....aa, server name=bb....bb
- The contents of the index information file named aa....aa do not match the condition of the database.
- aa....aa: Name of the index information file
- If the name of the index information file exceeds 80 characters, the last 80 characters of the file name are output.
- bb....bb: Server name
- S: Invalidates this transaction.
- Action
- Utility:
- Check whether there are utilities that are simultaneously using the same index information file, and re-execute the database load utility, database reorganization utility, or rebalancing utility.
- UAP:
- Because the index information file cannot be created together with the plug-in index, use the database reorganization utility (pdrorg -k ixrc command) to re-create the plug-in index.
KFPA11879-E A
Index aa....aa in cc....cc must be bb....bb to access table
- Index aa....aa stored in RDAREA cc....cc was not created by the batch method. Or, the table cannot be accessed because its index is unusable (is not completed).
This error occurs primarily in situations where the following operations were performed: - The database load utility (pdload -i n) or the database reorganization utility was used to reload table data (pdrorg -k rorg/reld -i n), but it accessed an index that was not batch-created.
- For table data stored in partitions in multiple RDAREAs, after performing the reorganization of the table data stored in a specific RDAREA, an attempt was made to access an index that had not yet been created.
- If a memory database is used, this error occurs primarily in situations where the following operations were performed:
- DEALLOCATE MEMORY TABLE was executed after XDS terminated, and an attempt was made to access the index of a table for which an index was not recreated
- While XDS is running, an attempt was made to access the index of a table waiting to be allocated to memory, but the index is unfinished. This occurs in the following cases:
While XDS is running, ALLOCATE MEMORY TABLE was executed on a table whose index was unfinished, and the access was attempted before XDS restarted.
If the system switchover facility is used, while XDS was stopped, it switched over to the standby system when an error occurred in database export processing, and then accessed the memory database allocation table on the disk database.
- aa....aa: Accessed index number
- bb....bb: Code indicating batch index creation:
{ loaded }
- cc....cc: Name of RDAREA storing the index
- S: Ignores this SQL statement, or invalidates the transaction.
- Action
- Take one of the following corrective actions, and then re-execute the SQL statement in this transaction:
- If you have the required index information file, execute batch index creation (pdrorg -k ixmk).
- Re-create the index (pdrorg -k ixrc).
- In addition, review operations to make sure that indexes are not accessed in an unfinished state.
KFPA11880-E A
Index information file open error,file name =aa....aa errno=bb....bb
- Index information file open processing failed during index information file creation.
- aa....aa: Name of index information file
- bb....bb: Error code
- If the error occurred in a HiRDB file system area, a HiRDB file system area error code is displayed. For the HiRDB file system area error codes, see 5.1 Error codes returned from HiRDB file system access requests.
- S: Invalidates this transaction.
- Action
- Refer to errno.h or the applicable OS manual to check the cause of the error indicated by the error code (external integer variable indicating the error status) and take action appropriate to the error cause as listed below, then re-execute the database load utility, database reorganization utility, rebalancing utility, or UAP.
Error cause | Explanation | Action |
---|
ENOENT, ENAMETOOLONG | File name is invalid. | Specify the correct index information file name and path name. |
EMFILE | The maximum number of files that can be opened for processing was reached. | Revise the estimate of the number of files that can be opened per process of the OS parameter, or specify the index creation method as the index update mode (-i s), and re-execute. |
KFPA11881-E A
Index information file aa....aa error, file name=bb....bb errno=cc....cc
- Processing aa....aa on an index information file failed during creation of the index information file.
- aa....aa: Type of error
- bb....bb: Name of the index information file
- cc....cc: Error code
- If the error occurred in a HiRDB file system area, a HiRDB file system area error code is displayed. For the HiRDB file system area error codes, see 5.1 Error codes returned from HiRDB file system access requests.
- S: Invalidates either this utility or the UAP.
- Action
- Based on the error code (an external integer variable that indicates the error status), check the cause of the error by referring to the errno.h file and the OS manual. Take an appropriate action according to the following list of causes of the error. After taking corrective action, take either of the following measures:
- For a utility:
- To create an index, re-execute the database load utility, database reorganization utility, or rebalancing utility to create a new index information file.
- For a UAP:
- If the error code is EIO, re-create the index. In other cases, re-execute the UAP.
Error cause | Explanation | Action |
---|
ENOSPC | Directory containing the index information file is full. | Delete unneeded files from the directory. |
KFPA11882-E A
System call error func=aa....aa, errno=bb....bb
- A system call error occurred during creation of an index information file.
- aa....aa: Type of system call
- bb....bb: Error code
- S: Invalidates this utility.
- Action
- Refer to errno.h or the applicable OS manual to eliminate the cause of the error indicated by the error code (external integer variable indicating the error status), then re-execute the database load utility or database reorganization utility.
KFPA11883-E A
Unable to use index records in aa....aa for bb....bb.cc....cc
- Because the contents of the specified index information file do not match the table data, the index information file cannot be used for batch creation of the index.
- aa....aa: Name of index information file
- bb....bb: Authorization identifier
- cc....cc: Table identifier
- S: Ignores batch index creation for the specified index and resumes processing.
- Action
- If an index with batch index creation specified is necessary, reorganize the table (pdrorg -k rorg -t table-name control-information-file-name).
KFPA11884-E A
Index information file used by other job filename=aa....aa
- An attempt was made to execute the database load utility, database reorganization utility, or rebalancing utility by specifying file aa....aa in an index information file while it was being accessed by another process.
- aa....aa: Name of the index information file
- S: Invalidates this utility.
- Action
- Change the name of the index information file and re-execute the database load utility, database reorganization utility, or rebalancing utility.
KFPA11886-E A
Multi-value columns in multi-column index must have same number of elements [, indexid=aa....aa]
- The repetition columns comprising an index have mismatched numbers of elements. Therefore, the following SQL statements and utility cannot be executed:
- CREATE INDEX
- INSERT statement
- UPDATE statement
- Database Load Utility (pdload)
- S: Invalidates this transaction.
- P: Correct the UAP so that the repetition columns comprising the index have consistent numbers of elements, and then re-execute.
KFPA11890-E A
Unable to call PLUGIN aa....aa, reason code="bb....bb"
- The plug-in aa....aa was not called due to the reason indicated in "bb....bb".
- aa....aa: Plug-in name
- bb....bb: Reason code
- UNAVAILABLE:
- The plug-in aa....aa is unavailable.
- UNDEFINED:
- The pdplugin operand for the plug-in aa....aa is not defined. Or, an error occurred during the initialization of the plug-in.
- S: If this error was caused by the execution of the SQL, the system cancels the execution of the SQL.
- Action
- Reason code UNAVAILABLE:
- Take an appropriate action based on the KFPYnnnnn (nnnnn: a 5-digit message number) message that was output prior to this message. Alternatively, execute only those SQL statements that do not require the plug-in aa....aa.
- Reason code UNDEFINED:
- Stop the HiRDB system, code a use declaration (pdplugin operand) for the plug-in aa....aa in the system common definition, and then activate the HiRDB system.
- In other cases, take an appropriate action based on the KFPYnnnnn (nnnnn: a 5-digit message number) message that was output prior to this message.
- Alternatively, execute only those SQL statements that do not require the plug-in aa....aa.
KFPA11891-E A
Unable to access LOB RDAREA, RDAREA name=aa....aa, tableID=bb....bb, reason code=c
- The area aa....aa in LOB RDAREA with the table ID bb....bb could not be accessed due to reason code c.
- aa....aa: Name of the RDAREA to which access was attempted
- bb....bb: The number of the table to which access was attempted
- c: Reason code indicating the condition of the LOB RDAREA
- 1: LOB RDAREA initialization status
- 3: LOB RDAREA is in reload-not-completed data status
- S: Invalidates this transaction.
- O:
- If the reason code is 1, execute the PURGE TABLE statement, pdload (with -d specified), or the reinitialization of the table storage RDAREA associated with the LOB RDAREA, to put the area in an available status. If the reason code is 3, restore the LOB RDAREA from the backup data and enable the LOB RDAREA.
KFPA11892-E A
Too many duplicate element values within row in index on aa....aa column, index id=bb....bb
- The number of duplicate elements in the same row in a repetition column exceeded the maximum value of the number of duplicate keys for a repetition column index.
Another possibility is that the number of duplicate XML element values in the same row in an XML-type column exceeded the maximum value for the number of duplicate keys in a substructure index. - aa....aa:
- For a repetition column (repetition column index): Multi-value
- For an XML-type column (substructure index): XML TYPE
- bb....bb:
- If a data manipulation SQL statement is executed:
- The index ID
- If either CREATE INDEX or the batch creation of an index is executed:
- CREATE
- S: Invalidates this transaction.
- P:
- When aa....aa is Multi-value (when data manipulation SQL or batch index creation was executed):
- Check the data specified in the repetition column index so that the number of duplicate elements per row does not exceed the value obtained from the formula below.
- When aa....aa is XML TYPE (when data manipulation SQL or batch index creation was executed):
- Check the data specified in the XML-type column index so that the number of duplicate XML element values per row does not exceed the value obtained from the following formula:
- number-of-duplicates =
(
index-storage-RDAREA-page-size
0.95
- 82)
4
- 1
- O:
- When aa....aa is Multi-value (when CREATE INDEX was executed):
- Check the data in the repetition column on which an attempt to define an index was made to ensure that the number of duplicate elements per row does not exceed the value obtained from the formula below.
- When aa....aa is XML TYPE (when CREATE INDEX was executed):
- Check the data in the XML-type column on which an attempt to define an index was made to ensure that the number of duplicate XML element values per row does not exceed the value obtained from the following formula:
- number-of-duplicates =
(
index-storage-RDAREA-page-size
0.95
- 82)
4
- 1
KFPA11893-E A
RDAREA not specified for aa....aa bb....bb
- No storage RDAREA is specified in ALTER TABLE ADD RDAREA for the index, primary key, cluster key, or column.
- aa....aa:
(INDEX |CLUSTER KEY |PRIMARY KEY |COLUMN}
- bb....bb:
- When aa....aa is INDEX
index-identifier
- When aa....aa is COLUMN
column-name
- When aa....aa is CLUSTER KEY or PRIMARY KEY
Blank (nothing is output)
- S: Ignores this SQL statement.
- O: Specify a storage RDAREA and re-execute.
KFPA11894-E A
Duplicate aa....aa "bb....bb" specified
- A column name or index name is specified more than once in ALTER TABLE ADD RDAREA.
- aa....aa:
{ INDEX |COLUMN }
- bb....bb:
- When aa....aa is INDEX
index-identifier
- When aa....aa is COLUMN
column-name
- S: Ignores this SQL statement.
- O: Specify the column name or index name only once and re-execute.
KFPA11895-E A
Failed to load PLUGIN, shared library=aa....aa, external function=bb....bb, reason=cc....cc
- The plug-in could not be loaded.
- aa....aa: Name of the shared library#
- bb....bb: Name of the external routine#
- #: If the name of the shared library or the external routine is less than or equal to 64 bytes, HiRDB outputs the entire name; if it is greater than 64 bytes, HiRDB outputs the first 62 bytes followed by two periods (..).
- cc....cc: Reason for the error
- NO LIBRARY:
- The specified library was not found.
- NO FUNCTION:
- The specified external routine was not found.
- NO PERMISSION:
- The user does not have access privilege for the library.
- NO SPACE:
- Either the area in which to load the library was unavailable or a memory shortage occurred.
- BROKEN:
- Either a non-library file was specified or the library is damaged.
- S: Either ignores this SQL statement or invalidates the transaction.
- Action
- cc....cc: NO LIBRARY
- Specify an existing library name and re-execute.
- cc....cc: NO FUNCTION
- Specify an existing external routine name and re-execute.
- cc....cc: NO PERMISSION
- Grant the user the necessary access privilege and re-execute.
- cc....cc: NO SPACE
- Re-execute the UAP. If this error persists, notify the HiRDB administrator.
- cc....cc: BROKEN
- Specify the correct library and re-execute.
KFPA11896-E E+L
Invalid return information for PLUGIN function, shared library=aa....aa, external function=bb....bb
- The information returned by the plug-in implementation function is invalid.
- aa....aa: Name of the plug-in shared library#
- bb....bb: Name of the plug-in implementation function (external routine name)#
- #: If the name of the shared library or the plug-in implementation function is less than or equal to 64 bytes, HiRDB outputs the entire name; if it is greater than 64 bytes, HiRDB outputs the first 62 bytes followed by two periods (..).
- S: Terminates abnormally.
- P: Notify the HiRDB administrator.
- Action
- Contact the customer support center.
KFPA11897-E A
Registry access error,code=a
- When code=1 is displayed, processing cannot continue because the referenced registry information has been updated.
When code=2 is displayed, other processing tried to update the referenced registry information. - a: Error code
- S: Terminates processing.
- P: When code=1 is displayed, re-execute the SQL; when code=2 is displayed, re-execute the command that caused the error.
KFPA11898-E A
Unable to add RDAREA for column "bb....bb"
- One of the following errors was detected for a column specified in ALTER TABLE:
- The column is not a BLOB type column or an abstract data type column.
- An ALLOCATE clause is specified for the BLOB type.
- A storage RDAREA is specified for an abstract data type column without specifying an ALLOCATE clause.
- aa....aa: Name of column involved in the error
- S: Ignores this SQL statement.
- P: Correct the error concerning the column and re-execute.
KFPA11899-E A
Unable to use "aa....aa", due to unsupported facility in XDS
- Facility aa....aa is not supported in the XDS, so it cannot be used.
- aa....aa: Unsupported facility name
aa....aa | Unsupported facility name |
---|
ARRAY | Facility that uses an array |
EXTENDED STATEMENT NAME | Extended statement name |
EXTENDED CURSOR NAME | Extended cursor name |
CHARACTER SET | Character set |
MULTI-VALUE COLUMN | Repeated column |
GET DIAGNOSTICS | Getting diagnostic information |
JAR | INSTALL JAR, REPLACE JAR, and REMOVE JAR |
CLIB | INSTALL CLIB, REPLACE CLIB, and REMOVE CLIB |
XA INTERFACE | XA interface |
COMMAND EXECUTE | Execute command from UAP |
OPNR | Open cursor declared multiple times for the same SQL statement identifier |
CALL COMMAND | CALL COMMAND statement |
DEFINITION SQL | Call for the definition SQL or the routine that contains the definition SQL |
PURGE TABLE | Call for the PURGE TABLE statement or the routine that contains the PURGE TABLE statement |
COMMIT IN ROUTINE | Call for the routine that contains the COMMIT statement |
ROLLBACK IN ROUTINE | Call for the routine that contains the ROLLBACK statement |
WRITE SPECIFICATION | Execution of the SQL statement that specified WRITE to the table in the RDAREA (if an XDS client was used) |
- S: Ignores this SQL statement.
- P:
- If aa....aa is DEFINITION SQL:
- Execute the facility in the client library used for the server providing the primary facilities or in the database definition utility (pddef).
- Execute the routine containing the definition SQL from the client for the server providing the primary facilities.
- If aa....aa is other than DEFINITION SQL:
- Correct the SQL statement so that the unsupported facilities are not used, and then re-execute.
- If you are working on a table that is not the memory database allocation table, execute from the client for the server providing the primary facilities.
- For a list of unsupported facilities, see Limitations regarding SQL when using the memory database description of the relevant scalar function in the manual HiRDB Version 9 SQL Reference.
KFPA11900-E A
Thread lock error occurs in management for LIST
- A lock error occurred during list management.
- S: Performs the following:
- SQL statement
Ignores this SQL statement.
- pdmod
Continues processing.
- P: Perform the following:
- SQL statement
Re-execute the SQL.
- pdmod
Re-create the list.
KFPA11901-E A
Execution or reference of SQL requested without normal preparation
- Dynamic execution of an SQL statement was requested before its preprocessing was completed. Or, the FETCH or CLOSE statement for a query specified in the cursor declaration (format 1) was executed before cursor open preprocessing was completed.
- S: Ignores this SQL statement.
- P: Complete the preprocessing and re-execute the UAP.
KFPA11902-E A
Unable to grant access privileges except SELECT privilege on audit trail table
- INSERT, UPDATE, and DELETE privileges for the audit trail table or the viewed table using an audit trail table as its base table were not granted for users other than auditors.
- S: Ignores this SQL statement.
- P: Specify SELECT as the only privilege that can be granted for the audit trail table or the viewed table using an audit trail table as its base table for users other than auditors, and re-execute.
KFPA11903-E A
Unable to grant DBA or connect privilege to auditor aa....aa
- DBA privilege cannot be granted to auditor aa....aa, or the password of auditor aa....aa cannot be changed using GRANT CONNECT.
- aa....aa: Authorization identifier of the auditor
- S: Ignores this SQL statement.
- P: Grant DBA privilege to a user other than the auditor. Alternatively, change the auditor's password using GRANT AUDIT.
KFPA11904-E A
Unable to grant RDAREA use privileges for RDAREA "aa....aa" because only auditor has privilege to use this RDAREA
- Only the auditor holds use privileges for the RDAREA for storing audit trail tables. Use privileges for the RDAREA for storing audit trail tables cannot be granted to users other than the auditor.
- aa....aa: RDAREA name
- S: Ignores this SQL statement.
- P: Grant usage privilege of another RDAREA.
KFPA11905-E A
Unable to execute aa....aa due to lack of audit privilege
- aa....aa cannot be executed due to lack of the audit privilege.
- aa....aa: One of the following is displayed:
- "CREATE AUDIT"
- "DROP AUDIT"
- "GRANT AUDIT"
- "DROP TABLE" for audit trail table
- S: Ignores this SQL statement.
- P: The auditor must perform this operation.
KFPA11906-E A
Unable to execute "DROP SCHEMA" due to audit trail table existence
- The auditor's schema cannot be deleted because there is an audit trail table.
- S: Ignores this SQL statement.
- P: To delete the auditor's schema, delete the audit trail table before executing this SQL statement.
KFPA11907-E A
Unable to revoke schema or connect privilege of auditor
- The auditor's schema definition privilege or CONNECT privilege cannot be deleted.
- S: Ignores this SQL statement.
- P: Confirm that the privileges will be deleted from the correct user. When deleting the auditor's privileges, delete other privileges also.
KFPA11908-E A
Duplicate audit for "aa....aa" whenever "bb....bb" audittype "cc....cc"
- The audit event specified by CREATE AUDIT was already defined.
- aa....aa: Operation type and index type
Operation type | Event type |
---|
ANY | Not applicable |
SESSION | CONNECT |
DISCONNECT |
AUTHORIZATION |
ANY |
PRIVILEGE | GRANT |
REVOKE |
ANY |
DEFINITION | CREATE |
DROP |
ALTER |
ANY |
ACCESS | SELECT |
INSERT |
UPDATE |
DELETE |
PURGE |
ASSIGN |
CALL |
LOCK |
NEXT VALUE |
ANY |
UTILITY | PDLOAD |
PDRORG |
PDEXP |
PDCONSTCK |
ANY |
- Note: A space is displayed between the operation type and the index type.
- bb....bb: Value specified in the WHENEVER clause
- ANY
- SUCCESSFUL
- UNSUCCESSFUL
- cc....cc: Value specified in the AUDITTYPE clause
- ANY
- PRIVILEGE
- EVENT
- S: Ignores this SQL statement.
- P: Change the audit event and re-execute.
KFPA11909-E A
Specified audit for "aa....aa" whenever "bb....bb" audittype "cc....cc" not defined
- The audit event specified by DROP AUDIT is not specified.
- aa....aa: Operation type and index type
Operation type | Index type |
---|
ANY | Not applicable |
SESSION | CONNECT |
DISCONNECT |
AUTHORIZATION |
ANY |
PRIVILEGE | GRANT |
REVOKE |
ANY |
DEFINITION | CREATE |
DROP |
ALTER |
ANY |
ACCESS | SELECT |
INSERT |
UPDATE |
DELETE |
PURGE |
ASSIGN |
CALL |
LOCK |
NEXT VALUE |
ANY |
UTILITY | PDLOAD |
PDRORG |
PDEXP |
PDCONSTCK |
ANY |
- Note: A space is displayed between the operation type and the index type.
- bb....bb: Value specified in the WHENEVER clause
- ANY
- SUCCESSFUL
- UNSUCCESSFUL
- cc....cc: Value specified in the AUDITTYPE clause
- ANY
- PRIVILEGE
- EVENT
- S: This SQL statement is ignored.
- P: Change the audit event and re-execute.
KFPA11911-E A
Deadlock occurred on aa....aa resource id=bb....bb
- Deadlock occurred.
- aa....aa: Type of resource
- bb....bb: Resource information
- S: Ignores this SQL statement.
- P: Re-execute the SQL statement.
KFPA11912-E A
Insufficient memory for DB exclusive control, reason code=a
- There is not enough work area for exclusive control to function.
- a: Reason code
- 1: There was a shortage of exclusive control resources.
- 2: The number of locked resource requests exceeded the maximum value specified in PDLOCKLIMIT.
- 3: A memory shortage occurred.
- 4: The number of table lock requests exceeded 63 + the value specified in pd_max_access_tables.
- S: Ignores this SQL statement or aborts processing of the utility.
- P:
- If the reason code is 1 or 2:
- Re-evaluate the program from the following viewpoints:
- Can the LOCK statement can be specified. Specify EXCLUSIVE if this is an update SQL statement.
- Can WITHOUT LOCK NOWAIT can be specified. If the program can be modified, modify it, and then re-execute it.
- If the above actions do not resolve the problem, contact the HiRDB administrator.
- If the reason code is 3 or 4:
- Contact the HiRDB administrator.
- Action
- If the reason code is 1:
- Increase the values set in pd_fes_lck_pool_size, pd_lck_pool_size, or pd_lck_until_disconnect_cnt. For details, see the KFPS00443-I message, which is output to the event log (in UNIX, syslogfile) or the message log file.
- If the reason code is 2:
- Increase PDLOCKLIMIT in the client environment definition. For details, see the KFPS00444-I message, which is output to the event log (in UNIX, syslogfile) or the message log file.
- If the reason code is 3:
- Take the following steps to increase the amount of available memory:
- Reduce the number of concurrently executing processes.
- Increase the real memory.
- Increase the swap area.
- Reduce the number of resident processes on the server (the value of pd_process_count).
- If the reason code is 4:
- Start HiRDB with a higher value specified in pd_max_access_tables.
KFPA11913-E A
DB exclusive control error occurred on aa....aa resource id=bb....bb code=cc....cc
- A lock error occurred.
- aa....aa: Type of resource
- bb....bb: Resource information
- cc....cc: Error code
- S: Ignores this SQL statement.
- O: Contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPA11914-E A
Insufficient memory on DYNAMIC_SHMPOOL for DB exclusive control
- Shared memory used for exclusive control is insufficient.
- S: Ignores this SQL statement.
- P: Check whether the UNTIL DISCONNECT specification for LOCK TABLE can be deleted.
- Action
- The value of pd_lck_until_disconnect_cnt in the server definition is incorrect. Check the value and increase it, and then restart the system.
KFPA11917-E A
Closed RDAREA "aa....aa"
- The indicated RDAREA is closed.
- aa....aa: RDAREA name
- S: Terminates processing.
- P: Ask the HiRDB administrator to open the RDAREA, and then re-execute the UAP or utility.
- Action
- Open the RDAREA with the pdopen command.
KFPA11918-E A
Global buffer pool undefined, RDAREA="aa....aa"
- No global buffer pool is defined.
- aa....aa: RDAREA name
- S: Terminates processing.
- P: Contact the HiRDB administrator.
- Action
- With the pdbuffer operand of the system common definition, define a global buffer pool for the corresponding RDAREA.
KFPA11919-E A
Insufficient global buffer, global buffer pool=aa....aa
- There are not enough global buffer sectors.
- aa....aa: Name of global buffer pool
- S: Terminates processing.
- P: Re-execute the UAP. If the same error recurs, contact the HiRDB administrator.
- Action
- Re-evaluate the estimated number of buffer sectors; if necessary, change the number of buffer sectors with the pdbuffer operand of the system common definition.
KFPA11920-E A
RDAREA "aa....aa" held
- The indicated RDAREA is shut down or was shut down due to an error.
- aa....aa: RDAREA name
- S: Terminates processing.
- P: Contact the HiRDB administrator. Reset the RDAREA shutdown status, and then re-execute the UAP or utility.
- Action
- Error shutdown:
- After the RDAREA has been recovered by the database recovery utility, release the RDAREA from shutdown status with the pdrels command.
- Command shutdown:
- Release the RDAREA from shutdown status with the pdrels command.
KFPA11925-E A
Cannot load compression library, name "aa....aa", return code bb, errno=cc....cc
- Compression library aa....aa cannot be loaded for the reason indicated in return code bb and error code cc....cc.
- aa....aa: Name of compression library
- PDZLIB
- bb: Return code
- 8: An error occurred when loading the compression library aa....aa.
- 12: The compression library loaded successfully, but an error occurred during symbol resolution.
- cc....cc: Error code (errno)
- When bb is 8: errno when loading the compression library
- When bb is 12: errno during symbol resolution in the compression library
- S: Invalidates the transaction.
- Action
- Contact the customer support center.
KFPA11927-E A
aa....aa processing error occurred in "bb....bb", rc=cc....cc
- An error occurred in compression or expansion processing, with error return information cc....cc.
- aa....aa: Processing
- Compress: Compression
- Expand: Expansion
- bb....bb: Name of compression library
- PDZLIB
- cc....cc: Error return information
- Return information for the error that occurred in bb....bb while processing aa....aa
- S: Invalidates the transaction.
- P: Contact the HiRDB administrator, and then re-execute the transaction after the HiRDB administrator takes corrective action.
- Action
- Eliminate the cause of the error based on the error return information, and then retry the operation.
Error return information | Action |
---|
A value (-1nnn) less than -1000 | Letting the absolute value of the error return information be the value that results when you add 1,000 to errno (nnn), look up errno (value 1 to 151) in errno.h and in the documentation of the applicable OS. |
-4 | Add the memory required to execute the compression library, about 260 KB, and then retry the operation. |
Other than the above | Contact the customer support center. |
- Legend: nnn: A numeric value from 1 to 151
KFPA11928-I L
RDAREA aa....aa held pdhold command in process
- Specified RDAREA aa....aa is being shut down by the pdhold command.
- aa....aa: RDAREA name
- S: Invalidates this transaction.
- Action
- Recover the RDAREA and re-execute this transaction.
KFPA11929-E A
Insufficient work pool, size=aa....aa, pool size=bb....bb
- There is not enough memory to process an SQL statement.
- aa....aa: Size (in bytes) of area that was to be allocated
- bb....bb: Size (in bytes) of memory pool
- S: Ignores this SQL statement.
- O: Contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPA11930-E A
Insufficient memory on aa....aa, size=bb....bb
- There is not enough memory to process an SQL statement.
- aa....aa: Character string indicating the type of area:
- PROCESS: Process private area
- SHARED: Shared memory
- bb....bb: Size (in bytes) of area that was to be allocated
- If the size of the area cannot be determined, the size is indicated as ********.
- S: Ignores this SQL statement. If a server process is being activated, cancels activation of the process. If there are connections, connection processing is terminated.
- O: Re-execute the UAP. If the same error recurs, contact the HiRDB administrator.
- Action
- Increase the available memory space by the following methods:
- Reduce the number of processes executed concurrently.
- Increase the swap area.
- Add real memory.
- Reduce the value specified in the pd_work_buff_size operand if a large value was specified.
- If this message was issued during activation of a server process, reduce the number of resident server processes (pd_process_count).
KFPA11931-E A
Insufficient pd_max_access_tables,resource id=aa....aa,resource count=bb....bb
- An attempt was made to access more tables or sequence generators than the value of the pd_max_access_tables operand specified in the system common definition (the total number of tables and sequence generators concurrently accessible by one user in one transaction).
- aa....aa: Maintenance information
- bb....bb: Maintenance information
- S: Invalidates the transaction being processed.
- P: Increase the number of times the COMMIT statement is issued and re-execute. If the same message is reissued, contact the HiRDB administrator.
- Action
- Check if the COMMIT statement was issued before the pd_max_access_tables operand value in the common system definition was reached. Or, re-evaluate whether or not the pd_max_access_tables operand value is appropriate to the entire system.
KFPA11932-E A
Number of connect users exceeded max users
- The number of connections to the HiRDB server exceeded the maximum number of concurrent connections. Another possibility is that the maximum number of startup processes was changed to 0 with the pdchprc command.
- S: Ignores this SQL statement. However, if the utility is executing, processing is terminated.
- P: Wait for other user processes to end, and then re-execute the UAP or utility. Use the pdls -d act command to check the user connection status.
- Action
- When HiRDB is operating:
- If you can increase the maximum number of startup processes on an SDS or FES (which you can check with the pdchprc command), use the pdchprc command to set the maximum number of startup processes to a value that is greater than or equal to the total number of UAPs, utilities, and pdorend application processes# that you want to execute simultaneously.
#
The total number of pdorend application processes is calculated as follows:
n: Number of simultaneous executions of the pdorend command
- Take the following actions when the maximum number of startup processes on an SDS or FES is less than the total number of UAPs, utilities, and pdorend application processes that can be executed simultaneously:
(1) If this error message is output when executing a UAP or utility process:
Decrease the number of UAPs or utility processes that can be executed simultaneously.
(2) Take the following actions if this error message is output when executing the pdorend command (if message KFPH27043-E, code=-52 is output after this message):
(a) Decrease the number of pdorend commands that can be executed simultaneously.
(b) Decrease the number of servers that can be executed simultaneously (the number of servers specified in the -s option) for each pdorend command executed.
(c) Reduce the pdorend application process multiplicity (the value specified in the -m option) each time the pdorend command is executed.
- Actions to take before the next normal startup:
- If this error message is output when executing a UAP or utility process:
Specify a large value for the pd_max_users operand if possible.
Specify the pdcltgrp operand in the system definition for the UAP or utility (only pddef is applicable) to be guaranteed.
- If this error message is output when executing the pdorend command (if message KFPH27043-E, code=-52 is output after this message)
Set the specification value of the pd_max_reflect_process_count operand in the system definition to a large value.
KFPA11934-E A
Insufficient memory on communication header, size=aa....aa or communication buffer, size=bb....bb
- A memory shortage occurred in the communication buffer.
- aa....aa: Size of communication header that was to be acquired
- bb....bb: Size of communication buffer that was to be acquired
- S: Invalidates this transaction.
- P: Re-execute the UAP. If the same error recurs, contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPA11935-E A
Unable to execute definition SQL for executing data processing SQL
- A definition SQL cannot be issued from within a transaction that issued a data manipulation SQL.
- S: Ignores this SQL statement.
- P: To issue a definition SQL after issuing a data manipulation SQL, specify the commit (COMMIT) statement and then specify the definition SQL.
KFPA11937-E A
Unable to execute this SQL in XA environment
- This SQL statement cannot be executed in the XA environment.
- S: Ignores this SQL statement.
- P: Delete this SQL statement.
KFPA11938-E A
Unable to modify attributes of abstract data type in which value is NULL
- The value of the abstract data type, which is a NULL value, has not been generated by the constructor function; its attributes cannot be updated.
- S: Ignores this SQL statement.
- P: Use the constructor function to generate the necessary values, and then update the attributes of the abstract data type.
KFPA11939-E A
Total length of attributes of abstract data type too long
- The total length of the attributes of the defined abstract data type is too large.
- S: Ignores this SQL statement.
- P: Reduce the total length by reducing the number of attributes and re-execute. For a description of how to estimate the total length or the maximum allowable value for the total length, see Syntax Create Type in the HiRDB Version 9 SQL Reference.
KFPA11940-E A
Connect command ignored, HiRDB is initializing or terminating
- Connection to HiRDB is disabled because HiRDB is starting or terminating.
- S: Ignores this SQL statement.
- O: If HiRDB is starting, re-execute the UAP after the startup processing terminates.
- If HiRDB is terminating, restart HiRDB and then execute the UAP.
KFPA11941-E A
HiRDB is under termination process
- An execution request was issued during HiRDB termination processing.
- S: Disconnects HiRDB.
- P: Terminate the UAP.
- O: Restart HiRDB, and then re-execute the UAP.
KFPA11945-E A
Unable to expand stack area for thread. size=aa....aa
- The attempt to expand the thread stack area by aa....aa bytes failed.
- aa....aa: Attempted expansion size (in bytes)
- If the area size cannot be determined, the size is indicated as ********.
- S: Either ignores this SQL statement or invalidates the transaction.
- P: Notify the HiRDB administrator.
- O: Notify the HiRDB administrator.
- Action
- Increase the maximum value for the thread stack size maximum value option pd_thread_max_stack_size in the system common definition.
KFPA11948-E A
Unable to aa....aa bb....bb without cc....cc
- Process bb....bb cannot perform aa....aa because cc....cc is not embedded.
When bb....bb is "PARTITIONED BY MULTIDIM", a matrix-partitioned table cannot be defined because HiRDB Advanced High Availability# is not embedded. - #
- HiRDB Advanced Partitioning Option in version 08-05 and earlier.
- aa....aa: {specify|use|invoke}
- bb....bb: {"PARTITIONED BY MULTIDIM"
- |"ALTER TABLE CHANGE RDAREA" statement}
- cc....cc: {Advanced High Availability}
- S: Ignores this SQL statement.
- P: Delete this SQL statement. Alternatively, embed the cc....cc option, and then re-execute the SQL statement.
KFPA11952-E A
Unable to aa....aa due to insufficient bb....bb
- An attempt was made to perform the following processing with a value that exceeded the value defined in bb....bb:
- aa....aa: assign LIST
- bb....bb: Defined operand name{pd_max_list_users|pd_max_list_count}
- S: Ignores this SQL statement.
- P:
- When bb....bb is pd_max_list_users:
- This SQL statement cannot be executed. To execute this SQL statement, increase the specification value of the pd_max_list_users operand.
- When bb....bb is pd_max_list_count:
- Either delete unnecessary lists and re-execute this SQL statement, or increase the specification value of the pd_max_list_count operand and re-execute this SQL statement.
- Action
- Check that the value of bb....bb in the system definition is appropriate.
KFPA11953-E A+L
Unable to execute aa....aa due to bb....bb, cc....cc
- Processing aa....aa cannot be executed because of bb....bb.
- aa....aa: Processing (See Actions.)
- bb....bb: Reason (See Actions.)
- cc....cc: Additional information (See Actions.)
- S: Cancels this transaction.
- Actions
Processing (aa....aa) | Reason (bb....bb) | Additional information (cc....cc) | Action |
---|
HASH JOIN Hash join or subquery hash execution | Insufficient work buffer | size=dd....dd, server=ee....ee dd....dd: Shortfall (in KB) ee....ee: Server name Displayed shortfall is the shortfall at the location where the first shortage was detected, not the entire shortage. | Take one of the following actions:
- Increase the specified value of the pd_work_buff_size operand or the pd_work_buff_expand_limit operand. Alternatively, decrease the specified value of the PDHASHTBLSIZE or pd_hash_table_size operand in the client environment definition.
- Do not select hash join, subquery hash execution using the client environment definition PDADDITIONALOPTLVL or the pd_additional_optimize_level operand. Also, do not specify HASH in the SQL optimization specification for the join method in the SQL statement or the SQL optimization specification in the subquery execution method.
|
Invalid work buffer allocation mode | server=dd....dd dd....dd: Server name | Take one of the following actions:
- Specify pool in the pd_work_buff_mode operand.
- Do not select hash join, subquery hash execution using the client environment definition PDADDITIONALOPTLVL or the pd_additional_optimize_level operand. Also, do not specify HASH in the SQL optimization specification for the join method in the SQL statement or the SQL optimization specification in the subquery execution method.
|
HASH JOIN Hash join or subquery hash execution | Insufficient private process area | size=dd....dd,server=ee....ee,pid=ff....ff dd.....dd: Total buffer length for work table in the applicable server process (KB) ee....ee: server-name ff....ff: Process-ID | An attempt was made to secure increased buffer area for work tables as specified by the pd_work_buff_expand_limit operand, but was not successful because there was insufficient private process area. Take one of the following actions to ensure there is sufficient memory available:
- Reduce the number of concurrently executing processes.
- Increase the swap area.
- Expand real memory.
Alternatively, take one of the following actions and reduce the usage amount of the work table buffer:
- Decrease the value of the PDHASHTBLSIZE operand in the client environment definition or the pd_hash_table_size operand.
- Do not use hash join, subquery hash execution in the PDADDITIONALOPTLVL operand in the client environment definition, pd_additional_optimize_level operand, or ADD OPTIMIZE LEVEL in the SQL compile options. Also, do not specify HASH in the SQL optimization specification of the join method in the SQL statement or the SQL optimization specification of the subquery execution method.
|
KFPA11958-E A
No work HiRDB file system area
- An available HiRDB file system area was not specified for storing a work table.
- S: Invalidates this transaction.
- P: Contact the HiRDB administrator. After the HiRDB administrator finishes the corrective actions, re-execute the transaction.
- Action
- During execution of the database initialization utility:
- Use the pdwork operand in the dictionary server definition or single server definition to specify a HiRDB file system area for storing a work table, then re-execute the database initialization utility.
- Other than above:
- If the pdwork operand is not specified in the server definition, specify the HiRDB file system area with the pdwork operand, and then restart HiRDB or the server.
- If the pdwork operand is specified in the server definition, eliminate the cause of the error based on the KFPH20006-W message that was output when the server starts, and then restart HiRDB or the server.
KFPA11959-E A
HiRDB file "aa....aa" failed, return code=bbbbb,HiRDB file name=cc....cc
- "aa....aa" for HiRDB file cc....cc terminated with return code bbbbb.
- aa....aa: HiRDB file system function
- close: Close HiRDB file.
- create: Create HiRDB file.
- expand: Expand HiRDB file.
- open: Open HiRDB file.
- read: Read HiRDB file.
- write: Write to HiRDB file.
- fstat: Acquire HiRDB file information.
- statfs: Acquire HiRDB file system area information.
- statdk: Acquire disk information.
- bbbbb: Return code
- cc....cc: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file
- If the path name of the HiRDB file exceeds 143 characters, the last 143 characters of the HiRDB file path name are output.
- S: Invalidates this transaction.
- P: Contact the HiRDB administrator.
- Action
- "aa....aa" is expand during execution of the database initialization utility:
- If a HiRDB file system area with no expansion specification in the pdwork operand in the server definition is specified, specify a HiRDB file system area with expansion specified and re-execute the database initialization utility. If this error message is output even though the specified HiRDB file system area includes an expansion specification, either specify the HiRDB file system area with the expansion count increased in the pdwork operand in the server definition, or specify the HiRDB file system area with the area length expanded. Then, re-execute the database initialization utility.
- "aa....aa" is expand during execution of a utility other than the database initialization utility:
- If a HiRDB file system area with no expansion specification in the pdwork operand in the server definition is specified, specify a HiRDB file system area with expansion specified and restart the server. If this error message is output even though the HiRDB file system area includes an expansion specification, either specify the HiRDB file system area with the expansion count increased in the pdwork operand in the server definition, or specify the HiRDB file system with the area length expanded. Then, restart the server.
- In other cases:
- See 5. HiRDB File System Error Codes to eliminate the cause of the error.
KFPA11964-E A
HiRDB file aa....aa error, errno=bb....bb, HiRDB file name=cc....cc
- HiRDB file open or close processing failed.
- aa....aa: HiRDB file system function:
{ open |close }
- bb....bb: Error code for HiRDB file system
- cc....cc: Name-of-HiRDB-file-system-area\Name-of-HiRDB-file
- If the path name of the HiRDB file exceeds 131 characters, the last 131 characters of the HiRDB file path name are output.
- S: Terminates processing.
- P: Contact the HiRDB administrator. After correcting the error, re-execute the UAP.
- Action
- See 5. HiRDB File System Error Codes to eliminate the cause of the error.
KFPA11966-E A+L
Error occurred on transaction transfer, inf1=aa....aa, inf2=bbbb
- An error occurred in transaction processing of the X/Open XA interface.
- aa....aa: Processing during which error occurred:
- Connect: Reconnection with HiRDB
- bbbb: SQL code for the processing during which the error occurred
- S: Terminates processing.
- P: Eliminate the cause of the error based on the SQL code for the processing underway when the error occurred and the client error log trace information (pderr process-number-*.trc), and then retry the operation.
KFPA11980-E A
Transaction branch already determined
- This transaction branch already accepted a completion request from another transaction branch and it has been completed.
- S: Ignores this SQL statement.
- P: SQL cannot be executed in this transaction branch. Terminate the transaction branch.
- O: Inasmuch as a completion request occurred while this transaction branch was being executed, an error may have occurred in the transaction manager. Check the transaction manager's log information.
KFPA11981-E A
Communication error occurred from aa....aa to bb....bb event cc....cc dd....dd ee....ee
- Processing cannot continue due to a communication error.
- aa....aa: Server name (send side)
- If the server name cannot be identified, ******** is displayed.
- bb....bb: Server name (receive side)
- If the server name cannot be identified, ******** is displayed.
- cc....cc: Event that occurred:
- Init: Server initialization
- Netdown: Network error
- System: System error
- Termin: Server termination processing
- Timeout: Timeout
- dd....dd: Debug information 1 (name of the function resulting in the error)
- ee....ee: Debug information 2 (return code from the function resulting in the error)
- S: Ignores this SQL statement, or invalidates the transaction.
- P:
- Take an action appropriate to the event:
- Init: Re-execute after contacting the HiRDB administrator to start the server.
- Termin: Start the server and re-execute.
- Other: Contact the HiRDB administrator.
- Action
- Take an action appropriate to the event:
- Init:
- Start the server.
- Netdown:
- Eliminate the cause of the communication error.
- Termin:
- Start the server.
- Timeout:
- Correct the communication monitoring interval (pd_lck_wait_timeout) specified in the system definition.
- System:
- If the server name on the receiving side is that of a dictionary server, and the value of debug information 2 is -330, the process count set for the dictionary server or for the back-end servers is insufficient. If this occurs, increase the value of operand pd_max_dic_process or pd_max_bes_process. In particular, this error tends to occur in multiple front-end server environments when several front-end servers are attempting to acquire definition information from the dictionary server, if the number of processes running on the dictionary server are fewer than the total of those running on the front-end servers.
- If the value of debug information 2 is -310, it is possible that the server on the receiving side has stopped. Use the pdls command to confirm that the server has stopped, start the server on the receiving side, and then re-execute.
- If the value of debug information 2 is one of the detail codes listed in 4.1 Detail codes for RPC-related errors, take the corresponding action.
- Other:
- Contact the customer support center.
KFPA11984-E A
Client version incompatible,HiRDB version=aa....aa, client version=bb....bb
- The version of the HiRDB client is invalid. The HiRDB client version in use is not supported by the HiRDB system.
- aa....aa: Version of HiRDB system
- bb....bb: Version of HiRDB client
- S: Ignores this request.
- P: Check the UAP preprocess, compilation, or linkage for an error. If there is no error, contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPA11986-E A
Function "aa....aa"."bb....bb"(cc....cc) executed no "RETURN" statement
- Execution of the function "aa....aa"."bb....bb" did not terminate at the RETURN statement.
- aa....aa: Authorization identifier
- bb....bb: Routine identifier
- cc....cc: Special name
- S: Either ignores this SQL statement or nullifies the transaction.
- P: Redefine the function and re-execute.
KFPA11987-E A
Unable to execute SQL except for rollback and disconnect
- Only the ROLLBACK or DISCONNECT SQL statement can be executed.
- S: Ignores this SQL statement.
- P: Execute the ROLLBACK or DISCONNECT statement.
KFPA11988-E A
Required function [aa....aa] is not supported
- The requested function aa....aa is not supported in this system.
- aa....aa: Requested, unsupported function (this is output only when the problem is detected on the client side)
- DESCRIBE TYPE: DESCRIBE TYPE statement
- TYPE OPTION: TYPE OPTION specified in PREPARE statement
- XA INTERFACE: XA interface used by the XDM/RD E2 connection facility
- ARRAY INSERT: Insert function that uses a matrix
- SET SESSION AUTHORIZATION: SET SESSION AUTHORIZATION statement
- JAR: INSTALL JAR, REPLACE JAR or REMOVE JAR
- SET: SET statement (assignment statement)
- SINGLE ROW SELECT: Dynamic single row retrieval
- ALLOCATE CURSOR: ALLOCATE CURSOR statement
- DEALLOCATE PREPARE: DEALLOCATE PREPARE statement
- DESCRIBE: Information acquired by DESCRIBE in a PREPARE statement
- EXTENDED STATEMENT NAME: Extended statement name specification
- EXTENDED CURSOR NAME: Extended cursor name specification
- CLIB: INSTALL CLIB, REPLACE CLIB, or REMOVE CLIB
- S: Ignores this SQL statement.
- P: When not using function aa....aa, delete the locations where this function is used. To upgrade HiRDB or XDM/RD E2 and use function aa....aa, contact the HiRDB administrator or the XDM/RD E2 system administrator.
- O: Confirm the client library linked to the UAP and the version of the server.
- Action
- Check the client libraries linked to the UAP and the server version. To use the functionality provided by aa....aa, upgrade HiRDB or XDM/RD E2.
KFPA11989-E A
Commit error
- An error occurred during commit processing.
- S: Invalidates this transaction.
- O: Refer to message KFPS00900-I or KFPS00972-I to eliminate the cause of the error and re-execute the UAP.
KFPA11990-E A
Incompatible character code set, HiRDB=aa....aa, client=bb....bb
- HiRDB system and client use different character codes.
- aa....aa: Character codes at the HiRDB system
- bb....bb: Character codes at the HiRDB client
- CHINESE: EUC Chinese kanji codes
- CHINESE-GB18030: Chinese character encoding GB18030
- LANG-C: One-byte character codes
- SJIS: Shift JIS kanji codes
- UJIS: EUC Japanese kanji codes
- UTF-8: Unicode
- ********: no supported character codes
- S: Declines connection to HiRDB.
- O: Check that the environmental variables when compiling the UAP (PDCLTLANG or LANG) or the environmental variables when executing (LANG or PDLANG) correspond to the character code classification supported by the HiRDB server. Contact the HiRDB administrator if there are no errors.
KFPA11992-E A
More than 32M bytes SQL OBJECT, size=aa....aa
- The SQL object's size exceeded 32MB.
- aa....aa: Size of the SQL object that was to be created (in bytes)
- S: Invalidates this transaction.
- P: Correct the SQL statement so that the size of the SQL object does not exceed 32MB, and re-execute.
KFPA11993-E A
Input data invalid for HASH function
- One of the following errors occurred in the input data for a partitioning column:
- The input data for the hash function specified in the table definition is too short.
- The following data type error occurred:
If the column data type is CHAR(8) (CHAR(16) if the character set is UTF16)
HASH0 or HASHZ was used as the hash function, but the format is not 'YYYYMMDD'.
If the column data type is CHAR(6) (CHAR(12) if the character set is UTF16)
HASH0 was used as the hash function, but the format is not 'YYYYMM'.
YYYY: 0001 to 9999 (year)
MM: 01 to 12 (month)
DD: 01 to the last day of the relevant month and year (day)
- S: Ignores this SQL statement.
- P: Check whether the hash function specified in the table definition is correct, and correct the table definition if it is incorrect.
- If HASH0 or HASHZ is used as the hash function, check whether there is an error in the data type of the input data, and if so, correct the input data.
- Make sure that the data length of the hashing target column into which INSERT is being done is no shorter than the minimum data length possible for the hash function specified in the table definition.
- If HASH0 is used as the hash function, make sure that the data in the hashing target column uses the format YYYYMMDD or YYYYMM.
- If HASHZ is used as the hash function, make sure that the data in the hashing target column uses the format YYYYMMDD.
KFPA11994-E A
Unable to execute definition SQL for holdable cursor opened
- Definition SQL cannot be issued because a holdable cursor is open.
- S: Ignores this SQL statement.
- P: Issue the definition SQL after closing all holdable cursors.
KFPA11996-E A
Holdable cursor lost because of server process down
- The holdable cursor could not be inherited. Also, the unit, server, or server process that was opened in the cursor might have terminated abnormally.
- S: Ignores this transaction.
- P: Eliminate the cause of the error, and then re-execute.
KFPA11997-E
Error occurred during execution of PLUGIN function, "aa....aa"
- An error occurred during the execution of the plug-in (implementation) function.
For queries that include an RDAREA name specification, retrieval is not possible because no index exists for an index-type plug-in-dependent function, or the index is not usable because the number of partitions of the index is different from the number of partitions of the table. - aa....aa: Error detail message
- S: Ignores this SQL statement or invalidates the transaction.
- P: Take one of the following actions:
- Resolve the problem identified in the detailed error message (aa....aa) by referring to the corresponding plug-in manual and re-execute the SQL.
- When aa....aa is Enable to use n-gram index (when the error detail message indicates that the necessary index for executing the index-type plug-in-dependent function does not exist) or something similar, and the query includes an RDAREA name specification, not only check whether the index-type plug-in-dependent function exists, but also make sure that the number of partitions of the index is equal to the number of partitions of the table, and then re-execute the SQL statement.
KFPA11998-E A
Unable to manipulate LIST yet, because transaction determination uncomplete
- An attempt was made to create, delete, or search a list before the previous transaction had completed. This error occurs when reconnect is performed before recovery processing is completed after processing in a single server or back-end server has aborted.
- S: Takes one of the following actions:
- SQL statement
Ignores this SQL statement.
- pdmod
Continues processing.
- P: Take one of the following actions:
- SQL statement
Wait for the transaction to be completed or complete the transaction manually, and then re-execute the SQL statement.
- pdmod
Wait for the transaction to be completed or complete the transaction manually, and then re-create or delete the list.
KFPA12000-I A
Processing of SQL completed
- Execution of SQL statement has been completed.
- S: Executes processing.
KFPA12100-I A
No rows satisfying search condition
- No row satisfies the condition. Or, row fetch has been completed.
- S: Resumes processing.
KFPA12110-I A
Row already deleted or updated
- Row that was to be retrieved via a search using a list had been deleted; the row's attribute value had been deleted or updated.
- S: Continues processing.
KFPA12120-I A
Processing of SQL completed, dynamic result set returned
- SQL statement execution has been completed, and a dynamic results set has been returned.
- S: Continues processing
KFPA12121-I A
Processing of SQL completed, additional result set returned
- Execution of the SQL statement has been completed. Furthermore, there is an additional result set.
- S: Continues processing.
KFPA12300-I A
RDAREA usage aaa%, RDAREA="bb....bb"cc....cc
- Meaning depends on the circumstances:
- System definition pd_rdarea_warning_point not specified:
- User RDAREA, user LOB RDAREA:
- The system started using the segment with relative location aaa% among all the segments of the last file in RDAREA "bb....bb".
- System definition pd_rdarea_warning_point specified:
- User RDAREA:
- The system started using the segment with usage factor aaa% among all the segments in the entire RDAREA "bb....bb". The current number of unused segments is cc....cc.
- User LOB RDAREA:
- The system started using the segment with relative location aaa% among all the segments in the entire RDAREA "bb....bb". The number of remaining segments for maintaining effective performance is cc....cc.#
- #: Effective performance:
- In the case of a user LOB RDAREA, the highest throughput can be achieved when the database area has not been used through the end. The effective performance indicates the high throughput status. Once a database is used through the end, throughput becomes lower. Therefore, some action such as database reorganization must be taken beforehand.
- aaa: One of the following is displayed:
- Relative location of the segment being used in the last file in the RDAREA
- Segment usage factor in the entire RDAREA
- Relative location in the RDAREA of the segment being used
- bb....bb: Applicable RDAREA name
- cc....cc: Additional information about segment usage factor, dd....dd segments unused (dd....dd: number of remaining segments)
- S:
- Resumes processing.
- If there is not enough space to allocate a new segment in this RDAREA but there is some space in existing segments used for addition or updating, the system continues processing using those segments.
- This message is displayed again if the indicated segment is used after it was released due to table deletion, reorganization, etc.
- P: Contact the HiRDB administrator.
- Action
- Use the command or utility shown below to check the remaining space in the RDAREA, then take the appropriate action shown in the table.
- Command for checking the remaining space:
- Database status display command (pddbls):
Specifying the -a option displays the RDAREA usage status. This command can be used for all RDAREAs.
- Database condition analysis utility (pddbst):
Physical or logical analysis displays the RDAREA usage status. This utility can be used for data dictionaries, user RDAREAs, and LOB RDAREAs.
- Action
- The table below shows the action:
Type of RDAREA | System definition pd_rdarea_warning_point not specified | System definition pd_rdarea_warning_point specified |
---|
User RDAREA | - Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst).
- Reorganize the table in the RDAREA according to the usage status. Or, extend the RDAREA.
| - Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst) or check the additional information about segment usage factor displayed in the message.
- Reorganize the RDAREA in units of table RDAREAs or tables according to the usage status. Or, extend the RDAREA.
|
User LOB RDAREA | - Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst).
- Reorganize the user LOB RDAREA in units of user LOB areas or tables according to the usage status. Or, extend the RDAREA.
| - Check the usage status of the RDAREA by using the database status display command (pddbls) or the database condition analysis utility (pddbst) or check the additional information about segment usage factor displayed in the message.
- Reorganize the user LOB RDAREA in units of user LOB RDAREAs or tables according to the usage status. Or, extend the RDAREA.
|
KFPA12350-W A+L
Column "aa....aa" added to FIX table "bb....bb"."cc....cc"
- Column aa....aa was added to FIX table bb....bb.cc....cc using ALTER TABLE.
- aa....aa: Name of added column
- bb....bb: Authorization identifier of the table to which the column was added
- cc....cc: Table identifier of the table to which the column was added
- S: Continues processing.
- P: Column aa....aa, which was added to table bb....bb.cc....cc, was added by excising it from a reserved column. Because 0x00 is stored regardless of the data type when the values are added, update the added column with meaningful values before using it.
KFPA19101-E A
Invalid SQL optimization specification for aa....aa
- The following error was detected in the SQL optimization specification:
- An SQL optimization specification in the subquery execution method was specified in a subquery other than the one in the predicate.
- aa....aa: subquery
- S: Ignores this SQL statement.
- P: Correct this SQL statement and re-execute.
KFPA19102-E A
Invalid file name "aa....aa" specified in client environment definition PDDELRSVWDFILE
- The following error occurred in the value specified for the client environment definition PDDELRSVWDFILE.
- This specifies a file name other than that specified by the system common definition pd_delete_reserve_word_file operand.
- aa....aa: File name specified in the client environment definition PDDELRSVWDFILE.
- S: Rejects the connection with HiRDB.
- P: Set the value specified in the client environment definition PDDELRSVWDFILE to the value specified in the system common definition pd_delete_reserve_word_file operand.
KFPA19104-E A
Invalid aa....aa "bb....bb" in character set specification
- One of the following specification errors was found:
- Schema name
- Character set name
- aa....aa: {schema name|character set name}
- bb....bb: {schema-name-other-than-MASTER|character-set-that-has-not-been-defined}
- S: Ignores this SQL statement.
- P: Correct the SQL statement as explained below, and then re-execute.
- If a schema name is invalid, correct it by changing the schema to MASTER or omitting it.
- If a character set name is invalid, change it to the correct character set name.
KFPA19105-E A
Specified value specification invalid in RDAREA name specification
- One of the following values was invalidly specified in the RDAREA name.
- A character string literal or a literal other than a mixed character string literal.
- A data type that is an SQL variable or SQL parameter other than CHAR, VARCHAR, MCHAR, or MVARCHAR.
- USER value function
- CURRENT_DATE value function
- CURRENT_TIME value function
- CURRENT_TIMESTAMP value function
- SQLCODE
- SQLCOUNT
- SQLCODE_OF_LAST_CONDITION
- SQLERRM_OF_LAST_CONDITION
- S: Ignores this SQL statement.
- P: For the RDAREA name specification, use values other than those listed above to specify VARCHAR, MCHAR, and MVARCHAR data type values, and then re-execute.
KFPA19106-E A
Unable to define reserved column except as last column in table
- Only the last column of the table can be specified as a reserved column. No other columns are permitted.
- S: Ignores this SQL statement.
- P: Correct the SQL so that the last column of the table is specified as the reserved column, and then retry the operation.
KFPA19110-E A
Unable to specify "aa....aa" statement in FOR statement because cursor is not holdable
- If there is no holdable cursor declared by the FOR statement, the SQL procedure statements in the FOR statement cannot specify the COMMIT, ROLLBACK, or PURGE TABLE statements.
- aa....aa: SQL statements that cannot be specified:
- {COMMIT | ROLLBACK | PURGE TABLE}
- S: Ignores this SQL statement and rolls back.
- P: Revise the SQL statement, and re-execute.
KFPA19111-E A
Table name missing except preparable dynamic "aa....aa" statement:positioned.
- A table name is missing when preprocessing of an UPDATE or DELETE statement using a cursor is not being performed.
- aa....aa: Erroneous SQL statement
- {UPDATE | DELETE}
- S: Ignores this SQL statement.
- P: Revise the SQL statement, and re-execute.
KFPA19130-E A
Authorization identifier specified for public aa....aa in bb....bb
- An authorization identifier cannot be specified in a public routine.
- aa....aa: routine
- bb....bb: Statement in which the authorization identifier was specified
- {CREATE PUBLIC FUNCTION
- |CREATE PUBLIC PROCEDURE
- |DROP PUBLIC FUNCTION
- |DROP PUBLIC PROCEDURE}
- S: Ignores this SQL statement.
- P: Delete the authorization identifier.
KFPA19140-E A
aa....aa specified in definition of bb....bb
- One of the following errors was detected in the specification for the SQL procedure statement or external routine:
- If aa....aa is EXTERNAL NAME
- The external routine is specified if SQL was specified for the LANGUAGE clause or if the LANGUAGE clause has been omitted.
- If aa....aa is SQL procedure statement
- The SQL procedure statement is specified if JAVA or C has been specified for the LANGUAGE clause.
- aa....aa: {External name|SQL procedure statement}
- bb....bb: {SQL routine|external routine}
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19150-E A
Unable to specify data type other than DATE or TIME type for column "aa....aa" with "SYSTEM GENERATED"
- The data type of the column specifying SYSTEM GENERATED was not the DATE type or the TIME type.
- aa....aa: The alias specified by mistake
- S: Ignores this SQL statement.
- P: Correct this SQL statement and re-execute.
KFPA19170-E A
Invalid argument of SQL/XML scalar function or SQL/XML predicate
- One of the following errors occurred in an SQL/XML scalar function or predicate argument.
- The XML query context items of the XMLQUERY or XMLEXISTS argument are specified two or more times.
- The VERSION or XMLSERIALIZE argument is specified as a value other than 1.0.
- An XML query context item is specified as an XQuery query in an XMLQUERY argument that specifies an XQuery transform expression.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19171-E A
Invalid token "aa....aa" appeared in bb....bb, query-no=ccc
- The term aa....aa specified in the bb....bb argument is invalid. Another possibility is that aa....aa was specified at the end of the bb....bb name without using the left parenthesis.
- aa....aa: Invalid term that does not follow the structure rules
- bb....bb: { XML constructor | XMLQUERY | XMLSERIALIZE | XMLPARSE | XMLAGG | XMLEXISTS }
- ccc: Query number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19180-E A
Duplicate prefix "aa....aa" in XQuery expression or partial structure path
- The aa....aa prefix specified in the XQuery or substructure is specified more than once. The same prefix cannot be declared more than once for an XML namespace.
- aa....aa: Duplicate prefix (first 30 characters)
- S: Ignores this XQuery specification or substructure specification.
- P: Correct the duplicate prefix and re-execute.
KFPA19181-E A
Prefix "aa....aa" not declared in XQuery expression or partial structure path
- The aa....aa prefix specified in the XQuery or substructure has not been declared in the XML namespace.
- aa....aa: Prefix without declaration (first 30 characters)
- S: Ignores this XQuery specification or substructure specification.
- P: Correct the prefix or declare it in the XML namespace, and then re-execute.
KFPA19182-E A
Invalid floating point numeric literal aa....aa in XQuery expression
- The format of the floating-point numeric literal specified in the XQuery is invalid.
- aa....aa: invalid floating-point numeric literal (first 30 characters)
- S: Ignores this XQuery specification.
- P: Correct the floating-point numeric literal and re-execute.
KFPA19183-E A
Invalid part "aa....aa" in XQuery expression or partial structure path
- One of the following errors was detected in an XQuery or substructure specification:
- Excess characters were detected at the end of the XQuery or substructure specification.
- A syntactically invalid character or keyword was specified.
- The first keyword in the XQuery specification or substructure specification is invalid.
- aa....aa: The first 30 characters and hexadecimal digits that follow enclosed in parentheses, corresponding to the invalid part or syntactically invalid characters in the XQuery or substructure specification
- S: Ignores this XQuery specification or substructure specification.
- P: Correct the syntax of the XQuery or substructure specification, and then re-execute.
KFPA19184-E A
Incomplete XQuery expression or partial structure path
- An XQuery specification or substructure specification is not complete.
- S: Ignores this XQuery specification or substructure specification.
- P: Complete the XQuery or substructure specification, and re-execute.
KFPA19185-E A
Invalid token "bb....bb" after token "aa....aa" in XQuery expression or partial structure path
- Syntactically, bb....bb cannot follow aa....aa in an XQuery or substructure specification.
- aa....aa: Last character string that satisfies the syntax rules (first 30 characters)
- bb....bb: Syntactically invalid character string (first 30 characters)
- S: Ignores this XQuery specification or substructure specification.
- P: Because either of the following errors is possible, correct the XQuery or substructure specification accordingly and then re-execute.
- The specification contains a syntax error.
- The order of expressions is invalid.
KFPA19186-E A
Invalid numeric literal aa....aa in XQuery expression
- The numeric literal specified in the XQuery contains a syntax error.
- aa....aa: Invalid numeric literal (first 30 characters)
- S: Ignores this XQuery specification.
- P: Correct the numeric literal and re-execute.
KFPA19187-E A
Numeric literal out of range in XQuery expression
- A numeric literal specified in the XQuery is outside the following permitted range:
Integer literal: -2,147,483,648 to 2,147,483,647
Decimal numeric literal: there are 38 or fewer displayed digits, and
1038 to
(1039 - 1)
Floating point numeric literal:
4.9E-324 to
1.7E+308 - S: Ignores this XQuery specification.
- P: Correct the specification of the numeric literal and re-execute.
KFPA19188-E A
Invalid XQuery function "aa....aa" in XQuery expression
- The XQuery function aa....aa specified in the XQuery was not found.
- aa....aa: XQuery function name that does not exist (first 30 characters)
- S: Ignores this XQuery specification.
- P: Make sure that there are no invalid or unsupported XQuery function name prefixes or local names. Then correct the XQuery specification as needed and re-execute.
KFPA19189-E A
XQuery variable in "return" clause different from XQuery variable in "copy" clause, in transform expression of XQuery, XQuery-no=aaa
- You cannot specify an XQuery transform in the return clause of an XQuery transform expression that is different from the XQuery transform specified in the copy clause. Specify the same XQuery transform specified in the copy clause in the return clause of the XQuery transform.
- aaa: Query number of the XQuery resulting in an error
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19198-E A
aa....aa missing in bb....bb statement for memory table access in XDS
- The lock option WITHOUT LOCK NOWAIT was not specified in the SELECT statement that searches the memory database allocation table. When the memory database allocation table is searched, either the lock option WITHOUT LOCK NOWAIT must be specified in the SELECT statement or 0 must be specified in the client environment definition PDISLLVL.
- aa....aa: WITHOUT LOCK NOWAIT
- bb....bb: SELECT
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19200-E A
Unable to specify referential constraint or check constraint without specifying "pd_check_pending" operand
- Because there is no system common definition pd_check_pending specification, a referential constraint or check constraint is not allowed.
- S: Ignores this SQL statement.
- P: Remove the referential constraint or check constraint definition statement part of the SQL statement, and re-execute. Or, ask the HiRDB administrator for the addition of a system common definition pd_check_pending.
KFPA19203-E A
Invalid value expression "aa....aa", query-no=bbb
- An invalid specification exists in the value expression aa....aa.
- If aa....aa is NEXT VALUE:
- The NEXT VALUE expression cannot be specified in the following locations:
- A location other than the selection expression and insertion value of the query specification of the INSERT statement query, or other than the update value of the UPDATE statement.
- Subquery
- CASE expression
- Scalar function VALUE
- Set function
- Query containing WINDOW function
- Query containing DISTINCT function
- Query containing GROUP BY clause, the HAVING clause, and the set function.
- Query containing a set operation other than UNION ALL
- aa....aa: NEXT VALUE
- bbb: Query number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19212-E A
Unable to specify expression except embedded variable or ? parameter in assignment statement for embedded SQL
- One of the following errors occurred in the specification of the assignment target or assignment value of the assignment statement:
- A value expression other than an embedded variable or ? parameter is specified as the assignment target.
- A value expression other than an embedded variable, ? parameter, scalar function LENGTH, scalar function SUBSTR, or scalar function POSITION is specified as the assignment target.
- An item other than an embedded variable or a ? parameter is specified as the value expression in the scalar function LENGTH, the value expression 1 of the scalar function SUBSTR, or the value expression 2 of the scalar function POSITION specified in the assignment value.
- One of the following is specified as the assignment value:
A value expression that includes a column specification
A value expression that includes a component specification that shows the attribute of an abstract data type column
- S: Ignores this SQL statement.
- P: Revise this SQL statement, and re-execute.
KFPA19219-E A
Unable to specify column "aa....aa" in "ORDER BY" clause,due to derived column, in XDS
- When you are accessing the memory database allocation table, you cannot specify the column name aa....aa in the ORDER BY clause, because it is not a colum that is output based on only a column specification.
- aa....aa: Column name specified in the ORDER BY clause
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19220-E A
Invalid cursor name "aa....aa" in "bb....bb" statement
- The cursor name declared in the FOR statement cannot be specified in the OPEN, CLOSE, or FETCH statement.
- aa....aa: Cursor name
- bb....bb: SQL statement that cannot be specified
- {OPEN | CLOSE | FETCH}
- S: Ignores this SQL statement and rolls back.
- P: Revise the SQL statement, and re-execute.
KFPA19221-E A
Invalid cursor specification in FOR statement.
- One of the following errors occurred in the cursor specification specified in the FOR statement:
- An unnamed column is specified in a derived column.
- In the FROM clause of a derived column, a repetition column with no unnesting specification and no subscript was specified.
- There are duplicate instances of the derived column name of a derived column.
- S: Ignores this SQL statement and rolls back.
- P: Revise the SQL statement, and re-execute.
KFPA19222-E A
Specified view aa....aa."bb....bb" unusable,because "pd_sql_dec_op_maxprec" changed
- If you change the specification value of the pd_sql_dec_op_maxprec operand in the system common definition, no operations can be performed on the following viewed tables of those viewed tables defined prior to the change.
- A viewed table defined in a version prior to 08-04
- A viewed table that was defined specifying any of the following operations:
- Arithmetic operation for DECIMAL type data of 29 digits or less only
- Set function AVG/SUM for DECIMAL type data of 29 digits or less only
- Scalar function MOD for DECIMAL type data of 29 digits or less only
- Scalar function in which precision was omitted because the argument type is FLOAT
- aa....aa: Authorization identifier
- bb....bb: Viewed table identifier
- S: Ignores this SQL statement.
- P: Delete the invalid viewed table(s), revise the definition, and then re-execute.
KFPA19225-E A
Invalid use of memory table due to aa....aa
- The method of using the memory database allocation table is invalid.
- aa....aa: Detailed information on error
aa....aa | Meaning | Action to take |
---|
access to memory table from compatible client library | S: One of the following operations is being performed:
- A memory database allocation table operation is being performed from the UAP that used the client library for the server providing the primary facilities.
- A utility that does not support the memory database allocation table is being executed on the memory database allocation table.
| If 1: When performing an operation on the memory database allocation table, use the XDS client library. If 2: Revise the table to be processed by the utility, specify a correct table if there are any errors, and then re-execute the command. To execute the utility on the memory database allocation table, release memory database allocation of the table once, and then re-execute the utility. |
access to different XDS from connected XDS | The specified memory database allocation table is stored in a different XDS than the one to which you are connected. | Revise the connection destination and connect to the host on which the XDS exists that is stored in the specification table. |
unsupported memory table and disk table mixing | A mix of tables has been specified in one SQL statement: tables to be added and tables not to be added to the memory database. | Revise the SQL statement so that tables to be added to the memory database are not mixed with other tables in a single SQL statement. |
memory table in WITH clause | The memory database allocation table is specified in the WITH clause query. | Either correct the SQL statement so that the memory database allocation table is not specified in the WITH clause query, or deallocate the specified table from the memory database. |
memory table in Java stored procedure | The memory database allocation table is specified in the Java stored procedure. | Either correct the memory database allocation table so that it is not specified in the Java stored procedure, or release memory database allocation of the table. |
- S:
- When the SQL statement executes: ignores this SQL statement.
- When the utility executes: terminates the processing.
- P: When the SQL statement executes, revise the SQL statement according to the aa....aa action procedure, and then re-execute.
- O: When the utility executes, revise the utility command line according to the aa....aa action procedure, and then re-execute.
KFPA19254-E A
Subquery specified in aa....aa
- A subquery was specified in an invalid location.
- aa....aa: {set function|assignment statement|RETURN statement|CALL statement|WRITE specification|WRITE LINE statement}
- S: Ignores this SQL statement.
- P: Revise the SQL statement, and re-execute.
KFPA19270-E A
Invalid item specified AS aa....aa in bb....bb,query-no=ccc,arg-no=ddddd
- One of the following errors was detected in aa....aa specified in the bb....bb argument.
- If aa....aa is value expression:
- When bb....bb is XML constructor
An item other than an SQL variable, SQL parameter, embedded variable, or ? parameter is specified in a value expression.
- When bb....bb is XMLSERIALIZE
An item other than a column specification, XMLQUERY, or XMLAGG is specified in a value expression.
Another possibility is that a named derived table column derived from an item other than a column specification is specified.
- When bb....bb is XMLAGG
An item other than a column specification or XMLQUERY is specified in a value expression.
Another possibility is that a named derived table column derived from an item other than a column specification is specified.
- When bb....bb is XMLPARSE:
A labeled interval is specified in a value expression.
- If aa....aa is XML query context item:
- Either a value expression other than a column specification, or a column of a table whose name was derived according to a value expression other than a column specification, is specified in the XML query context item that was specified as the ddddd XML query argument.
- If aa....aa is XML query context item:
- One of the following items is specified in the value expression of the XML query variable specified as the ddddd XML query argument:
- Component specification
- A table whose name was derived according to a component specification.
- Unary operation for the ? parameter or embedded variable
- SQLCODE, SQLCODE_OF_LAST_CONDITION, SQLCOUNT, or SQLERRM_OF_LAST_CONDITION
- aa....aa: {value expression|XML query context item|XML query variable}
- bb....bb: {XML constructor|XMLQUERY|XMLSERIALIZE|XMLAGG| XMLEXISTS|XMLPARSE}
- ccc: Query number
- ddddd: Argument or XML query argument number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19271-E A
Invalid data type of aa....aa in bb....bb, query-no=ccc, arg-no=ddddd
- An error was detected in the aa....aa data type specified in bb....bb.
- If bb....bb is XMLQUERY, XMLSERIALIZE, XMLAGG, or XMLEXISTS:
- A data type other than XML is specified in the ddddd aa....aa.
- If bb....bb is XML constructor:
- A data type other than BINARY is specified in the argument.
- If bb....bb is XMLPARSE:
- A data type other than the displayed data type is specified in the argument. Alternatively, a character set is specified in the argument.
- Character string data type (CHAR, VARCHAR)
- Mixed character string data type (MCHAR, MVARCHAR)
- BINARY type
- aa....aa: {argument|XML query context item}
- bb....bb: {XML constructor|XMLQUERY|XMLSERIALIZE|XMLPARSE|XMLAGG|XMLEXISTS}
- ccc: Query number
- ddddd: Argument or XML query argument number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19272-E A
Data type of XML query variable in aa....aa inconvertible to XQuery data type, query-no=bbb, arg-no=ccccc
- The data type for the value expression specified in the XML query variable in the aa....aa argument cannot be converted to the XQuery data type.
- The data type cannot be converted to an XQuery data type.
- INTERVAL YEAR TO DAY
- INTERVAL HOUR TO SECOND
- BLOB
- BINARY
- BOOLEAN
- Abstract data type
- aa....aa: { XMLQUERY | XMLEXISTS }
- bbb: Query number
- ccccc: XML query argument number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19273-E A
Unable to specify "BY VALUE" for variable except XML type in aa....aa, query-no=bbb, arg-no=ccccc
- BY VALUE cannot be specified to an XML query for which a value expression result is a data type other than an XML data type.
- aa....aa: { XMLQUERY | XMLEXISTS }
- bbb: Query number
- ccccc: XML query argument number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19274-E A
XML query variable "aa....aa" duplicate in bb....bb, query-no=ccc, arg-no=ddddd
- The name of the XML query variable aa....aa that was specified in bb....bb is a duplicate.
- aa....aa: XML query variable
- bb....bb: { XMLQUERY | XMLEXISTS }
- ccc: Query number
- ddddd: XML query argument number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19275-E A
No input value to XQuery variable "aa....aa" in bb....bb, query-no=ccc
- There is no input value for the XQuery variable aa....aa in bb....bb.
- aa....aa: XQuery variable (maximum of 30 bytes displayed)
- bb....bb: { XMLQUERY | XMLEXISTS }
- ccc: Query number
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19277-E A
Unable to specify RDAREA name specification for bb....bb aa....aa
- The RDAREA name cannot be specified in aa....aa.
The RDAREA name could not be specified in the following table bb....bb. - Read-only viewed table (read-only view)
- Query name (query name)
- Temporary table (temporary table)
- aa....aa: authorization-identifier."table-identifer", or the query name.
- bb....bb: { read-only view|query name|temporary table }
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19290-E A
Unable to specify aa....aa in bb....bb
- The following items cannot be specified in the search condition of a check constraint definition or in a trigger action condition.
- Search condition of a check constraint
- Subquery
- Set function, or SQL/XML set function
- Repetition column
- Embedded variable or ? parameter
- USER value function
- CURRENT DATE value function
- CURRENT TIME value function
- CURRENT TIMESTAMP value function
- Columns not defined in a table definition
- For a single column check constraint, a column not defined in the column specification
- A value expression of an abstract data type
- User-defined function
- Structured repetition predicate
- CAST specification that specified conversion from TIME to TIMESTAMP
- Scalar function VARCHAR_FORMAT that specifies TIME in the value expression
- Scalar function IS_USER_CONTAINED_IN_HDS_GROUP
- Window function
- SQL/XML scalar function
- Reserved column
- Trigger action condition
- Subquery
- Set function
- Repetition column
- Embedded variable, or ? parameter
- A column not qualified by an old or new values correlation name
- Value expression in the abstract data type
- Plug-in function
- Java stored function
- Structured repetition predicate
- Window function
- SQL/XML scalar function
- Reserved column
- aa....aa: Error causing conditions:
- { subquery| set function| SQL/XML set function| array column
- | variable or parameter
- | column "column-name" unqualified by old or new values correlation name
- | value expression of abstract data type
- | PLUGIN function| JAVA function| ARRAY predicate
- | function invocation| USER| CURRENT_DATE
- | CURRENT_TIME| CURRENT_TIMESTAMP| column "column-name"
- | CURRENT_DATE implied by scalar function VARCHAR_FORMAT or cast specification
- | scalar function IS_USER_CONTAINED_IN_HDS_GROUP
- | window function
- | SQL/XML scalar function
- | reserved column "column name"}
- bb....bb:{triggered action condition|check constraint definition}
- S: Ignores this SQL statement and rolls back.
- P: Correct this SQL statement and re-execute.
KFPA19291-E A
Invalid use of "LIMIT" clause
- One of the following errors was detected in the usage of the LIMIT clause:
- A column qualified by an old or new values correlation name was specified as the maximum row count or offset row count.
- The total value that can be specified in the maximum row count and offset row count exceeds 2,147,483,647.
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct the SQL statement and re-execute.
KFPA19292-E A
Unable to specify outer reference column "aa....aa" with data type "BINARY", query-no=bbb
- The BINARY data type cannot be specified for a column that makes an external reference.
- aa....aa: Name of column that made an external reference
- However, when an incorrectly specified column is in a named derived table, the column name of the base table for the applicable named derived table is displayed.
- bbb: The number of the query specifying the column that made an external reference.
- S: Ignores this SQL statement. However, a definition SQL statement rolls back.
- P: Correct this SQL statement and re-execute.
KFPA19293-E A
Invalid handler declaration or condition declaration code=aa(bb....bb)
- An error was detected in the condition declaration or handler declaration.
- aa: Reason code
- bb....bb: Additional error information
- The following table shows each reason code and the corresponding additional information or meaning.
Reason code (aa) | Additional information (bb....bb) | Meaning |
---|
01 | Condition name "cc....cc" already declared | Condition name cc....cc specified in the condition declaration was already defined. |
02 | SQLCODE value "dd....dd" in condition "cc....cc" already declared in other condition declaration | SQLCODE value dd....dd specified in condition declaration cc....cc was already defined as the SQLCODE value of another condition declaration. |
03 | Condition name "cc....cc" in handler declaration not found | The condition name cc....cc specified in the handler declaration was not found. |
04 | Unable to specify SQLCODE value or condition name together with "SQLERROR" or "NOT FOUND" | If either SQLERROR or NOT FOUND is specified in the condition value for the handler declaration, the SQLCODE value or condition name cannot be specified in the same handler declaration. |
05 | Duplicate condition value | The same SQLCODE value or condition name cannot be specified multiple times in the condition value of the handler declaration. Also, a condition name expressing the same SQLCODE as the SQLCODE value cannot be specified. |
06 | Unable to specify same condition as condition in other handler declaration | A condition value expressing the same condition cannot be specified in another handler declaration. |
07 | Zero specified in SQLCODE value | 0 is specified in the SQLCODE value of the condition declaration or handler declaration. |
- S: Ignores this SQL statement and rolls back.
- P: Correct this SQL statement and re-execute.
KFPA19294-E A
Invalid signal value aa....aa
- One of the following errors was detected in the signal value:
- (1) The condition name aa....aa specified in the signal value was not found.
- (2) One of the following errors was detected in SQLSTATE value aa....aa specified in the signal value:
- A literal other than a character literal less than 5 digits long was specified.
- Values other than uppercase letters between A and Z or numerals 0-9 were specified.
- The numerals 0-5, the uppercase letters A-I, and R were specified in the first character.
- aa....aa: {"condition-name"|SQLSTATE "SQLSTATE-value"}
- S: Ignores this SQL statement and rolls back.
- P: Correct the SQL statement and re-execute.
KFPA19295-E A
Invalid specification in UPDATE statement with update trigger
- The following manipulations cannot be performed on a table with a trigger that uses UPDATE as an event:
- Updating using component specifications on tables with a trigger defined that uses a new values correlation name
- Updating BLOB type data using a concatenation operation or BINARY type data with a definition length of 32,001 bytes or more in a table defining UPDATE as the trigger.
- S: Ignores this SQL statement (unless it is a definition SQL statement, in which case rollback is executed).
- P: Correct this SQL statement and re-execute.
KFPA19296-E A
Unable to translate character string literal from default character set to character set aa....aa
- You cannot compare or convert the character string literal of a pre-existing character set to a character string of an assignment target character set.
- aa....aa: UTF16
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19311-E A
Unable to generate aa....aa type key from value on specified partial structure due to bb....bb, index ID=cc....cc
- aa....aa data type key values cannot be generated from substructure values specified in substructure index definitions.
- If bb....bb is unmatched types:
- Substructure XQuery data types that are not xs:untypedAtomic or key value SQL data types are not supported.
- If bb....bb is invalid format:
- Character string formats for substructure values that are xs:untypedAtomic type are invalid.
- If bb....bb is invalid length:
- The substructure value length is invalid.
- aa....aa: Data type of a key value in the substructure index.
- {INTEGER|DECIMAL|FLOAT|VARCHAR}
- bb....bb: Reason for the error
- {unmatched types|invalid format|invalid length}
- cc....cc: Index number
- For CREATE INDEX, ********** is displayed.
- S: Ignores this SQL statement. The system may also invalidate this transaction.
- P:
- When bb....bb is unmatched types:
- If the executed SQL is data manipulation SQL, correct the XML schema so that the XQuery data type of the substructure supports xs:untypedAtomic types or key value SQL data types, re-parse the XML text, and then re-execute.
- If the executed SQL is a definition in the substructure index, correct the SQL data type of the key value to a data type corresponding to the XQuery data type for the substructure, and then re-execute.
- For details about compatibility between the XQuery data type and SQL data type, see the manual HiRDB Version 9 SQL Reference.
- If bb....bb is invalid format:
- If the executed SQL is data manipulation SQL, correct the substructure value so that it is a format that can be converted to a key value SQL data type, and then re-execute.
- If the executed SQL is a definition in the substructure index, correct the SQL data type of the key value to a data type that can be converted to the substructure value, and then re-execute.
- If bb....bb is invalid length:
- If the executed SQL is data manipulation SQL, correct the substructure to a value that can be stored in the SQL data type length of the key value, and then re-execute.
- If the executed SQL is a definition in the substructure index, correct the length of the SQL data type of the key value to a length that can be stored by the substructure value, and then re-execute.
KFPA19313-E A
Result of XML serialization too long
- The result of changing XML type values to value columns (conversion to character string) is too long.
The value must be equal to or less than the maximum length of the data type specified in AS data type of the XMLSERIALIZE function. - S: Ignores this SQL statement. The system may also invalidate this transaction.
- P: Change the maximum length of the data type specified in the AS data type of the XMLSERIALIZE function to a length that can be stored in the value column change result. Also, if 32,000 bytes is exceeded, specify the BINARY type.
KFPA19318-E A
Unable to specify XQuery function "aa....aa", because IXXML index unavailable, XQuery-no=bb....bb
- The XML type full-text search index cannot be used for one of the following reasons. Therefore, the XQuery function aa....aa cannot be used.
- The XML type full-text search index was not defined in the column specified in the XML query context item.
- The substructure path specified in the first argument does not match the usage conditions of the XML type full-text search index.
- aa....aa: XQuery function name {hi-fn:contains}
- bb....bb: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P: If the XML type full-text search index was not defined in the column specified in the XML query context item, define it. If the XML type full-text search index is defined in the column specified in the XML query context item, check the usage conditions of the XML type full-text search index, and correct them so that the substructure path specified in the first argument matches the usage conditions of the XML type full-text search index. For details about the usage conditions of the XML type full-text search index, see the HiRDB Version 9 Installation and Design Guide.
KFPA19319-E A
Conflicting types "aa....aa" and "bb....bb" in XQuery sequence for XQuery function "cc....cc", XQuery-no=dd....dd
- XQuery sequences into which non-comparable XQuery data type values have been mixed are specified as XQuery sequence cc....cc.
- aa....aa: The XQuery data type 1 value included in the XQuery sequence.
- {xs:string | xs:decimal | xs:int
- | xs:double | xs:dateTime | xs:date
- | xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}
- bb....bb: The XQuery data type 2 value included in the XQuery sequence.
- {xs:string | xs:decimal | xs:int
- | xs:double | xs:dateTime | xs:date
- | xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}
- cc....cc: XQuery function name
- {fn:max|fn:min}
- dd....dd: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P: Correct the XQuery query so that the evaluation results of the argument specified in the XQuery function become an XQuery sequence configured from comparable XQuery data type values only, and then re-execute.
KFPA19320-E A
Unable to convert "aa....aa" type value to "bb....bb" type in XQuery due to cc....cc, XQuery-no=dd....dd
- The XQuery data type aa....aa value cannot be converted to the XQuery data type bb....bb value.
- If cc....cc is invalid format:
- The format of a character string prior to conversion is invalid.
- If cc....cc is out of range:
- The value prior to conversion cannot be reflected in the XQuery data type after conversion.
- If cc....cc is incompatible types:
- The XQuery data type prior to conversion and the type after conversion are not a combination that can be converted.
- aa....aa: XQuery data type prior to conversion
- { xs:string | xs:decimal | xs:int | xs:double | xs:dateTime | xs:date | xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}
- bb....bb: XQuery data type after conversion
- { xs:decimal | xs:int | xs:double | xs:dateTime | xs:date | xs:time | xs:hexBinary | xs:boolean }
- cc....cc: Reason for the error
- { invalid format | out of range | incompatible types }
- dd....dd: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P:
- If cc....cc is invalid format:
- P: Correct the XQuery query so that the format of the character string prior to conversion is correct, and then re-execute. For details about the format of XQuery data type character strings, see the manual HiRDB Version 9 SQL Reference.
- If cc....cc is out of range:
- P: Correct the XQuery query so that the value prior to conversion can be expressed in the XQuery data type after conversion, and then re-execute.
- If cc....cc is incompatible types:
- P: Correct the XQuery query so that the XQuery data type prior to conversion and the data type after conversion become a convertible combination, and then re-execute. For details about the combinations of XQuery data types that can be converted, see the manual HiRDB Version 9 SQL Reference.
KFPA19321-E A
Unable to compare "aa....aa" type value with "bb....bb" type value in XQuery, XQuery-no=cc....cc
- The aa....aa and bb....bb XQuery data type values cannot be compared.
- aa....aa: XQuery data type of first operation item
- { xs:string | xs:decimal | xs:int | xs:double | xs:dateTime | xs:date | xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}
- bb....bb: XQuery data type of second operation item
- { xs:string | xs:decimal | xs:int | xs:double | xs:dateTime | xs:date | xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}
- cc....cc: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P: Correct the XQuery query so that the XQuery data types of the first and second operation items become a combination that can be compared, and then re-execute. For details about combinations of XQuery data types that can be compared, see the manual HiRDB Version 9 SQL Reference.
KFPA19322-E A
Unable to perform aa....aa operation between "bb....bb" type value and "cc....cc" type value in XQuery, XQuery-no=dd....dd
- In the bb....bb and cc....cc XQuery data type values, it is not possible to execute the aa....aa arithmetic operation.
- aa....aa: Type of arithmetic operation in which the error occurred
- { addition | subtraction | division | multiplication | idiv | mod }
- addition: Addition
- subtraction: Subtraction
- division: Division
- multiplication: Multiplication
- idiv: Integer division
- mod: Modulus calculation
- bb....bb: XQuery data type of first operation item
- { xs:string | xs:decimal | xs:int | xs:double | xs:dateTime | xs:date | xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}
- cc....cc: XQuery data type of second operation item
- { xs:string | xs:decimal | xs:int | xs:double | xs:dateTime | xs:date | xs:time | xs:hexBinary | xs:boolean | xs:untypedAtomic}
- dd....dd: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P: Correct the arithmetic operation so that the XQuery data types of the first and second operation items become a combination that can be compared, and then re-execute. For details about the combinations of XQuery data types that can be used in arithmetic operations, see the manual HiRDB Version 9 SQL Reference.
KFPA19323-E A
Invalid operand of aa....aa expression in XQuery due to bb....bb, XQuery-no=cc....cc
- One of the following errors was detected in the operand of the XQuery expression:
- If bb....bb is two or more items:
- An XQuery sequence has two or more XQuery items in the XQuery comparison (value comparison or node comparison), XQuery range, or XQuery monomial.
- If bb....bb is item except node:
- An XQuery sequence containing XQuery items other than nodes is specified in the XQuery comparison expression (node comparison) or in the XQuery set operation expression.
- If bb....bb is value except "xs:int" type:
- A non-integer value is specified in the XQuery range expression.
- aa....aa: Processing during which the error occurred:
- {value comparison | node comparison | range | union | intersect | except | unary | arithmetic}
- value comparison: XQuery comparison expression (value comparison)
- node comparison: XQuery comparison expression (node comparison)
- range: XQuery range expression
- union: XQuery union expression
- intersect: XQuery intersection expression
- except: XQuery union expression
- unary: XQuery monomial expression
- arithmetic: XQuery arithmetic expression
- bb....bb: Reason for the error
- { two or more items | item except node | value except "xs:int" type }
- cc....cc: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P:
- Correct the XQuery query as follows, and then re-execute:
- If bb....bb is two or more items:
- Specify either an XQuery sequence that has only one XQuery item or an empty XQuery sequence in the XQuery comparison (value comparison or node comparison), XQuery range, or XQuery monomial.
- If bb....bb is item except node:
- Specify an XQuery sequence that does not contain XQuery items other than nodes in the XQuery comparison expression (node comparison) or in the XQuery Set Operation expression.
- If bb....bb is value except "xs:int" type:
- Specify an integer value in the XQuery range expression.
KFPA19324-E A
Invalid context item for aa....aa in XQuery, XQuery-no=bb....bb
- During evaluation of XQuery expression aa....aa during an XQuery query, context items were found that are not nodes.
- aa....aa: Type of XQuery expression
- { path expression | function "fn:local-name" | function "fn:name" | function "fn:namespace-uri" }
- path expression: XQuery path expression
- function "fn: local-name": XQuery function fn:local-name
- function "fn: name": XQuery function fn:name
- function "fn namespace-uri": XQuery function fn:namespace-uri
- bb....bb: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P: Correct the XQuery query so that the context items are nodes, and then re-execute.
KFPA19325-E A
Overflow in aa....aa for "bb....bb" type in XQuery, XQuery-no=cc....cc
- An overflow occurred during operation aa....aa of XQuery data type bb....bb in an XQuery query.
- aa....aa: Operation type in which the overflow occurred:
- addition: Addition
- subtraction: Subtraction
- division: Division
- multiplication: Multiplication
- idiv: Integer division
- mod: Modulus calculation
- sign inversion: Sign inversion
- function "fn:abs": XQuery function fn:abs
- bb....bb: Data type resulting in the overflow:
- { xs:decimal | xs:int | xs:double}
- cc....cc: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P: Correct the XQuery query so that overflow does not occur, and then re-execute.
KFPA19326-E A
Zero divisor in arithmetic operation for"aa....aa" type in XQuery, XQuery-no=bb....bb
- A division by zero error occurred during an arithmetic operation on XQuery data type aa....aa in an XQuery query.
- aa....aa: XQuery data type resulting in the division by zero error:
- { xs:decimal | xs:int | xs:double }
- bb....bb: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P: Correct the XQuery query so that division by zero does not occur, and then re-execute.
KFPA19327-E A
Invalid argument of function fn:boolean in XQuery, XQuery-no=aa....aa
- The XQuery function fn:boolean argument in the XQuery query does not apply to any of the following:
- Empty XQuery sequence
- The initial XQuery item is the elemental node XQuery sequence.
- xs:boolean (basic unit value of type)
- xs:string type or xs:untypedAtomic type basic unit value
- Numeric data type basic unit value
- aa....aa: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P: Correct the XQuery query so that the argument of the XQuery function fn:boolean is one of the following, and then re-execute.
- Empty XQuery sequence
- The initial XQuery item is the elemental node XQuery sequence.
- xs:boolean (basic unit value of type)
- xs:string type or xs:untypedAtomic type basic unit value
- Numeric data type basic unit value
KFPA19328-E A
Unable to evaluate aa....aa-th argument value for parameter of function "bb....bb" in XQuery, XQuery-no=cc....cc
- The argument specified in the XQuery function bb....bb cannot be evaluated as a parameter.
- aa....aa: Parameter number
- bb....bb: XQuery function name
- {xs:string | xs:decimal | xs:int | xs:double | xs:dateTime | xs:date
- | xs:time | xs:hexBinary | xs:boolean
- | xs:untypedAtomic | fn:abs | fn:boolean | fn:ceiling
- | fn:compare | fn:concat | fn:contains | fn:count | fn:data
- | fn:day-from-date | fn:day-from-dateTime
- | fn:deep-equal | fn:distinct-values | fn:ends-with
- | fn:floor | fn:hour-from-dateTime | fn:hour-from-time
- | fn:index-of | fn:insert-before | fn:local-name
- | fn:max | fn:min | fn:minutes-from-dateTime
- | fn:minutes-from-time
- |fn:month-from-date | fn:month-from-dateTime
- | fn:name
- | fn:namespace-uri | fn:normalize-space
- | fn:number | fn:remove | fn:reverse
- | fn:round | fn:seconds-from-dateTime
- | fn:seconds-from-time
- | fn:starts-with | fn:string
- | fn:string-length | fn:subsequence | fn:substring
- | fn:substring-after | fn:substring-before | fn:sum
- | fn:translate | fn:year-from-date | fn:year-from-dateTime}
- cc....cc: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P: Correct the XQuery query so that the evaluation results of the argument specified in the XQuery function become XQuery data type values of compatible parameters, and then re-execute.
KFPA19329-E A
Unable to specify unary operation "a" for "bb....bb" type value in XQuery, XQuery-no=cc....cc
- The unary operation cannot be executed on the bb....bb value of the XQuery data type.
- a: Unary operation type
- { +|- }
- bb....bb: XQuery data type of operation item
- { xs:string | xs:dateTime | xs:date | xs:time
- | xs:hexBinary | xs:boolean }
- cc....cc: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P:
- Correct the XQuery query so that the XQuery data types of the operation items are numeric data or xs:untypedAtomic, and then re-execute.
- Note that for xs:untypedAtomic type, it must be a value that can be convert to xs:double type.
KFPA19330-E A
Result of last step expression in path expression contains both nodes and atomic values in XQuery, XQuery-no=aa....aa
- Nodes and basic unit values cannot be included in XQuery path expression XQuery sequences of the final step expression results.
- aa....aa: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P: Correct the XQuery query so that the evaluation results of the last step expression of the XQuery path expression become one of the following, and then re-execute.
- XQuery sequence containing nodes only
- XQuery sequence containing basic unit values only
KFPA19331-E A
Unable to evaluate aa....aa, because context item not defined in XQuery, XQuery-no=bb....bb
- aa....aa cannot be evaluated because a context item is not defined.
- aa....aa: Processing during which the error occurred:
- path expression: XQuery path expression
- context item expression: context item expression
- function "fn:last": XQuery function fn:last
- function "fn:local-name": XQuery function fn:local-name
- function "fn:name": XQuery function fn:name
- function "fn:namespace-uri": XQuery function fn:namespace-uri
- function "fn:normalize-space": XQuery function fn:normalize-space
- function "fn:number": XQuery function fn:number
- function "fn:position": XQuery function fn:position
- function "fn:string": XQuery function fn:string
- function "fn:string-length": XQuery function fn:string-length
- bb....bb: Number of the XQuery query resulting in an error
- S: Ignores this SQL statement.
- P: Use one of the following methods to define the context item at the time the invalid XQuery expression is evaluated, and then re-execute.
- Specifies XML query context items.
- An XQuery expression different from the invalid Xquery expression in the XQuery query is specified in front of that invalid XQuery expression.
KFPA19332-E A
Unable to execute CALL COMMAND statement for command or utility "aa....aa", because bb....bb
- Failed to execute a command or utility using the CALL COMMAND statement.
- aa....aa: Name of the command or utility that failed to execute
- If a command or utility name has not been specified, asterisks (*) are shown.
- bb....bb: Reason
- command not found
- No command or utility was specified.
- environment specification invalid
- An environment variable that cannot be set has been set in the environment specification.
- of no command execution privilege
- You do not have privileges to execute the command or utility.
- specified server not found
- Either the server specified in the server operand does not exist or it is not operating.
- child process creation failed
- A child process cannot be created.
- temporary file creation failed
- A temporary file cannot be created.
- use is restricted
- System configuration in which use of the CALL COMMAND statement has been restricted.
- child process terminated abnormally
- The child process terminated abnormally.
- S: Ignores this SQL statement.
- P:
- If bb....bb is command not found:
- Correct the specified command or utility file name and re-execute.
- If bb....bb is environment specification invalid:
- Check the list of environment variables that can be set in the environment specification, and then re-execute.
- If bb....bb is of no command execution privilege:
- Use the authorization identifier specified in pd_sql_command_exec_users operand.
- If bb....bb is specified server not found:
- Specify the name of another operating server, and then re-execute.
- If bb....bb is use is restricted:
- Release the invalid CALL COMMAND statement, and then re-execute.
- O:
- If bb....bb is child process creation failed:
- Use the following method to ensure that there is sufficient memory or a sufficient number of process that can be used:
- Reduce the number of processes that execute concurrently.
- Increase the number of processes that can be executed.
- Increase the swapping size.
- If bb....bb is temporary file creation failed:
- In UNIX, increase free space on disks that have CALL COMMAND. In Windows, increase free space on disks that have %PDDIR%\tmp.
- If bb....bb is child process terminated abnormally:
- Check if one of the following situations applies. Then, perform all applicable corrective actions and re-execute. If neither of the following situations is applicable, contact the customer support center.
- If the control command (pdcmdexec) process is being terminated by the pdkill command (In UNIX: the OS kill command), re-execute the CALL COMMAND statement so that the process will not be terminated by the pdkill command (or kill command).
- If the host that is executing the command or utility shut down, restart the host and re-execute the CALL COMMAND statement.
KFPA19333-E A
System function aa....aa error, code=bb....bb, during execution of CALL COMMAND statement
- An error occurred in an operating system function while the CALL COMMAND statement was executing.
- aa....aa: System function names
- bb....bb: Error code (errno)
- S: Ignores this SQL statement.
- Action
- Refer to 4.3 System call return codes, and investigate and eliminate the cause of the system function errno, and then re-execute the command.
KFPA19335-E A
Error returned from C function for aa....aa bb....bb.cc....cc, query-no=ddd, SQLSTATE=eeeee, detail="ff....ff"
- An error occurred during execution of the external C stored routine bb....bb.
- aa....aa: External C stored routine type{PROCEDURE|FUNCTION}
- bb....bb: Authorization identifier
- cc....cc: Routine identifier
- ddd: SQL query number
- eeeee: SQLSTATE value set ins the C function implementing the external C stored routine.
- ff....ff: Message text that was set in the C function packaging an external C stored routine, and that displays the detailed reason for an error occurrence.
- S: Ignores this SQL statement.
- P: Follow the specifications that are provided by the programmer of the implemented external C stored routine, and take corrective action according to the SQLSTATE that was set.
- Action
- If there is a problem in the C function that implemented the external C stored routine, contact the programmer who implemented the C function, and request correction of the program.
KFPA19336-E A
Invalid value appeared in output aa....aa parameter of C function for bb....bb cc....cc.dd....dd, inf=ee....ee, query-no=fff
- An invalid output parameter value was specified by the C function that implemented the external C stored routine dd....dd.
- If aa....aa is data(n):
- An invalid value was set in the data part of the nth parameter.
- If aa....aa is SQLSTATE:
- An invalid value was set in SQLSTATE.
- If aa....aa is MESSAGE_TEXT:
- Invalid message text length.
- aa....aa: Output parameter types
- data(n): SQL parameter data part or return value data part.
- n is the sequence number for the parameter of the C function that implemented the external C stored routine. However, return values of the C stored function are 0.
- SQLSTATE: SQLSTATE
- MESSAGE_TEXT: Message text
- bb....bb: External C stored routine type{PROCEDURE|FUNCTION}
- cc....cc: Authorization identifier
- dd....dd: Routine identifier
- ee....ee: Additional information for the output parameter type aa....aa
- If aa....aa is data(n):
SQL parameter data type | Additional information | Meaning |
---|
DECIMAL INTERVAL YEAR TO DAY INTERVAL HOUR TO SECOND DATE TIME TIMESTAMP | Character string with data that was converted to hexadecimals | Invalid data format |
NCHAR NVARCHAR(n) | Data length (unit: byte) | Invalid data length (odd number value) |
- For details about data types, data formats and data lengths, see the manual HiRDB Version 9 SQL Reference.
- If aa....aa is SQLSTATE:
- SQLSTATE value
- If aa....aa is MESSAGE_TEXT:
- Message text length
- fff: SQL query number
- S: Ignores this SQL statement.
- P: Use the following procedure to re-register the C library file, and then re-execute the SQL statement:
- Eliminate the cause of the error, and correct the library source.
For details about the values to set in each output parameter, see CREATE FUNCTION or CREATE PROCEDURE in the manual HiRDB Version 9 SQL Reference.
- Recreate the C library file from the corrected source.
- Use one of the following methods to re-register the C library file that you created:
- Create a UAP that executes REPLACE CLIB, and execute that UAP.
- Ask the administrator to execute the pdclibsync command.
- Action
- Contact the programmer who implemented the C function dd....dd, and request correction of the program. If a pdclibsync command must be executed according to the corrective action for the program, re-execute the command.
KFPA19342-E A
Failed to load aa....aa, C library file=bb....bb, external function=cc....cc
- Failed to load the C library file or external function specified in the routine.
- aa....aa: type{C library file | external function}
- bb....bb: C library file name (truncated just before the 51st character)
- cc....cc: External function identifier (truncated just before the 51st character)
- S: Ignores this SQL statement.
- P:
- If aa....aa is C library file:
- Define the routine using the correct C library file name, and then re-execute. Alternatively, re-register the C library file bb....bb that holds the function cc....cc, and then re-execute.
- If aa....aa is external function:
- Define the routine using the correct external function identifier, and then re-execute. Alternatively, add the function cc....cc to the C library file bb....bb, and then re-execute.
KFPA19345-E A
Unexpected SQL value of floating point numeric
- The following values are used as an SQL floating point:
- NaN (not a number)
- +INF (+ infinity)
- -INF (- infinity)
- S: Ignores this SQL statement.
- P: Change so that NaN, +INF, and -INF, are not used in the SQL floating point value, and then re-execute.
KFPA19346-E A
Unable to specify attribute node after non-attribute node in aa....aa in XQuery, XQuery-no=bb....bb, modify-no=cccc
- The attribute node in aa....aa was specified after a non-attribute node. Specify the attribute node before the non-attribute node.
- aa....aa: Type of XQuery expression resulting in the error
- {content sequence in element constructor|source expression in insert expression}
- content sequence in element constructor: XQuery expression in an XQuery element constructor
- source expression in insert expression: XQuery source expression in an XQuery insert expression
- bb....bb: Query number of the XQuery resulting in an error
- cccc: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression
- S: Ignores this SQL statement or invalidates the transaction.
- P: Correct the SQL statement and re-execute.
KFPA19347-E A
Invalid target expression in aa....aa in XQuery, XQuery-no=bb....bb, modify-no=cccc
- An error occurred in the XQuery target expression in aa....aa.
- aa....aa: Type of XQuery expression resulting in the error
- {insert expression with "into"|insert expression with "as first into"|insert expression with "as last into"|insert expression with "before"|insert expression with "after"|delete expression|rename expression|replace expression}
- bb....bb: Query number of the XQuery resulting in an error
- cccc: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression
- S: Ignores this SQL statement or invalidates the transaction.
- P: Correct the SQL statement as described in the following table, and then retry the operation:
Type of XQuery expression resulting in an error (aa....aa) | Explanation | Action |
---|
Any of the following:
- insert expression with "into" (XQuery insert expression with into specified)
- insert expression with "as first into" (XQuery insert expression with as first into specified)
- insert expression with "as last into" (XQuery insert expression with as last into specified)
| Only an XQuery sequence consisting of a single element node can be specified in the XQuery target expression. | Specify an XQuery sequence consisting of a single element node in the XQuery target expression. |
Either of the following:
- insert expression with "before" (XQuery insert expression with before specified)
- insert expression with "after" (XQuery insert expression with after specified)
| An XQuery sequence consisting of multiple nodes cannot be specified in the XQuery target expression. In addition, an XQuery sequence consisting of a document node, attribute node, or atomic value cannot be specified. | Specify an XQuery sequence consisting of a single element node, text node, comment node, or processing instruction node in the XQuery target expression. |
delete expression (XQuery delete expression) | An atomic value cannot be specified in the XQuery target expression. | Specify an XQuery sequence consisting of zero or more nodes in the XQuery target expression. |
rename expression (XQuery name change expression) | An XQuery sequence consisting of multiple nodes cannot be specified in the XQuery target expression. In addition, an XQuery sequence consisting of a document node, text node, comment node, or atomic value cannot be specified. | Specify an XQuery sequence consisting of a single element node, attribute node, or processing instruction node in the XQuery target expression. |
replace expression (XQuery replace expression) | An XQuery sequence consisting of multiple nodes cannot be specified in the XQuery target expression. In addition, an XQuery sequence consisting of a document node or atomic value cannot be specified. | Specify a single element node, attribute node, text node, comment node, or processing instruction node in the XQuery target expression. |
KFPA19348-E A
Node type of source expression conflicts with target expression in replace expression without "value of" in XQuery, XQuery-no=aa....aa, modify-no=bbbb
- An error occurred in an XQuery source expression in an XQuery replace expression that does not have a value of specification.
- If the XQuery target expression is an element node, text node, comment node, or processing instruction node:
You cannot specify attribute nodes in the XQuery source expression. Specify an XQuery sequence consisting of zero or more element nodes, text nodes, comment nodes, or processing instruction nodes in the XQuery source expression.
- If the XQuery target expression is an attribute node:
Only attribute nodes can be specified in the XQuery source expression. Specify an XQuery sequence of zero or more attribute nodes in the XQuery source expression.
- aa....aa: Query number of the XQuery resulting in an error
- bbbb: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression
- S: Ignores this SQL statement or invalidates the transaction.
- P: Correct the SQL statement and re-execute.
KFPA19349-E A
Target expression in "modify" clause not created by "copy" clause, in transform expression of XQuery, XQuery-no=aa....aa, modify-no=bbbb
- In the XQuery transform expression, only a node created by the copy clause can be specified in the XQuery target expression that specifies the target of the modify clause. Specify a node created by the copy clause in the XQuery target expression.
- aa....aa: Query number of the XQuery resulting in an error
- bbbb: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression
- S: Ignores this SQL statement or invalidates the transaction.
- P: Correct the SQL statement and re-execute.
KFPA19350-E A
Same target expression specified in more than one aa....aa in XQuery, XQuery-no=bb....bb, modify-no=cccc
- You cannot specify the same node for the XQuery target expression in more than one aa....aa. Specify different nodes for the XQuery target expression in each aa....aa.
- aa....aa: Type of XQuery expressions resulting in the error
- {rename expressions|replace expressions without "value of"|replace expressions with "value of"}
- rename expressions: XQuery name change expression
- replace expressions without "value of": XQuery replace expression without value of specified
- replace expressions with "value of": XQuery replace expression with value of specified
- bb....bb: Query number of the XQuery resulting in an error
- cccc: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression
- S: Ignores this SQL statement or invalidates the transaction.
- P: Correct the SQL statement and re-execute.
KFPA19351-E A
Empty sequence specified as target expression in aa....aa in XQuery, XQuery-no=bb....bb, modify-no=cccc
- An empty XQuery sequence cannot be specified in the XQuery target expression in aa....aa. Specify a non-empty XQuery sequence in the XQuery target expression.
- aa....aa: Type of XQuery expression resulting in the error
- {insert expression|rename expression|replace expression}
- insert expression: XQuery insert expression
- rename expression: XQuery name change expression
- replace expression: XQuery replace expression
- bb....bb: Query number of the XQuery resulting in an error
- cccc: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression
- S: Ignores this SQL statement or invalidates the transaction.
- P: Correct the SQL statement and re-execute.
KFPA19352-E A
Inserting attribute node "after" or "before" node without parent element node specified in XQuery, XQuery-no=aa....aa, modify-no=bbbb
- When you specify an attribute node in an XQuery source expression in an XQuery insert expression which specifies before or after, you cannot specify a node that does not have a parent element node in the XQuery target expression.
- aa....aa: Query number of the XQuery resulting in an error
- bbbb: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered starting from the first expression
- S: Ignores this SQL statement or invalidates the transaction.
- P: Correct the SQL statement and re-execute.
KFPA19353-E A
Unable to specify constructor expression in source expression of replace expression with "value of" in XQuery, XQuery-no=aa....aa, modify-no=bbbb
- An XQuery constructor cannot be specified in an XQuery source expression in an XQuery replace expression which specifies value of. Specify an XQuery expression alone in the XQuery source expression.
- aa....aa: Query number of the XQuery resulting in an error
- bbbb: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered from the first expression
- S: Ignores this SQL statement or invalidates the transaction.
- P: Correct the SQL statement and re-execute.
KFPA19354-E A
Result of atomization applied to new name expression in rename expression in XQuery not a single atomic value of type xs:string or xs:untypedAtomic, XQuery-no=aa....aa, modify-no=bbbb
- The result of atomizing an XQuery expression alone in an XQuery name change expression must be a single node or atomic value of type xs:string or xs:untypedAtomic. Specify an expression that will resolve to a single node or atomic value of type xs:string or xs:untypedAtomic.
- aa....aa: Query number of the XQuery resulting in an error
- bbbb: Number indicating the position of the XQuery modify expression within the XQuery transform expression resulting in an error, numbered from the first expression
- S: Ignores this SQL statement or invalidates the transaction.
- P: Correct the SQL statement and re-execute.
KFPA19400-E A
aa....aa statement executed, signal value=bb....bb
- The aa....aa statement caused an error.
- aa....aa: SQL statement types {SIGNAL|RESIGNAL}
- bb....bb: The signal values specified in the SIGNAL statement or RESIGNAL statement.
- If a condition name is specified in the signal name:
- condition-name
- When SQLSTATE is specified in the signal value:
- SQLSTATE:XXXXX (XXXXX is the SQLSTATE value).
- S: Ignores this SQL statement, or invalidates this transaction.
- P: Refer to the SQL procedure or trigger definition to check the reason why the SIGNAL statement or RESIGNAL statement was executed. If the RESIGNAL statement is executed, you can check the error information history by referring to the GET DIAGNOSTICS diagnostic information.
KFPA19403-E A
No error occurred before executing RESIGNAL statement
- No SQL procedure statement was found that caused an error before executing the RESIGNAL statement.
- S: Ignores this SQL statement, or invalidates this transaction.
- P: Correct the SQL procedure or trigger definition and re-execute the SQL statement. To cause an error after executing the SQL procedure statement that does not cause an error, use the SIGNAL statement.
KFPA19404-E A
Handler raised recursively
- The same handler was invoked recursively.
- S: Ignores this SQL statement, or invalidates this transaction.
- P: To prevent the same handler from being invoked again when handler operation is delayed, redefine the SQL routine or trigger and re-execute this SQL statement.
KFPA19405-E A
Invalid aa....aa of parameter in "LIMIT"clause.
- The value of the variable specified in the LIMIT clause is an invalid data type.
- aa....aa: Invalid type
- data type: The data type is not INTEGER or SMALLINT.
- value: The value of the variable either is not in the range 1-2,147,483,647 or is a null value.
- S: Ignores this SQL statement.
- P: When aa....aa is data type, change the data type of the variable specified in the LIMIT clause to INTEGER or SMALLINT, and then re-execute this SQL statement. If aa....aa is value, change the value of the variable specified in the LIMIT clause to between 1 and 2,147,483,647 inclusive, and then re-execute this SQL statement.
KFPA19406-E A
Unable to specify condition name associated with SQLCODE value in aa....aa statement, condition name=bb....bb
- The condition name associated with the SQLCODE value in the SIGNAL statement or RESIGNAL statement could not be specified.
- aa....aa: Type of SQL statement {SIGNAL|RESIGNAL}
- bb....bb: The condition name specified as the signal value in the SIGNAL statement or RESIGNAL statement
- S: Ignores this SQL statement, or invalidates this transaction.
- P: Re-evaluate the SQL procedure or trigger definition and check whether the condition name associated with the SQLCODE value in the SIGNAL statement or RESIGNAL statement was specified. When specifying the condition name in the SIGNAL statement or RESIGNAL statement, do not specify the SQLCODE value in the condition declaration.
KFPA19407-E A
Invalid specification in aaaaaaa statement with bbb clause
- The format of the INSERT, UPDATE, or DELETE statement specified in the FOR clause or the format of the EXECUTE statement specified in the BY clause is invalid.
- aaaaaaa: Type of SQL statement {INSERT|UPDATE|DELETE|EXECUTE}
- bbb: Clause name {FOR|BY}
- S: Ignores this SQL statement.
- P: Correct either the SQL statement or the UAP as follows, and then re-execute:
- To specify an embedded variable array and insert multiple columns into the table in column units:
FOR: Embedded variable
INSERT INTO [authorization-identifier.]table-identifier [(column-name[,column-name]...)]
VALUES(:embedded-variable-array[:indicator-variable-array]
[,:embedded-variable-array[:indicator-variable-array]]...)
[WITH ROLLBACK]
- To specify an embedded variable array and insert multiple columns into the FIX attributes table in column units:
FOR: Embedded variable
INSERT INTO [authorization-identifier.]table-identifier (ROW)
VALUES(:embedded-variable-array[:index-variable-array])
[WITH ROLLBACK]
- To preprocess SQL (the INSERT statement) and execute using the EXECUTE statement:
(SQL to be preprocessed)
INSERT INTO [authorization-identifier.]table-identifier [(column-name[,column-name]...)]
VALUES (? parameter [,? parameter]...)
[WITH ROLLBACK]
INSERT INTO [authorization-identifier.]table-identifier (ROW)
VALUES (? parameter)
[WITH ROLLBACK]
KFPA19408-E A
Unable to execute SQL except INSERT, UPDATE or DELETE using EXECUTE statement with BY clause
- The EXECUTE statement specified by the BY clause can only execute the INSERT, UPDATE, or DELETE statement.
- S: Ignores this SQL statement.
- P: When executing a query other than the INSERT, UPDATE, or DELETE statement in the EXECUTE statement, correct the SQL statement or the UAP to remove the specification of the BY clause, and then re-execute the SQL statement.
KFPA19409-E A
Unable to insert into aa....aa using bb....bb statement with cc....cc clause
- When inserting an INSERT statement specifying the FOR clause or an EXECUTE statement specifying the BY clause, insertions cannot be made into the following items:
- A BINARY type column with a definition length of 32,001 bytes or more
- A table with a BINARY column with a definition length of 32,001 bytes or more in the WITH DEFAULT specification
- A BLOB type column
- A table with a BLOB column in the WITH DEFAULT specification
- A column with the abstract data type
- aa....aa: Insertion target
- {column of BINARY data type (length over 32000)|table which has BINARY data type (length over 32000) column with WITH DEFAULT|column of BLOB data type|table which has BLOB data type column with WITH DEFAULT|column of abstract data type}
- bb....bb: Type of SQL statement {INSERT|EXECUTE}
- cc....cc: Clause name {FOR|BY}
- S: Ignores this SQL statement.
- P: When executing the INSERT statement specified in the FOR clause or the EXECUTE statement specified in the BY clause, correct the SQL statement or the UAP as follows and re-execute the SQL statement:
- Do not insert anything into a BINARY type column with a definition length of 32,001 bytes or more.
- Do not insert anything into a table with any BINARY columns with a definition length of 32,001 bytes or more specified in WITH DEFAULT.
- Do not insert anything into a BLOB type column (do not specify the null value as the insertion value).
- Do not insert anything into a table with any BLOB columns specified in WITH DEFAULT.
- Do not insert anything into an abstract data type column.
KFPA19411-E A
Unable to lock shared table in RDAREA which containing table used by cursor
- An attempt was made to execute the LOCK statement using the EXCLUSIVE specification for a shared table by an RDAREA that stores a shared table for which a cursor is open.
- S: Ignores this SQL statement.
- P: If the LOCK statement was executed using the EXCLUSIVE specification for a shared table, close the open cursor for the other shared table that is stored in the RDAREA that stores the target shared table, and then execute the LOCK statement.
KFPA19450-E A
Invalid trigger definition code=aa(bb....bb)
- An error was detected in the trigger definition.
- aa: Reason code
- bb....bb: Additional error information
Reason code (aa) | Additional information (bb....bb) | Meaning |
---|
01 | Another user's table | The trigger cannot be defined in another user's table. |
02 | Non base table cc....cc | The trigger can only be defined in a permanent base table. cc....cc: { view table | temporary table} |
03 | Table not found | A table for defining the trigger cannot be found. |
04 | Duplicate "OLD ROW" or "NEW ROW" | OLD ROW and NEW ROW can only be specified one time each in the old or new values alias list. |
05 | "OLD ROW" in insert trigger | When specifying INSERT in a trigger execution event, OLD ROW cannot be specified. |
06 | "NEW ROW" in delete trigger | When specifying DELETE in a trigger execution event, NEW ROW cannot be specified. |
07 | Duplicate name in old or new values alias | The same name cannot be specified in OLD ROW and NEW ROW. |
08 | "OLD ROW" or "NEW ROW" in "STATEMENT TRIGGER" | When specifying FOR EACH STATEMENT, NEW ROW or OLD ROW cannot be specified. |
09 | Num of trigger columns exceed 30000 | The number of columns specified by the trigger execution event exceeds 30,000. |
10 | Duplicate trigger columns "dd....dd" | The trigger execution event specified duplicate column names. dd....dd: Column name |
11 | Trigger column "dd....dd" not found in table | The column specified by the trigger execution event was not found in the table defining triggers. dd....dd: Column name |
12 | SQL data change statement in "BEFORE TRIGGER" | A trigger definition specifying BEFORE during the trigger action time cannot specify the update SQL statements (INSERT, UPDATE or DELETE) in the trigger SQL statement. |
13 | Invalid column reference "dd....dd" | A repetition column, abstract data type column, or reserved column cannot be referenced by an old or new values correlation name. dd....dd: Column name |
14 | Invalid triggered SQL statement | A PURGE TABLE statement, COMMIT statement, or ROLLBACK statement cannot be specified in the trigger SQL statement. |
15 | Trigger table in triggered SQL statement | A table defining triggers cannot be specified in the trigger SQL statement. |
16 | SQL function invocation in "BEFORE TRIGGER" | Only function invocation of the default constructor can be specified in the trigger SQL statement in the trigger definition specifying BEFORE during the trigger action time. |
17 | ROW for old or new values alias | ROW cannot be specified in the new or old values correlation name. |
19 | Unqualified column of trigger table in triggered action | To specify the column name of a table specified in the trigger action search condition or the trigger definition in the trigger SQL statement, you must qualify the column name in the new or old values correlation name. |
20 | Invalid use of ? parameter | The ? parameter cannot be specified in the trigger SQL statement. |
21 | Call statement in "BEFORE TRIGGER" | A CALL statement cannot be specified in the trigger SQL statement in the trigger definition specifying BEFORE during the trigger action time. |
22 | Invalid use of JAVA procedure or function | A Java stored procedure or a Java stored function cannot be specified in the trigger SQL statement. |
23 | Invalid use of GET_JAVA_STORED_ROUTINE_SOURCE specification | GET_JAVA_STORED_ROUTINE_SOURCE cannot be specified in the trigger SQL statement. |
24 | Invalid use of default specification | If the default value specifies the CURRENT_TIMESTAMP column of the USING BES specification in the assignment target of the assignment statement, DEFAULT cannot be specified as the assignment value. |
25 | Invalid use of reserved column "dd....dd" in trigger columns | A reserved column cannot be specified in the trigger event column. dd....dd: Column name |
- S: Ignores this SQL statement.
- P: Correct this SQL statement, and then re-execute.
KFPA19451-E A
Unable to execute trigger aa....aa.bb....bb due to cc....cc
- Trigger aa....aa.bb....bb cannot be executed due to the constraint indicated in cc....cc.
- aa....aa: Authorization identifier
- bb....bb: Trigger identifier
- cc....cc: Constraint
- more than 16 nest:
- The number of nesting levels exceeded 16 during trigger execution.
- COMMIT/ROLLBACK/PURGE TABLE statement:
- The COMMIT, ROLLBACK or PURGE TABLE statements cannot be executed by a trigger.
- Java routine:
- External Java stored routines cannot be executed by a trigger.
- S: Ignores this transaction.
- P: Take the following actions for each constraint:
- For more than 16 nest:
- Correct the trigger definition so the number of trigger nesting levels does not exceed 16, and then re-execute.
- For a COMMIT/ROLLBACK/PURGE TABLE statement:
- Correct the SQL stored procedure invoked by the CALL statement from inside a trigger so neither COMMIT nor ROLLBACK is executed, and then re-execute the statement.
- For Java routine:
- Make corrections so that the external Java stored routine is not executed by the trigger, and then retry the operation.
KFPA19452-E A
Unable to specify SQL optimization specification for "aaaaa" in query for table derived from "bb....bb"
- The following SQL optimization specifications cannot be specified by queries to a table join (including joined tables) and derived or by queries to tables derived by specifying set operations:
- SQL optimization specification of the index used
- SQL optimization specification of the joining format (joining type SQL optimization specifications can be specified for named derived tables generating internal derived tables)
- The following are the conditions for creating internal derived tables:
- One of the following items is either included in a subquery that is a named derived table in a query to a named derived table derived by specifying SELECT DISTINCT, or is directly included:
- GROUP BY clause, a HAVING clause, or a set function
- SELECT DISTINCT
- Table join (including outer join and inner join)
- Specification of value expressions other than a column specification in the selection expression
- One or more columns of a name derived table specified by the FROM clause are not specified one time each
- NEXT VALUE expression
- One of the following items is directly included in a query to a named derived table derived by specifying the GROUP BY clause, HAVING clause, or a set function:
- GROUP BY clause, a HAVING clause, or a set function
- Table join (including outer join and inner join)
- Window function
- NEXT VALUE expression
- A query for a named derived table, derived by specifying a value expression other than a column specification as the selection expression, directly includes one of the following:
- GROUP BY clause, HAVING clause, or set function
- Window function
- Joined table
- A query for a named derived table, derived by specifying a set function with DISTINCT, directly includes one of the following:
- GROUP BY clause, HAVING clause, or set function
- SELECT DISTINCT
- Window function
- A query for a named derived table, derived by specifying a table join (including both outer joins and inner joins), directly includes a table join (including both outer joins and inner joins) and one of the specified table join operations is a table join specification.
- A query for a named derived table, derived by specifying a scalar subquery as a selection expression, directly includes one of the following:
- SELECT DISTINCT
- GROUP BY clause, HAVING clause, or set function
- Table join (including both outer joins and inner joins)
- A value expression other than a column specification in a selection expression
- A scalar subquery specified in a selection expression
- The same column derived from a value expression containing a subquery, specified more than once in the selection expression for a named derived table
- A column derived from a value expression containing a subquery, specified as an external reference column in the selection expression for a named derived table
- A viewed table defined before HiRDB version 07-02
- A query for a named derived table, derived from a set operation, which satisfies one of the following:
- One of the operators of the set operation includes an internal derived table query, a query that specifies a derived table, or a query that specifies a subquery in a selection expression.
- One of the operators of the set operation and the query for the named derived table satisfy one of the conditions of 1 through 6.
- A query for a named derived table, derived from a set operation that includes other than UNION ALL, which directly includes one of the following:
- GROUP BY clause, HAVING clause, or set function
- SELECT DISTINCT
- Table join (including both outer joins and inner joins)
- WHERE clause
- Subquery
- Value expression other than a column specification in a selection expression
- Selection expression in which all of the columns of a named derived table specified in the FROM clause are not each specified once
- NEXT VALUE expression
- A query for a named derived table derived from a set operation that includes only UNION ALL, which directly includes one of the following:
- GROUP BY clause, HAVING clause, or a set function
- Window function
- WHERE clause or subquery (however, only a subquery, a set operation operator, or an INSERT statement query)
- Function call or system definition scalar function
- Component specification
- WRITE specification
- GET_JAVA_STORED_ROUTINE_SOURCE specification
- Sort specification with items not in the selection expression
- Subquery for a named derived table derived from a set operation specified in the FROM clause
- Subquery that specifies a derived table
- Subquery specified in a value expression other than a column specification in the GROUP BY clause
- The data type of an SQL variable specified in a selection expression or an SQL parameter is one of the following:
BLOB type
BINARY type 32,001 bytes or larger
Abstract data type
BOOLEAN type
- The query specification specified for the table-joining of named derived tables derived by a set operation consisting solely of UNION ALL specifies one of the following:
- A named derived table in a table reference other than at the leftmost outer table for an outer join
- The FROM clause specifying a named derived table, which specifies a comma join (that is, specifies a different table reference than the joined table for which a derived table is specified)
- A subquery or a derived table
- A query specification contained either in a subquery or in the operation term for a set operation
- A set operation term that derives named derived tables and contains one of the following:
Table join
GROUP BY clause, HAVING clause, or a set function
SELECT DISTINCT
A value expression in a selection expression other than a column specification
A query that creates an inner derived table
A query specifying a derived table
- A named derived table derived by specifying a set operation (in addition to a named derived table)
- One of the following, in the table reference to a joined table specifying a named derived table:
A named derived table derived by specifying the joining of tables
A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
A named derived table derived by specifying SELECT DISTINCT
A named derived table derived by specifying a value expression other than a column specification in a selection expression
A named derived table derived by specifying a query that creates an inner derived table
A named derived table derived by specifying a subquery
- The total number of tables obtained by the following expression is greater than 65:
Total number of tables = a + b
c + d
a: Total number of tables from which named derived tables are derived
b: Number of set operations from which named derived tables are derived + 1
c: Total number of tables specified on the right side of an outer join
d: If a query other than a query for which a named derived table is specified is also specified, the total number of tables specified in the query
- aaaaa: {index|join}
- bb....bb: {join|set operation}
- S: Ignores this SQL statement.
- P: Correct this SQL statement and re-execute.
KFPA19453-E A
Unable to specify SQL optimization specification for index to view or "WITH" query which derives internal table
- The following SQL optimization specifications for the used index cannot be specified by a query creating internal derived tables:
The following are the conditions for creating internal derived tables: - One of the following items is either included in a subquery that is a named derived table in a query to a named derived table derived by specifying SELECT DISTINCT, or is directly included:
- GROUP BY clause, HAVING clause, or set function
- SELECT DISTINCT
- Table join (including outer join and inner join)
- Specification of value expressions other than a column specification in the selection expression
- One or more columns of a name derived table specified by the FROM clause are not specified one time each
- One of the following items is directly included in a query to a named derived table derived by specifying the GROUP BY clause, HAVING clause, or a set function:
- GROUP BY clause, HAVING clause, or set function
- Table join (including outer join and inner join)
- Window function
- One of the following items is directly included in a query to a named derived table derived by specifying a value expression other than a column specification as a selection expression:
- GROUP BY clause, HAVING clause, or set function
- Window function
- Joined table
- A query on a named derived table derived by directly specifying a set function with DISTINCT contains one of the following:
- GROUP BY clause, HAVING clause, or set function
- SELECT DISTINCT
- Window function
- An inquiry to a named derived table derived by specifying a table join (including outer join and inner join) directly includes a table join (including outer join and inner join), and specifies the table join.
- A query on a named derived table derived by directly specifying a scalar subquery as a selection expression contains one of the following:
- SELECT DISTINCT
- GROUP BY clause, HAVING clause, or set function
- Table join (including outer join and inner join)
- A value expression other than a column specification specified in a selection expression
- A scalar subquery specified in a selection expression
- The same column derived from a value expression containing a subquery, specified more than once in the selection expression for a named derived table
- A column derived from a value expression containing a subquery, specified as an external reference column in the selection expression for a named derived table
- A viewed table defined before HiRDB version 07-02
- A query for a named derived table derived from a set operation, which satisfies one of the following:
- One of the operators of the set operation includes an internal derived table query, a query that specifies a derived table, or a query that specifies a subquery in a selection expression.
- One of the operators of the set operation and the query for the named derived table satisfy one of the conditions of 1 through 6 above.
- A query for a named derived table derived from a set operation that includes other than UNION ALL, which directly includes one of the following:
- GROUP BY clause, HAVING clause, or a set function
- SELECT DISTINCT
- Table join (including external or internal joins)
- WHERE clause
- Subquery
- Value expression other than a column specification in a selection expression
- In a selection expression, the columns of a named derived table specified in the FROM clause are not specified once each
- A query for a named derived table derived from a set operation that includes only UNION ALL, which directly includes one of the following:
- GROUP BY clause, HAVING clause, or a set function
- Window function
- WHERE clause or subquery (however, only a subquery, a set operation operator, or an INSERT statement query)
- Function call or system definition scalar function
- Component specification
- WRITE specification
- GET_JAVA_STORED_ROUTINE_SOURCE specification
- Sort specification with items not in the selection expression
- Subquery for a named derived table derived from a set operation specified in the FROM clause
- Subquery that specifies a derived table
- Subquery specified in a value expression other than a column specification in the GROUP BY clause
- The data type of an SQL variable specified in a selection expression or an SQL parameter is one of the following:
BLOB type
BINARY type 32,001 bytes or larger
Abstract data type
BOOLEAN type
- The query specification specified for the table-joining of named derived tables derived by a set operation consisting solely of UNION ALL specifies one of the following:
- A named derived table in a table reference other than at the leftmost outer table for an outer join
- The FROM clause specifying a named derived table, which specifies a comma join (that is, specifies a different table reference than the joined table for which a derived table is specified)
- A subquery or a derived table
- A query specification contained either in a subquery or in the operation term for a set operation
- A set operation term that derives named derived tables and contains one of the following:
Table join
GROUP BY clause, HAVING clause, or a set function
SELECT DISTINCT
A value expression in a selection expression other than a column specification
A query that creates an inner derived table
A query specifying a derived table
- A named derived table derived by specifying a set operation (in addition to a named derived table)
- One of the following, in the table reference to a joined table specifying a named derived table:
A named derived table derived by specifying the joining of tables
A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
A named derived table derived by specifying SELECT DISTINCT
A named derived table derived by specifying a value expression other than a column specification in a selection expression
A named derived table derived by specifying a query that creates an inner derived table
A named derived table derived by specifying a subquery
- The total number of tables obtained by the following expression is greater than 65:
Total number of tables = a + b
c + d
a: Total number of tables from which named derived tables are derived
b: Number of set operations from which named derived tables are derived + 1
c: Total number of tables specified on the right side of an outer join
d: If a query other than a query for which a named derived table is specified is also specified, the total number of tables specified in the query
- S: Ignores this SQL statement.
- P: Correct the SQL statement, and then re-execute.
KFPA19454-E A
Unable to insert using aa....aa statement with bb....bb clause into table with row-level trigger
- The following SQL statements cannot be used to batch-insert multiple rows into a table with row-level triggers defined:
- An INSERT statement specifying a FOR clause
- An EXECUTE statement specifying a BY clause
- aa....aa: {INSERT|EXECUTE}
- bb....bb: {FOR|BY}
- S: Ignores this SQL statement.
- P: Correct the SQL statement or the UAP to enable the insertion of one row at a time, and then re-execute the SQL statement.
KFPA19455-E A
Unable to update specified column using new values correlation name in BEFORE trigger
- A trigger definition specifying BEFORE during the trigger action time (BEFORE trigger) cannot use the new values correlation name to qualify and update the following columns:
- Columns specifying SYSTEM GENERATED
- Also, BEFORE triggers with INSERT trigger execution events cannot use the new values correlation name to qualify and update the following column:
- A column specifying the partitioning key of the partitioning table (excluding flexible hash partitioning tables)
- S: Invalidates this transaction.
- P: Correct the trigger definition so that the new values correlation name does not qualify and update the column specifying SYSTEM GENERATED and the column specified in the partitioning key.
KFPA19456-E A
Unable to execute SQL in 64bit version, because check constraint "aa....aa" in bb....bb."cc....cc" created in 32bit version
- HiRDB cannot execute SQL in 64-bit mode, because the table bb....bb."cc....cc" for which the check constraint was defined was created in 32-bit mode.
- aa....aa: Name of the check constraint
- bb....bb: Authorization identifier of the table that defined the check constraint
- cc....cc: Table identifier of the table that defined the check constraint
- S: Ignores this SQL statement. If it is a definition SQL statement, it is rolled back.
- P: Restart HiRDB in 64-bit mode, and then re-define the check constraint. For details on migrating tables that have a check constraint defined to 64-bit mode, see the HiRDB Version 9 Installation and Design Guide.
KFPA19459-E A
Unable to specify component specification for derived column from abstract data type, query-no=aaa
- A component specification cannot be made for an abstract data type column derived by a value expression other than a column specification.
- aaa: Query number
- S: Ignores this SQL statement. If it is a definition SQL statement, it is rolled back.
- P: Correct the SQL statement and re-execute.
KFPA19502-E A
Error occurred in UAP environment file aa....aa, operand=bb....bb,reason code=cc....cc
- An error occurred in the UAP environment definition file.
- aa....aa: UAP environment definition file name
- bb....bb: Name of the operand causing the error
- One asterisk (*) is displayed when no operand can be specified.
- cc....cc: Reason code
- S: Ignores this SQL statement.
- P: Take appropriate action for the output reason code.
- Action
- Take appropriate action for the output reason code.
Reason code | Description | Action by the programmer | Action by the HiRDB administrator |
---|
1 | A memory shortage occurred. | Re-execute the UAP. If the same error recurs, contact the HiRDB administrator. | Take the following steps to increase the amount of available memory:
- Reduce the number of concurrently executing processes.
- Increase the swap area.
- Increase the real memory.
- Reduce the number of RDAREAs specified in the -r option of the pdlbuffer operand. Note that a maximum of 3,200 RDAREAs can be defined with the -r option.
|
2 | Communication to the dictionary server failed. | Confirm that the dictionary server started normally. |
3 | Dictionary search failed. | None | Correct the status of the data dictionary RDAREA. |
99 | An internal HiRDB error occurred. | Save the files under %PDDIR%\spool, %PDDIR%\lib\sysconf, or %PDDIR%\lib\sysdef and contact the customer support center. |
100 | The UAP environment definition file could not be opened. | Confirm that the UAP environment definition file can be found or that the HiRDB administrator can open this file (check the permissions settings of the %PDCONFPATH%\pduapenv directory or the UAP environment definition file). |
101 | Invalid definition | Take corrective action according to the error message that is output to the event log (in UNIX, syslogfile) on the server machine of the connection target HiRDB server. |
300 | An error was detected in the RDAREA type specified in the pdlbuffer operand. | Correct the RDAREA name specified in the pdlbuffer operand of the UAP environment definition. |
301 | Option required for the pdlbuffer operand is missing, or an option that cannot be specified was specified. | Correct the option specification of the pdlbuffer operand in the UAP environment definition. |
302 | Duplicate local buffer names, RDAREA names, or index names are specified in the pdlbuffer operand. | Correct the local buffer name, RDAREA name, or index names specified in the pdlbuffer operand of the UAP environment definition. |
303 | The local buffer count exceeded the maximum value. | Set the number of pdlbuffer operands specified in the UAP environment definition to 100 or less. For HiRDB/Parallel Server, set the value for each server to 100 or fewer. |
KFPA19503-E A
Unable to begin transaction during maintenance of HiRDB
- The pdchgconf command or the pdprgrenew command is executing, or a transaction is queuing due to the pdtrnqing command. As a result, transactions executing a stored procedure, ALTER PROCEDURE, ALTER ROUTINE, or ALTER TRIGGER cannot be started.
- S: Ignores this SQL statement, or interrupts.
- P: If the pdchgconf or pdprgrenew command is executing, wait until the command terminates, and then re-execute the UAP. In the case of transaction queuing due to the pdtrnqing command, release transaction queuing, and then re-execute the UAP.
KFPA19506-E A
Extended statement name value "aa....aa" already defined
- The extended statement name value aa....aa identifies another SQL statement.
- aa....aa: SQL statement identifier that is the value of the extended statement name
- S: Ignores this SQL statement.
- P: Correct this SQL statement and re-execute.
KFPA19507-E A
PREPARE statment missing for extended statement name value "aa....aa"
- No PREPARE statement is defined for the SQL statement with the extended statement name value "aa....aa".
- aa....aa: SQL statement identifier that is the value of the extended statement name
- S: Ignores this SQL statement.
- P: Define the PREPARE statement for the extended statement name SQL statement.
KFPA19508-E A
Open cursor associated with prepared statement identified by "aa....aa" exists
- Because the associated cursor is open, assignment of the SQL statement for the extended statement name value "aa....aa" cannot be released.
- aa....aa: SQL statement identifier that is the value of the extended statement name
- S: Ignores this SQL statement.
- P: Before executing the DEALLOCATE PREPARE statement, close the associated cursor and re-execute.
KFPA19509-E A
ALLOCATE CURSOR statement missing for cursor "aa....aa"
- The cursor assignment is missing for the specified cursor "aa....aa".
- aa....aa: Cursor name
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19510-E A
Procedure aa....aa."bb....bb" not invoked
- The procedure aa....aa."bb....bb" is not invoked in the same SQL session.
- aa....aa: Authorization identifier
- bb....bb: Routine identifier
- S: Ignores this SQL statement.
- P: Before executing ALLOCATE CURSOR, revise the procedure specified by ALLOCATE CURSOR to be called in the same SQL session, and re-execute.
KFPA19511-E A
Another cursor already allocated for procedure aa....aa."bb....bb"
- A cursor is already assigned to the procedure aa....aa."bb....bb".
- aa....aa: Authorization identifier
- bb....bb: Routine identifier
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19512-E A
Preparation for requested SQL became invalid
- Preprocessing for the SQL statement that requested execution has become invalid.
- S: Ignores this SQL statement.
- P: Perform preprocessing of the SQL statement again using the PREPARE statement, and request execution of the SQL statement.
KFPA19513-E A
Number of aa....aa exceeds bbbb
- The number of aa....aa exceeds the maximum of bbbb.
- When aa....aa is extended statement name
The number of extended statement names that identify the preprocessed SQL statement exceeds 4095.
- When aa....aa is extended cursor name
The number of extended cursor names that identify the cursors allocated by ALLOCATE CURSOR exceeds 4095.
- aa....aa: {extended statement name | extended cursor name}
- bbbb: 4095
- S: Ignores this SQL statement.
- P: Revise the UAP so that the number of aa....aa does not exceed the maximum. By executing the DEALLOCATE PREPARE statement, you can ensure that the extended statement names and extended cursor names do not identify the SQL statements and cursors.
KFPA19517-E A
Error occurred in servers for primary facilities,"aa....aa"
- During connection, an error occurred in the server providing the primary facilities.
- aa....aa: Detailed error message
- If the details of the message exceed 190 characters, all subsequent characters are omitted.
- S: Ignores this SQL statement.
- P: Refer to the details of the error message that was output by the server providing the primary facilities, and then take one of the following actions:
- Refer to the output message, and if there is a programmer measure, resolve the problem and execute the SQL again.
- Refer to the output message, and if there is no programmer measure, contact the HiRDB administrator.
- O: Contact the HiRDB administrator.
- Action
- Eliminate the error based on the detailed error message returned by the server providing the primary facilities.
KFPA19518-E A
Unable to access from host aa....aa
- It is not possible to execute a related program product or utility from the host aa....aa.
- aa....aa: The IP address of the related program product or utility (in the format xxx.xxx.xxx.xxx)
- S: Ignores this SQL statement.
- Action
- Decide whether the host executing the related program product or utility must be added to the pd_security_host_group operand in the system common definition. Add a host if necessary, and then restart HiRDB.
KFPA19520-E A
Unable to execute SQL due to implicit rollback during execution of external routine.
- Because an error accompanied by an implicit rollback occurred during external routine execution, the SQL statement cannot be executed. For a Java stored procedure, a database manipulation method other than the close method for the Connection object cannot be executed.
- S: Ignores this SQL statement.
- P: If an error accompanied by an implicit rollback occurs, correct this so that the external routine terminates.
- For a Java stored procedure:
Execute the close method for the Connection object before terminating the Java stored procedure.
KFPA19521-E A
aa....aa in client environment variable PDTMPTBLRDAREA
- The error indicated in aa....aa occurred in the specification of the client environment definition PDTMPTBLRDAREA.
- aa....aa: Cause of error
- S: Terminates connection processing.
- O: Based on the cause of the error, take the appropriate corrective action as described in the following table, and then retry the operation:
Cause of error (aa....aa) | Meaning | Action |
---|
No avaliable RDAREA names | There are no temporary table RDAREAs available. | Search the dictionary table (the SQL_RDAREAS table) for possible errors in the temporary table RDAREA names specified in PDTMPTBLRDAREA, correcting any names that are not RDAREA names defined in HiRDB. |
More than 100 RDAREA names | The number of temporary table RDAREA names exceeds 100. | Reduce the number of temporary table RDAREA names to 100 or fewer. |
Duplicate RDAREA name "RDAREA-name" | A temporary table RDAREA name is a duplicate. RDAREA-name: The invalid temporary table RDAREA name (maximum of 30 bytes). If the RDAREA name is 0 bytes, "" is shown for RDAREA-name. | Delete the duplicate temporary table RDAREA name. |
Invalid character "invalid-character (hexadecimal-representation)" in RDAREA name "RDAREA-name" | A temporary table RDAREA name includes a character that cannot be used in an RDAREA name. invalid-character: Character that is not permissible in an RDAREA name. The invalid character is not displayed if it is outside the range of printable ASCII characters (0x20-0x7e). hexadecimal-representation: The hexadecimal representation of the invalid character. RDAREA-name: A character string (maximum of 30 bytes), starting from the beginning of the temporary table RDAREA name with the invalid character, ending just before the invalid character. | Check the character specified in the temporary table RDAREA name (the character next to the RDAREA name displayed in the message text). If the RDAREA name in the message text is blank, specify a permissible character at the beginning of the RDAREA name. |
Invalid length of RDAREA name "RDAREA-name" | The length of a temporary table RDAREA name exceeds 30 bytes, or is 0 bytes. RDAREA-name: The invalid temporary table RDAREA name (maximum of 30 bytes). If the RDAREA name is 0 bytes, "" is shown for RDAREA-name. | Revise the specified temporary table RDAREA name. |
Invalid characters "invalid-character-string" after RDAREA name "RDAREA-name"#1 | An invalid character string was specified after the temporary table RDAREA name. invalid-character-string: A character string (maximum of 30 bytes), starting from where the invalid character was detected, ending just before one of the following:
Single-byte space
Double quotation mark (")
Comma (,)
Terminating character of a specified value
Character outside the range of printable ASCII characters (0x20-0x7e) RDAREA-name: The temporary table RDAREA name specified immediately before the invalid characters (maximum of 30 bytes). | Separate the temporary table RDAREA names with a comma (,). |
Invalid character "(hexadecimal-representation)" after RDAREA name "RDAREA-name"#2 | An invalid character was specified after the temporary table RDAREA name. hexadecimal-representation: The hexadecimal representation of the invalid character. RDAREA-name: The temporary table RDAREA name specified immediately before the invalid character (maximum of 30 bytes). | Delete the invalid character or correct the RDAREA name. |
Double quote missing after RDAREA name "RDAREA-name" | The ending double quotation mark (") is missing from a temporary table RDAREA name that begins with a double quotation mark ("). RDAREA-name: The invalid temporary table RDAREA name (maximum of 30 bytes). If the RDAREA name is 0 bytes, "" is shown for RDAREA-name. | Enclose the temporary table RDAREA name in double quotation marks ("). |
- #1
- The codes of the invalid characters are displayed if they are within the range of printable ASCII characters (0x20 to 0x7e).
- #2
- The code of the invalid character is displayed if is outside the range of printable ASCII characters (0x20 to 0x7e).
KFPA19522-E A
"ON COMMIT" clause specified in table definition for persistent base table
- ON COMMIT was specified when defining a permanent base table.
- S: Ignores the SQL statement.
- O: To define the permanent base table, delete ON COMMIT, and then retry the operation. To define a temporary table, specify GLOBAL TEMPORARY, and then retry the operation.
KFPA19575-E A
Invalid shared table/index definition code=aa(bb....bb)
- There is an error in the shared table or shared index definition.
- aa: Reason code
- bb....bb: Additional error information
- S: Ignores this SQL statement.
- P: Reason codes and additional error information are shown below. Correct the SQL statement, and re-execute the job.
Reason code | Additional error information | Explanation |
---|
01 | Invalid specification for partitioning table | A shared table cannot use partitioned storage. |
02 | Invalid specification for WITHOUT ROLLBACK table | WITHOUT ROLLBACK cannot be specified for a shared table. |
03 | Specified RDAREA cc....cc for table not shared rdarea | When a shared table is defined for a HiRDB/Parallel Server, the shared table can only be stored in a shared RDAREA. cc....cc: RDAREA name |
04 | Specified RDAREA cc....cc for index not shared rdarea | When a shared index is defined for a HiRDB/Parallel Server, the shared index can only be stored in a shared RDAREA. cc....cc: RDAREA name |
KFPA19576-E A
Specified RDAREA aa....aa is shared RDAREA
- Because the specified RDAREA is a shared RDAREA, the following operations are invalid:
- Definition of a table other than a shared table
- Definition of an index other than a shared index
- Addition of an RDAREA
- Changing partitioned storage conditions
- Definition of a sequence generator
- aa....aa: RDAREA name
- S: Ignores this SQL statement.
- P: Specify an RDAREA that is not a shared RDAREA, and then retry the operation.
KFPA19577-E A
Unable to create partial structure index due to invalid data type for partial structure path
- Because of an invalid data type specified in the substructure path, the substructure index cannot be defined.
The data types that can be specified in the substructure path are as follows: - INTEGER
- DECIMAL
- FLOAT
- VARCHAR
- S: Ignores this SQL statement.
- P: Eliminate the cause of the error and re-execute the SQL statement.
KFPA19581-E A
Invalid constraint definition for table aa....aa."bb....bb" code=cc(dd....dd)
- There is an error in the referential constraint definition or the check constraint definition of table aa....aa."bb....bb".
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc: Reason code
- dd....dd: Additional error information
- S: Ignores this SQL statement.
- P: Reason codes and additional error information are shown below. Correct the SQL statement, and re-execute the job.
Reason code | Additional error information | Explanation |
---|
01 | shared table | Referential constraints cannot be defined for shared tables. |
02 | INSERT ONLY table | Referential constraints and checked constraints cannot be defined for falsification-prevented tables. |
KFPA19582-E A
Unable to drop column on aa....aa."bb....bb" due to cc....cc
- The column cannot be deleted, for one of the following reason:
- A check constraint has been defined for the table with the column is to be deleted.
- A referential constraint (foreign key) has been defined for the table with the column to be deleted.
- The table with a column to be deleted is a referential constraint referenced table.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc....cc:
- check constraint: A check constraint has been defined.
- referential constraint: A referential constraint (foreign key) has been defined.
- referenced table: This is a referential constraint referenced table.
- S: Ignores this SQL statement.
- P: Review the table name. Revise it as necessary, and re-execute the UAP.
KFPA19583-E A
Number of defined foreign keys on table aa....aa."bb....bb" exceeds 255
- The number of foreign keys that can be specified for a single table has exceeded the maximum (255).
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Ignores this SQL statement.
- P: Correct the number of CREATE TABLE foreign keys and re-execute.
KFPA19584-E A
More than 254 check constraint limits in aa....aa."bb....bb"
- Because the restriction on the number of check constraints (total number of Boolean operators specified in the check constraint search conditions [number of AND and OR, excluding the number of AND and OR in a CASE form's WHEN search conditions] and the total number of check constraints) that can be defined for a table has exceeded the maximum value (254), a check constraint cannot be defined.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Ignores this SQL statement.
- P: Make the check restraint limit value 254 or less and re-execute.
KFPA19587-E A
Unable to change check pending status for table aa....aa."bb....bb",code=cc(dd....dd)
- The check pending status of table aa....aa."bb....bb" cannot be changed.
- aa....aa: Authorization identifier
- bb....bb: table identifier
- cc: reason code
- dd....dd: optional information about the error
- S: Terminates the processing.
- O: The table below explains the reason codes for error-related optional information. Resolve the error, and then re-execute the command as necessary.
Reason code (cc) | Optional information (dd....dd) | Explanation |
---|
01 | Table not found in system | The table definition to be processed was deleted during the execution of the utility. |
02 | Table definition altered | The table definition to be processed was modified during the execution of the utility. |
KFPA19602-E A
Unable to define referential constraint aa....aa."bb....bb" due to duplicated constraint
- In a referential constraint, the same referenced table foreign key cannot be referenced from the same foreign key configuration column (independent of the order).
- aa....aa: Authorization identifier
- bb....bb: Constraint name
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19603-E A
Unable to alter table,due to aa....aa
- A column could not be altered for the following reasons:
- The applicable column used an old or new values correlation number under the search condition of the trigger action to reference another column. This column cannot be altered or deleted.
- The applicable column uses an old or new values correlation number in the trigger SQL statement to reference another column. This column cannot be altered or deleted.
- aa....aa:
- triggered action condition:
- The column that could not be altered is being used under the trigger action search condition.
- triggered SQL statement:
- The column that could not be altered is being used by the trigger SQL statement.
- S: Ignores this SQL statement.
- P: When the SQL object can be invalidated, specify WITH PROGRAM and re-execute the job.
KFPA19604-E A
COMPRESSED specification for column "aa....aa" invalid, due to bb....bb
- An error occurred in the compression specification in column aa....aa for the reason indicated in bb....bb.
- aa....aa: Column name
- bb....bb:
- unsupported data type:
- The specified column has a data type that cannot be compressed.
- data length less than 256:
- Compression was specified for a column whose defined length is less than 256 bytes.
- out of range partition size for compress:
- The compression partition size is outside of the range of permissible values.
- S: Ignores this SQL statement.
- P:
- When bb....bb is unsupported data type:
- If you want to compress the data, change the data type of the column to a data type that can be compressed. If you do not want to compress the data, delete the compression specification. For the data types that can be compressed, see the manual HiRDB Version 9 SQL Reference.
- When bb....bb is data length less than 256:
- Compression is not effective on a column with a defined length that is less than 256 bytes. Delete the compression specification.
- When bb....bb is out of range partition size for compress:
- For details about the range of compression partition size values, see Range of values that can be specified for the compression partition size in the manual HiRDB Version 9 SQL Reference.
KFPA19610-E A
Unable to aa....aa except bbb due to cc....cc
- Due to cc....cc, cannot grant or revoke privileges other than bbb.
- aa....aa: {grant access privileges|revoke access privileges}
- bbb: ALL
- cc....cc: temporary table
- S: Ignores this SQL statement.
- P: For a temporary table, it is not possible to grant only some privileges. Specify ALL when granting or revoking privileges on a temporary table to another user.
KFPA19612-E A
Invalid usage of MULTIDIM partitioning table code=aa,reason=bb....bb cc....cc dd....dd
- An error was detected in the specification of the matrix partitioning table.
- aa: Reason code
- bb....bb: Error information
- The following table shows the reason code (aa) and error information (bb....bb):
Error code (aa) | Error information (bb....bb) | Description |
---|
01 | only one RDAREA | Only one RDAREA was specified. |
03 | boundary values over | The sum of specified boundary values exceeds 4,096. |
04 | value and RDAREA unmatch | The number of boundary values and RDAREAs does not match. |
05 | RDAREA specification | An error was detected in the RDAREA specification. Possible causes:
- The specified table storage RDAREA does not match the specified BLOB or index storage RDAREA.
- For ALTER TABLE or CREATE INDEX, the specification does not match the specification for table definition.
- No non-partitioning key index storage RDAREA was specified.
|
06 | RDAREA LIST unmatch | The number of RDAREAs for each matrix partitioning RDAREAs list does not match. |
08 | invalid hash name | One of the following errors occurred in a hash function specification:
- The hash function name is invalid
- The column length of the partition key is invalid
|
09 | more than 15 columns for HASH KEY | The number of columns specified in the partition key of the hash partition exceeds 15. |
10 | invalid HASH function "HASH0" | One of the following errors occurred when HASH0 was specified as the hash function:
- An impermissible data type was specified for the partitioning key.
For details about data types that can be specified, see hash-function-name under CREATE TABLE (Define table) in the manual HiRDB Version 9 SQL Reference.
- More than one column was specified in the partitioning key.
|
11 | invalid HASH function "HASHZ" | One of the following errors occurred when HASHZ was specified as the hash function:
- An impermissible data type was specified for the partitioning key.
For details about data types that can be specified, see hash-function-name under CREATE TABLE (Define table) in the manual HiRDB Version 9 SQL Reference.
- More than one column was specified as the partitioning key.
|
- cc....cc: RDAREA specified location causing the error
- table: Table
- column: Column
- index: Index
- cluster key: Cluster key
- primary key: Primary key
- Otherwise, nothing is output.
- dd....dd: Nothing is output when the table name, column name, or index name cc....cc specifying the RDAREA causing the error is the cluster key or primary key.
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute.
KFPA19613-E A
Unable to ALTER TABLE aa....aa,bb....bb, code=cc
- Cannot execute aa....aa in ALTER TABLE for the reason indicated in bb....bb.
- aa....aa:
- ADD PRIMARY KEY: Add a primary key
- DROP PRIMARY KEY: Delete the primary key
- bb....bb: Additional error information
- cc: Reason code
- The following table lists the reason codes and provides additional error information:
Reason code | Additional error information | Meaning |
---|
01 | because primary key already exist | Cannot add a primary key because there already is a primary key. |
02 | because referencing table exists | Cannot delete the primary key because it is referenced from a foreign key. |
03 | because primary key not exist | Cannot delete the primary key because there is no primary key. |
04 | because nullable column specified | Cannot add a primary key because a column without the NOT NULL constraint was specified for the primary key configuration column. |
05 | due to primary cluster key | Cannot delete the primary key because it is a cluster key with PRIMARY specified. |
- S: Ignores this SQL statement.
- P: Eliminate the cause of error, which is indicated in reason code cc and the additional error information bb....bb, and then re-execute the SQL statement.
KFPA19615-E A
Unable to aa....aa because INSERT ONLY table bb....bb."cc....cc" not empty
- The definition SQL aa....aa cannot be executed for falsification prevented table bb....bb."cc....cc", in which data is stored.
- aa....aa: Definition SQL
- DROP TABLE: Delete the table
- DROP SCHEMA: Delete the schema
- bb....bb: Authorization identifier
- cc....cc: Table name
- S: Ignores this SQL statement.
- P: Falsification prevented tables in which data is stored cannot be deleted. Change the table name, and then re-execute this SQL statement.
KFPA19616-E A
Unable to drop insertion history column on INSERT ONLY table
- The insert history maintenance column specified during the deletion prevented duration of the falsification prevented table cannot be deleted.
- S: Ignores this SQL statement.
KFPA19617-E A
Only DATE type column with "SYSTEM GENERATED" can be specified for insertion history column on INSERT ONLY table
- Only DATE type columns with SYSTEM GENERATED specified can be specified in the insert history maintenance column of a falsification prevented table.
- S: Ignores this SQL statement.
- P: Specify a DATE type column with SYSTEM GENERATED specified in the insertion history column, and then re-execute this SQL statement.
KFPA19620-E A
Invalid delete prohibition interval for INSERT ONLY table
- An error was detected in the deletion prevented duration of the falsification prevented table.
- S: Ignores this SQL statement.
- P: Correct the specification of the deletion prevented duration and re-execute this SQL statement.
- When date interval data is specified:
As a decimal value, specify a 99-day interval between Year 0000 Month 00 Day 01 and Year 9999 Month 11 Day 99 (YYYYMMDD).
- When a label duration is specified:
Specify each value within the following ranges:
YEAR[S]: 1-9,998
MONTH [S]: 1-119,987
DAY [S]: 1-3,652,058
KFPA19621-E A
Unable to CREATE aa....aa TEMPORARY TABLE due to bb....bb, code=cc
- The temporary table cannot be defined due to bb....bb.
- aa....aa: GLOBAL
- bb....bb: Additional error information
- cc: Reason code
- S: Ignores this SQL statement.
- P: The reason codes and additional error information are described below. Eliminate the cause of the error, correct the SQL statement, and then retry the operation.
Reason code | Additional error information | Meaning |
---|
01 | insert only table | The falsification prevention option was specified. |
03 | WITHOUT ROLLBACK specification | The WITHOUT ROLLBACK option was specified. |
04 | SEGMENT REUSE specification | The SEGMENT REUSE option was specified. |
05 | invalid data type | The specified data type cannot be specified in a temporary table. For the data types that can be specified in a temporary table, see GLOBAL TEMPORARY under CREATE TABLE (Define table) in the manual HiRDB Version 9 SQL Reference. |
06 | updatable column specification | An updatable column was specified. |
07 | reserved column specification | A reserved column was specified. |
08 | cluster key specification | A cluster key was specified. |
09 | foreign key specification | A foreign key was specified. |
10 | check constraint | A check constraint was defined. |
11 | rdarea specification | RDAREA was specified. |
12 | shared table | SHARE was specified to try to use the temporary table as a shared table. |
KFPA19622-E A
Unable to CREATE aa....aa for temporary table due to bb....bb, code=cc
- The aa....aa for the temporary table cannot be defined due to bb....bb.
- aa....aa: INDEX
- bb....bb: Additional error information
- cc: Reason code
- S: Ignores this SQL statement.
- P: The reason codes and additional error information are described below. Eliminate the cause of the error, correct the SQL statement, and then retry the operation.
Reason code | Additional error information | Meaning |
---|
01 | rdarea specification | RDAREA was specified. |
02 | EMPTY specification | The EMPTY option was specified. |
KFPA19624-E A
Unable to aa....aa SEQUENCE because of "bb....bb",code=cc
- Because this is for bb....bb, it is not possible to use aa....aa in the sequence generator.
- aa....aa: CREATE
- bb....bb: Additional error information
- cc: Reason code
- S: Ignores this SQL statement.
- P: Reason codes and additional error information are shown below. Eliminate the cause of the error, correct the SQL statement and re-execute.
Reason code | Additional information on errors | Meaning |
---|
01 | DATA TYPE INVALID | There is an invalid data type specification. |
02 | START VALUE INVALID | There was an error in the specification of the sequence generator start option.
- A specification other than an integer literal or scale 0 decimal literal was made.
- The specification is outside the range of values permitted for the data type.
- The start option value of the sequence generator is smaller than the smallest option value of the sequence generator.
- The start option value of the sequence generator is larger than the largest option value of the sequence generator.
|
04 | INCREMENT VALUE INVALID | There was an error in the specification of the sequence generator extension option.
- A specification other than an integer literal or scale 0 decimal literal was made.
- The specification is outside the range of values permitted for the data type.
- A specification of 0 is made for the value of the sequence generator extension option.
|
05 | MAX VALUE INVALID | There was an error in the specification of the sequence generator maximum value option.
- A specification other than an integer literal or scale 0 decimal literal was made.
- The specification is outside the range of values permitted for the data type.
- The smallest option value of the sequence generator is larger than the largest option value of the sequence generator.
|
06 | MIN VALUE INVALID | There was an error in the specification of the sequence generator minimum value option.
- A specification other than an integer literal or scale 0 decimal literal was made.
- The specification is outside the range of values permitted for the data type.
|
07 | LOG INTERVAL INVALID | The specification for the acquiring count is invalid.
- A specification other than an integer literal was made.
- The specification exceeds the 1 to 231-1 range.
- The specification exceeds the specifiable range.
|
KFPA19625-E A
Invalid usage on ALTER TABLE CHANGE RDAREA,code=aa(bb....bb)
- The ALTER TABLE CHANGE RDAREA is incorrectly specified.
- aa: Reason code
- bb....bb: Additional error information
- S: Ignores this SQL statement.
- P: Reason codes and additional error information are shown below.
- Reason code 03:
Delete the index, execute ALTER TABLE, and then redefine the index.
- Reason code 22:
Unload the table, define the table without specifying the same value more than once# in a storage condition, and then reload the table.
#: The term same value refers to two or more literals that are identical, or a literal specified by HiRDB that, when corrected, produces a value that is the same.
- All other reason codes:
Revise the SQL statement, and re-execute the job.
Reason code | Additional error information | Explanation |
---|
01 | Non partition divided table | A non boundary value partitioned table is specified. |
02 | Insert only table | A falsification-prevented table is specified. |
03 | Not divided index exist on table | One of the following errors has occurred:
- When attempting to modify a row partition table on the server, the non-partitioning key index for the table is not row-partitioned.
- When attempting to modify a table not row-partitioned on the server, multiple partitioning storage conditions are stored in the same RDAREA and a non-partitioning key index is defined.
- When attempting to modify a table for which an index in a single RDAREA is defined, an attempt was made to change the RDAREA storing the table.
|
04 | Invalid partition value | The specified boundary value or storage condition value contains the following errors:
- Boundary value:
- The length of the boundary value character string is 0.
- The boundary value data type cannot be converted into the data type of a column specified in the partitioned storage conditions.
- The boundary value data length exceeds the data length of the column specified in the partitioned storage conditions.
- The boundary value is logically inappropriate.
- The boundary value data contents are invalid.
- The boundary value to be changed is not in an existing definition.
- The boundary value to be changed is not in ascending order.
- The boundary value to be changed is not continuous.
- After the change, the boundary values are not in ascending order.
- After the change, the boundary values contain duplicate specifications.
- After the change, there is an error in the specification range of boundary values.
- For a matrix-partitioned table, the boundary value specified last in the list of boundary values after the change does not match the boundary value specified last in the list of boundary values before the change.
- Storage condition value:
- The character string length in the storage condition value is 0.
- The data type of the storage condition value cannot be converted to a partitioning key column data type.
- The data length specified in the storage condition is greater than the data length for the partitioning key column.
|
05 | Invalid result | The result of partitioning or combining is as follows:
- One RDAREA is used.
- The total number of RDAREA partitions exceeds the maximum value. The maximum value is 4,096 including duplicates.
- The total number of literals specified in the partitioned storage condition is greater than 15,000.
- After combining, the total number of RDAREAs will be 1. Therefore, you cannot specify OTHERS, or an RDAREA for which storage conditions have not been specified.
- For a table with an index in a row-partitioned RDAREA, the number of RDAREAs for the table after the change will be 1.
- For a matrix-partitioned table, the number of first-dimension partitions or the number of second-dimension partitions will be 1.
|
06 | Index not found on table | The specified index, primary key, or cluster key is not defined for the relevant table. |
07 | Not specify all index | FOR INDEX, FOR PRIMARY KEY, or FOR CLUSTER KEY is not specified for all indexes. |
08 | Unmatch number of RDAREA | The number of RDAREAs specified in the modified boundary value partitioning specification, the modified storage condition partitioning specification, or the matrix-partitioned table storage RDAREA change specification is different from the number specified in the modified index storage RDAREA name list or the LOB column storage RDAREA change specification. |
09 | Invalid RDAREA for index or "LOB" | One of the following errors occurred in the relationship between the tables and indexes or between the tables and the RDAREAs that store the BLOB columns:
- The position in which a duplicated RDAREA is specified in the modified index storage RDAREA name list or the LOB column storage RDAREA change specification is different from the modified boundary value partitioning specification or the matrix-partitioned table storage RDAREA change specification.
- The position in which a new RDAREA is specified in the modified index storage RDAREA name list or the LOB column storage RDAREA change specification is different from the modified boundary value partitioning specification, the modified storage condition partitioning specification, or the matrix-partitioned table storage RDAREA change specification.
- The position in which an existing RDAREA is specified in the modified index storage RDAREA name list or the LOB column storage RDAREA change specification is different from the modified boundary value partitioning specification, the modified storage condition partitioning specification, or the matrix-partitioned table storage RDAREA change specification.
- If OTHERS is specified, the modified table storage RDAREAs, index storage RDAREAs, and LOB column storage RDAREAs do not have the correct correspondence with one another.
|
11 | Duplicate RDAREA | In an RDAREA that stores different LOB columns, the same RDAREA has multiple specifications, or an attempt was made to add an RDAREA that is already stored. |
12 | Invalid matrix table | One of the following errors occurred in the matrix-partitioned table change specification:
- MULTIDIM was specified for a table that is not a matrix-partitioned table.
- A dimensional partitioning column name that was specified is not assigned key range partitioning with boundary values.
- The number of partitions does not correspond to the number of RDAREA specifications.
|
13 | Invalid usage WITHOUT PURGE | There is an error in the WITHOUT PURGE specification.
- WITHOUT PURGE is specified, but the pre-change RDAREA is not specified as the post-change RDAREA.
|
14 | Invalid RDAREA | One of the following errors occurred in the RDAREA specification when changing the partitioning storage condition:
- If a boundary value was specified:
Identify the error by referring to the table Cause of an RDAREA specification error when modifying partitioning storage conditions (boundary value specification) following this table.
- If a storage condition was specified:
Identify the error by referring to the table Cause of an RDAREA specification error when modifying partitioning storage conditions (storage condition specification) following this table.
- For matrix partitioning:
Identify the error by referring to the table Cause of an RDAREA specification error when modifying partitioning storage conditions (for matrix partitioning) following this table.
|
15 | FOR COLUMN clause invalid | There is an error in the specified column.
|
16 | Duplicate INDEX name | Duplicate index names are specified. |
17 | Invalid index type | The type of the index specified in the FOR PRIMARY, FOR CLUSTER, or FOR INDEX clause is invalid. |
18 | Duplicate column name | Duplicate column names are specified. |
19 | Not specify all "LOB" | The FOR COLUMN clause is not specified for all LOB columns. |
20 | Invalid partitioning condition | When an attempt was made to specify partitioning storage conditions, one of the following errors occurred:
- A column name different from the partitioning key was specified.
- An RDAREA specifying storage conditions for the RDAREA to be partitioned was specified:
- Storage conditions for the RDAREA to be partitioned are not specified for all RDAREAs to be partitioned.
- A storage condition not contained in the storage conditions for the RDAREA to be partitioned is specified for partitioned RDAREAs.
- An RDAREA not specifying storage conditions for the RDAREA to be partitioned was specified, or OTHERS was specified:
- If the object of partitioning is an RDAREA for which no storage conditions are specified, or OTHERS, the storage conditions specified following partitioning already exist.
- Duplicate storage conditions are specified.
|
21 | Invalid partitioning condition table | Storage conditions on any of the following tables cannot be modified:
- Tables other than row-partitioned tables with a storage condition specified
- Row-partitioned tables for which a storage condition other than = is specified in a comparison operator
|
22 | Table with same values in partitioning condition | Partitioning storage conditions cannot be modified in a table for which the same value is specified more than once in a storage condition. The same value means that, given identical literals, and if literals for which HiRDB is specified are corrected, the same result is produced. For example, if the data type for a table partitioning key member column is INTEGER, same values means tables for which storage condition C1=(1,1,1) is specified or tables for which storage condition C1=(1.1,1.2,1.3) is specified. |
51 | Too many number of value | The number of specified boundary values exceeds the number that can be changed.
- During partitioning: The maximum to be changed is 1, and the maximum after changing is 16.
- During combining: The maximum to be changed is 16, and the maximum after changing is 1.
|
52 | Too many specify "FOR INDEX" | FOR INDEX was specified 256 or more times. |
53 | Too many specify "FOR PRIMARY" or "FOR CLUSTER" | FOR PRIMARY or FOR CLUSTER was specified 2 or more times. |
54 | Invalid duplicate columns | A column was specified twice when specifying a matrix-partitioned table. |
99 | User data type | The partition storage conditions cannot be changed for row partitioned tables used for abstract data type columns |
Cause of an RDAREA specification error when modifying partitioning storage conditions (boundary value specification)Error type | Cause |
---|
During partitioning | During combining |
---|
Error in modified boundary value partitioning specification | - A nonexistent RDAREA is specified.
- Contiguous boundary values are specified on the same RDAREA.
| - A nonexistent RDAREA is specified.
- The specified RDAREA is the same as the RDAREAs specified for the previous and next storage ranges.
|
Error in modified index storage RDAREA name list or LOB column storage RDAREA change specification | - A nonexistent RDAREA is specified.
- An RDAREA with OTHERS is specified.
| - A nonexistent RDAREA is specified.
- An RDAREA with OTHERS is specified.
|
Cause of an RDAREA specification error when modifying partitioning storage conditions (storage condition specification)Error type | Cause |
---|
During partitioning | During combining |
---|
Error in the RDAREA information list before change | - An RDAREA storing the table to be modified is not specified.
- An RDAREA with one storage condition is specified.
- OTHERS is specified on a table containing an RDAREA devoid of storage conditions.
| - An RDAREA storing the table to be modified is not specified.
- OTHERS is specified on a table containing an RDAREA devoid of storage conditions.
- Duplicate RDAREA names are specified.
|
Error in the storage condition partitioning specification after change | - After partitioning, there will be only one RDAREA.
- Duplicate RDAREA names are specified.
- A nonexistent RDAREA is specified.
- An RDAREA used in other storage conditions for the table to be modified is specified.
| - Two or more RDAREAs are specified.
- A nonexistent RDAREA is specified.
- An RDAREA used in other storage conditions for the table to be modified is specified.
|
Error in the combination between the RDAREA information list before change and the storage condition partitioning specification after change | Refer to the table Invalid combination between an RDAREA information list before change and a storage condition partitioning specification after change following this table. | OTHERS is specified after combination but an RDAREA without storage conditions or OTHERS specified is not included in the items to be combined. |
Error in the index storage RDAREA name list after change or the LOB column storage RDAREA modification specification after change | - A nonexistent RDAREA is specified.
- Duplicate RDAREA names are specified.
- An RDAREA for storage of indexes other than the table to be modified is specified.
- A LOB storage RDAREA other than the table to be modified is specified.
| - A nonexistent RDAREA is specified.
- An RDAREA for storage of indexes other than the table to be modified is specified.
- A LOB storage RDAREA other than the table to be modified is specified.
|
Invalid combination between an RDAREA information list before change and a storage condition partitioning specification after changeRDAREA specified in an RDAREA information list before change | RDAREA specified in a storage condition partitioning specification after change |
---|
RDAREA with storage conditions | - An RDAREA without storage conditions is specified.
- An RDAREA with OTHERS is specified.
|
RDAREA without storage conditions | An RDAREA without storage conditions or with OTHERS specification is not specified. |
RDAREA with OTHERS specified |
Cause of an RDAREA specification error when modifying partitioning storage conditions (for matrix partitioning)Error type | Cause |
---|
During partitioning | During combining |
---|
Error in the matrix-partitioned table storage RDAREA modification specification. | A nonexistent RDAREA is specified. | A nonexistent RDAREA is specified. |
Error in the index storage RDAREA name list after change or the LOB column storage RDAREA modification specification after change. | - A nonexistent RDAREA is specified.
- An RDAREA with OTHERS is specified.
| - A nonexistent RDAREA is specified.
- An RDAREA with OTHERS is specified.
|
KFPA19631-E A
Definition for INSERT ONLY table aa....aa."bb....bb" failed, code=cc(dd....dd)
- An error has occurred in a falsification-prevented table related definition.
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- cc: Reason code
- dd....dd: Additional error information
- S: Ignores this SQL statement.
- P: Reason codes and additional error information are shown below. Correct the SQL statement, and re-execute the job.
Reason code | Additional error information | Explanation | Action |
---|
01 | INSERT ONLY table | Consider the following causes:
- The INSERT ONLY option was specified for a falsification-prevented table.
- An updatable column attribute was specified for a falsification-prevented table.
| Revise the specified table name. |
02 | referential constraint | A table with a referential constraint defined cannot be a falsification-prevented table. |
03 | check constraint | A table with a check constraint defined cannot be a falsification-prevented table. |
04 | data type | UPDATE ONLY FROM NULL cannot be specified for the following data types:
- BLOB column
- BINARY type column 32,001 bytes or larger
| Revise the specified column name. |
05 | already defined | Consider the following causes:
- An updatable column attribute was specified for an updatable column.
- An attempt was made to change the data length for a BINARY type column, for which UPDATE ONLY FROM NULL is specified in the updatable column attribute, to 32,001 bytes or greater.
|
06 | SYSTEM GENERATED | An updatable attribute cannot be specified for a column with SYSTEM GENERATED specified. |
07 | NOT NULL | UPDATE ONLY FROM NULL cannot be specified for a column with a non-null attribute. |
08 | can not update | Consider the following causes:
- An updatable attribute was specified for a cluster key.
- An updatable attribute was specified for a column composed of a distributed key. However, for columns composed of a partitioning key that is a flexible hash partition, only the UPDATE specification is allowed.
|
09 | only UPDATE columns | Consider the following causes:
- An attempt was made to make a table for which all columns were specified with the updatable attribute into a falsification- prevented table.
- The result of operation on a falsification- prevented table cannot specify that all columns be updatable.
| - When CREATE TABLE is executed:
Specify at least one column without the updatable attribute.
- When ALTER TABLE CHANGE INSERT ONLY is executed:
Add a column without the updatable attribute.
- When ALTER TABLE DROP column name is executed:
Revise the column name.
|
10 | reserved column | Consider the following causes:
- An updatable attribute was specified for a reserved column.
- An attempt was made to make a table with a reserved column into a falsification-prevented table.
| - When CREATE TABLE is specified with the falsification prevention option:
Do not specify a reserved column.
- When a reserved column is defined with CREATE TABLE or a reserved column is added with ALTER TABLE:
Do not specify the updatable column attribute.
- When a table is changed to a falsification prevented table with ALTER TABLE:
Delete the reserved column before executing.
- When an updatable column attribute is changed with ALTER TABLE:
Check whether the column to be changed is a reserved column.
|
KFPA19632-E A
User aa....aa unable to execute CONNECT
- User with authorization identifier aa....aa cannot connect (CONNECT) to HiRDB.
- aa....aa: Authorization identifier
- S: Ignores this SQL statement.
- P: The following shows causes and actions:
Cause | Action |
---|
There is no CONNECT privilege. | Ask a user with the DBA privilege to grant the CONNECT privilege, and then retry the operation. |
An error occurred in the specified password. | If this message is output when connecting to HiRDB, specify the correct password, and then retry the operation. |
Consecutive certification failure account lock state. | Check with a user with the DBA privilege to be sure that the system is in consecutive certification failure account lock state. If it is in consecutive certification failure account lock state, have the HiRDB administrator release the consecutive certification failure account lock state, and then re-execute. |
Password-invalid account lock state. | Check with a user with the DBA privilege to be sure that the system is in password-invalid account lock state. If it is in password-invalid account lock state, have the HiRDB administrator change the password to one that satisfies the character column restrictions, and then re-execute. |
KFPA19633-E A
Unable to execute SQL for connection security,code=aa(bb....bb)
- Due to reason aa, connection security facility SQL statements cannot be executed.
- aa: Reason code
- bb....bb: Additional error information
- S: Ignores this SQL statement.
- P: Based on the output reason code and additional error information, eliminate the cause of the error and re-execute the SQL.
Reason code | Additional error information | Explanation |
---|
01 | Lack of privilege | This cannot be executed due to lack of the DBA privilege. Or, this cannot be executed because the password of a user with the DBA privilege is not registered with HiRDB. |
02 | Specified value for "PASSWORD MIN LENGTH" out of range | The specification for the minimum password length is out of range. |
03 | Specified value for "CONNECT PERMISSION COUNT" out of range | The specification for the permitted number of consecutive certification failures is out of range. |
04 | Specified value for "CONNECT LOCK" out of range | The specification for the account lock period is out of range. |
05 | Invalid Password of DBA or auditor | The DBA or auditor password violates the character string restrictions. |
06 | Already defined | The specified connection security facility is already defined. |
07 | Undefined | The specified connection security facility is not defined. |
KFPA19634-E A
Unable to execute "GRANT aa....aa" to bb....bb due to invalid password (cc....cc)
- The password violates one of the following restrictions, and therefore the GRANT statement cannot be executed.
- Minimum byte count
- Specification restrictions on the authorization identifier
- Specification restrictions on single character types
- aa....aa:
- DBA
- AUDIT
- CONNECT
- bb....bb: Authorization identifier
- cc....cc:
- min length
- user identifier
- similar
- S: Ignores this SQL statement.
- P: Change to a password that satisfies the password character string restrictions, and re-execute the SQL statement.
KFPA19635-E A
Unable to execute "GRANT DBA" to aa....aa for password account locked
- User aa....aa is in password-invalid account lock state, and therefore the DBA privilege cannot be granted by the GRANT DBA statement, or the password cannot be changed.
- aa....aa: Authorization identifier
- S: Ignores this SQL statement.
- P: Release the password-invalid account lock state, and execute the GRANT DBA statement. For details on how to release the password-invalid account lock state, see the HiRDB Version 9 System Operation Guide.
KFPA19670-E A
Unable to access aa....aa bb....bb."cc....cc" due to dd....dd [ee....ee ff....ff] currently in use,resource id=gg....gg
- aa....aa bb....bb."cc....cc" is not accessible, because another user is using the applicable resources in the definition SQL or the utility, you cannot access.
- aa....aa: {table|routine|sequence}
- bb....bb: {authorization identifier | PUBLIC | ********}
- If aa....aa is routine and you cannot specify an authorization identifier, eight asterisks (*) are output.
- cc....cc:
- If aa....aa is table, the table identifier
- If aa....aa is routine, the routine identifier
- If aa....aa is sequence, the sequence generator identifier
- dd....dd: Resource type name
- ee....ee: Resource name 1
- ff....ff: Resource name 2
- gg....gg: Resource information
- For details about resource types, resource names, and resource information, see Table 6-1 Resource types, resource names, and resource information for lock control errors.
- S: Invalidates this transaction.
- P: Re-execute after other users finish using the resources in question. You can use the The command pdls -d lck -a to determine whether resources are being used by another user.
KFPA19671-E A
Unable to access aa....aa of ID bb....bb due to cc....cc [dd....dd ee....ee] currently in use,resource id=ff....ff
- IDs that are bb....bb followed by aa....aa or abstract data types are not accessible, because another user is using the applicable resources in the definition SQL or the utility.
- aa....aa: {table|routine|sequence|abstract data type}
- bb....bb:
- If aa....aa is table:
- Table ID (value of the TABLE_ID column in the data dictionary table SQL_TABLES)
- If aa....aa is routine:
- Routine object ID (value of the OBJECT_ID column in the data dictionary table SQL_ROUTINES)
- If aa....aa is sequence:
- Sequence generator ID (value of the SEQUENCE_ID column in the data dictionary table SQL_SEQUENCES)
- If aa....aa is abstract data type:
- ********
- cc....cc: Resource type name
- dd....dd: Resource name 1
- ee....ee: Resource name 2
- ff....ff: Resource information
- For details about resource types, resource names, and resource information, see Table 6-1 Resource types, resource names, and resource information for lock control errors.
- S: Invalidates this transaction.
- P: Re-execute after other users finish using the resources in question. You can use the The command pdls -d lck -a to determine whether resources are being used by another user.
KFPA19680-E A
Invalid event type aa....aa bb....bb for specified audit definition
- In the event definition subject to audit, the combination of the operation type indicated by aa....aa, the event type indicated by bb....bb, and other operands is invalid.
- aa....aa: Operation type
- bb....bb: Event type
- The following shows operation types and event types:
Operation types | Event types |
---|
ANY | *** (Not applicable) |
SESSION | CONNECT |
DISCONNECT |
AUTHORIZATION |
ANY |
PRIVILEGE | GRANT |
REVOKE |
ANY |
DEFINITION | CREATE |
DROP |
ALTER |
ANY |
ACCESS | SELECT |
INSERT |
UPDATE |
DELETE |
PURGE |
ASSIGN |
CALL |
LOCK |
NEXT VALUE |
ANY |
UTILITY | PDLOAD |
PDRORG |
PDEXP |
PDCONSTCK |
ANY |
- S: Ignores this SQL statement.
- P: Correct the SQL statement and re-execute. For allowable combinations of operation types, event types, and other operands, see CREATE AUDIT in the manual HiRDB Version 9 SQL Reference.
KFPA19681-E A
Unable to specify aa....aa."bb....bb" in PUBLIC VIEW definition
- Table aa....aa."bb....bb" cannot be specified in a derived query expression in a public view definition.
- The following tables cannot be specified in a public view definition:
- A base table or viewed table owned by another user
- A public viewed table that was defined by another user
- A viewed table that is owned by the user but satisfies either of the following conditions:
(1) It uses a base table or viewed table, owned by another user, as the base table.
(2) It uses a public viewed table that was defined by another user as the base table.
- aa....aa: Authorization identifier
- bb....bb: Table identifier of the base table, viewed table, or public viewed table
- S: Ignores this SQL statement.
- P: Revise the base table of the public viewed table.
KFPA19683-E A
Unable to alter public procedure aa....aa."bb....bb", except by routine creator or DBA
- The routine cannot be re-created, because the executing agent of the public routine aa....aa."bb....bb" is neither the one who created the public routine nor a DBA privilege holder.
- aa....aa: PUBLIC
- bb....bb: Routine identifier
- S: Ignores this SQL statement.
- P: Take one of the following measures:
- Execute this SQL statement on the public procedure defined by the executing agent.
- Re-execute the public routine as a user with DBA privileges.
KFPA19700-E A
HiRDB is under maintenance code=a
- Either the pdchgconf command or the pdprgrenew command is currently running, or a transaction is queuing due to the pdtrnqing command. Therefore, a connection cannot be established to the client and a transaction cannot be started.
- a: Internal code
- S: Disconnects the client from HiRDB.
- P: Terminate the UAP.
- O:
- When the client library is version 07-00 or later:
- The pdchgconf command or pdprgrenew command may have failed. Request the HiRDB administrator to check the HiRDB status. After HiRDB starts, re-execute the UAP.
- For transaction queuing due to the pdtrnqing command, release transaction queuing, and then re-execute the UAP.
- When the client library is a version earlier than 07-00:
- After the pdchgconf command or pdprgrenew command has finished, re-execute the UAP.
- For transaction queuing due to the pdtrnqing command, release transaction queuing, and then re-execute the UAP.
KFPA19701-E A
Unable to execute required SQL in Online DB Reorganization, RDAREA = aa....aa
- The requested SQL cannot be executed while updatable online reorganization is in progress.
- aa....aa: RDAREA name
- S: Invalidates the applicable transaction.
- O: Contact the HiRDB administrator.
- Action
- Re-execute after the updatable online reorganization of the applicable RDAREA is released.
- To re-execute without releasing, consider the following items:
- If you are executing in a no-log environment, consider whether the client environment variable PDDBLOG can be changed to ALL.
- During updatable online reorganization, the UAP cannot operate on the original RDAREA. If such operation is desired, specify YES in the client environment definition PDDBORGUAP. For details on operation of the original RDAREA during online reorganization hold, see the manual HiRDB Version 9 Staticizer Option Description and User's Guide. Further, for details on updatable online reorganization commands, see the manual HiRDB Version 9 Command Reference.
KFPA19702-E A
Unable to execute SQL for definition,RDAREA name=aa....aa,tableID=bb....bb,reason code=c
- For the reason indicated in c, the definition SQL or utility cannot be executed.
- aa....aa: Name of RDAREA where invalid status was detected
- Asterisks (********) are displayed when the reason code is 1 or 3.
- bb....bb: The number of the table subject to the definition SQL or utility, or the number of the table on which an index subject to a definition SQL is defined
- Asterisks (********) are displayed for definition (CREATE TABLE).
- c: Reason code
- 1: Definition SQL or utility execution conditions are not satisfied for the application of the inner replica facility.
- 2: RDAREA aa....aa related to table number bb....bb is executing updatable online reorganization.
- 3: The command hold status and the closed status coexist with one or more other statuses in the RDAREA related to table number bb....bb.
- S: Ignores this SQL. Terminates the processing of the utility.
- Action
- For reason code 1:
- Execute the pdrdrefls command and check the RDAREA related to the applicable table. Then, execute the pddbls command and confirm that the RDAREA related to the applicable table meets all of the following conditions:
- RDAREAs where the inner replica facility is applied are not specified along with RDAREAs where it is not applied.
- The definition counts of the replica RDAREA match.
- The generation numbers of the replica RDAREA definition match.
- After the conditions are satisfied, re-execute the definition SQL or the utility. For details about conditions, see the manual HiRDB Version 9 SQL Reference.
- For reason code 2:
- Complete the updatable online reorganization, and then re-execute the definition SQL or the utility.
- For reason code 3:
- Execute the pdrdrefls command and the pddbls command. Check if the RDAREA related to the applicable table is in command hold status and closed status. Then, re-execute the definition SQL or the utility.
KFPA19703-E A
Error occurred during execution of transaction aa....aa, reason=bb....bb, code=cc....cc, server=dd....dd
- An error occurred during transaction control processing.
- aa....aa: Transaction control process
- begin: Transaction start process
- branch: Transaction branch process
- bb....bb: Error
- cc....cc: Reason code
- dd....dd: Name of server where the error occurred
- Asterisks (********) are displayed when the name of the server where the error occurred cannot be specified.
- S: Ignores this SQL statement, or invalidates the transaction.
- O: Contact the HiRDB administrator, eliminate the cause of the error, and re-execute the processing.
- Action
- Take appropriate action for the error or reason code.
Control process (aa....aa) | Error (bb....bb) | Reason code (cc....cc) | Description | Action by HiRDB administrator |
---|
begin | TRNPAUSE | -948 | The server (dd....dd) is suppressing the scheduling of new transactions. | If a KFPS01160-E message is output to the event log (in UNIX, syslogfile) of the system manager before or after the output of this message, resolve the problem according to message KFPS01160-E. If other than the above, if a unit applicable to the standby-less system switchover facility is switching back, wait until the system switchover has completed. |
STLSFES | -944 | (1) A connection is made from a UAP using the X/Open XA interface to a recovery-unnecessary front-end server (dd....dd). (2) Because the target HiRDB Datareplicator that uses a two-phase commit method is connected to an FES that uses a recovery-unnecessary front-end server, the target processing failed. | Set the client environment definitions PDFESHOST and PDSERVICEGRP to connect to an FES that does not use a recovery-unnecessary front-end server. Environment variables must be assigned to the following: (1) A UAP environment variable using the X/Open XA interface (2) Target side HiRDB Datareplicator environment variable. |
branch | TRNPAUSE | -376 | The server (dd....dd) is suppressing the scheduling of new transactions. | If a KFPS01160-E message is output to the event log (in UNIX, syslogfile) of the system manager before or after the output of this message, resolve the problem according to message KFPS01160-E. If other than the above, if a unit applicable to the standby-less system switchover facility is switching back, wait until the system switchover has completed. |
KFPA19704-E A
No available RDAREA for temporary table, code=aa....aa, kind="bb....bb", common id=cc....cc, RDAREA="dd....dd", server="ee....ee"
- The temporary table or temporary table index could not be stored in a temporary table RDAREA because no temporary table RDAREAs are available.
Note that if more than one temporary table RDAREA is a candidate destination, the cause of the error displayed in this message applies only to the RDAREA that is the first storage destination candidate. If this message is output repeatedly after you have taken corrective action for the RDAREA displayed in it, take corrective action after checking the status of the other temporary table RDAREAs and referring to Processing when there are no available temporary table RDAREAs in the HiRDB Version 9 Installation and Design Guide. - aa....aa: Cause of error
- bb....bb: Type
- TABLE: Temporary table
- INDEX: Temporary table index
- If the type cannot be determined, ***** is displayed.
- cc....cc: Common ID
- If it cannot be determined, 0 is displayed.
- dd....dd: Name of the RDAREA in which the error occurred
- In HiRDB/Parallel Server, it is the name of the temporary table RDAREA on the back-end server displayed in ee....ee, which is the RDAREA that will be the first storage destination candidate.
- If it cannot be determined, ******** is displayed.
- ee....ee: Name of server
- S: Ignores this SQL statement or invalidates the transaction.
- O: Based on the cause of the error, take the appropriate corrective action as described in the table below.
- Action
- Based on the cause of the error, take the appropriate corrective action as described in the following table, and then retry the operation:
Cause of error (aa....aa) | Meaning | Action |
---|
Operator | Administrator |
---|
NO_RDAREA | There is no temporary table RDAREA with an attribute shared among SQL sessions in the HiRDB system. | The action depends on whether the client environment definition PDTMPTBLRDAREA is specified.
- If specified:
Ask the HiRDB administrator to create a temporary table RDAREA with a specific SQL session lock attribute, and then specify that RDAREA in PDTMPTBLRDAREA.
- If not specified:
Contact the HiRDB administrator.
| Use pdmod to create a temporary table RDAREA that can be used. |
UNUSABLE#1 | There are no usable RDAREAs among the temporary table RDAREAs specified in the client environment definition PDTMPTBLRDAREA. | Specify a usable temporary table RDAREA with a specific SQL session lock attribute in the client environment variable PDTMPTBLRDAREA. If there is no available temporary table RDAREA with a specific SQL session lock attribute, ask the HiRDB administrator to create one, and then specify that RDAREA in PDTMPTBLRDAREA. |
MAX_OVER#2 | The number of temporary tables or temporary table indexes exceeds the maximum number that can be stored in the temporary table RDAREAs. | Wait for other transactions that are executing to finish, and then re-execute the SQL statement for this transaction. If the problem persists, contact the HiRDB administrator. |
RDAREA_HELD | The temporary table RDAREA cannot be accessed because it is in one of the following states listed:
- Close status
- Currently holding
- pdhold command reception status
| None | Use the pddbls command to check the status of the temporary table RDAREA and make it accessible to the UAP by taking steps such as opening the RDAREA or releasing the hold. In the case of an error shutdown, use pdmod to re-initialize the temporary table RDAREA (initialize rdarea statement). |
INVALID_PAGE_SIZE#2 | The page size is insufficient for one of the following reasons:
- If the temporary table to be stored is a FIX table, the row length of the temporary table exceeds the size that can be stored in the RDAREA.
- The total length of the columns in the temporary table index to be stored exceeds the size that can be stored in the RDAREA.
| None | - (a) If the row length of a FIX table exceeds 3,000 bytes:
- Delete the table, and then re-define the temporary table so that the row length of the FIX table can be stored in the temporary table RDAREA.
- (b) If the index key length exceeds 4,036 bytes:
- If the index is a single-column index, delete it.
- If the index is a multi-column index, delete it, and then redefine it so that the key length does not exceed the maximum.
- (c) Other than above:
- Using pdmod, take either of the following actions:
- Create a temporary table RDAREA with a page size that can store the temporary table, or change the page size of the temporary table RDAREA that was already created.
- Create a temporary table RDAREA with a page size that is larger than the key length of the temporary table index to be stored, or change the page size of the temporary table RDAREA that was already created.
|
LOCK_ERROR | A lock error occurred. | A required resource is currently engaged by another transaction. Wait for the executing transaction to finish, and then re-execute the SQL statement for this transaction. | None |
NO_SEGMENT#2 | There are no unused segments. | All segments are being used by other transactions. Wait for the executing transactions to finish, and then re-execute the SQL statement for this transaction. If the problem persists, contact the HiRDB administrator. | Use pdmod to take one of the following corrective actions:
- Add a temporary table RDAREA (create rdarea statement).
- Re-initialize the temporary table RDAREA that was already created (initialize rdarea statement).
- Expand the temporary table RDAREA that was already created (expand rdarea statement).
- Change the attributes of the temporary table RDAREA that was already created (alter rdarea) to apply automatic extension.
|
REQUEST_OVER | The number of temporary tables and temporary table indexes has exceeded the maximum number available. | Wait for other transactions that are executing to finish, re-execute the SQL statement for this transaction. If the problem persists, contact the HiRDB administrator. | Re-estimate and revise the value of the operand pd_max_temporary_object_no. |
DEL_RDAREA | There is no temporary table RDAREA with an attribute shared among SQL sessions in the HiRDB system. | The action depends on whether the client environment definition PDTMPTBLRDAREA is specified.
- If specified:
Ask the HiRDB administrator to create a temporary table RDAREA with a specific SQL session lock attribute, and then specify that RDAREA in PDTMPTBLRDAREA.
- If not specified:
Contact the HiRDB administrator.
| Use pdmod to create a temporary table RDAREA that can be used. |
- #1
- The RDAREA name that is displayed is the one specified first in the client environment variable PDTMPTBLRDAREA.
- #2
- The RDAREA name that is displayed depends on whether the client environment variable PDTMPTBLRDAREA is specified.
- If it is specified:
- The RDAREA name specified first in the client environment variable PDTMPTBLRDAREA is displayed.
- If it is not specified:
- Among the RDAREAs with an attribute shared among SQL sessions, the RDAREA that will be the first storage destination candidate name is displayed.
KFPA19705-E A
Failed to allocate local buffer pool,error=aa
- Failed to allocate the local buffer.
- aa: Error cause code
- S: Ignores this SQL statement for HiRDB/Single Server. Rolls back for HiRDB/Parallel Server.
- P: Contact the HiRDB administrator.
- Action
- Take the action corresponding to the error cause code.
Error cause code | Cause | Action |
---|
20 | A memory shortage occurred. | Take one of the following actions:
- Increase the swap area.
- Decrease the process count.
- Decrease the number of servers in the unit.
|
32 | Digit overflow occurred in the process private memory size calculation for the local buffer. | Digit overflow occurred in the process private memory size calculation for the local buffer. Decrease the number of local buffers or the number of buffer sectors on the server where the error occurred, and then reduce the process private memory size for local buffers to 231-1 or less (263-1 or less for the 64-bit mode). |
KFPA19706-E A
Please reorganize Table,due to LOB DIRECTORY overflow,RDAREA name=aa....aa,tableID=bb....bb
- The management information in the LOB RDAREA exceeded the upper limit.
- aa....aa: RDAREA name
- bb....bb: Table number
- S: Ignores this SQL statement.
- Action
- Take appropriate action for the applicable RDAREA.
- For the user LOB RDAREA:
Reorganize the LOB column stored in aa....aa or the table defining the LOB attributes.
- For the data dictionary LOB RDAREA:
Reorganize the dictionary table related to the stored procedure or the stored function.
- For the registry LOB RDAREA:
Reorganize the registry table.
KFPA19713-E A
There was a conflict between attempts to update rows in XDS. table ID = aa....aa, ROW ID = bb....bb
- An attempt was made to update or delete while another transaction was updating or deleting.
- aa....aa: DB area table ID (decimal)
- bb....bb: DB area row ID (hexadecimal)
- S: Invalidates this transaction.
- P: Re-execute the SQL statement after the active transaction has terminated. Use the pdvsta command to check the DB area names for the DB area table IDs.
KFPA19716-E A
Unusable page accessed,tableID=aa....aa,RDAREA name=bb....bb,file name=cc....cc
- A page that cannot be used was accessed during operations on the table ID aa....aa, which is defined in RDAREA bb....bb. If WAIT was specified in pd_lock_uncommited_delete_data operand, HiRDB file areas in excess of the following sizes cannot be used in the RDAREA stored in the table that defines the index.
- If the page length is 4096: 32 GB
- If the page length is 6144: 48 GB
- aa....aa: table ID
- bb....bb: RDAREA name
- cc....cc: HiRDB file name
- If the path name of the HiRDB file exceeds 120 characters, the last 120 characters of HiRDB file path name are output.
- S: Invalidates this transaction.
- Action
- Revise the HiRDB file size of the RDAREA that stores the table. For details about the maximum HiRDB file size when WAIT is specified in the pd_lock_uncommited_delete_data operand, see the manual HiRDB Version 9 System Definition. If you have exceeded the maximum size for the RDAREA configuration file, use the database structure modification utility (pdmod) to change the configuration so that the maximum size is not exceeded.
KFPA19717-E A
More than two keys in same row created for index with USING UNIQUE TAG,index id=aa....aa
- In the substructure index in which USING UNIQUE TAG was specified, two or more index keys were generated in the same row.
- aa....aa: Index number
- For CREATE INDEX, ****** is displayed.
- S: Ignores this SQL statement. The system may also invalidate the transaction.
- P: Correct the column value so that a unique XML type column substructure is decided on, and then re-execute the SQL statement or the transaction.
KFPA19718-E A
Failed to allocate in-memory data buffer,reason=aa....aa
- Allocation of the in-memory buffer failed.
- aa....aa: Reason for the error
- S: Invalidates this transaction.
- Action
- Take corrective action according to the cause of the error, as shown below.
Error cause | Error explanation | Action |
---|
process segment over | The number of shared memory segments that can be added in a process exceeded the maximum value for the OS. | Revise the algorithm for the required amount of memory. For details about the amount of memory required during in-memory processing, see the HiRDB Version 9 Installation and Design Guide. In UNIX, also revise the estimate of the OS operating system parameters. For a description of how to estimate operating system parameters, see the HiRDB Version 9 Installation and Design Guide or the applicable OS documentation. Note that in order to use the shared memory segments effectively, you must exercise caution when gathering together multiple RDAREAs to be processed in-memory. For details about segment allocation, see the manual HiRDB Version 9 Batch Job Accelerator. |
insufficient virtual memory | There is insufficient memory for allocating the in-memory buffer. | Refer to system call = shmat, errno = 12, and mnemonic = ENOMEM in 4.3 System call return codes and take corrective action. |
insufficient physical memory | The work area is not sufficient for attaching shared memory. | Either decrease the required amount of shared memory by decreasing the number of in-memory RDAREAs, or provide additional real memory. |
KFPA19719-E A
A transaction cannot be executed because the command is being executed or the transaction by UAP is being executed, in XDS.
- This transaction cannot be executed because a command or a UAP transaction is executing.
- S: Ignores this SQL statement.
- P: Re-execute this SQL statement.
KFPA19721-E A+E+S
DBAREA pages are insufficient in XDS. DBAREA = "aa....aa"
- A DB area aa....aa page shortage occurred. No more pages can be created in this DB area.
- aa....aa: DB area name
- S: Invalidates this transaction.
- Action
- If the target DB area is a data DB area or an index DB area:
- After normally terminating the XDS, take one of the following actions, and then restart the XDS.
- Take corrective action by following the KFPV46003-W or KFPV46004-W message, both of which were output in the XDS log.
- Increase the DB area page size (specification value of -p option of pdxdbarea command in the XDS database definitions).
- If the target DB area is a work table DB area:
- Terminate the XDS normally, increase the DB area page size (specification value of -p option of pdxdbarea command in the XDS database definitions), and then restart the XDS.
KFPA19724-E A
An error occurred during lock processing in XDS.
- An error occurred during lock processing between threads.
- S: Ignores this SQL statement. The system may also invalidate this transaction.
- P: Re-execute this SQL statement.
KFPA19725-E A
Lock processing timed out in XDS.
- An timeout occurred during lock allocation between threads.
- S: Ignores this SQL statement. The system may also invalidate this transaction.
- P: Re-execute this SQL statement.
KFPA19726-E A
Unable to execute an updating transaction during restart the standby system in XDS.
- During the process for recovering operational status for both systems, new update transaction reception is suppressed.
- S: Invalidates this transaction.
- P: After the suppression of new update transaction reception is released (after the KFPV82004-I message is output), re-execute the transaction.
KFPA19727-E A
Temporary table object not found, server="aa....aa", inf1="bb....bb", inf2="cc....cc"
- The SQL statement cannot be executed because the temporary table object does not exist. Before the SQL session terminates, an SQL session-specific temporary table object was not found for one of the following reasons:
- The back-end server terminated.
- A unit on the back-end server terminated.
- A system switchover occurred on the back-end server, or on a unit of the back-end server.
- aa....aa: Name of server
- bb....bb: Maintenance information 1
- cc....cc: Maintenance information 2
- S: Invalidates the transaction.
- O: Execute the DISCONNECT statement.
KFPA19800-E A
Output file aa....aa error occurred in EXECUTE UTL statment, errno=bb....bb
- An error occurred in EXECUTE UTL result file output processing.
- aa....aa: File operation contents
- open: File open
- write: File write
- bb....bb: Error code
- S: Terminates processing.
- P: Check the value of the error code, refer to errno.h and the manual for the OS used by the user, eliminate the cause of the error, and re-execute.
KFPA19801-E A
Invalid value of aa....aa
- One of the following errors occurred in the aa....aa value:
- The length is 0 or a negative value.
- An invalid character was used.
- aa....aa: {extended statement name|extended cursor name}
- S: Ignores this SQL statement.
- P: Take one of the following measures:
- Specify a value of 1 or greater in aa....aa.
- Specify valid characters in aa....aa.
KFPA19802-E A
Incompatible character code set, HiRDB=aa....aa, PDCLTCNVMODE=bb....bb
- The character code for the HiRDB server does not match the value specified in the client environment variable PDCLTCNVMODE.
- aa....aa: HiRDB code type
- SJIS: Shift JIS kanji code
- CHINESE: EUC Chinese kanji code
- UJIS: EUC Japanese kanji code
- LANG-C: Single-byte code
- UTF-8: Unicode
- CHINESE-GB18030: Chinese character encoding GB18030
- UNKNOWN: Unsupported character code
- bb....bb: Specification value in the client environment variable PDCLTCNVMODE
- UCS2_UTF8
- UCS2_UJIS
- UCS2_UJIS2
- S: Declines connection to HiRDB.
- P: Make sure the character code for the HiRDB server matches the value specified in the client environment variable PDCLTCNVMODE.
KFPA19864-E A
Unable to aa....aa MEMORY TABLE due to bb....bb, code=cc
- Because of bb....bb, it is not possible to set the memory database allocation table or memory database deallocation table.
- aa....aa: {ALLOCATE|DEALLOCATE}
- bb....bb: Additional error information
- cc: Reason code
- S: Ignores this SQL statement.
- P: If the specified table name is invalid, revise the table name and then re-execute. If the table name is valid, follow the additional instructions for error codes and errors, and then take corrective action. The meanings and actions in the additional information are as follows:
Reason code (cc) | Additional information (bb....bb) | Explanation | Action |
---|
01 | duplicate index names | Duplicate index names are specified. | Correct the SQL statement so that the index name is not duplicated, and then re-execute. |
02 | duplicate DBAREA names | In the index DB area, specify the same DB area that was specified in the data DB area. | Specify the data DB area in the data DB area name, and specify the index DB area in the index DB area name. Then re-execute. |
03 | already allocated table | The memory database allocation table was already set. | It is unnecessary to set the memory database allocation table. |
04 | divided table | Partitioned table | Set as not to be added to the memory database. |
05 | referential constraint | Referencing table |
06 | insert only table | Falsification-prevented table |
07 | shared table | Shared table |
09 | none-FIX table | Non-FIX table |
10 | LOCK PAGE table | Table in which LOCK PAGE was specified in the table option | Use ALTER TABLE to alter the minimum unit of locked resources for the table, and then re-execute.# |
11 | WITHOUT ROLLBACK table | Table in which WITHOUT ROLLBACK was specified in the table option | Set as not to be added to the memory database. |
12 | check constraint | Table in which the check constraint was defined |
13 | table with large SEGMENT REUSE value | Table in which a value in excess of 16,777,216 was specified for the number of segments of table option SEGMENT REUSE | Use ALTER TABLE to alter the segment number to 16,777,216 or less, and then re-execute.# |
14 | trigger table | Table that defined the trigger | Set as not to be added to the memory database. |
15 | too many columns | Table that defined over 3,000 columns |
16 | too many indexes | Table in which the number of defined indexes exceeds 16 | Decrease the number of indexes defined in the specified table to 16 or less, and then re-execute.# |
17 | table with DEFAULT clause or WITH DEFAULT | Table with columns that specify the DEFAULT clause or that specify WITH DEFAULT in the NOT NULL constraint | Set as not to be added to the memory database. |
18 | updatable column for insert only table | Table with columns that specify updatable column attributes for a falsification-prevented table |
19 | table using character set specification | Table with columns that specify a character set |
20 | no XDS | For HiRDB/Single Server, the XDS is not specified by the pdxds operand in the system common definition. For HiRDB/Single Server, the XDS that supports BES storing of the target table is not specified by the pdxds operand in the system common definition. | Contact the HiRDB administrator. |
21 | XDS in starting or terminating | The XDS is starting or terminating. | Re-execute when the XDS is operating or is shut down. For details about confirming completion of XDS start processing, see Memory database allocation procedure (XDS start) in the HiRDB Version 9 Memory Database Installation and Operation Guide. For details about confirming completion of XDS termination processing, see Memory database deallocation procedure (XDS termination) in the HiRDB Version 9 Memory Database Installation and Operation Guide. |
22 | insufficient table access privileges to public | Table to which full access privileges have not been granted to PUBLIC | Grant full access privileges to PUBLIC by using GRANT, and then re-execute.# |
23 | invalid data type | Table with the following data type columns.
- SMALLINT type
- FLOAT type
- SMALLFLT type
- NCHAR type
- MCHAR type
- DATE type
- TIME type
- INTERVAL YEAR TO DAY type
- INTERVAL HOUR TO SECOND type
- TIMESTAMP type
- DECIMAL TYPE precision that exceeds 29 digits
| Set as not to be added to the memory database. |
24 | large precision of DECIMAL for index column | Delete all of the indexes defined in columns in which DECIMAL type precision exceeds 19 digits, and then re-execute. | Delete all of the indexes defined in columns in which DECIMAL type precision exceeds 19 digits, and then re-execute.# |
25 | undefined index | The specified indexes have not been defined in the corresponding table. | Revise all of the specified indexes and then re-execute. |
26 | primary key | Table that defined the primary key | Set as not to be added to the memory database. |
27 | cluster key | Table that defined the cluster key |
28 | EXCEPT VALUES index | Table that defined an index that specified exception values in index options |
29 | UNBALANCED SPLIT index | Table that defined indexes that specified UNBALANCED SPLIT in index options |
30 | table used in view | Basic viewed table | Delete all of the viewed tables that are based on the specified table, and then re-execute.# |
31 | table used by inner replica facility | This is the table with the RDAREA to which the inner replica facility was applied or in which the index was defined | Cancel application of the inner replica function and re-execute.# |
33 | duplicate table name in XDS | The same table identifier as that of the memory database allocation table belonging to another user has been specified in an identical XDS. | Use ALTER TABLE to alter the table name, and then re-execute.# |
34 | duplicate index name in XDS | The specified table defines in the same XDS the same index defined in the memory database allocation table. | Use ALTER INDEX to alter the index name, and then re-execute.# |
35 | too many tables in XDS | The number of memory database allocation tables that are stored in the same XDS exceeds 1,024. | Find a way to achieve 1,024 or fewer memory database allocation tables stored in the same XDS.# |
36 | too many indexes in XDS | There are more than 2,048 index numbers in the memory database allocation table stored in the same XDS. | Find a way to achieve a total of 2,048 or fewer indexes in the memory database allocation table stored in the same XDS.# |
37 | too many tables in DBAREA | There are more than 200 memory database allocation tables stored in the same DB area. | Specify another DB area and re-execute. Alternatively, find a way to achieve 200 or fewer memory database allocation tables stored in the same DB area.# |
38 | too many indexes in DBAREA | There are more than 400 index numbers in the memory database allocation table stored in the same DB area. | Specify another DB area and re-execute. Alternatively, find a way to achieve a total of 400 or fewer indexes in the memory database allocation tables stored in the same DB area.# |
39 | abnormally terminated XDS | After DEALLOCATE MEMORY TABLE executed, the XDS terminated abnormally before memory database deallocation. | Contact the HiRDB administrator. |
40 | invalid DBAREA name | During cancellation of settings for the memory database deallocation table on which DEALLOCATE MEMORY TABLE was executed during XDS operation, the specifications for the data DB area name and index DB area name differed from what they were previously. | Specify the same data DB area name and index DB area name as when the previous ALLOCATE MEMORY TABLE was executed, and then re-execute. If you are checking the data DB area that was previously specified, see the DBAREA_NAME column of the data dictionary table SQL_TABLES. If you are checking the index DB area that was previously specified, see the DBAREA_NAME column of the data dictionary table SQL_INDEXES. |
41 | none-memory table | Not the memory database allocation table. | Invalid setting for deallocation of the memory database allocation table. |
42 | already deallocated table | Table that was already set to be deallocated from the memory database. |
44 | view | Viewed table | Set as not to be added to the memory database. |
45 | audit trail table | Audit trail table |
46 | insufficient index names | None of the indexes that are defined in the table have been specified. | Specify all of the indexes defined in the table, and then re-execute. |
47 | too many index names | The index identifier is specified 17 times or more. | Correct the syntax so that the number of specified indexes is 16 or less, and then re-execute.# |
48 | invalid last character in table name | Table that specified single byte spaces in the final characters of the table identifier | Use ALTER TABLE to alter the table name, and then re-execute.# |
49 | invalid last character in column name | Table with columns that specified single byte spaces in the final characters of the column names | Use ALTER TABLE to alter the column name, and then re-execute.# |
50 | invalid last character in index name | This is the table with an index in which the last characters of the index identifier are specified as single-byte spaces. | Use ALTER INDEX to alter the index name, and then re-execute.# |
51 | reserved column table | Table with a reserved column | Exclude from memory database allocation. |
52 | temporary table | Temporary table | Exclude from memory database allocation. |
53 | invalid SEGMENT REUSE option | Specify a value other than 0 for the reuse option value in the SEGMENT REUSE table option. | Use ALTER TABLE to change the reuse option value to 0, and then retry the operation.# |
- #: If you cannot take this corrective action, do not perform memory database processing.
- Action
- If the reason code is 20, specify XDS using the pdxds operand in the system common definition.
- If the reason code is 39, recover the error. For details about how to perform error recovery, see Corrective action to take when an error occurs in the HiRDB Version 9 Memory Database Installation and Operation Guide.
KFPA19865-E A
Unable to execute definition SQL due to memory table aa....aa."bb....bb"
- Because the table aa....aa."bb....bb" is the memory database allocation table, the following definition SQL cannot be executed.
- CREATE INDEX
- CREATE PROCEDURE
- CREATE TRIGGER
- CREATE TYPE
- CREATE VIEW
- ALTER INDEX
- ALTER PROCEDURE
- ALTER ROUTINE
- ALTER TRIGGER
- ALTER TABLE
- DROP INDEX
- DROP SCHEMA
- DROP TABLE
- REVOKE access privileges
- aa....aa: Authorization identifier
- bb....bb: Table identifier
- S: Ignores this SQL statement.
- P: Release table aa....aa."bb....bb" from memory database table allocation, and then re-execute.
KFPA19940-E A
PLUGIN "aa....aa"unsupports bbb compression facility
- Plug-in aa....aa cannot compress columns of the data type indicated in bbb.
- aa....aa: Plug-in name
- HiRDB XML Extension
- bbb: Data type
- XML
- S: Invalidates the transaction.
- P: Contact the HiRDB administrator, and then re-execute after the HiRDB administrator takes corrective action.
- Action
- Check the version of the plug-in. Register a version of the plug-in that supports the data compression function, and then restart HiRDB.
KFPA19941-E A
PLUGIN "HiRDB XML Extension" unsupports XML update facility
- HiRDB XML Extension plug-in does not support partial update of XML data.
- S: Invalidates the transaction.
- P: Contact the HiRDB administrator, and then re-execute after the HiRDB administrator takes corrective action.
- Action
- Check the version of the plug-in. Register a version of the plug-in that supports partial update of XML data, and then restart HiRDB.
KFPA20000-E A
System function error occurred, name=aa....aa, code=bbbb
- An error occurred in an internal system function.
- aa....aa: Name of function resulting in the error
- bbbb: System call errno
- S: Terminates abnormally.
- O: Based on the system call errno, check the cause of the error; after resolving the problem, re-execute the UAP or the command.
KFPA20001-E L
Communication buffer allocation error occurred, code=aaaa
- Allocation of communication buffer failed.
- aaaa: Error code
- S: Terminates abnormally.
- O: Reduce the number of resident processes (pd_process_count) for the server where this message was output.
KFPA20002-E L
Communication error,abort=aa....aa, code=bbbbb
- An error occurred during communication processing.
- aa....aa: Abort code
- bbbbb: Error detail code
- S: Resumes processing.
- O: See 4. Error Detail Codes to eliminate the cause of the error, then re-execute the UAP or command. If the operator cannot handle the error, contact the HiRDB administrator.
- Action
- Contact the customer support center.
KFPA20003-E E+L
Insufficient aa....aa memory, server=bb....bb, size=cc....cc
- There is not enough memory for HiRDB system processing.
- aa....aa: Type of area in which memory shortage occurred:
- SHARED: Shared memory
- PROCESS: Process private area
- bb....bb: Name of the server resulting in the error
- cc....cc: Specified size (in bytes)
- S:
- At server startup:
- Cancels server startup processing.
- At transaction input:
- Terminates abnormally the process that attempted to process the corresponding transaction.
- Action
- If the error occurred at the startup of a user server (executed by specifying the -s option with the pdstart command) that is not a back-end server using the standby-less system switchover (effects distributed) facility, and the unit terminated abnormally, specify server in the pd_shmpool_control operand in the system common definition and restart the unit. Otherwise, increase the size of the shared memory for the server that has insufficient shared memory, and restart the affected server. The size of shared memory can be specified in the following operands:
- pd_sds_shmpool_size (single server definition)
- pd_dic_shmpool_size (dictionary server definition)
- pd_bes_shmpool_size (back-end server definition)
- If the shortage occurred in the process private area, provide more memory space by taking the following actions:
- Reduce the number of concurrent processes.
- Increase the swap area.
- Increase the real memory.
- If the current value is large, reduce the pd_work_buff_size operand value in the server definition.
- Reduce the number of server resident processes (pd_process_count).
KFPA20004-I E+L
BES aa....aa used as a floatable server for FES bb....bb(cc....cc/dd....dd)
- Back-end servers aa....aa are being used as floating servers for SQL processing accepted by front-end server bb....bb.
Up to 12 back-end servers can be listed in aa....aa; this message is output in segments if there are more than 12 back-end servers. - aa....aa: List of names of the back-end servers used as floating servers
- bb....bb: Name of the front-end server
- cc....cc: Segment number of this message
- dd....dd: Total number of message segments
- S: Resumes processing.
- O:
- If pd_floatable_bes and pd_non_floatable_bes are both specified in the front-end server definition, pd_floatable_bes is effective. From the list of servers used as floating servers displayed in this message, check that the specification of the front-end server definition is correct. If it is not correct, stop the front-end server, correct the front-end server definition, and restart the server.
- When the message is divided into multiple segments, the segments may not be displayed in the order of the requests.
KFPA20005-E E+L
Invalid value bb....bb specified for operand aa....aa
- The value (identifier or unsigned integer) of operand aa....aa specified in the system definition is invalid.
- aa....aa: Operand name
- bb....bb: Operand specification value (first 30 bytes only if the value is longer than 30 bytes)
- S: Halts HiRDB startup processing.
- O: Contact the HiRDB administrator.
- Action
- Correct the specification of operand aa....aa in the system definition, and restart HiRDB.
KFPA20006-E E+L
aa....aa in FES definition bb....bb, file=cc....cc, pos=dd....dd
- Error aa....aa occurred in the bb....bb operand of the front-end server definition.
- aa....aa: Error cause
- Invalid option: The option is invalid.
- Invalid value: The option value is invalid.
- Duplicate options: The same option operand already exists.
- bb....bb: Name of the operand where the error occurred
- cc....cc: Definition file name (the first 30 bytes are displayed if the length of the file name exceeds 30 bytes)
- dd....dd: Position of the operand where the error occurred (information that indicates the cardinal number of the operand in the definition where the error occurred)
- S: Ignores the operand of the definition where the error occurred.
- O: Contact the HiRDB administrator.
- Action
- Respecify the dd....ddth bb....bb operand, and then restart HiRDB.
KFPA20007-E L
Java VM library not found at aa....aa, server=bb....bb, errno=ccc
- No Java Virtual Machine library was found.
- aa....aa: Library path name of the Java Virtual Machine (if the path name exceeds 160 characters, a hash mark (#) is displayed as the 160th character)
- bb....bb: Name of the server that executes the Java Virtual Machine
- ccc: Error code from the OS
- S: Terminates processing.
- Action
- Correct the error indicated by error code ccc by referring to errno.h and the OS documentation, and restart HiRDB.
- If file aa....aa does not exist, grant read privilege and execution privilege to HiRDB administrator. Also check the settings for the pd_java_runtimepath and pd_java_libpath operands in the system definition.
KFPA20009-W L
SQL inf(aa) bb....bb cc....cc dd....dd ee....ee ff....ff
- When the reason code is 00, the SQL information from when a server process was forcibly terminated by a UAP forced termination or other cause is displayed.
When the reason code is 01, the SQL information containing a warning from the SQL runtime warning output facility is displayed. - aa: Reason code
- 00: The server process abnormally terminated due to forced termination by a UAP or other cause, aborting the process.
- 01: The SQL runtime was longer than the time set in the SQL runtime warning output facility.
- bb....bb: Server information (is output in one of the following formats)
- single-server-name, connection-serial-number
- front-end-user-name, connection-serial-number
- cc....cc: Client information (is output in the following format):
- UAP-name UAP-process-ID (UAP-IP-address)
- Note that 0 is displayed for the process ID of the UAP if it is connecting from a Type 4 JDBC driver.
- dd....dd: Executed SQL information (is output in the following format):
- operation-code SQL-counter SQLCODE
- operation-code
For details about the operation code, see HiRDB Version 9 UAP Development Guide. When the reason code is 00, there are cases for which the operation code cannot be set. An asterisk (*) is displayed if the operation code cannot be set.
- SQL-counter
Expresses a value that is counted each time an SQL statement is received. An asterisk (*) is displayed if the SQL counter cannot be set.
- SQLCODE
Displays the SQLCODE of the result the SQL statement executed. When the reason code is 00, there are cases for which the SQLCODE cannot be set. In these cases, asterisks (*) are displayed.
- ee....ee: SQL runtime (output in one of the following formats):
- Percentage of the maximum wait time is specified as an unsigned integer
SQL-run-starting-time-SQL-run-ending-time
It is displayed in the format hh:mm:ss (hh: hours, mm: minutes, ss: seconds).
When the reason code is 00, there are cases for which the SQL run start time cannot be set. In these cases, asterisks (*) are displayed. Also, the time the SQL aborted is displayed in the SQL run end time.
- Percentage of the maximum wait time is specified as an unsigned decimal integer, and the output timing is specified
SQL-run-starting-time-SQL-run-ending-time
It is displayed in the format hh:mm:ss.xxxx (hh: hours, mm: minutes, ss: seconds, xxxx: microseconds).
If the reason code is 00, it may not be possible to set the SQL runtime start time. If it cannot be set, * is displayed. Furthermore, the SQL runtime end time displays the time the SQL statement was interrupted.
- ff....ff: Execution termination or the aborted SQL statement
- Asterisks (*) are displayed when the SQL statement cannot be set.
- Depending on the length of the SQL statement, display of the SQL statement may be truncated. When the display is truncated, a hash mark (#) is added to the end of the message.
- S: Executes the process.
- Action
- Take one of the following actions:
- When the reason code is 00
When unplanned forced termination of a server process occurs, refer to other messages to eliminate the cause.
- When the reason code is 01
See the SQL runtime warning information file and take one of the following steps:
Re-evaluate whether exclusive contention is occurring.
Re-evaluate whether a network failure occurred.
Fine tune the SQL code.
Increase the specification value of the PDCWAITTIME operand.
Check the increase of the data count to determine if the SQL runtime has increased.
For details about the SQL runtime warning output facility and about the SQL runtime warning information file, see HiRDB Version 9 System Operation Guide.
KFPA20010-W L
Invalid pd_delete_reserved_word_file operand
- The following error occurred in the specification of the system common definition pd_delete_reserved_word_file operand:
- The specified SQL reserved word deletion file does not exist.
- Duplicates of the specified SQL reserved word deletion file exist.
- S: Continues processing.
- Action
- Check that the specification of the system common definition pd_delete_reserved_word_file operand is correct. If not, stop HiRDB, correct the system common definition pd_delete_reserved_word_file operand specification, and re-execute.
KFPA20011-W L
Invalid "SQL_reserved_word_delete_file", file=aa....aa
- A reserved word that cannot be deleted is specified in the SQL reserved word deletion file.
- aa....aa: Name of the SQL reserved word deletion file that contains the error
- S: Continues processing.
- Action
- Check that the contents of the SQL reserved word deletion file are correct. If not, stop HiRDB, correct the SQL reserved word deletion file, and re-execute.
KFPA20012-W E+L
Invalid pd_sql_command_exec_users operand
- Because there is an invalid specification for the pd_sql_command_exec_users operand, ignore this operand. The error may be due to either of the following factors:
- A character string of nine characters or more is specified in the authorization identifier.
- The specified authorization identifier contains characters that cannot be used.
- S: Continues processing.
- Action
- Make sure that the specification for the pd_sql_command_exec_users operand is correct. If it is not, stop HiRDB, correct the pd_sql_command_exec_users operand value, and then re-execute.
KFPA20013-E L
Error occurred in C function for aa....aa bb....bb.cc....cc, library file=dd....dd, C function=ee....ee
- An error occurred during the C function ee....ee that implemented the external C stored routine.
- aa....aa: External C stored routine type{PROCEDURE|FUNCTION}
- bb....bb: Authorization identifier
- cc....cc: Routine identifier
- dd....dd: C library file name
- ee....ee: Name of the C function that implemented the external C stored routine
- S: Ignores this SQL statement.
- P: Use the following procedure to re-register the C library file, and then re-execute the SQL statement.
- Check the message (such as KFPS01820-E) that was output before this message, eliminate the cause of the error, and correct the library source.
- Recreate the C library file from the corrected source.
- Use one of the following methods to re-register the C library file that you created:
- Create the UAP that executes REPLACE CLIB, and execute that UAP.
- Ask the administrator to execute the pdclibsync command.
- Action
- Contact the programmer who implemented the C function dd....dd, and request correction of the program. If a pdclibsync command must be executed according to the corrective action for the program, re-execute the command.
KFPA20014-E E+L
Unable to use XDS in environment using aa....aa character code set
- The XDS that was set up with the character encoding aa....aa specified cannot be used in HiRDB.
The character encodings that can be used in XDS are as follows: - aa....aa: Character code classification
- {chinese|lang-c|chinese-gb18030}
- S: Interrupts HiRDB startup processing.
- O: Contact an HiRDB administrator.
- Action
- If you are using an XDS, perform setup again using the character encoding that can be used in the XDS and that is described in the message, and then start HiRDB. Note that if a database has already been created, it must be re-created using character encoding that can be used in an XDS.
- If an XDS is not used, delete the pdxds operand from the system common definition.
KFPA20015-E E+L
Unable to send message to client,RC=aa....aa,CNCTID=bb....bb,SQLNO=cc....cc,CLIENT=dd....dd,OPCD=eeee,TRANSACTION=ff....ff
- The result telegram cannot be sent to the client.
- aa....aa: Reason code
- bb....bb: connection ID
- For DISCONNECT, COMMIT RELEASE, or ROLLBACK RELEASE, an asterisk (*) output.
- cc....cc: SQL counter (SQL sequence numbers during connection)
- For DISCONNECT, COMMIT RELEASE, or ROLLBACK RELEASE, an asterisk (*) output.
- dd....dd: Client information
- This information is output in the following format:
- oo....oo pp....pp(qq....qq,rr....rr)
- oo....oo: UAP identification information (maximum of 30 bytes).
- If the client environment definition PDCLTAPNAME is specified:
Displays the value specified in PDCLTAPNAME.
The trailing single-byte spaces are also deleted.
- If the client environment definition PDCLTAPNAME is not specified:
Unknown is displayed.
- pp....pp: UAP IP address (maximum of 15 bytes)
- An IP address is a decimal numerical value delimited by periods (.) after each byte (example: 172.11.22.33).
- However, if the UAP is operating on the same machine (except JDBC Type 4 drivers), 0.0.0.0 is output.
- qq....qq: UAP process ID (maximum of 10 bytes)
- If you are connected from a Type 4 JDBC driver, 0 is output.
- rr....rr: UAP thread number (maximum of 10 bytes)
- If you are connected from a Type 4 JDBC driver, 0 is output.
- Note that for DISCONNECT, COMMIT RELEASE, and ROLLBACK RELEASE, asterisks (*) are output.
- eeee: Operation code
- For DISCONNECT, COMMIT RELEASE, or ROLLBACK RELEASE, an asterisk (*) output.
- ff....ff: Transaction status
- ACTIVE: During transaction
- The transaction is rolled back.
- NONE: Not during transaction
- To check transaction completion, refer to the administrator's action transaction completion check method.
- S: Interrupts the process and connection to the UAP. Note that if the transaction has not completed, rollback will occur.
- O: Contact an HiRDB administrator
- Action
- Refer to the following and take action as appropriate.
Reason code | Explanation | Action |
---|
-306 | The UAP has been disconnected. | Check the OS log and make sure that no network-related errors have occurred. Alternatively, check the operational status of the client by using the client information that was output in the message. After this, eliminate the error, check the results of the transaction completion, and then re-execute the UAP as needed. For details about checking transaction completion, see the explanation of embedded character ff....ff above, which provides details about how to check for transaction completion. |
-338 | Disconnection with the UAP was detected during SQL statement execution. |
-307 | A timeout occurred as a result of a network delay. | Take corrective action by following the KFPQ50314-E message, which was simultaneously output. After this, eliminate the error, check the results of the transaction completion, and then re-execute the UAP as needed. For details about checking transaction completion, see the explanation of embedded character ff....ff above, which provides details about how to check for transaction completion. |
-318 | A system error occurred. |
-41402 -41403 | SQL statement execution was cancelled while the telegram was being sent. | If the KFPQ50933-E message was output, take action according to this message. If it was not output, implement the same corrective action as that for reason code -338. After this, eliminate the error, check the results of the transaction completion, and then re-execute the UAP as needed. For details about checking transaction completion, see the explanation of embedded character ff....ff above, which provides details about how to check for transaction completion. |
Other than the above | -- | Back up the files under %PDDIR%\spool, and contact the customer support center. |
- Legend:
- --: Not applicable
- Method of checking transaction completion.
- When it is necessary to check transaction completion as part of a corrective action taken in response to this message, do so using the following procedure.
- Check the value of the embedded character ff....ff.
If it is ACTIVE, rollback is finished.
If it is NONE, follow steps 2 and 3 below.
- Specify the transaction that you want to check from the IP address and connection ID of the HiRTM information, based on the UAP IP address and connection ID in this message.
- Check the third digit of the HiRTM hexadecimal information status (status) for the transaction.
If the first bit from the left is 1 (0x80), commit is completed.
If the second bit from the left is 1 (0x40), rollback is completed.
- For details about HiRTM, see the HiRDB Version 9 Memory Database Installation and Operation Guide.
KFPA20016-E L
pd_max_tmp_table_rdarea_no operand in system definition file unmatch between units
- The values specified for the operand pd_max_tmp_table_rdarea_no are inconsistent between units.
- S: Terminates processing.
- O: Contact the HiRDB administrator.
- Action
- Run the pdconfchk command to check on the system definition. Eliminate the cause of the error, restart HiRDB, and then re-execute the database structure modification utility (pdmod).