Scalable Database Server, HiRDB Version 8 Messages

[Contents][Back][Next]

2.1 KFPA messages

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 8 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
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: 32,000
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.
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.

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 |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 |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, or Boolean predicate.
  • NULL predicate contains information other than the item specification.
  • A constant, USER, CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, ? parameter, or embedded variable was specified in the LIKE predicate, the XLIKE predicate value expression, or in the row-value-constructor-1 of the BETWEEN predicate.
  • CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, a ? parameter, or an embedded function is specified in a value expression in the SIMILAR predicate.
  • A row value constructor was specified in the value expression of a LIKE, XLIKE, SIMILAR, or Boolean predicate.
aa....aa: Predicate whose operand is invalid:
{NULL|LIKE|XLIKE|SIMILAR|BETWEEN|BOOL}
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

One of the following errors was found:
  • Invalid LIKE, XLIKE, or NULL predicate was specified as a search condition in a HAVING clause
  • 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:
    [Figure] BLOB
    [Figure] BINARY with a maximum length of 32,001 bytes or larger
    [Figure] Repetition column
    [Figure] 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 or window function is specified at an invalid location.
aa....aa: {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 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|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
 |insert columns|values in "VALUES" clause
 |view columns|"WITH" query columns
 |"java.sql.ResultSet[]" in EXTERNAL NAME clause
 |attributes in type definition|data types
 |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 }
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

A column, SQL variable, or SQL parameter of the aa....aa type is used incorrectly, an attribute of the aa....aa type is used incorrectly, or a function invocation of the aa....aa type is used incorrectly as a data type for a function return value.
aa....aa: Incorrectly used data type
{ BLOB |BINARY |abstract |BOOLEAN }
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 }
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 specified in the descriptor shown in bb....bb exceeds the maximum (255).
aa....aa: {value expressions|row value constructors}
bb....bb: Invalid specification in SQL statement:
{ "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
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.

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
  • CREATE TABLE or ALTER TABLE boundary values and storage conditions
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:
  • When a holdable cursor is specified, none of the following can be specified:
    [Figure] Table for another RD-node (for remote database access)
  • 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 when searching using an external table or a view table based on an external table.
S: Ignores this SQL statement.
P: Correct the SQL statement and re-execute.

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"

Either an SQL parameter or an SQL variable is specified in an SQL statement other than CREATE PROCEDURE, CREATE TRIGGER, CREATE FUNCTION, or CREATE TYPE.
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.
aa....aa: Name of the invalid clause:
{ FOR UPDATE OF|FOR READ ONLY }
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
  • 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 view table
  • UNION [ALL] or EXCEPT [ALL]
  • 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
  • External table, or a view table based on an external table
  • 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"

One of the following errors exists in the SQL statement:
  • A value or an identifier in a specified compile option is invalid.
  • The option value specified in CREATE FOREIGN TABLE is invalid.
  • The option value of OPTIONS specified in CREATE SERVER is invalid.
  • The option value of OPTIONS specified in CREATE USER MAPPING is invalid.
  • USER was not specified in OPTIONS for CREATE USER MAPPING.
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 national character or mixed character in environment using single-byte character code set or Unicode (UTF-8) character code set

While using Unicode (UTF-8), 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.
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 specification of argument in aa....aa

The argument specification in the function invocation contains the following errors:
  • Either a ? parameter or embedded variable was specified in an argument without specifying AS data-type.
  • A data type other than a predefined data type was specified in AS data-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.
One of the following errors occurred in the value expression specified in the argument of a scalar function (LENGTH, SUBSTR, POSITION) or in the assignment value of an assignment statement:
  • AS data-type was not specified, and a ? parameter or an embedded variable was specified in an argument
  • AS data-type, for which a data-type other than BLOB or BINARY was specified
  • AS data-type was specified in the value expression of other than a ? parameter or an embedded variable
  • A unary operation using a ? parameter or an embedded variable was specified in an argument
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:
  1. A structured repetition predicate
  2. A subquery
  3. A column other than those specified in ARRAY(repetition-column [, repetition-column]....).
  4. 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 |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.
  • The indexes included for all columns specified in FLAT are not defined.
  • The columns specified in FLAT do not include any repetition columns.
  • A view table, query name, external table, or table name 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:
    [Figure] FOR READ ONLY
    [Figure] FOR UPDATE clause
    [Figure] LIMIT clause
    [Figure] GROUP BY clause that specifies a value expression other than a column specification
    [Figure] Component specification
    [Figure] Set function containing a FLAT specification
    [Figure] Function call
    [Figure] Subquery
    [Figure] Set operation
    [Figure] Table join
    [Figure] Column that specifies a subscript
  • The following item is specified in a search condition:
    [Figure] Structured repetition predicate
S: Ignores this SQL statement.
P: Correct the SQL statement and re-execute.

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 scalar subquery or retrieval item is specified.
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 29 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 29.
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 29 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
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.
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.

KFPA11200-E A

Invalid table specification in CREATE ALIAS statement

The CREATE ALIAS statement contains an invalid table specification.
The RD-node name, authorization identifier, or table identifier format must be specified for a table in the CREATE ALIAS statement.
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

Table/index/trigger aa....aa. "bb....bb" not found in system

A table, table alias, index, or trigger aa....aa."bb....bb" was not found in the HiRDB system.
In the case of a data manipulation SQL that has a WITH clause specified, table aa....aa."bb....bb" was not found in the HiRDB system. Or, query name "bb....bb" was not found in the WITH clause.
aa....aa: Authorization identifier
bb....bb: Table identifier, table alias, index identifier, query name, or trigger 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.

KFPA11206-E A

Invalid aa....aa type

One of the following errors was detected in the table or the index specification:
Table:
  • DROP TABLE cannot be used to delete a view table definition or external table definition.
  • DROP VIEW cannot be used to delete a base table or external table definition.
  • DROP FOREIGN TABLE cannot be used to delete a base table or view table.
Index:
  • DROP INDEX cannot be used to delete an external index definition.
  • DROP FOREIGN INDEX cannot be used to delete an index definition.
aa....aa: { table | index }
S: Ignores this SQL statement.
P:
table:
If DROP TABLE was executed, specify a base table and re-execute. If DROP VIEW was executed, specify a view table and re-execute. If DROP FOREIGN TABLE was executed, specify an external table and re-execute.
index:
If DROP INDEX was executed, specify an index and re-execute. If DROP FOREIGN INDEX was executed, specify an external index and re-execute.

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 defined as NOT NULL.
  • 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 defined as NOT NULL.
  • 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

"ROW" can be specified only for "FIX" table

ROW cannot be specified for a table other than a table that has the FIX attribute.
S: Ignores this SQL statement.
P: Correct the SQL statement and re-execute.

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 SQLCODE or SQLCOUNT

Either SQLCODE or SQLCOUNT is used in a condition in an IF or WHILE statement, in an assignment value in a SET statement, or in a non-return value in a RETURN statement.
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-supplied 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.

KFPA11230-E A

Unable to specify other RDNODE in "CREATE PROCEDURE" or "ALTER PROCEDURE"

SQL for accessing another RD-node cannot be specified in the CREATE PROCEDURE statement. Or, SQL for accessing another RD-node was specified from the procedure to be re-created by the ALTER PROCEDURE statement.
S: Ignores this SQL statement.
P:
When the CREATE PROCEDURE statement was executed:
Correct the definition statement so that no other RD-node is accessed, and then re-execute.
When the ALTER PROCEDURE statement was executed:
Execute the DROP PROCEDURE statement, correct the definition statement so that no other RD-node is accessed, then re-create with the CREATE PROCEDURE statement. Or, execute the DROP PROCEDURE statement and modify the UAP so that this procedure will not be used.

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:
  • 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.
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 JavaTM 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, but a parameter style other than SQL 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

You cannot specify the routine "bb....bb"."cc....cc" whose authorization identifier, routine identifier, or the number of arguments matches the function or procedure being defined in a routine definition.
aa....aa:
{ function |procedure }
bb....bb: Authorization identifier
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:
  1. A plug-in index is defined in the first argument of the sending function for inter-function value passing.
  2. 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.
  3. 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
  4. A predicate including IS FALSE, IS UNKNOWN, or NOT was not specified in the sending function for inter-function value passing.
  5. No sending function for inter-function value passing was specified in CAST.
  6. 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.
S: Ignores this SQL statement.
P: Correct the SQL statement or review the index definition, and then re-execute.

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 input 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 (the data's length may be an odd number of bytes):
  • Data in the bbbbbth input variable, or 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
  • Data to be returned as a return value of a function
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:
  1. 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.
  2. 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.
  3. 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:
  1. 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.
  2. 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.
  3. 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 [Figure] SQLD [Figure] 30000 and SQLD [Figure] SQLN [Figure] 30000 and re-execute.

KFPA11311-E A

Invalid data type or length of variable aa....aa

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
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. When using UTF-8 as the character code, specify all data types other than national character data in the embedded variables and re-execute.

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 the specification in the SQL Data Area and re-execute.

KFPA11313-E A

Number of variables not equal to number of parameters

The number of embedded variables or parameters in the DECLARE CURSOR statement is not the same as the number of embedded variables specified in the OPEN statement or the number of parameters specified in the OPEN statement procedure (SQL Data Area). Or, the number of ? parameters in the SQL statement is not the same as the number specified for SQLD in the SQL Data Area.
S: Ignores this SQL statement.
P: Correct the SQL Data Area or the SQL statement so that the numbers of embedded variables or parameters are the same, then re-execute. Or, correct the value specified in the SQL Data Area and re-execute.

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.

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 Data Area is invalid or has not been set.
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 Data Area)
S: Ignores this SQL statement.
P:
  1. Check the type of embedded variable for receiving the retrieval result as to whether it correctly corresponds to the data type of the column.
  2. If the SQL Data Area is used directly, check if the value of SQLLEN is set correctly according to the data type of the corresponding column.
  3. If an indicator variable is used, check if the length of the receive area is correct.
  4. If a Column Name Descriptor Area (SQLCNDA) or a Type Name Descriptor Area (SQLTNDA) is used, check to verify 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 code for system-related error
See 4.2 Detail codes for system-related errors.
S: Ignores this SQL statement.
P: Remove the error cause 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:
  1. Check to be sure your work flow did not incorrectly issue a request to update an RDAREA in frozen update status.
  2. 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 pound sign (#) 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 pound sign (#) 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.

KFPA11369-E A

Unable to specify RDNODE name "aa....aa" for table specification in bb....bb statement

A qualification with an RD node name is found in either a procedure definition or a procedure body for a type definition.
Remote access using the distributed database function cannot be performed from a procedure.
aa....aa: Specified RD node name.
bb....bb: {CREATE PROCEDURE | CREATE TRIGGER | PROCEDURE definition in CREATE TYPE}
S: Ignores this SQL statement.
P: Correct the SQL statement and re-execute.

KFPA11371-E A

Invalid RDNODE name aa....aa

The specified RD-node name is invalid.
aa....aa: RD-node name
S: Ignores this SQL statement or invalidates this transaction.
P: Revise the RD node name specified in HiRDB or the RD node name specified in the DF/UX environment definition.

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.

KFPA11383-E A

Failure occurred in remote access, reason code=aa, process ID=bb....bb, connection ID=cc....cc, RMID=dd....dd

An error occurred during remote access processing.
aa: Reason code
bb....bb: Process ID of the single server or front-end server.
cc....cc: Connection ID between HiRDB and DF/UX. If the connection ID cannot be displayed, the asterisk (*) is displayed instead.
dd....dd: RMID to be passed from HiRDB to DF/UX. If the RMID cannot be displayed, the asterisk (*) is displayed instead.
S: Ignores this SQL statement.
Action
Take action appropriate to the reason code, as listed below:
Reason code Explanation Action
1 DF/UX has not been started or has terminated abnormally. If DF/UX has not been started, start DF/UX and re-execute the UAP. If DF/UX has terminated abnormally, refer to the message that was output by DF/UX to check the cause of the abnormal termination.
See the Distributed Database System DF/UX for details.
Contact a customer engineer, if necessary.
2 Maximum number of DF/UX users was exceeded. Reduce the number of concurrent users. Or, change the maximum number of DF/UX users.
See the Distributed Database System DF/UX for details.
3 Timeout was detected by DF/UX. Re-execute the UAP. Or, change the DF/UX abort time.
See the Distributed Database System DF/UX for details.
4 Communication error was detected by DF/UX. Refer to the message that was output by DF/UX to determine the cause of the communication error, eliminate the cause, and re-execute the UAP.
See the Distributed Database System DF/UX for details.
Contact a customer engineer, if necessary.
5 DF/UX version is invalid. Check the DF/UX version. If it is not the correct version, replace it with the correct version.
31 NOUSE is set in the dfux_extension_func clause of the DF/UX environment definition, or the DF/UX Extension has not been installed. Install DF/UX Extension and set USE in the dfux_extension_func clause of the DF/UX environment definition.

KFPA11384-E A

Invalid response from server system in remote access, reason code=aa

Invalid response from the server was detected during remote access.
aa: Reason code
S: Ignores this SQL statement.
Action
Contact a customer engineer.
Reason code Explanation
01 Data type of response information is invalid.
02 Error type of error response information is invalid.
03 A value other than 1 was returned as the SQL DBL RESULT VALUES count in an SQL statement other than the FETCH statement.

KFPA11388-E A

DF/UX error detected in remote access, process ID=aa....aa, connection ID=bb....bb, RMID=cc....cc, dd....dd

An error occurred in DF/UX during remote access processing.
aa....aa: Process ID of the single server or front-end server
bb....bb: Connection ID between HiRDB and DF/UX. If the connection ID cannot be displayed, the asterisk (*) is displayed instead.
cc....cc: RMID to be passed from HiRDB to DF/UX. If the RMID cannot be displayed, the asterisk (*) is displayed instead.
dd....dd: Maintenance information
S: Ignores this SQL statement.
Action
If a DF/UX message is output, refer to that message to determine the cause of the error. If the error cannot be identified, contact a customer engineer.

KFPA11390-E A

Permanent error occurred in remote access

An error occurred during remote access processing and remote access became disabled.
S: Ignores this SQL statement.
Action
Refer to the HiRDB message that was output before this message or the message that was output by DF/UX to eliminate the cause of the error, then re-execute the UAP. For information on DF/UX messages, see the Distributed Database System DF/UX.

KFPA11395-E A

Unable to execute SQL for foreign server aa....aa (b), reason=cc....cc

The SQL to the external server cannot be executed for reason cc....cc.
aa....aa: External server name
b: Server type
P: HiRDB
R: XDM/RD E2
O: ORACLE
I: DB2
cc....cc: Reason:
COMMUNICATION ERROR: Communication error
TIME OVER: Time-out
MEMORY EXCEEDS THE LIMIT: Memory limit exceeded
S: Terminates the process. Aborts SQL execution if this message is output.
P: Solve the problem according to the reason code.
MEMORY EXCEEDS THE LIMIT:
Reduce the sum of the column lengths to be searched in the external table or the value of the pd_hb_ary_fec_num operand (the number of array FETCH statements issued to the foreign server) in the foreign server information definition. Re-execute SQL. For details about the amount of memory required when SQL code is being executed on a foreign table, see the HiRDB Version 8 Installation and Design Guide.
In all other cases:
Check the error information for the previous SQL executed on the target foreign server and resolve the error.

KFPA11396-E A

Unable to access foreign server because External Data Access is reduced mode

The external server cannot be accessed because the HiRDB External Data Access facility is unavailable.
S: Terminates the process.
Action
Refer to the KFPW05039-E message that was output when the dictionary server was started to eliminate the cause of the error. If the KFPW05039-E message was not output, normally terminate HiRDB, and then start it normally. Contact a customer engineer if this error message is output again and the KFPW05039-E message is not.

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.
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#:
[Figure]1029 to [Figure](1030 - 1)
Floating point numeric literal:
[Figure]4.9 [Figure] 10-324 to [Figure]1.7 [Figure] 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 29 (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

An arithmetic operation cannot be specified for character string data, national character string data, mixed character string data, large object data (BLOB), binary data (BINARY), timestamp data, abstract data, or Boolean data (BOOLEAN).
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

Conversion is not applicable to the data type of the specified update or insert value.
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.

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.
aaa: Number of the query specifying a nonconvertable 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:
  • Numeric data
  • 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 [Figure] year [Figure] 9999
    01 [Figure] month [Figure] 12
    01 [Figure] day [Figure] 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 [Figure] hour [Figure] 23
    00 [Figure] minute [Figure] 59
    00 [Figure] second [Figure] 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 [Figure] fractional second [Figure] 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 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 cannot be specified in the SELECT clause.
aaa: Number of the query specifying the ? parameter
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"
 |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 8 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 value expression specified at aaa or type expression is invalid in scalar function "bb....bb".
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}
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 number aaa value expression of a scalar function (VALUE, BIT_AND_TEST, POSITION) or a CASE abbreviation (NULLIF, COALESCE) are not compatible.
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"
|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 [Figure] value-expression-2 [Figure] length of value-expression-1
  • 0 [Figure] value-expression-3 [Figure] 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 [Figure] value-expression-3 [Figure] 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:
  • BOOLEAN
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 a customer engineer.

KFPA11432-E A

Unable to specify local RDNODE name in CONNECT, DISCONNECT or SET CONNECTION statement

The RD-node name of the specified RD-node cannot be specified in the CONNECT, DISCONNECT, or SET CONNECTION statement.
S: Ignores this SQL statement.
P:
  1. To connect to HiRDB at the specified RD-node, use the CONNECT statement without specifying the RD-node.
  2. To disconnect a UAP from HiRDB at the specified RD-node, use the DISCONNECT statement without specifying the RD-node.
  3. To use the specified RD-node as the current RD-node, use the SET CONNECTION statement with DEFAULT specified.

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 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, the FOR READ ONLY predicate definition, view table definition, or query name cannot be derived.
  • BLOB
  • Abstract data type
  • BOOLEAN
If the result of a scalar subquery specified in a selection expression is one of the following data types, view tables cannot be defined and query names cannot be derived.
  • BLOB
  • BINARY 32,001 bytes or larger
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 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 the value expression in CASE does not match the data type of value expression aaa in WHEN in a simple 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 view table definition, this is the number of the query that specified the view 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:
    [Figure] Change the update conditions.
    [Figure] 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:
    [Figure] Change the deletion conditions.
    [Figure] 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:
    [Figure] Change the value of the foreign key to be inserted to an appropriate value.
    [Figure] 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:
    [Figure] Change the update conditions.
    [Figure] Change the update value of the foreign key to an appropriate value.
    [Figure] 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.
(Example) CAST(TIME-type AS INT)
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

Value expressions of an abstract data type cannot be specified in a view definition or in a derived query expression for a query in a WITH clause. If a CASE expression is specified in a selection expression in the outermost query, a repetition column cannot be specified in its search condition.
aa....aa:
{ abstract data |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 view table or the WITH clause is duplicated. A column name can be specified only once in a view table or in a query name in a WITH clause.
aa....aa: Duplicate column name
bb....bb: Name of the view 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 view 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 view 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 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
  • Repetition column
The conditions for creating an internal derived table are as follows:
  1. 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.
  2. 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
  3. 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
  4. 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
  5. 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.
  6. 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
  7. 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.
  8. 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
  9. 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
  10. 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:
      [Figure] Table join
      [Figure] GROUP BY clause, HAVING clause, or a set function
      [Figure] SELECT DISTINCT
      [Figure] A value expression in a selection expression other than a column specification
      [Figure] A query that creates an inner derived table
      [Figure] 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:
      [Figure] A named derived table derived by specifying the joining of tables
      [Figure] A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
      [Figure] A named derived table derived by specifying SELECT DISTINCT
      [Figure] A named derived table derived by specifying a value expression other than a column specification in a selection expression
      [Figure] A named derived table derived by specifying a query that creates an inner derived table
      [Figure] 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 [Figure] 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.

KFPA11462-E A

Unable to specify "aa....aa" "bb....bb" in view definition or "WITH" clause or "WITH" query expression body

A table alias defined for access to a table in another RD node, or table name qualified by another RD node, cannot be specified in a derived query expression of a view definition statement, or in a derived query expression or the query expression body in a query expression in a WITH clause.
aa....aa: ALIAS or OTHER RDNODE
bb....bb: Table alias or another RD-node name
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 query in a WITH clause:
  • Component specifications
  • Functions provided by a plug-in
  • Logical predicates
  • WRITE specifications
  • GET_JAVA_STORED_ROUTINE_SOURCE specifications
aa....aa:
{ component specification
 |PLUGIN function
 |boolean predicate
 |WRITE specification
 |GET_JAVA_STORED_ROUTINE_SOURCE specification }
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 RETURN statement and the RETURNS clause do not have convertible data types.
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
  • View 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:
  1. 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
  2. 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
  3. 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 8 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 8 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 8 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 8 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 of the CALL statement is not convertible to the data type of the "bb....bb"th parameter of the procedure to be called.
aa....aa: Argument number of the inconvertible data type
bb....bb: Data type of the parameter to which the procedure corresponds:
{ INTEGER |SMALLINT |DECIMAL(m,n)
 |FLOAT |SMALLFLT |CHARACTER(l)
 |VARCHAR(l) |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,n indicates 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.

KFPA11478-E A

Invalid aa....aa 'bb....bb'

One of the following errors was detected in the server type or server version of CREATE SERVER:
  • Server type specification exceeds 30 characters in length.
  • Server version specification exceeds 30 characters in length.
  • Server type that can be accessed was not specified.
  • Server version that can be accessed was not specified.
aa....aa: {TYPE|VERSION}
bb....bb: Invalid server type or server version
Displays the first 30 characters when the server type or server version is 30 characters or more in length.
S: Ignores this SQL statement.
P: When 'bb....bb' is incorrect, correct the SQL statement and re-execute. When 'bb....bb' is correct, contact the HiRDB administrator.
Action
When aa....aa is TYPE and 'bb....bb' is correct:
HiRDB External Data Access Adapter for 'bb....bb' is not installed. Check which HiRDB External Data Access Adapter is installed.
When aa....aa is VERSION and 'bb....bb' is correct:
The HiRDB External Data Access Adapter does not support the 'bb....bb' server version. Check which HiRDB External Data Access Adapter is installed.

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.

KFPA11481-E A+L

Error occurred in foreign server aa....aa (b), SQLCODE=cc....cc, inf=dd....dd

The external server returned an error when the HiRDB External Data Access facility was being used.
aa....aa: External server name
b: Server type
P: HiRDB
R: XDM/RD E2
O: ORACLE
I: DB2
cc....cc: SQLCODE returned from the external server
dd....dd: Message returned from the external server
When the message is 76 characters or more in length, the first 74 characters are output, followed by two periods (..).
S: Terminates the process. Aborts execution of the SQL statement if this message was output during SQL statement execution.
P: Confirm the type of the external server and refer to the SQLCODE and error message based on the applicable DBMS manual. After removing the cause of the error, re-execute the UAP.

KFPA11482-E A+L

Error occurred in External Data Access Adapter aa....aa (b), kind=cc, inf=dd....dd

The HiRDB External Data Access Adapter returned an error when the HiRDB External Data Access facility was being used.
aa....aa: External server name
b: Server type
P: HiRDB
R: XDM/RD E2
O: ORACLE
I: DB2
cc: Type of error returned from the HiRDB External Data Access Adapter
dd....dd:
Message returned from the external server
When the message is 76 characters or more in length, the first 74 characters are output followed by two periods (..).
S: Terminates the process. Aborts execution of the SQL statement if this message was output during SQL statement execution.
P: Take an action according to the error type.
Error type cc Description Action
1 Initialization error of the DB client Confirm that the DB client can operate in the current environment and re-execute UAP.
2 There is no indicator variable even though the data is a null value. Use CREATE FOREIGN TABLE to specify the column general option NULLABLE 'YES' in the column causing the error.
3 An overflow occurred when converting the output format into the DECIMAL type. Use CREATE FOREIGN TABLE to confirm the specified data type.
4 A data type that cannot be used was specified.
5 Data conversion error
Other than the above Does not apply. Contact a customer engineer.

KFPA11483-E A+L

External Data Access Adapter not installed for foreign server aa....aa, type=bb....bb, version=cc....cc

When the HiRDB External Data Access facility was being used, the HiRDB External Data Access Adapter corresponding to the foreign server is not installed.
aa....aa: External server name
bb....bb: Server type (server type specified by CREATE SERVER)
cc....cc: Server version (server version specified by CREATE SERVER)
S: Terminates the process. Aborts execution of the SQL statement if this message was output during SQL statement execution.
P: Request the HiRDB administrator to install the HiRDB External Data Access Adapter that corresponds to the server type and server version specified by CREATE SERVER.
Action
Install the HiRDB External Data Access Adapter that corresponds to the server type and server version specified by CREATE SERVER.

KFPA11484-E A+L

Fail to load External Data Access Adapter.

Loading of the HiRDB External Data Access Adapter failed.
S: Terminates the process.
Action
Follow the instructions in the KFPW message output before this message was output.

KFPA11485-E A+L

Fail to get symbol External Data Access Adapter.

An attempt to acquire a symbol for the common library of the HiRDB External Data Access Adapter failed.
S: Terminates the process.
Action
Follow the instructions in the KFPW message output before this message was output.

KFPA11486-E A+L

Unable to connect foreign server aa....aa (b), reason=cc....cc

When the HiRDB External Data Access facility was being used, an attempt to connect to the foreign server failed for the following reason:
  • User mapping for the foreign server was not defined.
aa....aa: External server name
b: Server type
P: HiRDB
R: XDM/RD E2
O: ORACLE
I: DB2
cc....cc: Reason (USER_MAPPING)
S: Terminates the process. Aborts execution of the SQL statement or invalidates the transaction if this message was output during SQL statement execution.
O: Define user mapping to the foreign server and re-execute the UAP.

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 dd....dd error, code=ee....ee, in copying JAR file "aa....aa" to "bb....bb" for cc....cc

An error occurred in a system function during JAR file registration, re-registration, or deletion.
aa....aa: JAR file name (first 80 characters only if the name exceeds 80 characters)
bb....bb: Temporary file name
cc....cc
{ install |replace |remove }
dd....dd: System function name
ee....ee: System-related error detail code
See 4.2 Detail codes for system-related errors.
S: Invalidates the transaction.
P: Remove the error cause and re-execute the transaction.

KFPA11490-E A

aa....aa JAR "bb....bb" failed, because cc....cc

JAR file registration, re-registration, or deletion failed.
aa....aa
{ install |replace |remove }
bb....bb: JAR file name (first 80 characters only if the name exceeds 80 characters)
cc....cc: Cause:
transaction already begin:
The transaction has already begun.
JAR file already installed:
JAR file has already been registered.
JAR file not found:
JAR file cannot be found.
JAR file synchronization failed:
An error occurred in the pdjarsync command.
S: Invalidates the transaction.
P:
  • When cc....cc is transaction already begin
    Before registration, re-registration, or deletion, commit the transaction (COMMIT or ROLLBACK).
  • When cc....cc is JAR file already installed
    If the existing JAR file may be overwritten, execute REPLACE JAR.
  • When cc....cc is JAR file not found
    Correct the specified JAR file name and re-execute.
  • When cc....cc is JAR file synchronization failed
    Use the pdjarsync command to display a list of JAR files, then check the contents of this JAR file. If necessary, re-execute registration, re-registration, or deletion with the pdjarsync 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, # 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, # is displayed as the 64th character)
dd....dd: One of the following (if the item exceeds 65 characters, # 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.
  • Remove 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 Java method ROUTINE aa....aa."bb....bb", reason_code=cc, message=dd....dd

Java stored procedure or Java stored function could not be executed for reason cc.
aa....aa: Owner name
bb....bb: Name of Java stored procedure or Java stored function
cc: Reason code:
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.
dd....dd: Message (if the message exceeds 109 characters, # is displayed as the 109th character):
  • Method name when cc is 02, 04, or 08
  • Class name when cc is 03 or 07
  • JAR file name when cc is 05 or 06
  • Return value type name specified by EXTERNAL NAME and return value type name of the Java method when cc is 09
S: Ignores this SQL statement.
P: Take one of the following actions:
  • Check the following in EXTERNAL NAME in the definition of the Java stored procedure or Java stored function:
    [Figure] Method name when cc is 02 or 04
    [Figure] Class name when cc is 03 or 07
    [Figure] JAR file name when cc is 05 or 06
    [Figure] Java class source file (whether or not the static qualifier is present in the method) when cc is 08
    [Figure] Return value type and Java method's return value type when cc is 09
  • Check whether the specified JAR file is registered correctly.

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.

KFPA11496-E A

Unable to specify subquery in SQL using foreign table

A subquery cannot be specified to an SQL that accesses a foreign table. Also, the view table including subqueries cannot mix specifications with a foreign 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.

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.
  • * is specified for the data size of the parameter data type or the data size of the return value data type.
  • void is not specified as the returns type name in the EXTERNAL NAME clause of the procedure that specifies Java 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:
  1. Cursor declaration or cursor assignment
  2. OPEN statement
  3. FETCH statement
  4. 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.
  • Connected to a distributed RD node.
  • This is not executed first in a transaction.
aa....aa: One of the following:
{ ACTIVE TRANSACTION |HOLDABLE CURSOR
 |LOCK WITH UNTIL DISCONNECT
 |DISTRIBUTED DATABASE ACCESS |NON-FIRST EXECUTION}
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 cannot 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 (table, index, or definition changes), redefine the procedure, and then re-execute.

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)
  • CREATE INDEX TYPE
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 HiRDB Version 8 SQL Reference.
For a CALL statement, a routine cannot be called if the data type of the argument of the statement is incompatible with the data type of the parameter of the routine.
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
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
  • Argument 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 authorization identifier, the routine identifier, the number of arguments, or the data types of the arguments.
During execution of CREATE INDEX TYPE:
Check there are no errors in any of the following specifications:
  • Authorization identifier
  • Routine identifier
  • Number of arguments
  • Data types of arguments
If there are no errors, redefine the function by using the CREATE FUNCTION or CREATE DATA TYPE statement as appropriate.

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 view 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 dd....dd privilege for table bb....bb.cc....cc

One of the following errors has occurred:
  • There is no dd....dd privilege for the applicable table; SQL statement aa....aa cannot be executed.
  • If CREATE VIEW is displayed in aa....aa when the Directory Server linkage facility is being used, CREATE VIEW cannot be executed because of the lack of the SELECT privilege on the base table for the work table. Even if the user has the SELECT privilege for the group or role in which he belongs, a viewed table cannot be defined using the privilege.
If the optimizing information collection utility (pdgetcst) is being used, the user does not have the SELECT privilege for the table to be processed.
aa....aa: SQL statement to be executed
bb....bb: Authorization identifier
cc....cc: Table identifier
dd....dd: Required access privilege
If the user attempted to execute LOCK TABLE with EXCLUSIVE specified and does not have the DELETE, INSERT, or UPDATE privilege, UPDATE is displayed for dd....dd.
S: Ignores this SQL statement.
P:
Acquire the required access privilege and re-execute.
When using the Directory Server linkage facility and CREATE VIEW is displayed in aa....aa, request the owner of the view table base table to grant base table SELECT privileges.
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, group ID, or role name. 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 view 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 view 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:
  • CREATE ALIAS
  • DROP ALIAS
  • GRANT DBA
  • GRANT CONNECT
  • GRANT RDAREA
  • GRANT SCHEMA
  • REVOKE DBA
  • REVOKE CONNECT
  • REVOKE RDAREA
  • REVOKE SCHEMA
  • CREATE SERVER
  • CREATE USER MAPPING
  • DROP SERVER
  • DROP USER MAPPING
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:
  1. When specifying columns in a value expression, columns other than dictionary table columns cannot be specified.
  2. 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.
  3. This scalar function cannot be specified in a search that uses a list.
  4. This scalar function cannot be specified in a selection expression or HAVING clause.
  5. 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.
  6. 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.
  7. 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
  8. More than one dictionary table was specified in the FROM clause.
  9. The length of the group ID or role name exceeded the limit.
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.
When using the Directory Server linkage facility, DBA privileges or schema definition privileges cannot be granted to a user who is not registered in the directory server.
aa....aa:
  • Authorization identifier of the user who does not have the CONNECT privilege
  • Authorization identifier of user who is not registered in the Directory Server
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. When using the Directory Server linkage facility, register the user of authorization identifier aa....aa on the Directory Server 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 version 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.
When using the Directory Server linkage facility
If the password registered in the Directory Server has expired, reset the password on the Directory Server and re-execute.
If this message is output when accessing a table, first disconnect from HiRDB. Then, specify the authorization identifier and password currently registered on the Directory Server and re-execute.

KFPA11561-E A

Specified authorization identifier aa....aa has no connect privilege

Specified authorization identifier aa....aa does not have the CONNECT privilege.
When using the Directory Server linkage facility, the user is not registered on the Directory Server. If this message is output when accessing a table, the user information was deleted from the Directory Server since the user previously connected to HiRDB.
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"
To use the Directory Server linkage facility, request the system administrator for the Directory Server to register the user.

KFPA11562-E A

Unable to bb....bb connect privilege due to aa....aa

The CONNECT privilege cannot be revoked due to aa....aa.
CONNECT privileges are not granted when the Directory Server linkage facility is being used.
aa....aa:
DBA privilege: DBA privilege
schema: Schema
using directory server: Directory Server linkage facility
bb....bb: revoke or grant
S: Ignores this SQL statement.
Action
Take one of the following actions:
  • When bb....bb is revoke
    Delete the DBA privilege or schema privilege and re-execute.
  • When bb....bb is grant
    Register the user on the Directory Server.

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 version 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

If aa....aa is Invalid
cc....cc required for the processing requested by operation code bbbb is not set correctly.
If aa....aa is Unexpected
Requested data cannot be set in the area specified by parameter cc....cc.
Data cannot be requested by the DESCRIBE call unless it was requested during preprocessing call. Data cannot be set if it was already set by the DESCRIBE call during preprocessing.
aa....aa: Type of preprocessing:
{ Invalid |Unexpected }
bbbb: Operation code (4 characters):
{ AUX |AUXI |AUXO |DESC |DEST |FETC |HVAR |OPEN |OPNR |RSDC |RSFT }
cc....cc: Name of the SQL Data Area field
S: Ignores this request.
P:
aa....aa is Invalid
Perform the following action, and then re-execute the UAP:
  • 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
FETC or RSFT Specify the SQL descriptor area name that sets the information required for retrieval.
DESC, DEST, HVAR, or RSDC Specify the SQL descriptor area name that receives the information.
OPEN, OPNR, AUX, AUXI, or AUXO Specify the SQL descriptor area name that sets the input ? parameter information.
  • cc....cc is SQLIASDA2
    Specify the SQL descriptor area name that sets the output ? parameter or the information required for retrieval.
aa....aa is Unexpected
If the data is required, request it by a preprocessing call. If the data has already been acquired, set 0 in SQL Data Area cc....cc and re-execute the UAP.

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 a customer engineer 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 of CREATE TABLE cluster key definition for the table storage RDAREAs, LOB column storage RDAREAs, or LOB attribute storage RDAREAs.
  • 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.
  • An attempt was made with ALTER TABLE ADD RDAREA to add the RDAREA in which is already stored an index, primary key, or cluster key that is defined for this table.
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 bbbbb cc....cc."dd....dd"

The RDAREA usage privilege cannot be revoked, because the specified RDAREA contains a table or index.
aa....aa: RDAREA name
bbbbb: Object of processing:
{ table |index }
cc....cc: Authorization identifier of the table or index in the RDAREA
dd....dd: Table identifier or index identifier in the RDAREA
S: Ignores this SQL statement.
Action
Delete the table or index from the RDAREA and re-execute.

KFPA11577-E A

Unable to revoke schema privilege due to table/routine existence

Because a table or routine is defined in a schema, the schema definition privilege cannot be revoked.
S: Ignores this SQL statement.
P: Delete the table, routine, or schema, then re-execute.

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

A schema or table alias cannot be defined because the user does not have the schema definition privilege.
aa....aa: Invalid SQL statement
{ schema |alias }
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"

The following table identifier, index identifier, routine identifier, trigger identifier, constraint name, data type identifier, index type identifier, or table alias specified in the SQL statement is already defined:
  • ALTER TABLE
  • CREATE ALIAS
  • CREATE FOREIGN INDEX
  • CREATE FOREIGN TABLE
  • CREATE FUNCTION
  • CREATE INDEX
  • CREATE INDEX TYPE
  • CREATE PROCEDURE
  • CREATE TABLE
  • CREATE TRIGGER
  • CREATE TYPE
  • CREATE VIEW
aa....aa: The SQL statement to be executed
{alias |constraint|datatype |index
|indextype |routine |table |trigger}
bb....bb: Authorization identifier
cc....cc: Table identifier, index identifier, routine identifier, table alias, trigger identifier, constraint name, data type identifier, or index type identifier
S: Ignores this SQL statement.
P: Change the table identifier, index identifier, routine identifier, table alias, trigger identifier, constraint name, data type identifier, or index type identifier, and re-execute.

KFPA11602-E A

Over 30000 defined 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. Or, 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
  • AS clause for the ? parameter or embedded variable
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 [Figure]
SQL parameter declaration declaration of SQL parameter SQL parameter name [Figure]
SQL variable declaration declaration of SQL variable SQL variable name [Figure]
Attribute definition definition of attribute Attribute name [Figure]
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 [Figure]
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 ******** [Figure]
CURRENT_TIMESTAMP CURRENT_TIMESTAMP ******** [Figure]
AS clause specified for the ? parameter or embedded variable AS clause for ? parameter or embedded variable ******** [Figure]
[Figure]: 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.

KFPA11606-E A

Unable to specify ALIAS for table in local RDNODE

A table alias cannot be defined for a table or view of a local RD-node.
S: Ignores this SQL statement.
P: Change the RD-node name and 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, view table, external table, index, and external index to be owned by another user
  • Deletion of a base table, view table, or index owned by another user
  • Modification to the definition of a base table owned by another user
  • Addition of a comment to a base table, view table, and external table owned by another user
  • Creation or deletion of a procedure owned by another user
  • Creation of a foreign table on a foreign server 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
In the Windows version 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|foreign server|trigger|function|datatype|indextype}
S: Ignores this SQL statement.
P: Delete this SQL statement.

KFPA11608-E A

Unable to create table/index without privilege for specified RDAREA "aa....aa"

The user does not have the RDAREA usage privilege for the specified RDAREA; therefore, the user cannot create a table or index.
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

There is no available public user RDAREA. Or, there is an available public user RDAREA, but it cannot be used for one of the following reasons, and the table cannot be defined. Furthermore, an unshared RDAREA is required for a HiRDB/Parallel server to define an unshared table, and a shared RDAREA is required to define a shared table. For a HiRDB/Single server, an unshared RDAREA is required to define 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 on shutdown status.
  • A table using the rebalancing facility is defined (applicable only for defining unshared tables).
  • An inner replica facility was used in the RDAREA.
  • If the cluster key or primary key is specified, the key length of the index relative to the RDAREA page length has exceeded the maximum length. Calculate the key length as follows:
    key-length [Figure] MIN((page-length-of-RDAREA-for-index-storage [Figure] 2) - 1242, 4036)
    For details about how to calculate key lengths, see the description of CREATE INDEX in the manual HiRDB Version 8 SQL Reference.
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 with a NOT NULL specification or DEFAULT clause specification, or addition of a column in the 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:
  • DECIMAL with a length of at least 20 digits
  • BLOB
  • User-defined type
  • BINARY
When bb....bb is create foreign index:
A BINARY type column cannot be specified in a column comprising a foreign index.
aa....aa: Name of the column with the invalid data type
bb....bb: {create index|define foreign key|create foreign 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:
  • FLOAT
  • SMALLFLT
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 [Figure] MIN((page-length-of-RDAREA-for-index-storage [Figure] 2) - 1242, 4036)
For details about how to calculate key lengths, see the description of CREATE INDEX in the manual HiRDB Version 8 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 or CREATE FOREIGN 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 or CREATE FOREIGN 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:
  1. The specified hash function name could not be found.
  2. 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
  3. The hash function of tables not using the rebalancing facility cannot be changed to HASHA, HASHB, HASHC, HASHD, HASHE, or HASHF.
  4. The hash function of tables using the rebalancing facility cannot be changed to HASH1, HASH2, HASH3, HASH4, HASH5, or HASH6.
  5. HASHA, HASHB, HASHC, HASHD, HASHE, or HASHF cannot be specified in a table hash function defining a cluster key or primary key.
  6. 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.
  7. In the following cases, HASH0 cannot be specified in a hash function:
    [Figure] The data type of the column specified for partitioning is not CHAR(6), CHAR(8), DATE, or TIMESTAMP.
    [Figure] Multiple columns are specified in a 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.

KFPA11624-E A

aa....aa bb....bb."cc....cc" not found in system

Table alias bb....bb "cc....cc" cannot be found in the HiRDB system, or foreign server "cc....cc" is not in the HiRDB system.
aa....aa: { ALIAS | FOREIGN SERVER }
bb....bb: Authorization identifier (is not displayed when aa....aa is FOREIGN SERVER)
cc....cc: { table alias | foreign server name }
S: Ignores this SQL statement.
P: Check if the specified table alias or foreign server name is correct. If it is not correct, make the necessary correction and re-execute the SQL statement. If it is correct, delete this SQL statement.

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.

KFPA11628-E A

Unable to define "NOT NULL" constraint for multi-value column

When defining a table or modifying a table definition, NOT NULL (NOT NULL constraint) cannot be specified for a repetition column.
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 single column table

The specified column cannot be deleted, because it is the only column in the table.
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"

A storage condition column, boundary value partition column, or hash partitioning key column does not have the NOT NULL attribute.
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:
{1|1024}
bbbb:
{ 1|3000 }
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:
  1. 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.
  2. 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
  3. 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, or set function
    • Window function
    • Joined table
  4. 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
  5. 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 join operations is a table join specification.
  6. 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.
  7. 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.
  8. 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
  9. 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
  10. 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:
      [Figure] Table join
      [Figure] GROUP BY clause, HAVING clause, or a set function
      [Figure] SELECT DISTINCT
      [Figure] A value expression in a selection expression other than a column specification
      [Figure] A query that creates an inner derived table
      [Figure] 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:
      [Figure] A named derived table derived by specifying the joining of tables
      [Figure] A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
      [Figure] A named derived table derived by specifying SELECT DISTINCT
      [Figure] A named derived table derived by specifying a value expression other than a column specification in a selection expression
      [Figure] A named derived table derived by specifying a query that creates an inner derived table
      [Figure] 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 [Figure] 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 "COUNT(*)" in view or "WITH" query

Outer reference was specified for the following column:
  • Column in a view table defined from COUNT(*)
  • A column derived from the COUNT(*) specified in a selection expression in a derived query expression in the WITH clause
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 view table cannot be specified in a derived query expression joined table if the view table or the base table comprising the view table is defined as follows:
  • With subquery specified
  • By specifying the joining of tables, SELECT DISTINCT, a GROUP BY clause, or a HAVING clause
  • View 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 view 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 view 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:
  1. 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.
  2. 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)
  3. 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
  4. A query for a named derived table, derived by specifying a set function with DISTINCT specification, directly includes SELECT DISTINCT specification.
  5. 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
  6. 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 view 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 view 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
aa....aa:
{ ? parameter or embedded variable |ARRAY predicate }
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 TABLE
  • CREATE INDEX
  • 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:
aa....aa, the RDAREA applying the inner replica facility, is not applicable to falsification- prevented tables.
For these reasons, the following SQL statements cannot be executed:
  • ALTER TABLE
  • CREATE TABLE
  • CREATE INDEX
  • GRANT RDAREA
  • DROP INDEX
  • DROP TABLE
  • DROP SCHEMA
aa....aa: RDAREA-name
bb....bb: {not for user|replicated rdarea|used by inner replica facility}
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.

KFPA11654-E A

Number of aa....aa exceeds bbb

The number of tables or indexes in an RDAREA exceeds the maximum.
A maximum of 500 tables or indexes can be specified per RDAREA.
aa....aa: Object of processing:
{ tables |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 PROCEDURE
  • 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 FUNCTION, CREATE PROCEDURE, CREATE TABLE, CREATE TRIGGER, CREATE TYPE, or CREATE VIEW, use the CREATE SCHEMA statement to create a schema before executing the desired statement.
You do not have to execute DROP SCHEMA, ALTER PROCEDURE, or ALTER ROUTINE, 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:
[Figure]
Note
[Figure] [Figure] 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.
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 view table.
  • Table definition change cannot be performed on an audit trail table.
  • Foreign index cannot be created in a base table.
  • Index creation, trigger creation, or table definition change cannot be performed on a foreign table.
aa....aa: One of the following items is displayed:
  • alter table
  • create foreign index
  • create index
  • create trigger
bb....bb: One of the following items is displayed:
  • view
  • table
  • foreign table
  • audit trail table
S: Ignores this SQL statement.
P: Delete this SQL statement.

KFPA11661-E A

Identical structure index aa....aa."bb....bb" already exists

The same structure as index aa....aa."bb....bb" already exists.
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 [Figure] MIN ((page-length-of-index-storage-RDAREA [Figure] 2) - 1242, 4037)
For details about how to calculate key lengths, see the description of CREATE INDEX in the manual HiRDB Version 8 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.

KFPA11663-E A

Unable to drop server "aa....aa" due to defined bb....bb

Foreign server aa....aa cannot be deleted because it defines bb....bb.
aa....aa: Foreign server name
bb....bb
{ foreign table |user mapping }
S: Ignores this SQL statement.
P: Delete the user mapping definition and external table of the specified foreign server, and re-execute the SQL statement.

KFPA11664-E A

Specified aa....aa bb....bb already exists

The specified schema or foreign server is already defined.
aa....aa: { schema | foreign server }
bb....bb: { authorization identifier | foreign server name }
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 view table or the name of the view table is invalid. Or, the name of a base table for a view table is the same as the name of the view table.
S: Ignores this SQL statement.
P: Correct the SQL statement and re-execute.

KFPA11670-E A

"UPDATE" specified for aa....aa

The error shown by aa....aa occurred during update processing of a read-only view table, foreign table, falsification-prevented table, or audit trail table.
aa....aa: {read only view|foreign table supplied by DB2 UDB OS/390 V6|view table derived from foreign table supplied by DB2 UDB OS/390 V6|foreign table supplied by ORACLE, using "WITH ROLLBACK"|view table derived from foreign table supplied by ORACLE, using "WITH ROLLBACK"|foreign table, with cursor|view table derived from foreign table, with cursor|foreign table, using ROWID|view table derived from foreign table, using ROWID|INSERT ONLY table|view table derived from INSERT ONLY table|UPDATE ONLY FROM NULL column|AUDIT TRAIL TABLE}
read only view:
INSERT, UPDATE, or DELETE was executed on a read-only view table.
foreign table supplied by DB2 UDB OS/390 V6, or view table derived from foreign table supplied by DB2 UDB OS/390 V6:
A foreign server is executing an INSERT, UPDATE, or DELETE statement on a foreign table of DB2 UDB OS/390 V6 or on a viewed table having a foreign table as a base table.
foreign table supplied by ORACLE, using "WITH ROLLBACK", or view table derived from foreign table supplied by ORACLE, using "WITH ROLLBACK":
A foreign server is executing an INSERT, UPDATE, or DELETE statement specifying WITH ROLLBACK on an ORACLE foreign table or on a viewed table having a foreign table as a base table.
foreign table, with cursor, or view table derived from foreign table, with cursor:
A cursor-using UPDATE or DELETE statement is being executed on a foreign table or on a viewed table having a foreign table as a base table.
foreign table, using ROWID, or view table derived from foreign table, using ROWID:
An UPDATE or DELETE statement is being executed on a foreign table or on a viewed table having a foreign table as a base 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 view table using a falsification-prevented table as its base table.
  • UPDATE was executed specifying ROW for a falsification-prevented table or a view 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 view 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:
  1. 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
  2. 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
  3. 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
  4. 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
  5. 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.
  6. 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
  7. 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.
  8. 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
  9. 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
  10. 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:
      [Figure] Table join
      [Figure] GROUP BY clause, HAVING clause, or a set function
      [Figure] SELECT DISTINCT
      [Figure] A value expression in a selection expression other than a column specification
      [Figure] A query that creates an inner derived table
      [Figure] 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:
      [Figure] A named derived table derived by specifying the joining of tables
      [Figure] A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
      [Figure] A named derived table derived by specifying SELECT DISTINCT
      [Figure] A named derived table derived by specifying a value expression other than a column specification in a selection expression
      [Figure] A named derived table derived by specifying a query that creates an inner derived table
      [Figure] 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 [Figure] 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 view 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 view table were not specified once each in the view definition or SELECT clause in the derived query expression in the WITH clause for a view 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 }
bb....bb: Specified statement
{ CREATE TABLE |CREATE INDEX
 |CREATE PROCEDURE |CREATE FOREIGN TABLE
 |CREATE SERVER |CREATE USER MAPPING |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 }
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) in the CREATE TABLE statement.
aa....aa: Item exceeding the maximum number of columns:
CLUSTER KEY: Cluster key
FOREIGN KEY: Primary key
HASH KEY: Column subject to multicolumn hash partitioning
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 NOT NULL 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 view table, foreign table, or falsification prevented table.
aa....aa: {view table|foreign table|INSERT ONLY table}
S: Ignores this SQL statement.
P: Correct the SQL statement and re-execute.

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.

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 table aa....aa."bb....bb" in use

Because table aa....aa."bb....bb" is being used by another user, the SQL statement or operation command cannot be executed.
aa....aa: Authorization identifier
bb....bb: Table identifier
S: Ignores this SQL statement.
P: Check the SQL to be executed for an error. If there is no error, execute the SQL statement or operation command after the other user finishes using the table. The following command can be used to determine whether or not a table is being used by another user:
pdls -d lck -a

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.

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 1024 servers

A table cannot be defined to be partitioned into more than 1,025 back-end servers.
S: Ignores this SQL statement.
P: Set the number of back-end servers for partitioning to no more than 1,024 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 foreign table:
Cannot specify the following data types to a foreign table:
  • CHAR, VARCHAR, MCHAR, or MVARCHAR data longer than 256 bytes
  • NCHAR or NVARCHAR statements longer than 128 characters
  • BINARY statements longer than 256 bytes
aa....aa: {"BLOB"|"BINARY"|long data}
bb....bb: {"FIX" table|foreign table}
S: Ignores this SQL statement.
P:
When bb....bb is "FIX" table:
Either do not specify the data type BLOB or BINARY, or delete the FIX attribute specification and re-execute.
When bb....bb is foreign table:
Respecify the data type and re-execute.

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

If the same table RDAREA is specified for multiple boundary values, during the boundary value partition of a table, the specification of the table RDAREA does not agree with the specification of one of the following items:
  • LOB column storage RDAREA
  • LOB attribute storage RDAREA
S: Ignores this SQL statement.
P: Make the LOB column storage RDAREA or the LOB attribute storage RDAREA consistent with the associated table RDAREA and re-execute.

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 aaaaaa 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.
aaaaaa: 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 bbbbb

The value of "aa....aa" exceeds the system maximum value bbbbb.
aa....aa: Applicable item
{ ADT LEVEL (number of generations of abstract data types) }
bbbbb: 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 view table, then re-execute.

KFPA11717-E A

Unable to rename aaaaaa name on "bb....bb" due to cc....cc

Table or column name cannot be changed for the following reason:
  • A view 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.
  • A 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.
  • A column to be changed is comprised of a foreign key.
  • A table to be changed is a referenced table of a referential constraint.
  • A column to be changed is comprised of the primary key of a referenced table of a referential constraint.
  • The table to be changed is specified in a stored procedure or trigger SQL statement.
  • An attempt was made to change a column name of a view 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 referred column 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.
aaaaaa: Item to be changed:
COLUMN: Column name
TABLE: Table name
bb....bb: Table or view table name
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 view 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 view table, stored procedure, or trigger that uses the table to be changed and re-execute the ALTER TABLE statement. Then, re-create the view 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 error log file where the error was output, and contact a customer engineer.
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.

KFPA11721-E A

User mapping for aa....aa on foreign server "bb....bb" cc....cc

User mapping definition for user aa....aa on foreign server bb....bb could not be created or deleted for one of the following reasons:
  • If cc....cc is already exists, the specified user mapping definition is already defined.
  • If cc....cc is not found in system, the specified user mapping definition was not found in the HiRDB.
aa....aa
{ authorization identifier |PUBLIC }
bb....bb
Foreign server name
cc....cc
{ already exists |not found in system }
S: Ignores this SQL statement.
Action
This SQL statement need not be executed.

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
SERVER PROCESS DOWN:
  • Check the cause of the server process shutdown, correct the error, then re-execute the UAP.
  • If the high-speed connection feature (PDSERVICEPORT in the client environment definition) is used, the value specified for PDSERVICEPORT may be invalid. Check if the KFPS00860-W message was output during HiRDB startup or if the value of PDSERVICEPORT is the same as the value of pd_service_port (system common definition or unit control information definition). If applicable, correct the value of the PDSERVICEPORT specification, and then re-execute the UAP.
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.
INVALID DATA:
Back up the error log file and contact a customer engineer.
Do not specify the pd_work_buff_expand_limit operand.

KFPA11723-E L+A

Communication error occurred, reason=aa....aa

A communication error occurred between the HiRDB system or the HiRDB server. Or, the HiRDB system or HiRDB server is down.
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.
S: Terminates processing.
P:
HiRDB BUSY displayed as aa....aa:
Wait a while, then re-execute. If the same message is reissued, contact the HiRDB administrator.
Other message displayed as aa....aa:
Report the nature of the error to the HiRDB administrator, correct the error, then re-execute.
Action
Check the error log file (created under PDCLTPATH) the HiRDB client outputs for the cause of the failure, eliminate the cause, and re-execute.
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 of the PDHOST or PDNAMEPORT operands in the client environment definition. Also, use the event log (in UNIX, syslogfile) to determine whether an error has occurred in the HiRDB server.
If the value of the PDHOST or PDNAMEPORT operand is correct and the KFPZ02444-E message (func=connect and the value indicated by errno is either ETIMEDOUT or ECONNREFUSED) is output to an error log file, there may be too many connection requests for the HiRDB server. In this case, wait for a short time and re-execute or increase the specification value of the Listen queue. For details about the Listen queue, see the HiRDB Version 8 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 that is the case, ask the HiRDB administrator about the condition. If necessary, change the connection destination to the application site HiRDB, and re-execute the command.
If this message is output, the connection with the HiRDB server was disrupted. It may be necessary to re-execute the command beginning with the CONNECT statement.

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 L+A

Time over, no response from HiRDB[,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 Type4 JDBC driver is being used.
aaaaa: The client's maximum wait time (value of the PDCWAITTIME operand of the client environment definition or the value of Statement#setQueryTimeout).
S: Terminates processing.
P:
If the HiRDB server was shut down, check that the HiRDB server is active, and re-execute. If the HiRDB server was not shut down, increase the client's maximum wait time (value of the PDCWAITTIME operand of the client environment definition or the value of Statement#setQueryTimeout), and 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.
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 the PDCLTRCVADDR variable in the client environment definition. From the host containing a single server or a front-end server for the HiRDB server, check whether the IP address specified in the PDCLTRCVADDR variable can be transmitted by means of the ping command.
This error can also occur if the address associated with the host name assigned to PDCLTRCVADDR differs between 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.

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 error log file is output, back up the error log file, eliminate the cause of the error in the server, then contact a customer engineer.

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

FES(SDS) canceled

SQL execution was cancelled based on a cancellation request received from the UAP. Processing cannot continue.
S: Terminates processing.
P: Because the requested processing has been cancelled, re-execute the UAP if necessary.

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: View 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"

  1. The routine aa....aa."bb....bb" for the SQL object that uses the resource to be deleted or changed exists. Therefore, the following definition SQL statements that invalidate the SQL objects cannot be executed. Or, because the routine aa....aa."bb....bb" for the SQL object that uses the resource to be deleted or changed is being executed, the following definition SQL statements cannot be executed:
    • ALTER TABLE (change the table definition)
    • CREATE TABLE (define a table)
    • CREATE TRIGGER (define a trigger)
    • CREATE TYPE (define a data type (subtype))
    • DROP DATA TYPE (delete a data type)
    • DROP FOREIGN TABLE (delete a foreign table)
    • DROP FUNCTION (delete a function)
    • DROP INDEX (delete an index)
    • DROP PROCEDURE (delete a procedure)
    • DROP SCHEMA (delete a schema)
    • DROP TABLE (delete a table)
    • DROP TRIGGER (delete a trigger)
    • DROP VIEW (delete a view)
    • REVOKE access permission (delete access permission)
  2. The view 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 a function)
    • DROP DATA TYPE (delete data type)
    • DROP SCHEMA (delete a schema)
  3. Because the trigger aa....aa."bb....bb" used in the search conditions of a trigger operation exists for the deleted function, the following definition SQL statements cannot be executed:
    • DROP FUNCTION (delete a function)
    • DROP SCHEMA (delete a schema)
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 view 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. Remove 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.

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. Remove the cause of the error, and re-execute the SQL statement.
Reason code (cc) Additional error information (dd....dd) Explanation
01 foreign table, view, or alias A foreign table, view table and table alias 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 storage condition cannot be specified in a hash partitioning key or in the following attribute 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
aa....aa: Column name where the error occurred
S: Ignores this SQL statement.
P: Specify the partitioning condition in an attribute column that can be used to specify partitioning conditions and re-execute.
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 re-execute.

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.
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: Convert the storage condition value into a data type that can be converted and re-execute.

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.

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 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.
  1. RDAREA extension
    Use the database structure modification utility to expand the size of the insufficient RDAREA.
  2. 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.
  3. Change the percentage of unused area 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|CREATE FOREIGN 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 system table

LOCK statements cannot be executed on a system table or on a view table that is based on a system table.
S: Ignores this SQL statement.
P: Correct the SQL statement and re-execute.

KFPA11770-I A

aa....aa [bb....bb cc....cc] currently in use, resource id=dd....dd

An SQL statement or a utility cannot be executed because the resource indicated by resource ID dd....dd is occupied by another transaction.
aa....aa: 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 8 System Operation Guide.
S:
SQL statement
If NO WAIT is specified in the lock option, this SQL statement is ignored and processing continues. Otherwise, the transaction is rolled back. However, even if NO WAIT is specified, the transaction might be rolled back. For details, see the explanation of the NO WAIT operand in the manual HiRDB Version 8 SQL Reference.
Utility
Processing terminates.
P:
If this message is output frequently with this SQL statement, consider revising the SQL lock option and the UAP lock control. For details, see the lock option explanation in the manual HiRDB Version 8 SQL Reference and the explanation of UAP design in the HiRDB Version 8 UAP Development Guide.
O:
Re-execute. Depending on the timing, this might be successful. For details, see the explanation of measures for deadlocks and timeouts in the HiRDB Version 8 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 re-execute.
Action
If this message is output frequently for an SQL statement for which NO WAIT and WITH ROLLBACK are not specified in the lock option, consider changing the value of the pd_lck_wait_timeout operand.

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 view table was specified.
  • A table alias was specified.
  • A table at another RD node was specified.
  • A foreign table was specified.
  • A shared table was specified.
  • A table with WITHOUT ROLLBACK specified 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, USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP is specified on both sides of the comparison operator in a search condition.
  • A literal, USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP is specified on the left side of the IN predicate in a search condition.
  • A literal, USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP is specified in value expression 1 of the BETWEEN predicate in a search condition.
  • A literal, USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP is specified on the left side of the LIKE predicate or XLIKE predicate in a search condition.
  • A literal, USER, CURRENT_DATE, CURRENT_TIME, or CURRENT_TIMESTAMP 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 8 UAP Development Guide).
S: This SQL statement is ignored.
P: Correct the SQL statement, and then re-execute it.

KFPA11777-E A

Unable to execute due to type aa....aa."bb....bb" in use

This SQL statement cannot be executed because the abstract data type aa....aa."bb....bb" is being used by another user.
aa....aa: Authorization identifier
bb....bb: Data identifier
S: Ignores this SQL statement.
P: Re-execute this 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.
  • A single column index is required in the column of the IN predicate specifying a subquery.
  • 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.
  • 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:
    [Figure] When there is one IN column, there are no more than 5 values specified.
    [Figure] When there are two or more IN columns, the total number of values specified in each column must be 5 or less.
  • If a search condition is not specified, any column (excluding a repetition column) in the table requires an index (excluding an index with an exception key value or a plug-in index).
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, the list has not been created; in such a case, create the list and then re-execute.

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: If the table in question is being used as the user's list, first delete all lists that use this table as a base table, and then re-execute.

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 specification does not correspond to an RDAREA for a table partitioned by boundary values.
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 exceeded the maximum of 1024.
aa....aa: Processing subject
{ table |index }
bbbb: Maximum number of duplicates-exclusion RDAREAs (512)
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:
01: The DEFAULT clause and WITH DEFAULT cannot be specified simultaneously.
02: The DEFAULT clause cannot be specified in a repetition 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
07: USER 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 with a data type other than TIME or CHAR(8).
10: NULL cannot be specified in a column with a NOT NULL constraint.
12: A DEFAULT clause cannot be specified in columns or SQL variables of the following data types:
  • BLOB
  • Abstract data type
  • BINARY of 32,001 bytes or more
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).
31: DROP DEFAULT cannot be specified in a column with no DEFAULT clause specification.
32: WITH DEFAULT cannot be specified in a column with a DEFAULT clause specification.
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 }
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.

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 COUNT is displayed as the function, the number of data items subject to processing exceeded 2,147,483,647.
  • If SUM or AVG is displayed as the function, overflow occurred while adding data.
aa....aa: specified function:
{ SET |WINDOW }
bb....bb: the type of the set or window function:
{ SUM |AVG |COUNT }
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.

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.

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 a customer engineer.

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 a customer engineer.

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 a customer engineer.

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 the SQL statement
Unload the table, redefine the table in an RDAREA with sufficient page length, then reload the table.
When issued by the database load utility (pdload)
Use the database structure modification utility (pdmod) to re-initialize the RDAREA (change the page length), and then re-execute the command.

KFPA11810-E A

Duplicate key value detected in unique index while loading index index id=aa....aa

A duplicated key value was detected while loading an index for which UNIQUE is specified or an index for the primary key.
aa....aa: Index identifier
S: Invalidates this transaction.
P:
Delete the index, correct the duplicated key value, 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.

KFPA11811-E A

MASTER DIRECTORY RDAREA full

The master directory RDAREA does not have enough space for an RDAREA, table, index, or view 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 aaaaa exceeds bbbb in RDAREA "cc....cc"dd....dd

The number of specified table or index definitions 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).
aaaaa: Type of definition information:
{ TABLE |INDEX }
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 or index:
    Either define the table or index in another RDAREA or delete the defined table or 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:
    [Figure] 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.

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

aaaaaID not found in DIRECTORY data, RDAREA="bb....bb" ID=cc....cc

No definition information for the specified table, index, or list was found in RDAREA "bb....bb".
aaaaa: Table, index, or list type:
{ TABLE |INDEX |LIST }
bb....bb: RDAREA name
cc....cc: Table, index, or list number
S: Terminates abnormally.
Action
Take one of the following actions:
  • Table or index
    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 8 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

Environment group file access error occurred, file name=aa....aa, func=bb....bb, errno=cccc

Loading of environment variable group file aa....aa failed.
aa....aa: Environment variable group name (the last 100 bytes only if the file name is longer than 100 bytes)
bb....bb: Name of function in which error occurred:
fopen: Opening
fgets: Loading
stat: Status acquisition
cccc: 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. This error may occur when the size of 0-length data has not been added to the RDAREA size estimate.
aa....aa: Applicable RDAREA name
S: Ignores this SQL statement.
Action
To allocate sufficient data management area for the LOB RDAREA, re-estimate the applicable RDAREA and expand it.
For details of estimating the required RDAREA size, see the HiRDB Version 8 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.

KFPA11829-E A

Invalid use of ALIAS aa....aa."bb....bb"

The following error was detected in the specification of table alias aa....aa.bb....bb:
  • A table alias that was created based on a table at the local RD-node is specified.
aa....aa: Authorization identifier
bb....bb: Table alias
S: Ignores this SQL statement.
P: Correct the SQL statement and re-execute.

KFPA11836-E A

Specified tables must exist in same RDNODE

A table specified in an SQL statement must be a table in the same RD-node. Or, an index in the CREATE INDEX statement must be defined in the same RD-node as the table.
S: Ignores this SQL statement.
P: Correct the SQL statement and re-execute.

KFPA11838-E A

Unable to specify "aa....aa" in LOCK TABLE with "UNTIL DISCONNECT"

A table from another RD node, a foreign table, or a view table based on a foreign table cannot be specified in a LOCK statement specifying UNTIL DISCONNECT.
aa....aa: {table on other RDNODE|foreign table|view table derived from foreign table}
S: Ignores this SQL statement.
P: Correct the SQL statement and re-execute.

KFPA11839-E A

RDNODE name cannot be specified in table specification without specifying local RDNODE name

A table name qualified with an RD-node name cannot be specified because the RD-node name of the local node does not exist.
S: Ignores this SQL statement.
P: Delete the RD-node name from the table name specification. Or, ask the system administrator to set the RDAREA name of the local node in the system common definition, then re-execute.

KFPA11841-E A

Unable to nest remote access

During distributed database access, a distributed database access request was issued from HiRDB in the distributed server to another RD-node. A possible cause may be that a table alias identical to the table name in the SQL statement was defined in the HiRDB system on the distributed server side.
For a description of table aliases, see the HiRDB Version 8 SQL Reference.
S: Ignores this SQL statement; however, if a transaction was generated, executes rollback.
P:
Correct the UAP so that it accesses an RD-node containing a table to be manipulated.
If the distributed client is HiRDB, correct the RD-node name in the defective SQL statement or correct the definition of the table alias that is referenced in the defective SQL statement.

KFPA11842-E A

Unable to load shared libraries of aa....aa, inf=bb....bb

A shared library of a prerequisite program for the distributed database facility cannot be loaded.
aa....aa: Name of the prerequisite program or shared library
bb....bb: Maintenance information
S: Ignores this SQL statement.
Action
The following are possible causes:
  • The shared library of the related program does not exist.
  • The contents of the shared library of the related program are invalid.
  • The read or execution permission of the related program was rejected.
  • Memory space is insufficient for loading the shared library of the related program.
Check whether the related program has been installed correctly.
If the program is not installed correctly:
Terminate the UAP, install the program, then re-execute the UAP.
If the program is installed correctly:
Reduce the system workload, then re-execute the UAP.
If the error recurs:
Contact a customer engineer.

KFPA11843-E A

Unable to connect to DF/UX, reason code=aa....aa

The specified client function cannot be connected to DF/UX.
aa....aa: DF/UX reason code
S: Ignores this SQL statement.
P: Refer to the DF/UX reason code and take appropriate action. For information on the DF/UX reason codes, see the Distributed Database System DF/UX.

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.

KFPA11848-E A

Specified RDNODE not connected

RD-node specified in the DISCONNECT statement with RD-node specified or in the SET CONNECTION statement has not been connected.
S: Ignores this SQL statement.
P: Check the RD-node name for any error. If the specified RD-node name is correct, check the program and modify it as follows:
DISCONNECT statement with RD-node specified:
Delete any unneeded DISCONNECT statements with RD-node specified.
SET CONNECTION statement:
Issue the CONNECT statement with the correct RD-node specified before issuing the SET CONNECTION statement.

SQLCODE=-849

There is no HiRDB message for SQLCODE=-849

This SQLCODE has not been returned from a HiRDB in the distributed server. This SQLCODE indicates that an error occurred in DF/UX at an ORACLE distributed client.
DF/UX outputs a reason code indicating the cause of the error along with the SQLCODE code.
For details, see the manual Distributed Database System DF/UX.

KFPA11850-E A

SQLDA was modified after first blocked fetch

When the FETCH statement with batch retrieval specified is executed several times, the contents of the SQL data area specified in the FETCH statement parameter must not change.
S: Ignores this SQL statement.
P: Modify so that when the FETCH statement is executed several times with batch retrieval specified, the same SQL data area is used.

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
Take the following action:
  • CHARACTER SET NOT SUPPORTED or DF NOT SUPPORTED
The distributed database facility cannot be used, so delete it with the pd_node_name operand in the single server definition or front-end server definition.

KFPA11856-E A

Invalid number of variables from server system, reason code=aa

Because the retrieval result passed from the server system during remote access with batch retrieval is invalid, the specified processing cannot be executed.
aa: Reason code
S: Ignores this SQL statement.
Action
Check whether the system status allows connection to the server. Contact a customer engineer, if necessary.
The reason codes are explained below:
Reason code Explanation
00 The number of SQL DBL RESULT VALUES is 1 or less. Or, the number of SQL RESULT VALUES exceeds the repetitions count specified by the client
01 The number of SQL VALUES does not match the number of retrieval items that was specified by the client.
02 FETCH processing is not aborted even though an SQL error occurred in the server system during repeat processing.
03 The retrieval result is not returned even though SQLCODE=0 is returned from the server.

KFPA11857-E A

Data aa....aa of variable bb....bb is not supported in remote access

One of the following errors has occurred:
  • A data type not supported for remote access is specified in a variable in the SQL statement.
  • Either a data type or a data length not supported on the server-side system is specified.
  • A variable with a repetition structure is specified.
aa....aa: Error type
type: Data type not supported
length: Data length not supported
structure: Data structure (repetition structure) not supported
bb....bb: Ordinal number of the variable
S: Ignores this SQL statement.
P: Take one of the following actions:
  • Check the data type of the variable used in the SQL statement; specify a variable of the data type supported for remote access.
  • Specify either the data type or the data length that is supported by the server-side system.
  • Do not use variables of a repetition structure.

KFPA11858-E A

Unable to use aa....aa in remote access

aa....aa cannot be used in remote access.
aa....aa: WRITE specification
S: Ignores this SQL statement.
P: Correct the SQL statement and re-execute.

KFPA11860-E A

Negative SQLCODE received from server during remote access, SQLCODE=aa....aa, SQLSTATE=bb....bb, server=cc....cc, process ID= dd....dd, connection ID=ee....ee, RMID=ff....ff

Negative SQL code was returned from a distributed server's system or a distributed client's DF/UX Extension during remote database access.
aa....aa:
SQL code returned from distributed server's system or distributed client's DF/UX Extension. In the case of SQLCODE returned from a distributed server's system, the meaning depends on the server system.
bb....bb:
SQLSTATE returned from distributed server's system or distributed client's DF/UX Extension. In the case of SQLSTATE returned from a distributed server's system, the meaning depends on the server system.
cc....cc:
Character string indicating the DBMS type of the distributed server (the actual character string is set by the distributed server's system; if it cannot be displayed, one asterisk (*) is displayed)
dd....dd:
Process ID of the single server or front-end server
ee....ee:
ID of connection between HiRDB and DF/UX (if this information cannot be displayed, one asterisk (*) is displayed)
ff....ff:
RMID passed from HiRDB to DF/UX (if this information cannot be displayed, one asterisk (*) is displayed)
S: Ignores this SQL statement.
O: Confirm whether the SQLCODE was set by DF/UX Extension.
SQLCODE set by DF/UX Extension:
Resolve the error, and then re-execute the UAP.
SQLCODE not set by DF/UX Extension:
Eliminate the cause of the error by referencing the distributed server's system manuals and re-execute.

KFPA11861-E A

Negative SQLCODE received from server during remote access, SQLCODE=aa....aa, error text=bb....bb

A negative SQL code was returned from the server system during remote access.
aa....aa:
SQL code or SQLCODE returned from the server system; the meaning conforms to the server system.
bb....bb:
Error text that supplements the contents of the SQL code (the contents are set by the server system):
Error text not output:
The asterisk (*) is displayed.
Number of characters exceeds 104:
One number sign (#) is output after the 104th character.
When the server system is HiRDB, variable parts may be included in the message. If the message includes several variable parts, they are displayed in the format variable-part-1, variable-part-2, .... For an XDM/RD server system, assign the following information.
SQLERRMC:
Detailed information (XDM/RD SQLCA information) that corresponds to the return code from XDM/RD.
S: Ignores this SQL statement.
O: Refer to the contents of SQLCAIDE in the SQL Communications Area (SQLDA) to check the server system type. Refer to the SQL code in the appropriate server system manual to eliminate the cause of the error, then re-execute.

KFPA11862-E A

Remote access error occurred, OSI-RDA service code=aaa, reason code=bbb, text=cc....cc, process ID=dd....dd, connection ID=ee....ee, RMID=ff....ff

An RDA error occurred during OSI-RDA remote access.
aaa: RDA service code:
Service code RDA service resulting in the error
0 R-initialize
1 R-Terminate
2 R-Begin Transaction
3 R-Commit
4 R-Rollback
5 R-Cancel
6 R-Status
7 R-Open
8 R-Close
9 R-ExecuteDBL
10 R-DefineDBL
11 R-InvokeDBL
12 R-DropDBL
bbb: Reason code
Following are the reason codes:
Reason code Explanation
0 Access Control Violation
1 Bad Repetition Count
2 Command Handle Unknown
3 Control Authentication Failure
4 Control Service Not Allowed
5 Data Resource Already Open
6 Data Resource Handle Not Specified
7 Data Resource Handle Unknown
8 Data resource Name Not Specified
9 Data Resource Not Available
10 Data Resource Unknown
11 Dialogue ID Unknown
12 Duplicate Command Handle
13 Duplicate Data Resource Handle
14 Duplicate Dialogue ID
15 Duplicate Operation ID
16 Invalid Sequence
17 No Data Resource Available
18 Operation Aborted
19 Operation cancelled
20 Service Not Negotiated
21 Transaction Rolled Back
22 User Authentication Failure
23 Host Identifier Error
24 Invalid SQL Conformance Level
25 RDA Transaction Not Open
26 RDA Transaction Open
27 SQL Access Control Violation
28 SQL Database Resource Already Open
29 SQL DBA ArgumentCount Mismatch
30 SQL DBA Argument Type Mismatch
31 SQL DBA NO Char Set
32 SQL DBA Transaction Statement Not Allowed
33 SQL Usage Mode Violation
cc....cc: Variable part appropriate to reason code bbb:
No variable part:
The asterisk (*) is displayed.
Several variable parts:
Variable parts are displayed in the format variable-part-1, variable part 2.
Number of characters exceeds 75:
One number sign (#) is output after the 75th character.
Following are the message variable parts corresponding to the reason codes displayed as bbb:
Reason code Variable part 1 Variable part 2
5 RD-node name [Figure]
16 Invalid Sequence. This is supplemented by the codes shown below. If no code is output, the asterisk (*) is displayed instead.
1: dialogue Not Active
2: dialogue Initializing
3: dialogue Already Active
4: transaction Not Open
5: Transaction Open
6: transaction terminating
7: dialogue terminating		 [Figure]
9
18
21		 Indication of whether the error is temporary or permanent.
TRANSIENT: Temporary error
PERMANENT: Permanent error		 Diagnostic information (message providing additional information about the cause of the error) is output. The information is set by the server system. If no supplemental information item is output, the asterisk (*) is displayed instead.
Check the server manual as well.
Other * [Figure]
[Figure]: Not applicable
dd....dd: Process ID of single server or front-end server
ee....ee: Connection ID between HiRDB and DF/UX:
If the connection ID cannot be displayed, asterisks (*) are displayed.
ff....ff: RMID passed from HiRDB to DF/UX:
If the RMID cannot be displayed, asterisks (*) are displayed.
S: Ignores this SQL statement.
P: Take action appropriate to the reason code:
Reason code Action at HiRDB server Action at other server
21 The following message is set as diagnostic information:
HITACHI HiRDB MSGID=aa....aa, TEXT=bb....bb
aa....aa: HiRDB message ID
bb....bb: Variable part of the message (if there is no variable part in the message, the asterisk (*) is displayed instead)
Refer to the message indicated by MSGID and TEXT to eliminate the cause of the error. Or, contact the HiRDB administrator.		 Contact the HiRDB administrator. Server system is XDM/RD:
The following message is set as diagnostic information:HITACHI XDM/RD SQLICODE=aaaaa, SQLERRM=bb....bb
aaaaa: SQLICODE (return code (XDM/RD SQLIOA information) from XDM/RD)
bb....bb: SQLERRMC (detailed information (XDM/RD SQLCA information) corresponding to the return code from XDM/RD)
Server system is ORACLE:
The following information is set as diagnostic information:ORACLE SQLCODE=aa....aa bb....bb
aa....aa: SQLCODE of ORACLE
bb....bb: ORACLE error message (if the last character is the dollar sign ($), the error message text has been truncated)
22 Contact the HiRDB administrator. Because the authorization identifier or password specified in the server is not registered in the server system, either correct the authorization identifier or password or contact the HiRDB administrator to register the authorization identifier or password in the server system.
Other Contact the HiRDB administrator.
O: Take action appropriate to the reason code:
Reason code Action at HiRDB server Action at other server
9 Re-execute the UAP. When this message is displayed repeatedly, contact the HiRDB administrator. Contact the HiRDB administrator.
21 Refer to the diagnostic information and contact the programmer or HiRDB administrator.
22 Contact the programmer.
Other Contact the HiRDB administrator.
Action
Take action appropriate to the reason code:
Reason code Action at HiRDB server Action at other server
1 Zero or a negative value is specified as the number of repetitions. Contact a customer engineer. Contact a customer engineer.
21 Refer to the diagnostic information to check the cause of the error. Or, contact a customer engineer.
22 If necessary, request the server system administrator to register the authorization identifier and password.
Other Contact a customer engineer.

KFPA11863-E A

Specified application context in DF/UX not supported

Remote access by the application context specified by DF/UX is not supported.
S: Ignores this SQL statement.
Action
Change the application context DF/UX specifies into a supported context. For details of application contexts that can be specified by DF/UX, see the Distributed Database System DF/UX.

KFPA11864-E A

Error occurred in remote access, reason code=aaa, bb....bb

An error occurred during remote database access processing.
aaa: Reason code
bb....bb:
Detailed information for reason code aaa (if no detail information is available, an asterisk (*) is displayed)
Following are the reason codes and detail information:
Reason code Detail information Explanation
1 Maximum number of sections for DF/UX Extension The number of sections used with the UAP (number of SQL statements executed) exceeds the maximum number of sections for DF/UX Extension.
2 Maximum number of cursors for DF/UX Extension The number of cursors used with the UAP exceeds the maximum number of cursors for DF/UX Extension.
3 Required length of output area Shortage occurred in the output area.
S: Ignores this SQL statement.
P: Take action appropriate to the reason code:
Reason code Programmer's action
1 Reduce the number of sections used by the UAP and re-execute.
2 Reduce the number of cursors used by the UAP and re-execute.
3 The number of columns, type, or length of retrieval data may be invalid. Correct the error and re-execute.

KFPA11865-E A

Negotiation failed due to aa....aa

Because negotiation with the server system failed during remote access, remote access is disabled.
aa....aa: Reason remote access has been disabled:
  1. IMMEDIATE-DBL:
    The server system does not accept immediate execution DBL.
  2. INVALID SQLCONFORMANCE LEVEL:
    SQL CONFORMANCE LEVEL that is not supported by client HiRDB was returned.
  3. NO SQLCONFORMANCE LEVEL:
    No SQLCONFORMANCE LEVEL was returned.
  4. SQLCONFORMANCE LEVEL:
    Remote access was attempted again after error 2 or 3 had been returned.
  5. CHARSET NOT SUPPORTED (CLIENT):
    CHARSET (character codes) requested by the server cannot be used at the client.
  6. CHARSET NOT SUPPORTED (SERVER):
    CHARSET (character codes) requested by the client cannot be used at the server.
  7. CHARSET NOT SUPPORTED:
    Remote access was attempted again after error 5 or 6 had been returned.
S: Ignores this SQL statement.
O: Contact the HiRDB administrator.
Action
Check whether the server system can be connected with HiRDB.

KFPA11866-E A

Invalid data received from server system reason code=aaa, No=bb....bb, inf=cc....cc

Retrieval result returned from the server system during remote access is invalid.
aaa: Reason code:
Reason code Explanation
1 Data type of data returned from the server differs from data type requested by the client.
2 Number of data items returned from the server differs from the number of data items requested by the client.
3 Data type returned from the server is invalid.
4 Data value returned from the server is invalid.
5 Data length returned from the server is invalid.
6 Indicator variable value returned from the server is invalid.
7 Unsupported data type was returned from the server.
8 A data value outside the permissible range was returned from the server.
9 Data could not be found.
bb....bb: Column number of the output variable in which the error occurred (when the error code is 2, the number of data items returned from the server is displayed)
cc....cc: Maintenance information
S: Ignores this SQL statement.
Action
Check whether data in the server system can be retrieved.

KFPA11867-E A

Unable to execute specified SQL in remote access

The specified SQL statement cannot be executed in remote access for one of the following reasons:
  • The specified SQL is not supported for the distributed database facility.
  • One dynamic SELECT statement for specifying a query to another RD-node was opened by declaring or assigning several cursors.
  • A holdable cursor was used.
S: Ignores this SQL statement.
P:
Use an SQL statement that can be executed in remote access. Or, modify the UAP so that only one cursor can be declared or assigned for one dynamic SELECT statement.
If a holdable cursor was used, modify the UAP so that holdable cursor is not used.

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).
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
After executing batch index creation (pdrorg -k ixmk -t table-name control-information-file-name), re-execute the SQL statement in this transaction.

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 Multi-value column, index id=aa....aa

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.
aa....aa:
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:
Execution of a data manipulation SQL statement:
Check the data specified in the repetition column for which an index was defined to ensure that the number of duplicate elements per row does not exceed the value of the following formula:
Number of duplicate keys =
[Figure] ([Figure] page size of index-storage RDAREA [Figure] 0.95 [Figure]-82) [Figure] 4[Figure] - 1
O:
Execution of CREATE INDEX or batch creation of index:
Check the data specified in the repetition column for which an attempt to define an index was made to ensure that the number of duplicate elements per row does not exceed the value determined by the following formula:
Number of duplicate keys =
[Figure] ([Figure] page size of index-storage RDAREA [Figure] 0.95 [Figure] - 82) [Figure]4[Figure] - 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
Notify a customer engineer.

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.

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 view 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 view 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
AUTHORIZATION
ANY
PRIVILEGE GRANT
REVOKE
ANY
DEFINITION CREATE
DROP
ALTER
ANY
ACCESS SELECT
INSERT
UPDATE
DELETE
PURGE
ASSIGN
CALL
LOCK
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
AUTHORIZATION
ANY
PRIVILEGE GRANT
REVOKE
ANY
DEFINITION CREATE
DROP
ALTER
ANY
ACCESS SELECT
INSERT
UPDATE
DELETE
PURGE
ASSIGN
CALL
LOCK
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

The work area for exclusive control is insufficient.
S: Ignores this SQL statement, or aborts utility handling.
P:
If this error occurs when SQL is being executed:
(1) Check the current resource lock status, wait until the load becomes low, and then re-execute.
(2) When an error similar to (1) occurs:
If the PDLOCKLIMIT client environment definition is specified, increase the specification value for the permissible range.
Alternatively, re-execute this SQL statement without setting a value.
If this error message recurs in this situation, take action (3).
(3) Re-evaluate the program from the following viewpoints:
  1. Investigate whether the LOCK statement can be specified. Specify EXCLUSIVE if this is an update SQL statement.
  2. Investigate if WITHOUT LOCK NOWAIT can be specified. If the program can be modified, modify it, and then re-execute it. Otherwise, contact the HiRDB administrator.
If this error occurs when pdload, pdrorg, or pdrbal is executed:
(1) Check the current resource lock status, wait until the load becomes low, and then re-execute.
(2) If this error occurs even when the load is low, a table for managing locked resources that is large enough for the utility to handle the applicable table cannot be secured. Request the HiRDB administrator to increase the specification value of the pd_lck_pool_size operand or the pd_lck_until_disconnect_cnt operand. For specification values, see the section on locked resources required for each server when executing the database load utility or the section on locked resources required for each server when executing the database reorganization utility in the manual HiRDB Version 8 Command Reference.
Action
Take action according to the KFPS00443-I or KFPS00444-I message that is output to the event log (in UNIX, syslogfile) or message log file.
If the KFPS00443-I or KFPS00444-I message is not output, there are insufficient table locked resources. Increase the specification value of the pd_max_access_tables operand in the system common definition and start HiRDB.

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 a customer engineer.

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.

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 a customer engineer.

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.
P: 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 than the value of the pd_max_access_tables operand (number of concurrently accessible tables) specified in the system common definition.
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. Or, the starting server count 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:
  1. If you can increase the SDS or FES maximum start process count (can be checked using the pdchprc command), set a value that is greater than or equal to the total number of UAPs, utilities, and discrepancies application processing processes that can be executed simultaneously.
    Note
    To calculate the total number of discrepancies application processing processes:

    [Figure]

    n: Number of simultaneous executions of the pdorend command
  2. Take the following actions when the maximum number of SDS or FES start processes is less than the total number of UAPs, utilities, and discrepancies operation processing 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 discrepancies process multiplicity (value the -m option specifies) 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 a customer engineer.

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 8 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.
  • If bb....bb is "PARTITIONED BY MULTIDIM", the matrix partitioning table cannot be defined because HiRDB Advanced Partitioning Option is not embedded.
  • If process bb....bb is routine using foreign table, the routine defined in the foreign table cannot be invoked because HiRDB External Data Access is not embedded.
aa....aa: {specify}{use}{invoke}
bb....bb: {"PARTITIONED BY MULTIDIM"
|"ALTER TABLE CHANGE RDAREA" statement
|"CREATE SERVER" statement
|"DROP SERVER" statement
|"CREATE FOREIGN TABLE" statement
|"DROP FOREIGN TABLE" statement
|"CREATE FOREIGN INDEX" statement
|"DROP FOREIGN INDEX" statement
|"CREATE USER MAPPING" statement
|"DROP USER MAPPING" statement}
{foreign table}
{routine using foreign table}
cc....cc: {External Data Access|Advanced Partitioning Option}
S: Ignores this SQL statement.
P: Delete this SQL statement. Alternatively, embed the cc....cc option (HiRDB External Data Access, or HiRDB Advance Partitioning Option), and then re-execute this SQL statement.

KFPA11950-E A

Unable to aa....aa due to using bb....bb without cc....cc

When cc....cc is directory server:
aa....aa that uses bb....bb cannot be executed because it is not linked to the Directory Server.
When cc....cc is External Data Access:
aa....aa that uses bb....bb cannot be executed because HiRDB External Data Access is not embedded.
aa....aa: {drop schema|grant access|revoke access}
bb....bb: {group|foreign table}
cc....cc: {directory server|External Data Access}
S: Ignores this SQL statement.
P: Take one of the following actions:
  • When cc....cc is directory server:
    Link to the Directory Server and re-execute the SQL statement.
  • When cc....cc is External Data Access:
    Delete this SQL statement. Alternatively, embed HiRDB External Data Access and re-execute this SQL statement.

KFPA11952-E A

Unable to aa....aa due to insufficient bb....bb

An attempt was made to perform either of the following processing tasks in excess of the value defined in aa....aa:
  • List creation
  • Foreign server definition
aa....aa: { assign LIST |create server }
bb....bb: defined-operand-name
{ pd_max_list_users |pd_max_list_count |pd_max_foreign_server}
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.
When bb....bb is pd_max_foreign_server:
Delete this SQL statement because it cannot be executed.
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_buf_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_buf_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 process (in kilobytes).
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.
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.
During server startup:
Use the pdwork operand in the server definition to specify a HiRDB file system area for storing a work table, and restart 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.
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: Correct the error based on the SQL code for the processing underway when the error occurred and on the error log trace information (pderr process-number-*.trc), and re-execute.

KFPA11970-E A

Invalid SQL, code=aa, SQL="bb....bb"

A specified SQL statement in OSI-RDA remote access is invalid.
aa: Reason code:
01: An SQL statement that cannot be executed in OSI-RDA remote access is specified.
02: An SQL statement that cannot be executed in OSI-RDA remote access is specified in the PREPARE statement.
03: The length of an SQL statement is 0.
04: The length of an SQL statement exceeds 20,000.
05: A syntax error was detected in characters or a keyword.
06: An SQL statement that cannot be executed in OSI-RDA remote access is specified in the EXECUTE IMMEDIATE statement.
bb....bb:
SQL statement resulting in the error. However, this SQL statement does not always match the SQL statement issued by the UAP because the system at the distributed client or distributed server sometimes changes the SQL statement. When the reason code is 03 or 04, bb....bb is omitted.
S: Ignores this SQL statement.
P: Correct the error in the UAP at the distributed client and re-execute.

KFPA11971-E A

Invalid identifier in SQL, code=aa

The cursor name or SQL statement identifier in an SQL statement in OSI-RDA remote access is invalid.
aa: Reason code:
01: The format of a cursor name in an SQL statement is incorrect.
02: The format of an SQL statement identifier in an SQL statement is incorrect.
03: The number of cursor names exceeds 1,024.
04: The total number of cursors specified directly in DECLARE CURSOR statements and SQL statement identifiers exceeds 4,095.
05: A cursor name that was not declared was used to specify an SQL statement to be executed.
06: An SQL statement identifier that was not declared was used to specify an SQL statement to be executed.
07: A cursor name that is already declared for another cursor is specified in a DECLARE CURSOR statement.
08: An SQL statement identifier that is already in use for another cursor is specified in a DECLARE CURSOR statement.
S: Ignores this SQL statement.
P: Correct the error in the UAP at the distributed client and re-execute.

KFPA11972-E A

Inconvertible data for aa....aa variable bb....bb of data type cc....cc

Conversion of a variable value at the RDA server is disabled in OSI-RDA remote access for the following reason:
  • When data type is REAL or DOUBLE PRECISION, overflow occurred.
  • When data type is DATE, value is not in YYYY-MM-DD format.
aa....aa: Segment of the input or output variable
{ input|output }
bb....bb: Sequence number of the input or output variable
cc....cc: Data type
S: Ignores this SQL statement.
P: Check the contents shown below and take appropriate action:
Data type Explanation
REAL Correct the UAP so that the data type of the variable for receiving the result value is DOUBLE PRECISION, then re-execute.
DOUBLE PRECISION This result value cannot be received in OSI-RDA remote access.
DATE Correct the error in the UAP at the distributed client and re-execute.

KFPA11973-E A

Invalid data type of aa....aa variable bb....bb

A data type that cannot be specified in a variable is specified in OSI-RDA remote access. Or, the data length is incorrect.
aa....aa: Segment of the input or output variable
{ input | output }
bb....bb: Sequence number of the input or output variable
S: Ignores this SQL statement.
P: Correct the error in the UAP at the distributed client and re-execute.

KFPA11974-E A

Unexecutable request, code=aa

The specified SQL statement cannot be processed because an error was found in the service parameter of R-Execute-DBL during OSI-RDA remote access.
aa: Reason Code
01: A value greater that 1 is specified as the repeats count in the execution request for an SQL statement other than FETCH.
02: List of arguments is specified.
03: Charset object identifier specified at R-open or R-Execute-DBL is not supported.
04: Argument specification is made in an SQL statement that cannot have an argument specification.
05: Result specification is made in an SQL statement with no result value.
06: Result specification is not made in an SQL statement that requires a result value.
S: Ignores this SQL statement.
P: Contact the HiRDB administrator.
Action
Contact a customer engineer.

KFPA11975-E A

Invalid "DESCRIBE" statement

One of the following errors occurred in the DESCRIBE statement in OSI-RDA remote access:
  • The SQLNAME request is incorrect.
  • The SQLN value is the null value.
  • The argument specification or result specification is invalid.
S: Ignores this SQL statement.
P: If SQLN (maximum number of retrieval columns) was not specified in the distributed client UAP, correct the UAP and re-execute. If SQLN was specified, contact the HiRDB administrator.
Action
Contact a customer engineer.

KFPA11976-E A

More than 30000 variables

The specified SQL statement cannot be processed because the number of variables is too large for OSI-RDA remote access.
S: Ignores this SQL statement.
P: Correct the error in the UAP at the distributed client and re-execute.

KFPA11977-E A

Number of variables not equal to number of retrieval-columns

The number of columns in the retrieval result does not match the number of variables for receiving that retrieval result in OSI-RDA remote access.
S: Ignores this SQL statement.
P: Correct the error in the UAP at the distributed client and re-execute.

KFPA11980-E A

Transaction branch already determined

This transaction branch already accepted a determination request from another transaction branch and has been determined.
S: Ignores this SQL statement.
P: SQL cannot be executed in this transaction branch. Terminate the transaction branch.
O: Inasmuch as a determination 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 receiver 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 set in the pd_max_dic_process or pd_max_bes_process operand. 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 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 a customer engineer.

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 a customer engineer.

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
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 the KFPS00900-I or KFPS00972-I message 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
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 length too short for HASH function

The input data length of a partitioning column for the hash function specified in the table definition is too short.
S: Ignores this SQL statement.
P:
Check whether the data length to be input satisfies the partitioning key condition of the hash function specified in the table definition. If it is incorrect, correct the input data table definition. Or, check whether the hash function specified in the table definition is correct. If it is incorrect, correct the table definition.

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.

KFPA11997-E

Error occurred during execution of PLUGIN function, "aa....aa"

An error occurred during the execution of the plug-in (implementation) function.
aa....aa: Detailed error message
S: Either ignores this SQL statement or invalidates the transaction.
P: Resolve the problem identified in the detailed error message by referring to the corresponding plug-in manual and re-execute.

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.

KFPA12601-I A

Positive SQLCODE other than +100 received from server, SQLCODE=aa....aa

A positive SQL code other than +100 was returned from the server in remote access.
aa....aa: L code returned from the server system
S: Resumes processing.
O: Refer to the contents of SQLCAIDE in the SQL Communications Area (SQLCA) to check the server system type. Refer to the appropriate server system manual to check the SQL code.

KFPA12603-I A

Retrieved string data length is 0, the data is converted to a blank

Character string, national character string, or mixed character string data with a real length of 0 was retrieved during remote access. This data was converted to one space because the distributed client does not support character string, national character string, or mixed character string data with a real length of 0.
S: Resumes processing.
P: If it is not acceptable for UAP processing to convert the character string, national character string, or mixed character string data with a real length of 0 to one space, change the search condition in such a manner that data with a real length of 0 is not retrieved.

KFPA12900-W A+L

Warning occurred in foreign server aa....aa (b), SQLCODE=cc....cc, inf=dd....dd

A warning was returned from a foreign server when the HiRDB External Data Access facility was being used.
aa....aa: Foreign server name
b: Server type:
P: HiRDB
R: XDM/RD E2
O: ORACLE
I: DB2
cc....cc: SQLCODE returned from the foreign server
dd....dd: The message returned from the foreign server
When the message is 76 characters or more in length, two periods (..) are added to the 74th character when the message is output. Where there is no message, asterisks (*) are displayed.
S: Continues the process.
P: Check the server type of the foreign server and refer to the SQLCODE and warning message based on the applicable DBMS manual. When dd....dd is *, check the SQL contact area from SQLWARN0 to SQLWARNF. When W is set to SQLWARND, re-evaluate the foreign table definition, because the column length defined by the foreign table definition may be longer than a column in the real table.

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.

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.

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.

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.

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:
    [Figure] A value expression that includes a column specification
    [Figure] 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.

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.

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.

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
  • Repetition column
  • Embedded variable or ? parameter
  • USER
  • CURRENT DATE or CURRENT_DATE
  • CURRENT TIME or CURRENT_TIME
  • CURRENT TIMESTAMP or CURRENT_TIMESTAMP
  • 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 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
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
aa....aa: Error causing conditions:
{ subquery| 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 }
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.

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-32,767 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 32,767 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 base table.
cc....cc: {view table|foreign table|ALIAS}
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 or an abstract data type 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.
18 Foreign table in triggered SQL statement The name of a foreign table cannot be specified in the trigger SQL statement.
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.
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:
Java 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:
Correct so that the Java routine is not executed from inside the trigger, and then re-execute.

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:
  1. 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
  2. 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
  3. 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, a HAVING clause, or a set function
    • Window function
    • Joined table
  4. 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
  5. 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.
  6. 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
  7. 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.
  8. 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
  9. 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
  10. 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:
      [Figure] Table join
      [Figure] GROUP BY clause, HAVING clause, or a set function
      [Figure] SELECT DISTINCT
      [Figure] A value expression in a selection expression other than a column specification
      [Figure] A query that creates an inner derived table
      [Figure] 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:
      [Figure] A named derived table derived by specifying the joining of tables
      [Figure] A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
      [Figure] A named derived table derived by specifying SELECT DISTINCT
      [Figure] A named derived table derived by specifying a value expression other than a column specification in a selection expression
      [Figure] A named derived table derived by specifying a query that creates an inner derived table
      [Figure] 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 [Figure] 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:
  1. 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
  2. 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
  3. 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
  4. 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
  5. 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.
  6. 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
  7. 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.
  8. 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
  9. 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
  10. 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:
      [Figure] Table join
      [Figure] GROUP BY clause, HAVING clause, or a set function
      [Figure] SELECT DISTINCT
      [Figure] A value expression in a selection expression other than a column specification
      [Figure] A query that creates an inner derived table
      [Figure] 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:
      [Figure] A named derived table derived by specifying the joining of tables
      [Figure] A named derived table derived by specifying a GROUP BY clause, a HAVING clause, or a set function
      [Figure] A named derived table derived by specifying SELECT DISTINCT
      [Figure] A named derived table derived by specifying a value expression other than a column specification in a selection expression
      [Figure] A named derived table derived by specifying a query that creates an inner derived table
      [Figure] 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 [Figure] 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 8 Installation and Design Guide.

KFPA19458-E A

Unable to execute aa....aa statement using foreign table due to bb....bb

Unable to execute the aa....aa statement specifying a foreign table because it contains bb....bb.
aa....aa: {INSERT|UPDATE|DELETE}
bb....bb: Error information
The table below summarizes the contents of the error information.
  • The following items represent a syntax that cannot be executed on the foreign server:
    Error information Explanation
    function invocation Function call or system-defined scalar function
    IS_USER_CONTAINED_IN_HDS_GROUP function IS_USER_CONTAINED_IN_HDS_GROUP function
    HEX function HEX function
    TIMESTAMP function TIMESTAMP function
    TIMESTAMP_FORMAT function TIMESTAMP_FORMAT function
    BIT_AND_TEST function BIT_AND_TEST function
    VARCHAR_FORMAT function VARCHAR_FORMAT function
    DATE function with datetime format DATE function specifying a date format
    TIME function with datetime format TIME function specifying a time format
    POSITION function POSITION function
    Row value constructor with more than two elements Row value constructor with two or more row value constructor elements
    Right-hand side of "IN" predicate not value specification Among the IN predicates, one that has a non-specified row value constructor on the right-hand side
    CAST specification CAST specification
    SIMILAR predicate SIMILAR predicate
    Internal derived table generated for underlying table of derived table Given a query specification specifying a viewed table, a query name with a WITH clause, or a derived table; if, in the viewed table definition, a viewed table, a WITH clause, or a derived table that, in turn, becomes an inner derived table is specified in the derived table specified in a derived query expression in the WITH clause or in the FROM clause, the former query specification
  • If any of the following items is specified in a selection expression, the selection expression will represent a syntax that cannot be executed on the foreign server:
    Error information Explanation
    {embedded-variable, SQL-parameter, or SQL-variable|USER|CURRENT_DATE|CURRENT_TIME|CURRENT_TIMESTAMP} in select expression [Figure] Embedded variable, SQL parameter, or SQL variable
    [Figure] USER
    [Figure] CURRENT_DATE
    [Figure] CURRENT_TIME
    [Figure] CURRENT_TIMESTAMP
  • If any of the following items is coded in an arithmetic operation, a date operation, a concatenation operation, a scalar function, or a CASE expression, the item will represent a syntax that cannot be executed on the foreign server:
    Error information Explanation
    {embedded variable, ? parameter, SQL parameter, or SQL variable|USER}CURRENT_DATE|CURRENT_TIME|CURRENT_TIMESTAMP} in scalar operation [Figure] Embedded variable, ? parameter, SQL parameter, or SQL variable
    [Figure] USER
    [Figure] CURRENT_DATE
    [Figure] CURRENT_TIME
    [Figure] CURRENT_TIMESTAMP
  • A value expression, predicate, GROUP BY clause, ORDER BY clause, or a selection expression (containing a GROUP BY clause, an ORDER BY clause, DISTINCT, a set function, a HAVING clause, or a set operation) will represent a syntax that cannot be executed on the foreign server:
    Error information Explanation
    TIME_STAMP type Time stamp data type
    BINARY type Binary data type
  • The following items cannot be executed, because they are execution-disabled in the Hub optimization information definition on the foreign server. To execute these items, modify the Hub optimization information definition on the foreign server:
    Error information Explanation
    SET functions for pd_hub_opt_set_func Set function
    CASE expressions for pd_hub_opt_case CASE expression
    LIKE or XLIKE predicate for pd_hub_opt_like LIKE predicate, XLIKE predicate
    ABS function for pd_hub_opt_abs ABS function
    Column specification of DATE type, DATE function, or CHAR function with DATE argument for pd_hub_opt_date DATE-type column specification, scalar function DATE(), or a date type specified in CHAR()
    TIME or CHAR function with TIME argument for pd_hub_opt_time TIME or CHAR function with a time type specified
    DIGITS function for pd_hub_opt_digits DIGITS function
    LENGTH function for pd_hub_opt_length LENGTH function
    LOWER or UPPER functions for pd_hub_opt_lower_upper_type LOWER function, UPPER function
    MOD function for pd_hub_opt_mod_div_type MOD function
    Set function AVG for pd_hub_opt_mod_div_type Set function AVG
    Division operation for pd_hub_opt_mod_div_type Division
    SUBSTR function for pd_hub_opt_substr SUBSTR function
    DECIMAL, FLOAT, or INTEGER functions for pd_hub_opt_num DECIMAL function, FLOAT function, or INTEGER function involving a type conversion to a numeric data type
    Scalar functions for extraction of date or time for pd_hub_opt_datetime Scalar function that extracts a date or time
    Date or time operations for pd_hub_opt_datetime_op Date or time operation
    Variable-length character string with possibility of including trailing space for pd_hub_opt_trailing_spc Variable-length character string containing a trailing space or with potential to contain the same
    Concatenation operation including column with NULLABLE option for pd_hub_opt_nullable Concatenation operation including the column, if YES is specified in the NULLABLE column option or if the NULLABLE column option is not specified
    Value specification with possibility of including 0-length character string for pd_hub_opt_use_zero_string 0-byte character string or a value specification with that possibility
    TIME type for pd_hub_opt_time_24hour TIME type
    FLOAT type for pd_hub_opt_float Value expression including the FLOAT type, predicate, GROUP BY clause, ORDER BY clause, or selection expression (with one of the following specifications: GROUP BY clause, ORDER BY clause, DISTINCT, set function, or HAVING clause)
    Number of nesting levels of a scalar operation or set function for pd_hub_opt_nest_scalar is too large. Exceeds the maximum number of nesting levels for scalar operations or set functions
    Length of the result of a value expression of character type for pd_hub_opt_date_len is too long. Exceeds the maximum length for the result of a value expression involving a fixed-length character type, a fixed-length national character type, a variable-length national character type, a fixed-length mixed character type, or a variable-length mixed character type.
    National character string except double-byte character for pd_hub_opt_nchar The character code set for the national character type on the foreign server is not a 2-byte fixed width, or the embedding character is not a 2-byte character space.
    Outer join for pd_hub_opt_on_cnd Outer join (LEFT OUTER JOIN)
    Table join for pd_hub_opt_joined_table Table joining
    Grouping for pd_hub_opt_grouping GROUP processing
    Number of tables in single SQL for pd_hub_opt_table_num is too large. The number of tables specified in the 1SQL statement is larger than the maximum value.
  • The following items cannot be executed on a foreign server:
    Error information Explanation
    Set operation Set operations
    Tables on different servers The table subject to row insertion, update, or deletion is a foreign table, and the server is specifying more than one different table.
    No selection of column derived from set function A set function is specified in a view definition or in a selection expression for a derived query expression in a WITH clause, and a column specification derived from the set function is not included in the selection expression in the query specification specified in the FROM clause in which the viewed table or the query name of the WITH clause is specified.
    Reference to neither column nor set function in query with HAVING A set function or GROUP BY clause is not specified, and a column is not specified in the selection expression in the query specification with HAVING.
    Duplication of underlying columns for grouping The same column is specified in a view definition or in the selection expression in a derived query in the WITH clause, and the column is specified in the GROUP clause in the query specification in which the viewed table or the query name of the WITH clause is specified in the FROM clause.
  • If any of the following items is coded in a comparison predicate operand that does not contain a column specification, the item will represent a syntax that cannot be executed on a foreign server:
    Error information Explanation
    {SQL parameter, or SQL variable|USER|CURRENT_DATE|CURRENT_TIME|CURRENT_TIMESTAMP} in comparison predicate without column [Figure] SQL parameter or SQL variable
    [Figure] USER
    [Figure] CURRENT_DATE
    [Figure] CURRENT_TIME
    [Figure] CURRENT_TIMESTAMP
S: Ignores this SQL statement.
P: Refer to the explanation given in the table, revise the SQL statement, and then re-execute the UAP.

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 one of the following actions to have extra available memory:
Reduce the number of concurrently executing processes.
Increase the swap area.
Increase real memory.
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 a customer engineer.
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 is executing, or the pdprgrenew command is executing. Therefore, transactions executing a stored procedure, ALTER PROCEDURE, ALTER ROUTINE, or ALTER TRIGGER cannot be started.
S: Ignores this SQL statement, or interrupts.
P: Once the pdchgconf or pdprgrenew command has been completed, 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.

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

Specify 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
aa....aa: RDAREA name
S: Ignores this SQL statement.
P: Specify an RDAREA that is not a shared RDAREA and re-execute.

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

With a referential constraint, from the same column set (the order need not be the same), the same referenced table primary key cannot be referenced.
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.

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.
02 same RDAREA The same RDAREA name was specified for all RDAREAs.
03 boundary values over The sum of specified boundary values exceeds 3,000.
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.
07 duplicated RDAREA exists in RDAREA LIST The same RDAREA name is specified multiple times in a matrix partitioning RDAREAs list.
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" If HASH0 was specified in a hash function, one of the following errors occurred:
  • CHAR(6), CHAR(8), DATE, or TIMESTAMP is not specified for the data type for the column specified for partitioning.
Multiple columns are specified in a partition 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.

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

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:
    • In an attempt to modify a row partition table in the server, the non-partitioning key index for the table is not row-partitioned.
    • In an attempt to modify a table not row-partitioned in the server, partition storage conditions are stored in the same RDAREA, and a non-partitioning key index is defined.
    A non-row-partitioned index is defined on the table to be modified. An attempt is being made to partition 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.

    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 1,024.
    • The total number of characters in the RDAREA name is greater than 3,000.
    • 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.
    • A row-partitioning index is not defined on the table to be modified. Therefore, you cannot perform combining that converts a row partition table to a non-partitioned table.
    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 modified boundary value partitioning or modified storage condition partitioning 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.
    • Duplicate RDAREAs was specified, but the boundary value partition specification after the change is different from the RDAREA name list that stores the indexes after the change or the RDAREA change specification that stores the LOB columns.
    • The position in which a new RDAREA is specified in modified boundary value partitioning or modified storage condition partitioning is different from the position specified in the modified index storage RDAREA name list or the LOB column storage RDAREA change specification.
    • The position in which an existing RDAREA is specified in modified boundary value partitioning or modified storage condition partitioning is different from the position specified in the modified index storage RDAREA name list or the LOB column 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.
    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 When an attempt was made to modify partitioning storage conditions, an RDAREA was specified incorrectly. If a boundary value was specified, identify the error by referring to the table [Figure] 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 [Figure] Cause of an RDAREA specification error when modifying partitioning storage conditions (storage condition specification) following this table.
    15 FOR COLUMN clause invalid There is an error in the specified column.
    • It is not a BLOB 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.
    99 User data type or matrix table The partition storage conditions of the following partitioning tables cannot be changed:
    • Row partitioned tables used for abstract data type columns
    • Matrix partitioned tables
[Figure] 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.
[Figure] 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 [Figure] 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.
[Figure] Invalid combination between an RDAREA information list before change and a storage condition partitioning specification after change
RDAREA 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

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.

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.
  • When using the directory server linkage facility, the user is not registered in the directory server.
  • If this message is output during table access, the user information in the directory server from the time the user connected to HiRDB until the present time is deleted.
  • Ask a user with the DBA privilege to grant the CONNECT privilege, and re-execute.
  • When the directory server linkage facility is used, ask the system administrator to register the user in the directory server.

  • The specified password is incorrect.
  • When the directory server linkage facility is used, the specified password differs from the password registered in the directory server, or the password has expired.
  • If this message is output during table access, the password user information in the directory server changed from the time the user connected to HiRDB until the present time, or the password expired.
  • If this message is output during connection to HiRDB, specify a valid password and re-execute.
  • If the password registered in the directory server has expired, reset the password in the directory server and re-execute.
  • If this message is output during table access, release the connection to HiRDB, and then specify the authorization identifier and password currently in the directory server. Then, restart HiRDB and re-execute.
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, remove the cause 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.
08 Using directory server This cannot be executed when the directory server linkage facility is used.

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 8 System Operation Guide.

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
AUTHORIZATION
ANY
PRIVILEGE GRANT
REVOKE
ANY
DEFINITION CREATE
DROP
ALTER
ANY
ACCESS SELECT
INSERT
UPDATE
DELETE
PURGE
ASSIGN
CALL
LOCK
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 8 SQL Reference.

KFPA19681-E A

Unable to specify aa....aa."bb....bb" in PUBLIC VIEW definition

The following tables cannot be specified in a public view definition:
  • Base tables, view tables, or foreign tables of other users
  • Public view tables where the definer is another user
  • Base tables, view tables that use a view table or foreign table as the base table, or foreign tables where the owner is another user
  • View tables that use public view tables as the base table or foreign tables where the definer is another user
aa....aa: Authorization identifier
bb....bb: Table identifier of base table, view table, public view table, or foreign table
S: Ignores this SQL statement.
P: Revise the base table of the public view table.

KFPA19700-E A

HiRDB is under maintenance code=a

Either the pdchgconf command or the pdprgrenew command is currently running. 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.
When the client library is a version earlier than 07-00:
After the pdchgconf command or pdprgrenew command has finished, 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:
  1. If you are executing in a no-log environment, consider whether the client environment variable PDDBLOG can be changed to ALL.
  2. 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 Staticizer Option Version 7. Further, for details on updatable online reorganization commands, see the manual HiRDB Version 8 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 8 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.
f_expand_limit operand.

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 HiRDB administrator, remove 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.

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 HiRDB administrator.
Action
Take the action appropriate for the error code.
Error 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.

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, remove 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: UTF8 code
UNKNOWN: Unsupported character code
bb....bb: Specification value in the client environment variable PDCLTCNVMODE
UCS2_UTF8
UCS2_UJIS
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.

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 HiRDB administrator.
Action
Contact a customer engineer.

KFPA20003-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
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 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 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 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, # 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.

KFPA20008-W L

External Data Access optimization definition file not found, foreign server=aa....aa

The hub optimization information definition file corresponding to foreign server aa....aa could not be found. The default value has been assumed for all operands specified in the hub optimization information definition file of the applicable foreign server.
aa....aa: Foreign server name
S: Terminates processing.
Action
When the hub optimization information definition file is specified:
Check the file name for errors.
When the hub optimization information definition file is not specified:
Because specifying a hub optimization information definition file when accessing the foreign server may improve performance, consider creating one of these files. HiRDB External Data Access Adapter of the applicable foreign server has a hub optimization information definition file containing the recommended values. Hitachi recommends using this hub optimization information definition file in its present form.

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)
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 8 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 pound sign (#) 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:
    [Figure] Re-evaluate whether exclusive contention is occurring.
    [Figure] Re-evaluate whether a network failure occurred.
    [Figure] Fine tune the SQL code.
    [Figure] Increase the specification value of the PDCWAITTIME operand.
    [Figure] 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 8 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.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2007, Hitachi, Ltd.