Hitachi Advanced Database Messages

3000-6-505-T0(E)

Notices

Relevant program products

P-8862-CG12 Hitachi Advanced Database version 06-01 (for Red Hat Enterprise Linux Server 9 (64-bit x86_64), and Red Hat Enterprise Linux Server 10 (64-bit x86_64))

P-8862-CN12 Hitachi Advanced Database Client version 06-01 (for Red Hat Enterprise Linux Server 9 (64-bit x86_64), and Red Hat Enterprise Linux Server 10 (64-bit x86_64))

P-2W62-C117 Hitachi Advanced Database Client version 06-01 (for Windows 10, Windows 11, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 2022, and Windows Server 2025)

This manual can be used for products other than the products shown above. For details, see the Release Notes.

Trademarks

Company and product names mentioned in this document may be the trademarks of their respective owners.

1. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)

2. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

3. This product includes software written by Tim Hudson (tjh@cryptsoft.com).

4. This product uses OpenSSL Toolkit software in accordance with the OpenSSL License and Original SSLeay License, which are described as follows.

LICENSE ISSUES

==============

The OpenSSL toolkit stays under a double license, i.e. both the conditions of

the OpenSSL License and the original SSLeay license apply to the toolkit.

See below for the actual license texts.

OpenSSL License

---------------

/* ====================================================================

* Copyright (c) 1998-2019 The OpenSSL Project. All rights reserved.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

*

* 1. Redistributions of source code must retain the above copyright

* notice, this list of conditions and the following disclaimer.

*

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in

* the documentation and/or other materials provided with the

* distribution.

*

* 3. All advertising materials mentioning features or use of this

* software must display the following acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

*

* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to

* endorse or promote products derived from this software without

* prior written permission. For written permission, please contact

* openssl-core@openssl.org.

*

* 5. Products derived from this software may not be called "OpenSSL"

* nor may "OpenSSL" appear in their names without prior written

* permission of the OpenSSL Project.

*

* 6. Redistributions of any form whatsoever must retain the following

* acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit (http://www.openssl.org/)"

*

* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR

* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

* OF THE POSSIBILITY OF SUCH DAMAGE.

* ====================================================================

*

* This product includes cryptographic software written by Eric Young

* (eay@cryptsoft.com). This product includes software written by Tim

* Hudson (tjh@cryptsoft.com).

*

*/

Original SSLeay License

-----------------------

/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)

* All rights reserved.

*

* This package is an SSL implementation written

* by Eric Young (eay@cryptsoft.com).

* The implementation was written so as to conform with Netscapes SSL.

*

* This library is free for commercial and non-commercial use as long as

* the following conditions are aheared to. The following conditions

* apply to all code found in this distribution, be it the RC4, RSA,

* lhash, DES, etc., code; not just the SSL code. The SSL documentation

* included with this distribution is covered by the same copyright terms

* except that the holder is Tim Hudson (tjh@cryptsoft.com).

*

* Copyright remains Eric Young's, and as such any Copyright notices in

* the code are not to be removed.

* If this package is used in a product, Eric Young should be given attribution

* as the author of the parts of the library used.

* This can be in the form of a textual message at program startup or

* in documentation (online or textual) provided with the package.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in the

* documentation and/or other materials provided with the distribution.

* 3. All advertising materials mentioning features or use of this software

* must display the following acknowledgement:

* "This product includes cryptographic software written by

* Eric Young (eay@cryptsoft.com)"

* The word 'cryptographic' can be left out if the rouines from the library

* being used are not cryptographic related :-).

* 4. If you include any Windows specific code (or a derivative thereof) from

* the apps directory (application code) you must include an acknowledgement:

* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"

*

* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND

* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE

* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

* SUCH DAMAGE.

*

* The licence and distribution terms for any publically available version or

* derivative of this code cannot be changed. i.e. this code cannot simply be

* copied and put under another distribution licence

* [including the GNU Public Licence.]

*/

■Double precision SIMD-oriented Fast Mersenne Twister (dSFMT)

Copyright (c) 2007, 2008, 2009 Mutsuo Saito, Makoto Matsumoto

and Hiroshima University.

Copyright (c) 2011, 2002 Mutsuo Saito, Makoto Matsumoto, Hiroshima

University and The University of Tokyo.

All rights reserved.

Redistribution and use in source and binary forms, with or without

modification, are permitted provided that the following conditions are

met:

* Redistributions of source code must retain the above copyright

notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above

copyright notice, this list of conditions and the following

disclaimer in the documentation and/or other materials provided

with the distribution.

* Neither the name of the Hiroshima University nor the names of

its contributors may be used to endorse or promote products

derived from this software without specific prior written

permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS

"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT

LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR

A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT

OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT

LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,

DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY

THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE

OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Microsoft product screen shots

Microsoft product screen shots reprinted with permission from Microsoft Corporation.

Microsoft product name abbreviations

This manual uses the following abbreviations for Microsoft product names:

Abbreviation

Full name or meaning

Azure

Microsoft Azure

Windows

Windows 10

Windows 10 x86

Windows(R) 10 Pro (32-bit)

Windows(R) 10 Enterprise (32-bit)

Windows 10 x64

Windows(R) 10 Pro (64-bit)

Windows(R) 10 Enterprise (64-bit)

Windows 11

Windows(R) 11 Pro

Windows(R) Enterprise

Windows Server 2012

Windows Server(R) 2012 Standard

Windows Server(R) 2012 Datacenter

Windows Server 2012 R2

Windows Server(R) 2012 R2 Standard

Windows Server(R) 2012 R2 Datacenter

Windows Server 2016

Windows Server(R) 2016 Standard

Windows Server(R) 2016 Datacenter

Windows Server 2019

Windows Server(R) 2019 Standard

Windows Server(R) 2019 Datacenter

Windows Server 2022

Windows Server(R) 2022 Standard

Windows Server(R) 2022 Datacenter

Windows Server 2025

Windows Server(R) 2025 Standard

Windows Server(R) 2025 Datacenter

Restrictions

Information in this document is subject to change without notice and does not represent a commitment on the part of Hitachi. The software described in this manual is furnished according to a license agreement with Hitachi. The license agreement contains all of the terms and conditions governing your use of the software and documentation, including all warranty rights, limitations of liability, and disclaimers of warranty.

Material contained in this document may describe Hitachi products not available or features not available in your country.

No part of this material may be reproduced in any form or by any means without permission in writing from the publisher.

About the translation of this manual

Some parts of this manual were created by using AI translation.

Issued

Jan. 2026

Copyright

All Rights Reserved. Copyright (C) 2012, 2026, Hitachi, Ltd.

Preface

This manual describes the messages output by Hitachi Advanced Database.

Note that, in this manual, and in the information output by the product (messages, command output results, and so on), HADB is often used in place of Hitachi Advanced Database.

Intended readers

This manual is intended for:

System engineers who design and set up HADB systems, and system administrators

Application developers

Readers of this manual must have:

A basic knowledge of Linux or Windows system management

A basic knowledge of RDBMS operation management

A basic knowledge of SQL

Organization of this manual

This manual is organized into the following chapters:

1. Message Format and Output Locations

Chapter 1 explains the locations to which HADB outputs messages. It also explains the format in which messages are output, how to interpret them, the relationship between message IDs and SQLCODEs, and query position numbers.

2. Messages

Chapter 2 lists the messages that HADB outputs, and explains their meanings and the corrective action to take in response to each message.

3. Output Codes

Chapter 3 lists the abort codes that HADB outputs, and explains their meanings and the corrective action to take in response to each abort code.

4. SQLSTATE Values

Chapter 4 explains the SQLSTATE values that HADB outputs.

Related publications

This manual is part of a related set of manuals. The manuals in the set are listed below (with the manual numbers):

Hitachi Advanced Database Setup and Operation Guide (3000-6-501(E))

Hitachi Advanced Database Application Development Guide (3000-6-502(E))

Hitachi Advanced Database Command Reference (3000-6-503(E))

Hitachi Advanced Database SQL Reference (3000-6-504(E))

Hitachi Code Converter (for UNIX) (3020-7-358)#

HA Monitor Cluster Software Guide (for Linux(R) (x86) Systems) (3000-9-201(E))

For Public Cloud Systems HA Monitor Cluster Software Guide (3000-9-204)#

JP1 Version 11 JP1/Base User's Guide (3021-3-A01(E))

JP1 Version 11 JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide (3021-3-B14(E))

JP1 Version 11 JP1/Audit Management - Manager Construction and Operation Guide (3021-3-A17)#

JP1 Version 12 JP1/Base User's Guide (3021-3-D65(E))

JP1 Version 12 JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide (3021-3-D23(E))

#: These manuals have been published in Japanese only; they are not available in English.

In references to Hitachi Advanced Database manuals, this manual uses HADB in place of Hitachi Advanced Database.

Example: HADB Setup and Operation Guide

In references to the HA Monitor manual, this manual uses:

HA Monitor for Linux(R) (x86) in place of HA Monitor Cluster Software Guide (for Linux(R) (x86) Systems)

Example: HA Monitor for Linux(R) (x86)

HA Monitor for Public Cloud in place of For Public Cloud Systems HA Monitor Cluster Software Guide

Example: HA Monitor for Public Cloud

In references to the JP1/Base manual, this manual uses JP1/Base User's Guide in place of JP1 Version 11 JP1/Base User's Guide or JP1 Version 12 JP1/Base User's Guide.

Example: JP1/Base User's Guide

In references to the JP1/Automatic Job Management System 3 manual, this manual uses JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide in place of JP1 Version 11 JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide or JP1 Version 12 JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Example: JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide

In references to the JP1/Audit manual, this manual uses JP1/Audit Construction and Operation Guide in place of JP1 Version 11 JP1/Audit Management - Manager Construction and Operation Guide.

Example: JP1/Audit Construction and Operation Guide

Conventions: Abbreviations for product names

This manual uses the following abbreviations for product names:

Abbreviation

Full name or meaning

HADB

HADB server

Hitachi Advanced Database

HADB client

Hitachi Advanced Database Client

Linux

RHEL 8

Red Hat Enterprise Linux Server 8 (64-bit x86_64)

RHEL 9

Red Hat Enterprise Linux Server 9 (64-bit x86_64)

RHEL 10

Red Hat Enterprise Linux Server 10 (64-bit x86_64)

HDLM

Hitachi Dynamic Link Manager Software

Hitachi Code Converter

Hitachi Code Converter - Runtime for C/COBOL (64)

JP1/AJS3

Job Management Partner 1/Automatic Job Management System 3

JP1/Audit

Job Management Partner 1/Audit Management - Manager

Conventions: Acronyms

This manual also uses the following acronyms:

Acronym

Full name or meaning

AD

Active Directory

Amazon S3

Amazon Simple Storage Service

APD

Application Parameter Descriptor

API

Application Programming Interface

ARD

Application Row Descriptor

AWS

Amazon Web Services

BI

Business Intelligence

BLOB

Binary Large Object

BNF

Backus-Naur Form

BOM

Byte Order Mark

CLI

Call Level Interface

CLOB

Character Large Object

CPU

Central Processing Unit

CSV

Character-Separated Values

DB

Database

DBMS

Database Management System

DMMP

Device Mapper Multipath

DNS

Domain Name System

DRBD

Distributed Replicated Block Device

EBS

Amazon Elastic Block Store

EC2

Amazon Elastic Compute Cloud

EFS

Amazon Elastic File System

ELF

Executable and Linking Format

ER

Entity Relationship

HBA

Host Bus Adapter

HDD

Hard Disk Drive

ID

Identification number

IEF

Integrity Enhancement Facility

IP

Internet Protocol

IPD

Implementation Parameter Descriptor

IRD

Implementation Row Descriptor

JAR

Java Archive File

JDBC

Java Database Connectivity

JDK

Java Developer's Kit

JNDI

Java Naming and Directory Interface

JRE

Java Runtime Environment

JSON

JavaScript Object Notation

JTA

Java Transaction API

LDAP

Lightweight Directory Access Protocol

LOB

Large Object

LRU

Least Recently Used

LV

Logical Volume

LVM

Logical Volume Manager

LWP

Light Weight Process

MSDN

Microsoft Developer Network

NFS

Network File System

NIC

Network Interface Card

NTP

Network Time Protocol

ODBC

Open Database Connectivity

OS

Operating System

OSS

Open Source Software

PAM

Pluggable Authentication Module

PP

Program Product

PV

Physical Volume

PVC

Persistent Volume Claim

RAID

Redundant Array of Independent Disks

RDBMS

Relational Database Management System

SELinux

Security-Enhanced Linux

SSD

Solid State Drive

SSSD

System Security Services Daemon

TLB

Translation Lookaside Buffer

URI

Uniform Resource Identifier

URL

Uniform Resource Locator

UUID

Universally Unique Identifier

VG

Volume Group

VPC

Amazon Virtual Private Cloud

WWN

World Wide Name

XFS

Extents File System

Conventions: Fonts and symbols

The following table explains the fonts used in this manual:

Font

Convention

Bold

Bold type indicates text on a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example:

From the File menu, choose Open.

Click the Cancel button.

In the Enter name entry box, type your name.

Italics

Italics are used to indicate a placeholder for some actual text to be provided by the user or system. For example:

Write the command as follows:

copy source-file target-file

The following message appears:

A file was not found. (file = file-name)

Italics are also used for emphasis. For example:

Do not delete the configuration file.

Code font

A code font indicates text that the user enters without change, or text (such as messages) output by the system. For example:

At the prompt, enter dir.

Use the send command to send mail.

The following message is displayed:

The password is incorrect.

Conventions: Path names

$INSTDIR is used to indicate the server directory path (for installation).

$ADBDIR is used to indicate the server directory path (for operation).

$DBDIR is used to indicate the DB directory path.

%ADBCLTDIR% (for a Windows HADB client) or $ADBCLTDIR (for a Linux HADB client) is used to indicate the client directory path.

%ADBODBTRCPATH% is used to indicate the folder path where HADB's ODBC driver trace files are stored.

Conventions: Method abbreviations

This manual uses "getXXX method" to represent any method whose name begins with get.

This manual uses the "setXXX method" to represent any method whose name begins with set.

Conventions: Symbols used in mathematical formulas

The following table explains special symbols used by this manual in mathematical formulas:

Symbol

Meaning

↑ ↑

Round up the result to the next integer.

Example: The result of ↑34 ÷ 3↑ is 12.

↓ ↓

Discard digits following the decimal point.

Example: The result of ↓34 ÷ 3↓ is 11.

MAX

Select the largest value as the result.

Example: The result of MAX(3 × 6, 4 + 7) is 18.

MIN

Select the smallest value as the result.

Example: The result of MIN(3 × 6, 4 + 7) is 11.

Conventions: Symbols used in message text

The table below explains the symbols used by this manual in message text.

Example of message text:

Usage: adbinfoget {-m | -o <output-directory>} [-f <core-file>]

Symbol

Meaning

{ }

Curly brackets indicate that only one of the enclosed items is to be selected. In the above example, either -m or -o option can be selected.

< >

Angle brackets indicate that the enclosed item is an argument, such as an option argument or a command argument, that is specified in a command.

[ ]

Square brackets indicate that the enclosed item or items are optional. In the above example, the -f option can be omitted.

Conventions: KB, MB, GB, TB, PB, and EB

This manual uses the following conventions:

1 KB (kilobyte) is 1,024 bytes.

1 MB (megabyte) is 1,024² bytes.

1 GB (gigabyte) is 1,024³ bytes.

1 TB (terabyte) is 1,024⁴ bytes.

1 PB (petabyte) is 1,024⁵ bytes.

1 EB (exabyte) is 1,024⁶ bytes.

Conventions: Version numbers

The version numbers of Hitachi program products are usually written as two sets of two digits each, separated by a hyphen. For example:

Version 1.00 (or 1.0) is written as 01-00.

Version 2.05 is written as 02-05.

Version 2.50 (or 2.5) is written as 02-50.

Version 12.25 is written as 12-25.

The version number might be shown on the spine of a manual as Ver. 2.00, but the same version number would be written in the program as 02-00.

1 Message Format and Output Locations

This chapter explains the locations to which HADB outputs messages. It also explains the format in which messages are output, how to interpret them, the relationship between message IDs and SQLCODEs, and query position numbers.

1.1 Message output locations

HADB outputs messages to the following locations:

Standard output

Standard error output

Message log files

syslog file

SQLException

ODBC diagnostic information

Different messages are output to different locations.

For details about the destination of each message, see 2.8 List of message output locations.

The description of each message also contains the message output locations. For details about where message output locations are indicated, see 1.3 Interpreting messages.

1.1.1 Standard output

Information and query messages are output to standard output. With regard to messages KFAA30000 to KFAA39999, however, there might be additional types of messages that are output to standard output. Messages KFAA96400 to KFAA96499 might not be output to standard output if the adbsql command is started with the -s option specified.

Some of the messages that are output to standard output might be output to a message log file, depending on when and for what reason they are output.

1.1.2 Standard error output

Error and warning messages are output to standard error output. With regard to messages KFAA30000 to KFAA39999, however, there might be additional types of messages that are output to standard error output.

Some of the messages that are output to standard error output might be output to a message log file, depending on when and for what reason they are output.

1.1.3 Message log files

HADB messages are output as message logs to a message log file.

Four message log files each are created for the HADB server and the HADB client. When output of message logs causes a message log file to reach its maximum capacity, the message log destination switches to another message log file. The maximum capacity of a message log file is the value specified in the environment variable ADBMSGLOGSIZE.

The message log files created for the HADB server and HADB client are shown below. The XX in each file name represents a number between 01 and 04.

For the HADB server (server message log files)

ADBDIR/spool/adbmessageXX.log

For the HADB client (client message log files)

%ADBCLTDIR%\spool\adbmessagecltXX.log (Windows edition of HADB client)

$ADBCLTDIR/spool/adbmessagecltXX.log (Linux edition of HADB client)

Use a text editor or similar tool to access messages in the message log files.

1.1.4 syslog file

Messages such as those containing HADB error information, transaction information, and system file information are output to syslog.

The output location is defined by /etc/syslog.conf.

You can specify the output level of the messages output to syslog in the environment variable ADBSYSLOGLV. For example, you can choose to output only high priority messages, or you can output all messages.

For more information on environment variable ADBSYSLOGLV, see Setting environment variables in Building a System in the HADB Setup and Operation Guide.

For details about the output level of each message, see 2.8 List of message output locations.

1.1.5 SQLException

SQLException is an SQLException object that stores the HADB JDBC driver's errors. You can obtain the details of an error by using a method of the SQLException interface such as getMessage(). The HADB JDBC driver's errors are also output to the Exception trace log. For details about the Exception trace log, see Exception trace log in the HADB Application Development Guide.

1.1.6 ODBC diagnostic information

The ODBC diagnostic information is a diagnostic data structure for storing the HADB ODBC driver's errors. For details about acquiring the ODBC diagnostic information, see SQLGetDiagField, SQLGetDiagFieldW, SQLGetDiagRec, SQLGetDiagRecW, and Troubleshooting in the HADB Application Development Guide.

1.2 Message output format

HADB outputs messages in the following format.

KFAAnnnnn-Y message-text

KFAAnnnnn: This is the HADB message ID.

Y: Message type (explained below.)

Table 1‒1: Types of messages

Message type

Definition

E

Indicates an error message. These messages are output when HADB processing does not execute correctly.

They are also output when processing cannot be executed because there are errors in the specifications of environment settings, definitions, or commands.

W

Indicates a warning message. Outputs the status of resource usage as a warning message. A warning message is also output when the specification for a definition or command is incorrect, but processing has continued with a default value.

I

Indicates an information message. These are messages other than the E and W messages above that simply report operations (such as startup, termination, or command execution). They are output when processing starts, terminates, and so on.

Q

Indicates a query message. When this type of message is output, the system waits for a response from the user.

Note that when messages are output to a message log file or syslog, they are output with additional information such as process IDs. The format in which messages are output to message log files or syslog is as follows.

Message format for output to a message log file

yyyy/mm/dd hh:mm:ss AA....AA BB....BB CC....CCDD....DD KFAAnnnnn-Y message-text

The following additional information is also output:

yyyy/mm/dd: Year/month/date (10 characters)

hh:mm:ss: Hours:minutes:seconds (8 characters)

AA....AA: Local process ID (10 numeric characters)

BB....BB: Real thread ID (10 numeric characters)

CC....CC: Client process ID (10 numeric characters)

Note that for messages output in the following cases, 0 is output:

• When a connection for processing was established from an HADB client that uses a JDBC driver

• When no connection has been established

• When processing is unrelated to the connection

• When the message is output from an HADB client or a command process#

DD....DD: Connection sequence number (10 numeric characters)

Note that for messages output in the following cases, 0 is output:

• When no connection has been established

• When processing is unrelated to the connection

• When the message is output from an HADB client or a command process#

For messages output by processing of the updated-row columnizing facility, 9999000001 is output in the connection sequence number.

#

Excluding messages that are output from the server process while a command that connects to the HADB server is establishing a connection to the HADB server.

For details about the commands that connect to the HADB server, see List of commands in List of Commands and Common Rules in the manual HADB Command Reference.

Message format for output to syslog

AA....AA BB....BB CC....CCDD....DD KFAAnnnnn-Y message-text

The following additional information is also output:

AA....AA: Local process ID (10 numeric characters)

BB....BB: Real thread ID (10 numeric characters)

CC....CC: Client process ID (10 numeric characters)

Note that for messages output in the following cases, 0 is output:

• When a connection for processing was established from an HADB client that uses a JDBC driver

• When no connection has been established

• When processing is unrelated to the connection

• When the message is output from an HADB client or a command process#

DD....DD: Connection sequence number (10 numeric characters)

Note that for messages output in the following cases, 0 is output:

• When no connection has been established

• When processing is unrelated to the connection

• When the message is output from an HADB client or a command process#

#

Excluding messages that are output from the server process while a command that connects to the HADB server is establishing a connection to the HADB server.

For details about the commands that connect to the HADB server, see List of commands in List of Commands and Common Rules in the manual HADB Command Reference.

1.3 Interpreting messages

This section explains how message information is presented in this manual.

#

The following abbreviations are used to indicate the message output locations:

S: Standard output

E: Standard error output

L: syslog file

M: Message log file

J: SQLException

O: ODBC diagnostic information

If there are multiple destinations, they are indicated with a plus sign (such as M+S).

If the description under Action indicates to contact the customer support center, it means that the HADB administrator is to contact the customer support center noted in the purchase agreement.

1.4 Interpreting SQLCODEs

If an SQLCODE is output, you need to see the corresponding message and take actions as shown in the following table.

Table 1‒2: Messages corresponding to SQLCODEs

No.

Format of the output SQLCODE

Corresponding message (message to be checked)

1

nnn

KFAA32nnn

Example: If 100 is indicated for the SQLCODE

The corresponding message is the KFAA32100-I message. See the KFAA32100-I message.

2

-nnn

KFAA30nnn

Example: If -204 is indicated for the SQLCODE

The corresponding message is the KFAA30204-E message. See the KFAA30204-E message.

3

-1nnn

KFAA31nnn

Example: If -1301 is indicated for the SQLCODE

The corresponding message is the KFAA31301-E message. See the KFAA31301-E message.

4

-4nnn

KFAA34nnn

Example: If -4003 is indicated for the SQLCODE

The corresponding message is the KFAA34003-E message. See the KFAA34003-E message.

5

-1071nnn

KFAA71nnn

Example: If -1071680 is indicated for the SQLCODE

The corresponding message is the KFAA71680-E message. See the KFAA71680-E message.

6

0

KFAA32000-I

Example: If 0 is indicated for the SQLCODE

The corresponding message is the KFAA32000-I message. See the KFAA32000-I message.

Legend:

n: Integer

1.5 Query position numbers

Query specifications and table value constructors specified in an SQL statement are assigned position numbers starting from 1 in order of specification from the beginning. These numbers are called query position numbers. They might be output in an error message for an SQL statement.

Example:

KFAA30202-E Column "C1" is not found in any table. (query number = 2)

The above message is output if, for example, the specified column name is invalid. At this time, the query position number is displayed in the underlined part.

For example, if the above message is output when the following SQL statement is executed, this indicates that an error exists in the query specification or table value constructor whose query position number is 2.

Example of the executed SQL statement

SELECT * FROM "T1" WHERE EXISTS (SELECT "C1" FROM "T2")

This example indicates that the underlined query specification (the second query specification from the beginning of the statement) is invalid. An error occurred in the SQL statement because table T2 does not contain column C1.

▪ Examples of query position numbers

For the SELECT statement

For the INSERT statement (VALUES specified) or PURGE CHUNK statement

The following shows an example of the INSERT statement (VALUES specified). In the case of the PURGE CHUNK statement, inquiry position numbers are also specified in the same manner.

▪ Notes

If the error is caused by a viewed table, the position number of the query specification designating that viewed table is displayed.

Example:

KFAA30323-E The specification of the multiset value expression is invalid.
(reason = a subquery of a multiset value expression is a correlated subquery,
query number = 2)

Example of the executed SQL statement

SELECT * FROM TABLE (ADB_CSVREAD(MULTISET(SELECT "C1" FROM "V1"),
                                'COMPRESSION_FORMAT=GZIP;'))
                                "DT"("DC1" INT)

In this example, the underlined query specification (the second query specification from the start of the statement) is invalid. An error occurred in the SQL statement because a disallowed viewed table (a viewed table that includes an external reference column in a view definition) is specified in a table subquery of a multiset value expression.

If the invalid part is other than a query specification or table value constructor in an SQL statement, 0 is displayed for the query position number.

(Example)

KFAA30117-E The number of insert values is not equal to the number of insert columns.
(query number = 0)

Example of the executed SQL statement

INSERT INTO "T1"("C1") VALUES('XYZ',100)

In this example, an error occurred in the SQL statement because the number of insertion values does not equal the number of insertion columns.

1.6 Notes on messages

Since HADB processes asynchronously using multiple threads, with some types of processing, the same message might be output numerous times. If this occurs, take the corrective action shown the first time the message is output.

Because HADB processes asynchronously using multiple threads, messages might not be output to the message log file in timestamp order.

When a command is executed, an error message beginning with KFAA3 might be output caused by an SQL statement that is executed as an extension of the command.

If an error message beginning with KFAA3 is output during execution of the command, replace the SQL statement with the command in the description under Action for the output message.

2 Messages

This chapter lists and describes the messages output by HADB.

2.1 Messages from KFAA30000 to KFAA39999

KFAA30101-E

The number of nested operations exceeded 255, or the SQL statement could not be executed because of restrictions on system processing. (M+J+O)

The depth of nesting of the operation exceeded 255. Another possibility is that the SQL statement could not be executed because of a restriction on system processing. <SQLSTATE: 427A0>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement by, for example, reducing the table or column count.

KFAA30102-E

The length of character string literal exceeds 32,000 bytes. (M+J+O)

The length of a character string literal exceeds 32,000 bytes. <SQLSTATE: 42501>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the length of the character string literal to 32,000 bytes or less.

KFAA30103-E

The format of the specified floating-point numeric literal aa....aa is invalid. (M+J+O)

The specification format of the floating-point numeric literal is invalid. <SQLSTATE: 42512>

aa....aa:

Invalid floating-point numeric literal

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the specification of the floating-point numeric literal.

KFAA30104-E

There is an unnecessary part "aa....aa" in the SQL statement. (M+J+O)

The SQL statement contains an error such as one of the following:

A name contains a character that cannot be specified. (such as a character encoding mismatch) <SQLSTATE: 42510>

A name with a length of 0 exists. <SQLSTATE: 42510>

The statement contains a character or keyword not allowed by the syntax. <SQLSTATE: 42510>

The first keyword of the SQL statement is invalid. <SQLSTATE: 42530>

The only character is a separator character. <SQLSTATE: 42530>

An extra character string exists after the SQL statement. <SQLSTATE: 42601>

aa....aa: The part of the SQL statement that contains the error.

If there is a character that cannot be specified under the rules, that character and its hexadecimal display are shown in parentheses.

If the part containing the error cannot be displayed as characters, a question mark (?) is displayed.

If an SQL statement contains only a separator character, a single-byte space is displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

If all the following conditions are satisfied, the system might determine that the name contains a character that cannot be specified.

A double-byte character is specified in the SQL statement.

The character encoding of the SQL statement does not match that of the HADB server.

In this case, make sure that the character encoding of the SQL statement matches that of the HADB server.

Action:

Correct the SQL statement.

KFAA30105-E

Token "aa....aa"(bb....bb), which is after token "cc....cc", is invalid. (M+J+O)

The SQL statement contains a syntax error. <SQLSTATE: 42602>

aa....aa:

Character that does not conform to syntax rules.

bb....bb: Type of aa....aa

non-reserved word: aa....aa is not a reserved word.

reserved word: aa....aa is a reserved word.

cc....cc:

Final character that conforms to syntax rules.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

An error such as one of the following might be present. Correct the SQL statement accordingly.

The SQL statement was not specified according to the syntax rules.

The clause specification order is invalid.

If bb....bb is reserved word, an error such as the following might have occurred:

A reserved word is specified as an identifier, such as a table name or a column name.

KFAA30106-E

The SQL statement is incomplete. (M+J+O)

One of the following errors was detected:

A character string literal is incomplete. <SQLSTATE: 42505>

An SQL statement is incomplete. <SQLSTATE: 42603>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30107-E

The length of identifier "aa....aa" exceeds 100 bytes. (M+J+O)

The length of a name exceeds 100 bytes. Another possibility is that a keyword was specified incorrectly. <SQLSTATE: 42520>

aa....aa:

An identifier specified with a name that exceeds 100 bytes

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement. Correct the length of the DB area name to 30 bytes or less.

KFAA30112-E

The argument of aa....aa function "bb....bb" is invalid. (M+J+O)

The aggregated argument specified in set function bb....bb is invalid. Another possibility is that the argument specified in window function bb....bb is invalid. <SQLSTATE: 42710>

aa....aa: Type of function

set: Set function

window: Window function

bb....bb:

Invalid set function name or window function name

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement according to rules for set function bb....bb or window function bb....bb. For details about the rules for set functions or window functions, see Set Functions or Window Functions in the manual HADB SQL Reference.

The possible errors are as follows:

Data whose data type cannot be specified for the argument indicated by bb....bb is specified

For the argument indicated by bb....bb, specify data whose data type can be specified.

The data type of the data specified for the argument indicated by bb....bb cannot be compared with the data type of the data specified for other arguments

For the argument indicated by bb....bb and other arguments, specify data whose data type can be compared. For details about comparable data types, see Set Functions or Window Functions in the manual HADB SQL Reference.

Only a single dynamic parameter is specified for the argument indicated by bb....bb

Use the scalar functions CAST or CONVERT to specify a dynamic parameter. Alternatively, do not use a dynamic parameter.

The following shows an example of specifying a dynamic parameter by using the scalar functions CAST and CONVERT.

Example of specifying a dynamic parameter by using the scalar function CAST

CAST(? AS CHAR(10))

Example of specifying a dynamic parameter by using the scalar function CONVERT

CONVERT(?, CHAR(10))

KFAA30113-E

The set function "aa....aa" is specified in argument of set function. (M+J+O)

A set function contains set function aa....aa as an argument. <SQLSTATE: 42711>

aa....aa:

Name of set function whose argument is invalid.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the set function argument.

KFAA30114-E

The use of the "aa....aa" predicate is invalid. (invalid factor = bb....bb, operand number = c, query number = dd....dd) (M+J+O)

The specification of predicate aa....aa is invalid. <SQLSTATE: 42561>

aa....aa: Type of predicate that contains error

COMPARISON: A comparison predicate

BETWEEN: A BETWEEN predicate

QUANTIFIED: Quantified predicate

bb....bb: Description of error

COMBINATION: A combination of options is invalid.

DATA TYPE: A data type is invalid.

c:

Asterisk (*) is displayed.

dd....dd: Position number of the query that specified predicate aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30117-E

The number of aa....aa is not equal to the number of bb....bb. (query number = cc....cc) (M+J+O)

The number of aa....aa is not equal to the number of bb....bb. <SQLSTATE:42720>

aa....aa:

insert values: Insertion values

derived column list: A derived column list

"WITH" column list: A WITH column list

row value constructor elements on left side of the predicate: Row value constructor elements on the left side of the predicate

bb....bb:

insert columns: Insertion columns

derived columns: Derived columns

row value constructor elements on right side of the predicate: Row value constructor elements on the right side of the predicate

cc....cc: Position number of the query that specified the derived column list or row value constructor

For details about query position numbers, see 1.5 Query position numbers.

If the error did not occur in a derived column list or row value constructor, the position number of the query will be 0.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30118-E

Table "aa....aa" to be updated is specified as a table from which data is to be retrieved. (M+J+O)

The table to be updated aa....aa cannot be specified as a table from which data is to be retrieved. <SQLSTATE: 42793>

aa....aa:

Table identifier

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30119-E

In a query using a GROUP BY clause or a set function specification, the column "aa....aa" specified in a select expression, a HAVING clause or an ORDER BY clause must be specified as an argument of the GROUP BY clause or the set function. (query number = bb....bb, cc....cc) (M+J+O)

In a query using a GROUP BY clause or set function specification, column aa....aa specified in a selection expression, HAVING clause, or ORDER BY clause must be specified as an argument of the GROUP BY clause or set function. <SQLSTATE: 42746>

aa....aa: Name of the column with the invalid column specification

Note that *** is displayed when no column name can be output.

bb....bb:

Position number of the query that specified column aa....aa#

cc....cc:

Position number of the query specification that has the referenced table in its FROM clause#

#

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

If this message is output in either of the following cases, take the corrective action described under Procedure.

The ALTER VIEW statement is executed.

A viewed table is re-created during version upgrading of the HADB server.

For details, see Re-creation of viewed tables in the event of a version upgrade in Notes on version upgrading in the HADB Setup and Operation Guide.

Procedure

Check viewed table definition information.

Check the CREATE VIEW statement that was used when the target viewed table was defined. You can acquire viewed table definition information by searching a dictionary table. For details about examples of searching the dictionary table, see Finding out viewed table definition information in Searching a dictionary table in the HADB Setup and Operation Guide.

Delete the viewed table.

Delete the target viewed table by using the DROP VIEW statement.

Correct the information specified in the CREATE VIEW statement.

Correct the information specified in the CREATE VIEW statement you checked in step 1.

Redefine the viewed table by using the CREATE VIEW statement.

Use the CREATE VIEW statement you corrected in step 3 to redefine the viewed table deleted in step 2.

If this message is output because an asterisk (*) is specified in the selection expression for the query specification in the CREATE VIEW statement, do not specify the asterisk (*). Correct the information specified in the CREATE VIEW statement to explicitly specify the column name in the selection expression for the query specification.

Note that if aa....aa is an array-type column, the column cannot be specified in the GROUP BY clause. Consider correcting the SQL statement as follows.

Specify a aa....aa column or a value expression that includes that column as the argument for a set function.

Correct the value expression so that the value expression that contains the aa....aa column or the value expression with the grouping specification is of the same format.

KFAA30120-E

A aa....aa function "bb....bb" cannot be specified in the cc....cc. (query number = dd....dd, ee....ee) (M+J+O)

Set function bb....bb cannot be specified in cc....cc. Another possibility is that window function bb....bb cannot be specified in cc....cc. <SQLSTATE: 42714>

aa....aa: Type of function

set: Set function

window: Window function

bb....bb:

Function name

cc....cc: Name of the clause or statement in which aa....aa is specified

"WHERE" clause: WHERE clause, or WHERE search condition in a DELETE statement or UPDATE statement

update value: Update value specified in an UPDATE statement

insert value: Insertion value specified in an INSERT statement

"FROM" clause: FROM clause

"ORDER BY" clause: ORDER BY clause

"GROUP BY" clause: GROUP BY clause

"HAVING" clause: HAVING clause

sort specification: Sort specification

row value constructor element: Row value constructor element

dd....dd:

Position number of the query specification in which the table referenced by the aggregated column specification in aa....aa is specified as the FROM clause#

ee....ee:

Position number of the query specification that specified aa....aa#

#

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30121-E

The update columns or insert columns are duplicated. (M+J+O)

An update column or insertion column is duplicated. <SQLSTATE: 42731>

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30122-E

The number of aa....aa in bb....bb exceeds cc....cc. (M+J+O)

One of the following clauses is invalid:

GROUP BY clause <SQLSTATE: 425B2>

The number of grouping columns specified in a GROUP BY clause exceeds the maximum allowed value.

Window partition clause <SQLSTATE: 425BG>

The number of value expressions specified in a window partition clause exceeds the maximum allowed value.

aa....aa: Element that exceeds the maximum allowed value

grouping columns: Grouping column

value expressions: Value expression

bb....bb: Invalid clause

"GROUP BY" clause: GROUP BY clause

"window partition" clause: Window partition clause

cc....cc: Maximum allowed value

16: Maximum number of value expressions allowed in a window partition clause

64: Maximum number of grouping columns allowed in a GROUP BY clause

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Reduce the number of grouping columns specified in the GROUP BY clause. Alternatively, reduce the number of value expressions specified in the window partition clause.

KFAA30123-E

Column "aa....aa" specified in bb....bb is duplicated. (M+J+O)

The column aa....aa specified in bb....bb is duplicated. <SQLSTATE: 42732>

aa....aa:

Column name

bb....bb: Location where column aa....aa is specified

"GROUP BY" clause: GROUP BY clause

derived table: A derived table

collection derived table: A collection derived table

table function column list: Table function column list

query name: A query name

"window partition" clause: Window partition clause

"window order" clause: Window order clause

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30124-E

The number of sort keys in aa....aa exceeds 64. (M+J+O)

The number of sort keys specified in aa....aa exceeds 64. <SQLSTATE: 425B3>

aa....aa: Clause that exceeds the maximum number of sort keys allowed

"ORDER BY" clause: ORDER BY clause

"window order" clause: Window order clause

"within group specification": WITHIN group specification

S:

Ignores this SQL statement.

Action:

Reduce the number of sort keys to 64 or fewer.

KFAA30125-E

The sort item specification number (aa....aa) in the "ORDER BY" clause is invalid. (M+J+O)

The sort item specification number specified in the ORDER BY clause is invalid. <SQLSTATE: 42743>

aa....aa:

Invalid sort item specification number

S:

Ignores this SQL statement.

Action:

Correct the sort item specification number displayed as aa....aa. The permitted range of sort item specification numbers is from 1 to the number of columns in the table that is derived from the query expression body.

KFAA30126-E

Sort item specification numbers cannot be specified for "ROW". (M+J+O)

Sort item specification numbers for ROW cannot be specified. <SQLSTATE: 427HD>

S:

Ignores this SQL statement.

Action:

Correct the sort item specification number specified in the ORDER BY clause.

KFAA30127-E

"DISTINCT" is specified more than once in a query specification. (reason = aa....aa, query number = bb....bb) (M+J+O)

DISTINCT cannot be specified more than once in a single query specification.

aa....aa: Cause of the error

SELECT DISTINCT: The SELECT DISTINCT and DISTINCT set functions are both specified. <SQLSTATE: 42716>

different column name: Multiple DISTINCT set functions containing different column names in the arguments are specified. <SQLSTATE: 42717>

value expression: Another DISTINCT set function is specified in addition to the DISTINCT set function specified in the value expression of an argument. <SQLSTATE: 42718>

bb....bb: Position number of the query that specified DISTINCT

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30129-E

The specified number aa....aa exceeds the maximum of bb....bb. (M+J+O)

A specification has exceeded its maximum number.

aa....aa:

Specification that exceeded its maximum number

Value of aa....aa

Meaning

SQLSTATE

parameters

Dynamic parameters

425A0

parameters of COALESCE function

Target data specified in the COALESCE scalar function

425A0

parameters of DECODE function

Arguments specified in the DECODE scalar function

425A0

parameters of GREATEST function

Target data specified in the GREATEST scalar function

425A0

parameters of LEAST function

Target data specified in the LEAST scalar function

425A0

parameters of LTDECODE function

Arguments specified in the LTDECODE scalar function

425A0

when

WHEN

425A4

row value constructor elements

Row value constructor elements in a row value constructor

425A6

row value constructors

Row value constructors in a table value constructor

425A7

parameters of system-defined function

Arguments specified in a system definition function

425A8

multiset elements

Number of multiset elements

425A9

query specifications

Query specifications and table value constructors

425AA

columns in table function column list

Column name in a table function column list

425AI

partition key column definition

A partition key column definition

425AJ

select tables

Tables specified in the FROM clause of a query specification (including those in view definitions)

425B0

tables

Tables specified in an SQL statement

425B0

select columns

Columns to be derived by a query specification

425B1

insert values

Insertion values specified in an INSERT statement

425B5

insert columns

Insertion columns specified in an INSERT statement

425B6

update columns

Update columns specified in an UPDATE statement

425B7

derived columns

Columns specified in a derived columns list

425BB

with columns

Columns in WITH clauses

425BC

DISTINCT set functions

DISTINCT set function specified in a query specification as a set function

425BJ

columns in collection derived table

Column specification of collection derived tables

425BK

ARRAY_AGG set functions

ARRAY_AGG set function specified in the query specification

425BL

LISTAGG set functions

LISTAGG set function specified in the query specification

425BM

view columns

Columns in view definitions

425C1

foreign keys

Foreign keys

425C2

authorization identifier

Authorization identifier specified in the SQL statement

425CA

nest of struct data and array data

Nesting of structure data and array data

425CB

fields of struct data

Number of fields in structure data

425CC

value expression

Value expressions

425CF

nests of value expression

Levels of nested value expressions

425CG

nests of subquery

Nested subqueries

425CH

bb....bb:

Maximum that can be specified

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the number of aa....aa to bb....bb or less.

If you specify viewed tables or query names, apply the internal derived table corresponding to each specification, and then calculate the maximum number of specifications.

If you specify archivable multi-chunk tables, calculate the maximum number of specifications based on the SQL statement that has been converted to a derived table by equivalent exchange.

For details about equivalent exchange of archivable multi-chunk tables, see Equivalent exchange of SQL statements that search archivable multi-chunk tables in the HADB Application Development Guide.

If this message is output in either of the following cases, take the corrective action described under Procedure.

The ALTER VIEW statement is executed.

A viewed table is re-created during version upgrading of the HADB server.

For details, see Re-creation of viewed tables in the event of a version upgrade in Notes on version upgrading in the HADB Setup and Operation Guide.

Procedure

Check viewed table definition information.

Check the CREATE VIEW statement that was used when the target viewed table was defined. You can acquire viewed table definition information by searching a dictionary table. For details about examples of searching the dictionary table, see Finding out viewed table definition information in Searching a dictionary table in the HADB Setup and Operation Guide.

Delete the viewed table.

Delete the target viewed table by using the DROP VIEW statement.

Correct the information specified in the CREATE VIEW statement.

Correct the information specified in the CREATE VIEW statement you checked in step 1.

Redefine the viewed table by using the CREATE VIEW statement.

Use the CREATE VIEW statement you corrected in step 3 to redefine the viewed table deleted in step 2.

If this message is output because an asterisk (*) is specified in the selection expression for the query specification in the CREATE VIEW statement, do not specify the asterisk (*). Correct the information specified in the CREATE VIEW statement to explicitly specify the column name in the selection expression for the query specification.

KFAA30131-E

The precision of the decimal number for the seconds for aa....aa is invalid. (M+J+O)

The fractional seconds precision aa....aa that was specified is invalid. <SQLSTATE: 42591>

aa....aa: Datetime information acquisition function in which the error occurred

CURRENT_TIME

CURRENT_TIMESTAMP

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the specification for the fractional seconds precision.

KFAA30137-E

The number of values in the IN predicate exceeds 30,000. (M+J+O)

The number of value expressions or row value constructors specified on the right side of an IN predicate has exceeded the upper limit of 30,000. <SQLSTATE: 427A2>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The number of value expressions or row value constructors specified to the right of the IN predicate should not exceed 30,000. Correct the SQL statement, and then retry the operation.

KFAA30142-E

The national character identifier is invalid. (M+J+O)

The following syntax error was found in the identifier specified for the national character set: <SQLSTATE: 42532>

A double-byte space character was used.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30144-E

The specification for aa....aa is invalid. (M+J+O)

The specification for aa....aa is invalid. <SQLSTATE: 42509>

aa....aa: Type of binary literal

binary: Binary literal in binary format

hex: Binary literal in hexadecimal format

uuid: UUID literal

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the error.

For binary literals in binary format:

The number of binary characters specified in a binary-format binary literal is not a multiple of 8.

The binary characters specified in a binary-format binary literal include a character that is not 0 or 1.

For binary literals in hexadecimal format:

The number of hexadecimal characters specified in a hexadecimal-format binary literal is not a multiple of 2.

The hexadecimal characters specified in a hexadecimal-format binary literal include a character that is not 0 to 9, A to F or a to f.

For UUID literals:

Check that the following specification rules are followed.

Specify UUID literals in the format AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE.

Specify hexadecimal characters for each of the A through E characters above.

KFAA30145-E

The length of aa....aa exceeds bb....bb bytes. (M+J+O)

aa....aa is more than bb....bb bytes long. <SQLSTATE: 42502>

aa....aa: Type of binary literal

binary: Binary-format binary literal

hex: Hexadecimal-format binary literal

bb....bb: Maximum length of literal

256000: Maximum length of binary-format binary literal

64000: Maximum length of hexadecimal-format binary literal

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30149-E

"ROW" is used incorrectly. (M+J+O)

The way ROW is specified contains one of the following errors. <SQLSTATE:42572>

ROW was specified in a query that specified a set function.

ROW was specified in a query that specified a window function.

ROW was specified in a query that specified DISTINCT.

Something other than a dynamic parameter was specified in the insertion value or update value for ROW.

ROW was specified in an expression other than the selection expression in the outermost query specification.

ROW was specified in a query expression in the viewed table.

In a joined table specification, ROW was specified for a table for which the null value is specified.

ROW was specified in a query expression body in a WITH clause.

ROW was specified in a query that specifies a set operation.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30154-E

A subquery is specified for the aa....aa. (query number = bb....bb) (M+J+O)

A subquery was specified at aa....aa. <SQLSTATE: 42715>

aa....aa: Position where subqueries cannot be specified

"GROUP BY" clause: GROUP BY clause

set function: Set function

window function: Window function

"ON" search conditions of "FULL OUTER JOIN": ON search conditions of joined tables that specified FULL OUTER JOIN

row value constructor element: Row value constructor element

bb....bb: Position number of the query that specified the subquery

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30166-E

The aa....aa in the bb....bb is incorrect. (reason = cc....cc) (M+J+O)

The SQL statement specification contains one of the following errors.

The sort key specified in the ORDER BY clause contains one of the following errors:

• The name of a derived column (excluding a derived column that consists of a column specification only) is specified in the value expression. Alternatively, the derived column name that is derived by a set operation is specified in the value expression (even a derived column consisting of only column specifications cannot be specified). <SQLSTATE:427HC>

The window partition clause contains the following error:

• The value expression contains no column specification. <SQLSTATE: 427HA>

aa....aa: Invalid specification

sort key: Sort key

value expression: Value expression

bb....bb: Invalid clause

"ORDER BY" clause: ORDER BY clause

"window partition" clause: Window partition clause

cc....cc: Cause of the error

not specified column: The value expression contains no column specification.

specified by the derived column: The name of a derived column is specified in the value expression.

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30177-E

The system-defined function "aa....aa" is invalid. (reason = bb....bb, query number = cc....cc) (M+J+O)

The specification of system-defined function aa....aa is invalid.

aa....aa:

System-defined function name, or schema identifier and system-defined function name

bb....bb: Cause of the error

number of arguments is incorrect: The number of arguments specified in the system-defined function is invalid. <SQLSTATE: 4277E>

argument data type is incorrect: The data type of the argument specified in the system-defined function is invalid. <SQLSTATE: 4277F>

argument value is incorrect: The value of the argument specified in the system-defined function is invalid. <SQLSTATE: 4277G>

function name is incorrect: The specified system-defined function name is invalid. <SQLSTATE:42786>

cc....cc: Query position number

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30183-E

Array data cannot be specified in aa....aa. (query number = bb....bb) (M+J+O)

Array data cannot be specified in aa....aa. <SQLSTATE:42755>

aa....aa: Invalid specification

sort key: Sort key

select expression of the outermost query for a set operation:

Selection expression of the outermost query specification for a set operation

select expression of the outermost query specification (limited to array data whose element data type is array-type or struct-type) in statements other than COPY and CREATE VIEW:

Selection expression of the outermost query specification (other than COPY and CREATE VIEW statements)

Array data whose element data type is array type or STRUCT type cannot be specified in a selection expression.

select expression of scalar subquery: Selection expression of scalar subquery

select expression of query expression body for INSERT statement: Selection expression of the query expression body of an INSERT statement

grouping column: Grouping column

row value constructor element: Row value constructor element

IN predicate: An IN predicate

QUANTIFIED predicate: A quantified predicate

CASE expression: A CASE expression

bb....bb: Query position number

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30186-E

The value of aa....aa specified in an array element reference is outside the valid range. (M+J+O)

The value outside the specified range is specified as aa....aa in the array element reference. <SQLSTATE:42580>

aa....aa: Invalid specification

subscript: Subscript

identification number: Identification number

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30187-E

Array data cannot be specified in aa....aa that includes DISTINCT. (query number = bb....bb) (M+J+O)

Array data cannot be specified in aa....aa with DISTINCT specified. <SQLSTATE:42759>

aa....aa: Invalid specification

select expression: Selection expression

set function: Set function

bb....bb: Query position number

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30188-E

There is an error in the specification method of a collection derived table. (reason = aa....aa, query number = bb....bb) (M+J+O)

The specified collection derived table is invalid. <SQLSTATE:4275A>

aa....aa: Reason

one or more column specifications are not array data:

The column specification is not array data.

one or more columns are not columns of a real table or a foreign table joined with the collection derived table by using a comma join:

One or more columns are not columns of a base table joined with the collection derived table by using a comma join. Or, one or more columns are not columns of a foreign table joined with the collection derived table by using a comma join.

column specifications of different tables are specified:

The column specification of a different table is specified.

bb....bb: Position number of the query that specified the collection derived table

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

For details about the rules for specification of collection derived tables, see Table references in the manual HADB SQL Reference.

KFAA30189-E

There is an error in the maximum number of elements in the array-type column "aa....aa" specified in the bb....bb statement. (M+J+O)

The specified maximum number of elements of the array-type column aa....aa specified in the bb....bb statement is invalid. <SQLSTATE:42581>

aa....aa:

Array-type column name that is invalid

bb....bb: Invalid SQL statement

CREATE TABLE

CREATE FOREIGN TABLE

ALTER TABLE

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30192-E

Multiple selection expression are specified for the subquery. (query number = aa....aa) (M+J+O)

Two or more selection expressions have been specified for a retrieval item. <SQLSTATE: 42722>

aa....aa: Position number of the query that contains the subquery that specifies two or more retrieval items

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement so that there is a single retrieval item.

KFAA30194-E

The aa....aa cannot be specified in the "ORDER BY" clause for the query that used the bb....bb. (M+J+O)

aa....aa cannot be specified in the ORDER BY clause for a query in which bb....bb is specified.

One of the following errors occurred:

For a query that uses a set operation, a column name qualified in the table specification cannot be specified as a sort key. <SQLSTATE: 427B2>

For a query that uses a set operation, no value expression can be specified in the ORDER BY clause. <SQLSTATE: 427B6>

For a query that specifies SELECT DISTINCT, no value expression can be specified in the ORDER BY clause. <SQLSTATE: 427HE>

aa....aa: Sort key specification in the ORDER BY clause

qualified column name: Column name qualified in the table specification

value expression: Value expression

bb....bb: Constituent element specified in the query that is incompatible with aa....aa

"SET OPERATION": Set operation

"SELECT DISTINCT": SELECT DISTINCT

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30195-E

The derived tables for a set operation must have the same number of columns. (M+J+O)

In a specified set operation, the tables derived from individual query expression bodies do not have the same number of columns. <SQLSTATE: 42721>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement so that the tables derived from individual query expression bodies have the same number of columns. For details, see Rules for set operations in Rules in Specification format and rules for query expressions in the manual HADB SQL Reference.

KFAA30197-E

The data types of the aa....aa specified in the bb....bb are not compatible. (list number = cc....cc, query number = dd....dd) (M+J+O)

The data types of aa....aa specified in bb....bb are not compatible. <SQLSTATE: 42804>

aa....aa: Location of error

derived columns for each query: Derived columns for each query

element for each row value constructor: Row value constructor element for each row value constructor

bb....bb: Corresponding item

set operation: Set operation

table value constructor: Table value constructor

cc....cc: List number resulting in an error

If bb....bb is set operation: List number of the selection list for the derived table

If bb....bb is table value constructor: Number indicating the position where the relevant row value constructor element is specified

dd....dd: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

If aa....aa is derived columns for each query

Correct the SQL statement so that the data types indicated in aa....aa are compatible.

If aa....aa is element for each row value constructor

The data type of the i-th row value constructor element in each row value constructor is not comparable. Correct the specified row value constructors. For details, see Rules in Specification format and rules for table value constructors in the manual HADB SQL Reference.

KFAA30201-E

The table specification qualifying the column name is not a valid name in an SQL statement. The invalid qualifier is "aa....aa"."bb....bb" or "cc....cc". (query number = dd....dd) (M+J+O)

The qualifying table specification contains a name that is not valid to specify in an SQL statement. <SQLSTATE: 42740>

aa....aa:

The identifier specified within the table specification, or the default schema name

bb....bb:

Table identifier, correlation name, or query name

cc....cc:

Table identifier, correlation name, or query name

dd....dd: Position number of the query that specified the invalid identifier

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30202-E

Column "aa....aa" is not found in any table. (query number = bb....bb) (M+J+O)

The specified column aa....aa does not exist in any table of the SQL statement or query specification. Another possibility is that the name is invalid. <SQLSTATE: 42742>

aa....aa:

Column specified in an SQL statement

bb....bb: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

If this message is output as a result of executing the ALTER VIEW statement, see When viewed tables are invalidated by using the ALTER VIEW statement to rebuild a viewed table that is the underlying table of those viewed tables in Releasing a viewed table from invalidation in the HADB Setup and Operation Guide.

KFAA30203-E

Column "aa....aa" cannot be determined in the SQL statement. (query number = bb....bb) (M+J+O)

The specified column aa....aa cannot be identified as the name of a column in a specific table. Two or more tables specified in a query have the same column name. <SQLSTATE: 42744>

aa....aa:

Column name that belongs to two or more tables specified in the query

bb....bb: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Qualify the column name with a table name so that the column name can be identified as belonging to a specific table.

KFAA30204-E

The table or index "aa....aa"."bb....bb" is not found in the system. (M+J+O)

The specified table or index has not been defined. <SQLSTATE: 42741>

aa....aa:

Schema name

bb....bb:

Table or index identifier

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

If this message is output when the ALTER VIEW statement is executed, see When viewed tables are invalidated due to erroneous deletion of a table in Releasing a viewed table from invalidation in the HADB Setup and Operation Guide.

KFAA30205-E

The "aa....aa" column does not exist in the "bb....bb"."cc....cc" table, the correlation name, or the query "dd....dd". (M+J+O)

Column aa....aa was not found in table bb....bb.cc....cc, a correlation name, or a query dd....dd. <SQLSTATE: 42742>

aa....aa:

Column name

bb....bb:

Schema name

cc....cc:

Table identifier, correlation name, or query name

dd....dd:

Table identifier, correlation name, or query name

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

If this message is output when the ALTER VIEW statement is executed, see When viewed tables are invalidated by using the ALTER VIEW statement to rebuild a viewed table that is the underlying table of those viewed tables in Releasing a viewed table from invalidation in the HADB Setup and Operation Guide.

KFAA30206-E

aa....aa is specified as the table name in the "bb....bb" statement. (M+J+O)

An SQL statement contains an error similar to the following: <SQLSTATE:42I01>

A viewed table or foreign table is specified in the ALTER TABLE statement.

A base table or foreign table is specified in the ALTER VIEW statement.

A viewed table or foreign table is specified in the CREATE INDEX statement.

A base table or viewed table is specified in the DROP FOREIGN TABLE statement.

A viewed table or foreign table is specified in the DROP TABLE statement.

A base table or foreign table is specified in the DROP VIEW statement.

aa....aa: Type of table

A base table: A base table

A viewed table: A viewed table

A foreign table: A foreign table

bb....bb: The erroneous SQL statement

ALTER TABLE: Changes a table definition

ALTER VIEW: Re-creates a viewed table

CREATE INDEX: Defines an index

DROP FOREIGN TABLE: Deleting a foreign table

DROP TABLE: Deletes a base table

DROP VIEW: Deletes a viewed table

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30208-E

The column "aa....aa" specified in the ORDER BY clause is not specified as a column in the SELECT clause of the query. (M+J+O)

A column that is not specified in the selection expression cannot be specified in the ORDER BY clause due to one of the following reasons: <SQLSTATE:42743>

A SELECT DISTINCT was specified.

A set operator for the query specification, which is the first set operation operand in the set operation, is specified.

aa....aa:

Column name

S:

Ignores this SQL statement.

Action:

Correct the SQL statement so that it satisfies one of the following conditions.

The same value expression as the value expression specified in the ORDER BY clause is specified in the selection expression of the query specification that specifies SELECT DISTINCT.

The same value expression as the value expression specified in the ORDER BY clause is specified in the selection expression of the query specification, which is the first set operation operand of the set operation.

KFAA30210-E

An attempt was made to set a null value in a column specified as "NOT NULL". (M+J+O)

An attempt was made to set a null value in a column for which null values cannot be set. <SQLSTATE: 23503>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30211-E

The name "aa....aa" is duplicated in a "FROM" clause. (query number = bb....bb) (M+J+O)

The name aa....aa is duplicated within a FROM clause. <SQLSTATE: 42730>

aa....aa:

Name

bb....bb: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30213-E

"ROW" applies to more than 1 table in the SQL statement. (M+J+O)

There are two or more corresponding tables in a query with ROW specified. Therefore, in the SQL statement, the table to which ROW corresponds cannot be determined. <SQLSTATE: 42744>

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30214-E

"ROW" cannot be specified. (reason = aa....aa) (M+J+O)

You cannot specify ROW for a table that is not a FIX table. <SQLSTATE: 42750>

aa....aa: Item that cannot specify ROW

non-"FIX" attribute table: Table that is not a FIX table

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30220-E

The column "aa....aa" specified in the "ORDER BY" clause is found more than once in the derived table. (M+J+O)

A column specified in an ORDER BY clause is found more than once in a table derived as a result of a query. <SQLSTATE: 42745>

aa....aa:

Column name specified in the ORDER BY clause

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30229-E

The total memory for execution of this SQL exceeds 2 GB. (M+J+O)

The total memory required to execute this SQL statement exceeds 2 GB. <SQLSTATE: 56006>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Consider one of the following corrective actions:

If a column with an extremely long definition is specified in an SQL statement, can that column be omitted from the SQL statement? Alternatively, can the definition of that column be shortened?

Can the number of columns specified in SQL statements be reduced?

KFAA30239-E

For the identifier "aa....aa", there are no target candidates in the valid scope. (query number = bb....bb) (M+J+O)

There are no target candidates for the specified identifier aa....aa within the valid range. <SQLSTATE: 42742>

aa....aa:

Invalid identifier

bb....bb: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Check the identifier aa....aa specified in the SQL statement.

KFAA30257-E

The aa....aa specified in the window function "bb....bb" is invalid. (reason = cc....cc, query number = dd....dd) (M+J+O)

aa....aa specified in window function bb....bb is invalid.

aa....aa: Location of error

"window frame extent": Window frame border

"window partition" clause: Window partition clause

"window order" clause: Window order clause

"window frame value specification": Window frame value specification

bb....bb:

Window function name

cc....cc: Cause of the error

combination: The combination of the window frame borders for a range specification window frame is invalid. <SQLSTATE: 427G0>

none "window order" clause: No window order clause is specified. <SQLSTATE: 427G1>

"sort specification list" number: An invalid number of sort specification lists are specified. <SQLSTATE: 427G2>

data type of "sort key": The data type of a sort key is invalid. <SQLSTATE: 427G3>

data type: The data type is invalid in an unsigned value specification. <SQLSTATE: 427G4>

"labeled duration" specified: The information specified in an unsigned value specification is invalid. <SQLSTATE: 427G4>

data type of the "partition value": The data type of the value specified in the window partition clause is invalid. <SQLSTATE: 427G5>

incompatible data type: The data type of a sort key is not compatible with the data type in an unsigned value specification. <SQLSTATE: 4280F>

dd....dd: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30264-E

The window function "aa....aa" is invalid. (reason = bb....bb, query number = cc....cc) (M+J+O)

Window function aa....aa is invalid.

aa....aa:

Window function name

bb....bb: Cause of the error

none "window order" clause: No window order clause is specified. <SQLSTATE: 427H0>

specified "window frame" clause: A window frame clause is specified. <SQLSTATE: 427H1>

specified "window order" clause: A window order clause is specified. <SQLSTATE: 427H2>

cc....cc: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30302-E

The input data is outside the valid range for values of the column data type. (column name = "aa....aa") (M+J+O)

The input data exceeds the range of values permitted for the column's data type. <SQLSTATE: 22003>

aa....aa: The column name that caused the error

If the column name cannot be output, *** is displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Check the data of the substitution source, and correct any errors found.

KFAA30312-E

The total size of aa....aa exceeds 2 GB. (M+J+O)

The total length of aa....aa exceeds 2 GB. <SQLSTATE: 56001>

aa....aa: Cause

dynamic parameters: The total value of data lengths specified in the dynamic parameters exceeds 2 GB.

search results: The total value of data lengths in the search results exceeds 2 GB.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement using one of the following methods:

If aa....aa is dynamic parameters

Reduce the number of dynamic parameters in the SQL statement.

If aa....aa is search results

Reduce the search result column count in the SQL statement. If the number of batch-transmission rows when FETCH processing is performed is specified with the client definition's adb_clt_fetch_size operand, reduce the specified value of the adb_clt_fetch_size operand.

KFAA30318-E

An internal contradiction was detected. (information = aa....aa) (M+O)

An internal conflict was found. <SQLSTATE: 5C011>

aa....aa:

Used by system

S:

Ignores this SQL statement.

Action:

Restart the application program. If the problem occurs again after the application program is restarted, make a backup of the client message log file, and then contact the customer support center.

KFAA30319-E

SQL processing is already being executed for the same connection. (M+O)

An SQL statement that uses this connection is already being executed. <SQLSTATE: 54202>

S:

Ignores this SQL statement.

Action:

Wait for the SQL statement that is using the connection to terminate, and then re-execute the SQL statement.

KFAA30322-E

An internal contradiction was detected. (information 1 = aa....aa, information 2 = bb....bb, information 3 = cc....cc, information 4 = dd....dd, information 5 = ee....ee, information 6 = ff....ff) Save troubleshooting information by the "adbinfoget" command, and then contact customer service. (M+J+O)

This message is output when an internal conflict is detected. <SQLSTATE:5C011>

aa....aa to ff....ff: Troubleshooting information

If no information to display exists, three asterisks (***) are displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Contact an HADB administrator.

The HADB administrator must execute the adbinfoget command, collect troubleshooting information, and then contact the customer support center.

After that, re-execute the SQL statement or command.

KFAA30323-E

The specification of the multiset value expression is invalid. (reason = aa....aa, query number = bb....bb) (M+J+O)

The specified multiset value expression is invalid.

aa....aa: Cause of the error

a subquery of a multiset value expression is a correlated subquery: An external reference column cannot be specified in a table subquery of a multiset value expression. <SQLSTATE: 427I9>

data types are not all comparable: The data type of data specified for the multiset element is not comparable. <SQLSTATE: 427IA>

bb....bb: Query position number

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30324-E

The specified argument in the system-defined function "ADB_CSVREAD" is invalid. (argument number = aa....aa, option = bb....bb, reason = cc....cc, query number = dd....dd) (M+J+O)

The argument specified in the ADB_CSVREAD function is invalid.

aa....aa:

Position number of the argument

bb....bb: Function option that caused the error

compression_format: Compression format option

field_num: Specification column option

binary_string_format: Binary string format option

enclosing_char: Enclosing character specification option

delimiter_char: Delimiting character specification option

***: Items other than the above

cc....cc:

Cause of the error

dd....dd: Query position number

For details about query position numbers, see 1.5 Query position numbers.

The following describes the causes of the error.

No.

Value of aa....aa

Value of bb....bb

Value of cc....cc

Cause of the error

SQLSTATE

1

1

***

data type is incorrect

The data type of an element of the multiset value expression specified in the first argument is invalid.

427J0

2

2

***

option format is incorrect

The specification format of the function option is invalid.

427J1

3

2

***

option is duplicated

The function option is specified more than once.

427J2

4

2

compression_format

option is missing

A function option that cannot be omitted is not specified.

427J3

5

2

compression_format

value is incorrect

The value specified in the function option is invalid.

427J4

6

2

field_num

7

2

binary_string_format

8

2

enclosing_char

9

2

delimiter_char

10

2

field_num

field data number is duplicated

The field data number is specified more than once.

427J5

11

2

binary_string_format

12

2

field_num

over specified num

The number of specified field data numbers exceeds the upper limit.

427J6

13

2

field_num

the number of field_num numbers is not the same as the number of columns in the table function column list

The number of field data numbers is different from the number of columns in the table function column list corresponding to the table function derived table.

427J7

14

2

binary_string_format

the value for the binary_string_format option is not specifiable for a field_num option

The field data number specified in the binary string format option is invalid.

Select a field data number from those specified in the specification column option.

427J8

15

2

binary_string_format

only a number corresponding to a binary data type column can be specified for the field data number

The field data number specified in the binary string format option is invalid.

The field data specified for the field data number is not binary type data.

427J9

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30326-E

The length or precision of the data entered for a dynamic parameter (item aaaa) is invalid. (M+J+O)

The data that was input for the dynamic parameter has one of the following errors.

If the input data is a fixed-point number represented as decimal data, the number of decimal digits specified does not match the precision. <SQLSTATE: 22003>

If the input data is floating-point numeric data, the input data is NaN (not a numeric) or infinity. <SQLSTATE: 22003>

If the input data is datetime data, the data format is invalid, or the specified datetime does not exist. <SQLSTATE: 22007>

If the input data is fixed-length character string data, its length is invalid. <SQLSTATE: 22505>

If the input data is variable-length character string data or variable-length binary data, the length of the input data exceeds the maximum or is less than 0. <SQLSTATE: 22505>

The input data's indicator value is invalid. <SQLSTATE: 22521>

aaaa:

The order number of the invalid input data

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the input data or its indicator value.

Specify values for the data type and data length that are valid for the dynamic parameters assumed to be in the input data. For details about the data types and data lengths that are valid for dynamic parameters, see Variables (dynamic parameters) in the manual HADB SQL Reference.

For details about the data formats of input data, see Data Types in the manual HADB SQL Reference.

For details about the indicator values, see a_rdb_SQLInd_t (indicator) in the HADB Application Development Guide.

KFAA30361-E

A character string expression specified in a scalar function does not match the specified format. (function name = "aa....aa", position = bb) (M+J+O)

A character string representation used in scalar function "aa....aa" does not match the format specification. <SQLSTATE: 2250G>

aa....aa:

Scalar function name

bb: Location that does not match

This indicates byte bb in the format specification. Byte 1 is the first character that is not a single-byte space in the format specification.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Specify a character string that matches the format specification or correct the format specification.

KFAA30401-E

The data types of both operands specified in predicate "aa....aa" are not compatible. (query number = bb....bb) (M+J+O)

The data types of the results of the value expression or row value constructors specified in predicate aa....aa cannot be compared to each other or converted. <SQLSTATE: 42801>

aa....aa: Type of predicate

BETWEEN: A BETWEEN predicate

COMPARISON: A comparison predicate

IN: An IN predicate

LIKE: LIKE predicate

LIKE_REGEX: LIKE_REGEX predicate

QUANTIFIED: A quantified predicate

bb....bb: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30402-E

The data type of the argument in the aggregate function "aa....aa" is invalid. (query number = bb....bb) (M+J+O)

The data type of the aggregated argument in set function aa....aa is invalid. Another possibility is that the data type of an argument in an inverse distribution function is invalid. <SQLSTATE: 42712>

aa....aa:

Name of set function

bb....bb: Position number of the query that specified the set function

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30403-E

"aa....aa"."bb....bb" cannot be specified for the set function "cc....cc". (query number = dd....dd) (M+J+O)

"aa....aa"."bb....bb" cannot be specified in set function cc....cc. <SQLSTATE: 42713>

aa....aa:

Table identifier, correlation name, or query name

bb....bb:

Column name

cc....cc:

Name of set function

dd....dd: Position number of the query that specified the set function

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30404-E

The input data is longer than the defined column. (column name = "aa....aa") (M+J+O)

The input data is longer than the column. <SQLSTATE: 22001>

aa....aa: The column name that caused the error

If the column name cannot be output, *** is displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the substitution source data.

KFAA30405-E

The numeric literal is outside the valid range. (M+J+O)

A numeric literal that is outside the specification range was specified. The range for numeric literal specifications is as follows: <SQLSTATE: 42513>

Decimal literals: -(10³⁸-1) to -10⁻³⁸, 0, or 10⁻³⁸ to (10³⁸-1)

More than 38 digits were specified.

Floating-point numeric literals: About -1.7 × 10³⁰⁸ to 1.7 × 10³⁰⁸

The number of digits specified in the mantissa exceeds 17, or the number of digits specified in the exponent exceeds 3.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the numeric literal specification.

KFAA30406-E

An invalid data type was specified in an operation. (operation = aa....aa, query number = bb....bb) (M+J+O)

An invalid data type was specified in the operand of an operator. <SQLSTATE: 42802>

aa....aa: Operation type

ARITHMETIC: An arithmetic operation

bb....bb: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30407-E

A data type other than a character string type is specified in the "aa....aa" predicate. (query number = bb....bb) (M+J+O)

The data type of the value expression specified in the aa....aa predicate is not character string data. <SQLSTATE: 42801>

aa....aa: Type of predicate

LIKE: A LIKE predicate

LIKE_REGEX: A LIKE_REGEX predicate

bb....bb: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30408-E

The update value or insert value is not compatible with the data type of column "aa....aa". (M+J+O)

The data type of the update value or insertion value is not a data type that can be converted. <SQLSTATE: 42803>

aa....aa:

Column name of update column or insertion column

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30410-E

The numeric literal aa....aa is invalid. (M+J+O)

The numeric literal that was specified is invalid. <SQLSTATE: 42511>

aa....aa:

Invalid numeric literal

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the numeric literal.

KFAA30411-E

An invalid data type was specified in a concatenation operation. (query number = aa....aa) (M+J+O)

An invalid data type was specified in the first or second operand of a concatenation operation. <SQLSTATE: 42802>

aa....aa: Position number of the query that specified the invalid concatenation operation

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the specified concatenation operation.

KFAA30413-E

An invalid data type was specified with an arithmetic operator for the datetime operation. (query number = aa....aa) (M+J+O)

A data type that cannot be specified in a datetime operation was specified with an arithmetic operator. <SQLSTATE: 42780>

aa....aa: Position number of the query that specified the invalid datetime operation

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30414-E

Labeled duration can be specified only for the operands of plus or minus operations involving datetime data. (query number = aa....aa) (M+J+O)

Labeled durations can only be specified for the operands of addition and subtraction operations on datetime data. <SQLSTATE: 42780>

aa....aa: Position number of the query that specified the invalid labeled duration

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30415-E

The method of specifying the labeled duration is invalid. (reason = aa....aa, query number = bb....bb) (M+J+O)

The specification of the labeled duration is invalid.

aa....aa: Cause of the error

the combination of the datetime data type that is the target of the operation and the labeled duration modifier is invalid: The combination of the datetime data that is the target of the operation and the labeled duration qualifier is invalid. <SQLSTATE:4278G>

a left data type of the labeled duration modifier is wrong: The data type of value-expression-primary specified in the labeled duration is invalid. <SQLSTATE:4278H>

the data type specified for multiplication or division is incorrect: The data type specified for multiplication or division for the labeled duration is invalid. <SQLSTATE:4278I>

bb....bb: Position number of a query that specified an invalid labeled duration qualifier

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30416-E

The character expression for the data type "aa....aa" is invalid. (M+J+O)

A representation that uses a character string is invalid. <SQLSTATE: 22007>

aa....aa: Invalid literal

DATE: A date literal

TIME: A time literal

TIMESTAMP: A time stamp literal

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the data of the representation that uses a character string.

KFAA30417-E

The dynamic parameter cannot be specified in both operands of a comparison predicate or in the left operand of other predicates. (query number = aa....aa) (M+J+O)

One of the following errors is found. <SQLSTATE:42770>

A dynamic parameter has been specified on both sides of a comparison predicate.

If a row value constructor is specified on both sides of the comparison predicate, the dynamic parameter is specified for both corresponding row value constructor elements.

A dynamic parameter has been specified in a value expression on the left side of a predicate.

aa....aa: Position number of the query that specified the dynamic parameter

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30418-E

The dynamic parameter cannot be specified in aa....aa. (M+J+O)

A dynamic parameter cannot be specified in aa....aa. <SQLSTATE: 42550>

aa....aa: Invalid specification

a selection expression: Selection expression

"GROUP BY" clause: GROUP BY clause

"ORDER BY" clause: ORDER BY clause

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30419-E

The specification of dynamic parameters is invalid. (operation = aa....aa, query number = bb....bb) (M+J+O)

The dynamic parameter specified in an operation is invalid. <SQLSTATE: 42771>

aa....aa: Operation type

ARITHMETIC: A dynamic parameter is specified on both sides of an arithmetic operator.

SET FUNCTION: A dynamic parameter is specified in a set function.

CASE expression: The specification of a dynamic parameter in a CASE expression is invalid.

CONCATENATION: A dynamic parameter is specified as an operator in a concatenation operation.

window function: A dynamic parameter is specified in a window function.

BIT OPERATION: A dynamic parameter is specified in a bit operation.

bb....bb: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30420-E

The result of aa....aa exceeds 32,000 bytes. (query number = bb....bb) (M+J+O)

The maximum length of the result of aa....aa exceeds 32,000 bytes. <SQLSTATE: 42812>

aa....aa: Operation type

CONCATENATION: Concatenation operation

bb....bb: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30421-E

An error occurred while trying to execute a scalar function. (function name = aa....aa, query number = bb....bb, details = cc....cc) (M+J+O)

An error occurred while trying to execute scalar function aa....aa.

The character string returned by scalar function TRANSLATE exceeded the permitted data length for execution results. <SQLSTATE: 22001>

An overflow error occurred in numeric data. <SQLSTATE: 22003>

An overflow error occurred in datetime data. <SQLSTATE: 22008>

A division by zero error occurred. <SQLSTATE: 22012>

An out-of-range value was specified in the LN scalar function. <SQLSTATE: 2201E>

An out-of-range value was specified in the POWER or SQRT scalar function. <SQLSTATE: 2201F>

An out-of-range value was specified in a scalar function. <SQLSTATE: 2250H>

aa....aa:

Scalar function name

bb....bb: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

cc....cc: Error detail message

division by zero error: A division by zero error occurred.

domain error: An out-of-range value was specified in a scalar function.

overflow error: An overflow occurred.

data length insufficient: The returned value cannot be stored due to the limit on the data length for scalar function execution results.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The following table shows the corrective action to take:

Error detail message

(cc....cc)

Corrective action to take

division by zero error

Correct the SQL statement so that the division by zero error will not occur.

For details about the condition that results in a division by zero error, see Scalar Functions in the manual HADB SQL Reference (see the details of the scalar function displayed in place of aa....aa).

domain error

Correct the SQL statement so that an out-of-range value will not be passed to the scalar function.

For details about the value range permitted for the scalar function, see description of the scalar function displayed in place of aa....aa under Scalar Functions in the manual HADB SQL Reference.

overflow error

Correct the SQL statement so that an overflow error will not occur.

data length insufficient

Correct the SQL statement to increase the data length for scalar function execution results. If this message was issued when scalar function TRANSLATE was executing, see Rules in TRANSLATE in the manual HADB SQL Reference.

KFAA30424-E

The specification of the value of "aa....aa" of a "LIKE predicate" is invalid. (details = bb....bb) (M+J+O)

The specification of the value expression specified for aa....aa of the LIKE predicate is invalid.

aa....aa:

escape character: Escape character

bb....bb: Cause of the error

data length error: The data length of the value expression specified for the escape character is invalid. <SQLSTATE: 22019>

escape character value error: The data content of the value expression specified for the escape character is invalid. <SQLSTATE: 2250A>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the specified escape character, and then retry the operation.

KFAA30425-E

An invalid data type was specified in scalar function. (argument number = aa....aa, function name = "bb....bb", query number = cc....cc) (M+J+O)

The argument aa....aa of scalar function bb....bb contains an error. <SQLSTATE: 42782>

aa....aa: Number of the argument that contains the error

For example, if bb....bb is SUBSTR and 2 is displayed, it means there is an error in the specification for the start position of the SUBSTR function. The specification format for the SUBSTR function is as follows:

SUBSTR(character-string-data-of-extraction-source, start-position(, number-of-characters-to-be-extracted))

bb....bb:

Scalar function name

cc....cc: Position number of the query that specified bb....bb

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement according to rules for scalar function bb....bb. For details about the rules for scalar functions, see Scalar Functions in the manual HADB SQL Reference.

The possible errors are as follows:

Data whose data type cannot be specified for the argument indicated by aa....aa is specified

For the argument indicated by aa....aa, specify data whose data type can be specified.

The data type of the data specified for the argument indicated by aa....aa cannot be compared with the data type of the data specified for other arguments

For the argument indicated by aa....aa and other arguments, specify data whose data type can be compared.

For example, if you execute the following SQL statements with character string data that is the predefined character-string representation for datetime data specified as the argument, this message might be displayed.

▪ Example of SQL statement specification (For a column specification where "CDATE" is DATE type)

COALESCE ("CDATE", '2000/01/01')

LTDECODE ('2000/01/01', '2010/01/01', 0, "CDATE", 1)

For the rules for specifying character string data that is the predefined character-string representation for datetime data, follow the rules for scalar function bb....bb. For details about the rules for scalar functions, see Scalar Functions in the manual HADB SQL Reference.

Only a single dynamic parameter is specified for the argument indicated by aa....aa

Use the scalar functions CAST or CONVERT to specify a dynamic parameter. Alternatively, do not use a dynamic parameter.

The following shows an example of specifying a dynamic parameter by using the scalar functions CAST and CONVERT.

Example of specifying a dynamic parameter by using the scalar function CAST

CAST(? AS CHAR(10))

Example of specifying a dynamic parameter by using the scalar function CONVERT

CONVERT(?, CHAR(10))

KFAA30437-E

The schema object "aa....aa"."bb....bb" is not found in the system. (object type = cc....cc) (M+J+O)

The specified schema object aa....aa.bb....bb does not exist. <SQLSTATE: 42I05>

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc: Type of schema object

TABLE: Table

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30447-E

The data types of a "THEN" or "ELSE" operand specified in a CASE expression are not compatible. (query number = aa....aa) (M+J+O)

The data types of the results of value expressions specified for THEN and ELSE in a CASE expression are not compatible. <SQLSTATE: 42806>

aa....aa: Position number of the query that specified the CASE expression that contains the error

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30448-E

At least one "THEN" operand in searched CASE must be a value expression. (query number = aa....aa) (M+J+O)

A value expression must be specified for at least one of the THEN operands specified in a CASE expression. <SQLSTATE: 42784>

aa....aa: Position number of the query that specified the CASE expression that contains the error

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30450-E

A cardinality violation occurred in the query. Two or more rows exist in the search results of "aa....aa". (query tree number = bb....bb) (M+J+O)

A cardinality violation occurred in the query at query tree number bb....bb. Two or more results were found in aa...aa at query tree number bb....bb. <SQLSTATE: 21502>

aa....aa:

SCALAR SUBQUERY: A scalar subquery

bb....bb: Query tree number of subquery that had two or more results

A query tree number is used to identify each query tree output to access path information. For details about query tree numbers, see Example of displayed access path information in About access paths in the HADB Application Development Guide.

Note that if a set operation is specified for the subquery, the following query tree number is output.

Query tree number that is output in the first QUERY SCAN(QUERY query-tree-number) under the corresponding set operation specification (SET OPERATION) in access path information

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement so that there is no more than one subquery result.

KFAA30453-E

There is an error in the specification method of a scalar function argument. (function name = "aa....aa", reason = "bb....bb", query number = cc....cc) (M+J+O)

There is an error in the specification format of scalar function aa....aa.

aa....aa:

Scalar function name

bb....bb: Cause of the error

data length insufficient: The result data was too short. <SQLSTATE: 22001>

overflow: An overflow occurred. <SQLSTATE: 22003>

format: There is an error in the character string format of the data to be converted. <SQLSTATE: 22018>

value: The value of the data to be converted is invalid. <SQLSTATE: 22018>

data type: The data type that was specified cannot be used. <SQLSTATE: 42785>

combination: An error occurred when the value expression data type was combined with the result data type. <SQLSTATE: 42807>

cc....cc: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30454-E

The viewed table "aa....aa"."bb....bb" cannot be accessed because it is invalid. (M+J+O)

The viewed table "aa....aa"."bb....bb" cannot be accessed because it is invalidated. <SQLSTATE: 4292A>

aa....aa:

Schema name of viewed table

bb....bb:

Table identifier of viewed table

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The invalidation of the viewed table must be released. For details about the corrective action to take, see Releasing a viewed table from invalidation in the HADB Setup and Operation Guide.

KFAA30458-E

The query name "aa....aa" specified in a "WITH" clause is a duplicate. (M+J+O)

The query name aa....aa has been specified more than once in a WITH clause. <SQLSTATE:42733>

aa....aa:

Query name

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30459-E

The column name "aa....aa" of viewed table "bb....bb" is already in use. (M+J+O)

Column name aa....aa has been specified more than once in viewed table bb....bb. <SQLSTATE: 42734>

aa....aa:

Column name that is duplicated

bb....bb:

Name of viewed table that has a column name that is duplicated

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The action to take differs depending on whether column names are specified.

If column names are specified

Change column names so that there is no duplication.

If column names are omitted

Duplication of a column name in the viewed table is due to duplication of a column name in a query specification. Do not omit column names, which allow column names to be specified that do not include duplicates.

If this message is output in either of the following cases, take the corrective action described under Procedure.

The ALTER VIEW statement is executed.

A viewed table is re-created during version upgrading of the HADB server.

For details, see Re-creation of viewed tables in the event of a version upgrade in Notes on version upgrading in the HADB Setup and Operation Guide.

Procedure

Check viewed table definition information.

Check the CREATE VIEW statement that was used when the target viewed table was defined. You can acquire viewed table definition information by searching a dictionary table. For details about examples of searching the dictionary table, see Finding out viewed table definition information in Searching a dictionary table in the HADB Setup and Operation Guide.

Delete the viewed table.

Delete the target viewed table by using the DROP VIEW statement.

Correct the information specified in the CREATE VIEW statement.

Correct the information specified in the CREATE VIEW statement you checked in step 1.

Redefine the viewed table by using the CREATE VIEW statement.

Use the CREATE VIEW statement you corrected in step 3 to redefine the viewed table deleted in step 2.

If this message is output because an asterisk (*) is specified in the selection expression for the query specification in the CREATE VIEW statement, do not specify the asterisk (*). Correct the information specified in the CREATE VIEW statement to explicitly specify the column name in the selection expression for the query specification.

KFAA30460-E

If a viewed table contains a column without a name, the column name specification cannot be omitted. (M+J+O)

A viewed table contains a column for which no derived column name has been set, and the column name specification was omitted. <SQLSTATE: 42929>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Specify the column name.

KFAA30464-E

The specification of the recursive query is invalid. (reason = aa....aa, with list number = bb....bb) (M+J+O)

The specification of the recursive query is invalid.

aa....aa: Cause of the error

an anchor member is not specified, or an anchor member is not specified before a recursive member:

An anchor member is not specified. Alternatively, all anchor members are not specified before a recursive member. <SQLSTATE: 427N5>

the recursive query name is specified in a subquery:

A recursive query name is specified in a subquery. <SQLSTATE: 427N6>

the recursive member is not specified in an operand of a UNION ALL set operation:

UNION ALL is not specified as the set operation for the recursive member. <SQLSTATE: 427N7>

the last anchor member specified and the first recursive member specified are not specified in the operands of a UNION ALL set operation:

UNION ALL is not specified as the set operation for the last specified anchor member and the first specified recursive member. <SQLSTATE: 427N8>

bb....bb:

List number of the WITH list element corresponding to the recursive query

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30465-E

There is an error in the specification method of Logical predicate. (reason = aa....aa, query number = bb....bb) (M+J+O)

The logical predicate specification is invalid. <SQLSTATE: 42802>

aa....aa: Description of error

the data type of the value expression is not BOOLEAN

The data type of the value expression is not BOOLEAN.

bb....bb: Position number of the query of the logical predicate with an incorrect specification

For details about the position number of the query, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30467-E

A table function derived table that includes the system-defined function "aa....aa" cannot be specified in the bb....bb. (query number = cc....cc) (M)

A table function derived table with the system-defined function aa....aa specified cannot be specified in bb....bb. <SQLSTATE: 42849>

aa....aa:

System-defined function name

bb....bb: SQL statement in which the table function derived table is specified

DELETE statement: DELETE statement

INSERT statement: INSERT statement

PURGE CHUNK statement: PURGE CHUNK statement

UPDATE statement: UPDATE statement

CREATE VIEW statement: CREATE VIEW statement

cc....cc: Position number of the query that specified the table function derived table

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30501-E

The cursor is not opened. (M+J+O)

The cursor has not been opened. <SQLSTATE: 24504>

S:

Ignores this SQL statement.

Action:

Correct the application program so that it opens the cursor, fetches the row, and then closes the cursor.

KFAA30502-E

The cursor is already opened. (M+J+O)

An attempt was made to open a cursor that is already open. <SQLSTATE: 24505>

S:

Ignores this SQL statement.

Action:

Correct the application program so that it closes the cursor before it opens the cursor again.

KFAA30505-E

Preparation of query with a cursor opened was requested. (M+J+O)

Preprocessing was requested for a query that has a cursor open. <SQLSTATE: 24506>

S:

Ignores this SQL statement.

Action:

Correct the application program so that it closes the cursor before it performs preprocessing.

KFAA30506-E

A query cannot be executed with EXECDIRECT. (M+J+O)

Queries cannot be executed with the CLI function a_rdb_SQLExecDirect(), which performs preprocessing and execution of SQL statements. <SQLSTATE: 07003>

S:

Ignores this SQL statement.

Action:

Correct the application program so that it executes the CLI functions shown below during query execution.

a_rdb_SQLPrepare() (SQL statement preprocessing)

a_rdb_SQLBindCols() (binds search result columns)

a_rdb_SQLExecute() (executes preprocessed SQL statements)

a_rdb_SQLFetch() (fetches rows)

a_rdb_SQLCloseCursor() (closes cursors)

KFAA30512-E

An SQL statement (other than a prepared query) cannot be executed. (M+J+O)

SQL statements other than queries whose SQL statement is preprocessed cannot be executed. <SQLSTATE: 07005>

S:

Ignores this SQL statement.

Action:

Correct the application program.

KFAA30547-E

Viewed tables cannot be defined from dictionary / system tables. (M+J+O)

A viewed table cannot be defined with a dictionary table or a system table as its underlying table. <SQLSTATE: 428A3>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Make a table other than a dictionary table or a system table the underlying table, and then define a viewed table.

KFAA30548-E

The user does not have permission to access the specified schema or schema object. (schema name = "aa....aa", schema object name = "bb....bb") (M+J+O)

You do not have the privileges to access the schema or schema object that was specified. <SQLSTATE: 42820>

The possible causes are as follows:

The specified schema does not exist.

The specified schema object does not exist.

You do not have access privileges to the specified schema object.

aa....aa:

Schema name

bb....bb:

Schema object name

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Check the following:

Are the correct names specified for the schema, table, and index?

Ask the HADB user who has the grant option of access privileges for the target schema object to grant you access privileges for the schema object.

If the specified schema object is a viewed table that you own, make sure that the viewed table has not been invalidated. Then, ask the HADB user who has the grant option of access privileges for the underlying table to grant you access privileges for the underlying table of the viewed table.

KFAA30549-E

The aa....aa "bb....bb" cannot be specified. (M+J+O)

The authorization identifier or schema name specification is invalid. <SQLSTATE:42I08>

The possible causes are as follows:

An attempt was made to connect to the HADB server with ALL, HADB, or PUBLIC specified as the authorization identifier.

An attempt was made to update a dictionary table or a system table (a table with a schema name of MASTER).

ALL, HADB, or PUBLIC was specified as the authorization identifier and an attempt was made to execute one of the following SQL statements:

• ALTER USER

• CREATE USER

• DROP USER

• GRANT

• REVOKE

aa....aa: Invalid specification

authorization identifier: The authorization identifier is invalid

schema: The schema name is invalid

bb....bb:

The character string specified in the authorization identifier or schema name

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the authorization identifier or schema name specified in the SQL statement.

KFAA30550-E

The aa....aa privilege is required to access the "bb....bb"."cc....cc" table. (M+J+O)

The table to be searched cannot be referenced because you do not have aa....aa. <SQLSTATE: 42K01>

aa....aa:

Privilege required to reference the table to be searched

AUDIT ADMIN: Audit admin privilege

bb....bb:

Schema name of the table that cannot be referenced

cc....cc:

Table identifier of the table that cannot be referenced

S:

Ignores this SQL statement.

Action:

Make sure that the table name to be searched is correct. If the table name is invalid, specify the correct table name. If the table name is correct, ensure that an HADB user with aa....aa searches the relevant table.

KFAA30551-E

The operation "aa....aa" cannot be executed. (reason = bb....bb) (M+J+O)

The SQL statement aa....aa could not be executed. <SQLSTATE: 42K02>

aa....aa:

SQL statement whose execution was attempted

bb....bb:

Cause of the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The following explains how to handle this:

If the grantor's access privileges do not include the grant option is displayed for bb....bb

The user who executed the GRANT statement is invalid. Execute the GRANT statement by using the authorization identifier of the HADB user who has the grant option of access privileges for the target schema object.

If the revoker's access privileges do not include the grant option is displayed for bb....bb

The user who executed the REVOKE statement is invalid. Execute the REVOKE statement by using the authorization identifier of the HADB user who granted the access privilege that is to be revoked.

KFAA30552-E

The DBA privilege is required to execute the operation in "aa....aa". (M+J+O)

The DBA privilege is required to perform aa....aa. <SQLSTATE: 42K03>

aa....aa: Operation that requires the DBA privilege

ALTER SERVER: Changing the foreign server definition

ALTER USER: Changing information about HADB users

CREATE SERVER: Defining a foreign server

CREATE USER: Creating HADB users

DROP SERVER: Deleting a foreign server

DROP USER: Deleting HADB users

GRANT AUDIT ADMIN: Granting the audit admin privilege

GRANT AUDIT VIEWER: Granting the audit viewer privilege

GRANT DBA: Granting the DBA privilege

GRANT CONNECT: Granting the CONNECT privilege

GRANT CRYPTO ADMIN: Granting the CRYPTO ADMIN privilege

GRANT SCHEMA: Granting the schema definition privilege

REVOKE DBA: Revoking the DBA privilege

REVOKE CONNECT: Revoking the CONNECT privilege

REVOKE CRYPTO ADMIN: Revoking the CRYPTO ADMIN privilege

REVOKE SCHEMA: Revoking the schema definition privilege

If multiple privileges were specified in the GRANT or REVOKE statement, only one of those privileges is displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Ensure an HADB user with the DBA privilege performs aa....aa.

Note that if aa....aa is REVOKE CRYPTO ADMIN, the HADB user who has CRYPTO ADMIN privilege can revoke the CRYPTO ADMIN privilege he has.

KFAA30555-E

The aa....aa privilege that you granted to yourself cannot be removed by you. (M+J+O)

A user cannot revoke any privilege aa....aa that the user has granted to himself or herself. <SQLSTATE: 42K05>

aa....aa: Privilege that cannot be revoked

DBA: DBA privilege

CONNECT: CONNECT privilege

AUDIT ADMIN: Audit admin privilege

If multiple privileges were specified in the REVOKE statement, only one of those privileges is displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

If this message is output when you attempt to revoke the DBA or CONNECT privilege

You cannot revoke the DBA or CONNECT privilege granted to you. Ask another HADB user who has the DBA privilege to revoke your DBA or CONNECT privilege.

If this message is output when you attempt to revoke the audit admin privilege

If you are the only HADB user who has both the audit admin privilege and CONNECT privilege, you cannot revoke your audit admin privilege. Therefore, if you want to change the HADB user who has the audit admin privilege, you must first grant the audit admin privilege and CONNECT privilege to another HADB user. Then, revoke your audit admin privilege. An HADB user who has the DBA privilege must grant the audit admin privilege and CONNECT privilege.

If this message is output when you attempt to revoke your audit admin privilege in order to stop operation of the audit trail facility, follow the procedure in Stopping use of the audit trail facility in the HADB Setup and Operation Guide.

KFAA30556-E

The operation cannot be executed because the authorization identifier "bb....bb" specified in aa....aa is cc....cc. (M+J+O)

The aa....aa operation could not be executed. <SQLSTATE: 42K06>

aa....aa: Operation whose execution was attempted

GRANT: Granting of a privilege by a GRANT statement

GRANT AUDIT ADMIN: Granting the audit admin privilege by a GRANT statement

GRANT AUDIT VIEWER: Granting the audit viewer privilege by a GRANT statement

GRANT CRYPTO ADMIN: Granting the CRYPTO ADMIN privilege by a GRANT statement

REVOKE: Revocation of a privilege by a REVOKE statement

REVOKE CONNECT: Revocation of a CONNECT privilege by a REVOKE statement

REVOKE CRYPTO ADMIN: Revocation of a CRYPTO ADMIN privilege by a REVOKE statement

REVOKE DBA: Revocation of a DBA privilege by a REVOKE statement

REVOKE SCHEMA: Revocation of a schema definition privilege by a REVOKE statement

bb....bb:

Authorization identifier specified in the SQL statement

cc....cc:

Cause of the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The following explains how to handle this:

If the owner of the target schema object is displayed for cc....cc

The authorization identifier whose privilege is to be granted or revoked is the authorization identifier of the schema object owner. Check if the specified authorization identifier and the specified schema object are correct.

If connected to the HADB server is displayed for cc....cc

The CONNECT privileges cannot be revoked for an authorization identifier that is currently connected to the HADB server. Re-execute the REVOKE statement after the target authorization identifier has been disconnected from the HADB server.

If you want to revoke the CONNECT privilege immediately, use the adbcancel command to forcibly disconnect the target authorization identifier from the HADB server.

If a special keyword that can be specified only by the owner of the target schema object is displayed for cc....cc

To execute the GRANT statement with PUBLIC specified, use the authorization identifier of the owner of the target schema object for access privileges.

If a user with privileges on which the privileges you are trying to grant depend is displayed for cc....cc

An attempt is made to grant access privileges to an HADB user who cannot be granted access privileges. You cannot grant access privileges to the following HADB users:

An HADB user who has granted himself or herself the target access privilege

An HADB user on the line of users who granted the target access privilege to the above HADB user

Yourself

If the auditor is displayed for cc....cc

You cannot revoke the CONNECT privilege and schema definition privilege of an HADB user who has the audit privilege. Revoke the audit privilege, and then revoke the CONNECT privilege or schema definition privilege. An HADB user who has the audit admin privilege must revoke the audit privilege.

If a user who has the CRYPTO ADMIN privilege is displayed for cc....cc

You cannot revoke the CONNECT privilege of an HADB user who has the CRYPTO ADMIN privilege. Revoke the CRYPTO ADMIN privilege, and then revoke the CONNECT privilege. An HADB user who has the DBA privilege must revoke the CRYPTO ADMIN privilege. An HADB user having the CRYPTO ADMIN privilege can revoke their own CRYPTO ADMIN privilege.

If the last user who has the CRYPTO ADMIN privilege is displayed for cc....cc

At least one HADB user with CRYPTO ADMIN privilege is required. Therefore, when there is only one HADB user with CRYPTO ADMIN privilege, it is not possible to revoke CRYPTO ADMIN privilege from that HADB user. After granting another HADB user CRYPTO ADMIN privilege, re-execute the REVOKE statement.

If a user who does not have the CONNECT privilege is displayed for cc....cc

You cannot grant the CRYPTO ADMIN privilege to an HADB user who has the CONNECT privilege. Therefore, when granting CRYPTO ADMIN privilege to an HADB user who does not have CONNECT privilege, also grant them CONNECT privilege at the same time. Or, grant the HADB user who has CONNECT authority CRYPTO ADMIN privilege.

If a user who uses PAM or Keycloak authentication is displayed for cc....cc

An attempt is made to grant privileges that cannot be granted to an HADB user that uses PAM authentication or Keycloak authentication. Specify the authorization identifier of the HADB user who is using database authentication and then re-execute the GRANT statement.

If the last user who has both DBA and CONNECT privileges and who uses database authentication is displayed for cc....cc

At least one HADB user with DBA and CONNECT privileges is required, using database authentication as the user authentication method. Therefore, when there is only one such HADB user, it is not possible to revoke privileges from that HADB user.

Re-execute the REVOKE statement after confirming that database authentication is used for the user authentication method and that there are two or more HADB users with DBA and CONNECT privileges.

If the owner of the foreign servers is displayed for cc....cc

The REVOKE statement resulted in an error because the HADB user, who attempted to revoke DBA privileges, owns foreign servers. Revoking DBA privileges from HADB users who own external servers will have the following impacts.

The foreign servers owned by the user will be deleted.

Foreign tables that use the foreign server being deleted will be deleted.

View tables that depend on the deleted foreign tables will be deleted or invalidated.

If there are no problems, execute the REVOKE statement with CASCADE specified for the drop behavior or without specifying the drop behavior. For details on specifying the drop behavior, see REVOKE (revoke privileges) in the manual HADB SQL Reference.

Note

Even if multiple authorization identifiers cause an error, only the error message for one of them will be output.

KFAA30559-E

The operation "aa....aa" cannot be executed using an authorization identifier "bb....bb" that does not exist. (M+J+O)

An attempt was made to perform aa....aa on nonexistent authorization identifier bb....bb. <SQLSTATE: 42K07>

aa....aa: Operation attempted

ALTER USER: Changing information about HADB users

DROP USER: Deleting HADB users

GRANT: Granting the privileges

REVOKE: Revoking the privileges

bb....bb:

Specified authorization identifier

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Re-execute the SQL statement with an existent authorization identifier specified.

Note

Even if multiple authorization identifiers cause an error, only the error message for one of them will be output.

KFAA30560-E

The specified password is invalid. (M+J+O)

The specified password violates the password specification rules. <SQLSTATE: 28501>

Possible causes are as follows:

The specified password contains a syntax error.

The specified password exceeds 255 bytes.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the password specification, and then re-execute the SQL statement.

For details about the password specification rules, see Specification format and rules for the CREATE USER statement or Specification format and rules for the ALTER USER statement in the manual HADB SQL Reference.

KFAA30561-E

The specified authorization identifier or password is invalid. (M+J+O)

The specified authorization identifier or password is invalid. <SQLSTATE: 28502>

Possible causes are as follows:

The specified authorization identifier does not exist.

An invalid password was specified.

The specified authorization identifier does not have the CONNECT privilege.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Specify the correct authorization identifier or password, and then re-execute the SQL statement.

If the specified authorization identifier and password are correct, the specified authorization identifier might not have the CONNECT privilege. For details about how to determine the privileges that have been granted to a specified authorization identifier, see Checking the user privileges and schema operation privilege granted to an HADB user in the HADB Setup and Operation Guide. If the authorization identifier does not have the CONNECT privilege, grant the CONNECT privilege.

KFAA30562-E

The user of the specified authorization identifier cannot be deleted. (reason = aa....aa) (M+J+O)

The HADB user having the authorization identifier specified in the DROP USER statement cannot be deleted. <SQLSTATE: 42K19>

aa....aa: Cause of the error

users cannot delete themselves: The user attempted to delete his or her own account.

users cannot delete schemas they own: The user owns schemas.

users cannot delete foreign servers they own: The user owns foreign servers.

the user is connected to the HADB server: The user is connected to the HADB server.

the user grants access privileges to other users: The user has granted access privileges to other HADB users.

the user is the auditor: The user has the audit privilege.

the last user who has the CRYPTO ADMIN privilege cannot be deleted: The last HADB user with CRYPTO ADMIN privilege.

the last user who has both DBA and CONNECT privileges and who uses database authentication cannot be deleted: The last HADB user who uses database authentication for the user authentication method and who has DBA and CONNECT privileges.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take the following action depending on the cause of error displayed in aa....aa:

If aa....aa is users cannot delete themselves:

A user cannot delete an HADB user assigned one's own authorization identifier. Specify an authorization identifier that belongs to another HADB user.

To delete an HADB user assigned one's own authorization identifier, ask another HADB user with the DBA privilege to execute the DROP USER statement.

If aa....aa is users cannot delete schemas they own:

The DROP USER statement resulted in an error because the HADB user subject to deletion owns schemas. Check if the schemas, tables, and indexes owned by the HADB user with the specified authorization identifier can be deleted.

If the tables owned by the HADB user are deleted by executing the DROP USER statement, the viewed tables and foreign keys of other schemas are affected as described below.

Viewed tables (viewed tables of other schemas) that depend on a table deleted by executing the DROP USER statement are deleted (or invalidated).

Foreign keys (foreign keys of other schemas) whose referenced table is deleted by executing the DROP USER statement are deleted.

If there is no problem with the above influence, execute the DROP USER statement with CASCADE specified for drop behavior or without specifying the drop behavior. For details about the drop behavior specification, see Specification format and rules for the DROP USER statement in the manual HADB SQL Reference.

If aa....aa is users cannot delete foreign servers they own:

The DROP USER statement resulted in an error because the HADB user subject to deletion owns foreign servers. Check if the foreign servers owned by the HADB user having the specified authorization identifier can be deleted.

If the foreign tables that uses foreign servers owned by the HADB user are deleted by executing the DROP USER statement, the viewed tables of other schemas are affected as described below.

Viewed tables (viewed tables of other schemas) that depend on a foreign table using a foreign server deleted by executing the DROP USER statement are deleted (or invalidated).

If there is no problem with the above influence, execute the DROP USER statement with CASCADE specified for drop behavior or without specifying the drop behavior. For details about the drop behavior specification, see Specification format and rules for the DROP USER statement in the manual HADB SQL Reference.

If aa....aa is the user is connected to the HADB server:

An HADB user assigned an authorization identifier currently connected to the HADB server cannot be deleted. Execute the DROP USER statement after the specified authorization identifier has been disconnected from the HADB server.

If you want to delete the HADB user immediately, use the adbcancel command to forcibly disconnect the target authorization identifier from the HADB server.

If aa....aa is the user grants access privileges to other users:

The DROP USER statement resulted in an error because the HADB user subject to deletion has granted access privileges to other HADB users. Take one of the following corrective actions:

Revoke all access privileges granted to other HADB users by the HADB user whose authorization identifier is to be deleted. Then, re-execute the DROP USER statement.

Make sure that no problem occurs even if all access privileges granted to other HADB users are revoked by the HADB user whose authorization identifier is to be deleted. Then, re-execute the DROP USER statement with CASCADE specified for the drop behavior.

If aa....aa is the user is the auditor:

An HADB user who has the audit privilege cannot be deleted. Revoke the audit privilege, and then delete the HADB user. An HADB user who has the audit admin privilege must revoke the audit privilege.

If aa....aa is the last user who has the CRYPTO ADMIN privilege cannot be deleted

At least one HADB user with CRYPTO ADMIN privilege is required. Therefore, when there is only one HADB user with CRYPTO ADMIN privilege, it is not possible to delete that HADB user. After granting another HADB user the CRYPTO ADMIN privilege, delete the HADB user.

If aa....aa is the last user who has both DBA and CONNECT privileges and who uses database authentication cannot be deleted

At least one HADB user with DBA and CONNECT privileges is required, using database authentication as the user authentication method. Therefore, when there is only one such HADB user, that HADB user cannot be deleted.

Delete the HADB user after confirming that there are at least two HADB users with DBA and CONNECT privileges and that database authentication is used as the user authentication method.

KFAA30563-E

The SQL cannot be executed before a connection is established. (M+J+O)

An SQL statement could not be executed because no connection has been established to the HADB server. <SQLSTATE: 54201>

S:

Ignores this SQL statement.

Action:

Carefully review the application program. Check the SQL statement call sequence, and then correct any errors found.

If you are using the multi-node function, the connection with the HADB server might have already been disconnected by the adbcancel command or the like. If an SQL statement is executed in such situations, this message might be output. In this case, reconnect to the HADB server, and then re-execute the SQL statement.

KFAA30564-E

The authorization identifier "aa....aa" is invalid. (reason = bb....bb) (M+J+O)

The specified authorization identifier aa....aa is invalid due to one of the following reasons:

The length of the authorization identifier is outside the range of 1 to 100 bytes. <SQLSTATE: 42529>

A character that is not an alphanumeric character was specified. <SQLSTATE: 42539>

A character that cannot be specified with normal identifiers was specified. <SQLSTATE: 42539>

If there is a nondisplaying character in the specified authorization identifier, the identifier might not display correctly.

aa....aa: Authorization identifier or invalid character

If the authorization identifier cannot be displayed, * is displayed.

bb....bb: Cause of the error

string error: A non-alphanumeric character or a character that cannot be specified in a normal identifier was specified.

length error: The length of the authorization identifier is outside the range of 1 to 100 bytes.

S:

Ignores the processing.

Action:

Correct the authorization identifier specification.

Note

Even if multiple authorization identifiers cause an error, only the error message for one of them will be output.

KFAA30565-E

Argument aa....aa in the CLI function is invalid. (M+J+O)

A CLI function argument is invalid. <SQLSTATE: 54001>

aa....aa:

Invalid argument

S:

Ignores this SQL statement.

Action:

Correct the argument.

Note that if the return code of the CLI function is -565 and this message is not output, the value of the argument ConnectionHandle might be invalid.

KFAA30566-E

The specified authorization identifier is currently being used. (M+J+O)

The specified authorization identifier is already in use. <SQLSTATE: 42K43>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Specify a valid authorization identifier.

KFAA30572-E

The privilege "aa....aa" that is specified in the statement "bb....bb" is duplicated. (M+J+O)

A privilege specified in a GRANT or REVOKE statement is duplicated. <SQLSTATE: 425D7>

aa....aa: Type of privilege that is duplicated

DBA: DBA privilege

CONNECT: CONNECT privilege

SCHEMA: Schema definition privilege

AUDIT ADMIN: Audit admin privilege

AUDIT VIEWER: Audit viewer privilege

CRYPTO ADMIN: CRYPTO ADMIN privilege

SELECT: SELECT privilege

INSERT: INSERT privilege

UPDATE: UPDATE privilege

DELETE: DELETE privilege

TRUNCATE: TRUNCATE privilege

COPY: COPY privilege

REFERENCES: REFERENCES privilege

IMPORT TABLE: IMPORT TABLE privilege

REBUILD INDEX: REBUILD INDEX privilege

GET COSTINFO: GET COSTINFO privilege

EXPORT TABLE: EXPORT TABLE privilege

MERGE CHUNK: MERGE CHUNK privilege

CHANGE CHUNK COMMENT: CHANGE CHUNK COMMENT privilege

CHANGE CHUNK STATUS: CHANGE CHUNK STATUS privilege

ARCHIVE CHUNK: ARCHIVE CHUNK privilege

UNARCHIVE CHUNK: UNARCHIVE CHUNK privilege

bb....bb:

SQL statement that was executed

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Delete the duplicated privilege specification.

KFAA30575-E

The operation "aa....aa" cannot be executed, because the audit trail facility is INACTIVE. (M+J+O)

The aa....aa operation cannot be performed because the audit trail facility is disabled. <SQLSTATE: 52011>

aa....aa: Operation that could not be performed

CREATE AUDIT: Defining an audit target

DROP AUDIT: Deleting an audit target definition

REVOKE AUDIT ADMIN: Revoking the audit admin privilege

REVOKE AUDIT VIEWER: Revoking the audit viewer privilege

audit trail search by using the system-defined function ADB_AUDITREAD: Searching for an audit trail by using the ADB_AUDITREAD function

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Execute the adbaudittrail --start command to enable the audit trail facility. Then, retry the aa....aa operation.

If this message (aa....aa indicates REVOKE AUDIT ADMIN) is output when you attempt to revoke your audit admin privilege in order to stop using the audit trail facility, the operation failed for one of the following reasons:

Another HADB user has the audit privilege.

You have the audit viewer privilege.

In this case, use the following procedure:

Enable the audit trail facility.

Revoke the audit privilege of the other HADB user.

Revoke your audit viewer privilege.

Disable the audit trail facility.

Revoke your audit admin privilege.

KFAA30577-E

The schema definition privilege cannot be deleted because the user of the specified authorization identifier "aa....aa" owns the schema. (M+J+O)

The schema definition privilege cannot be deleted because the HADB user assigned the authorization identifier specified in the REVOKE statement owns the schema. <SQLSTATE: 42K10>

aa....aa:

Authorization identifier specified in the REVOKE statement

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The REVOKE statement resulted in an error because the HADB user whose schema definition privilege was to be deleted owns the schema. Check if the schemas, tables, and indexes owned by the HADB user having the specified authorization identifier can be deleted.

If the tables owned by the HADB user are deleted by executing the REVOKE statement, the viewed tables and foreign keys of other schemas are affected as described below.

Viewed tables (viewed tables of other schemas) that depend on a table deleted by executing the REVOKE statement are deleted (or invalidated).

Foreign keys (foreign keys of other schemas) whose referenced table is deleted by executing the REVOKE statement are also deleted.

If there is no problem with the above influence, execute the REVOKE statement with CASCADE specified for drop behavior or without specifying the drop behavior. For details about the drop behavior specification, see Revoking user privileges, schema operation privileges, audit privileges, and CRYPTO ADMIN privileges in the manual HADB SQL Reference.

Note

Even if multiple authorization identifiers cause an error, only the error message for one of them will be output.

KFAA30579-E

The schema definition privilege is required to execute the operation "aa....aa". (M+J+O)

The schema definition privilege is required to perform the operation aa....aa. <SQLSTATE: 42K12>

aa....aa: Operation that requires the schema definition privilege

CREATE SCHEMA: Defining schemas

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Ensure an HADB user with the DBA privilege grants the schema definition privilege.

KFAA30601-E

"aa....aa"."bb....bb" of cc....cc is duplicated. (M+J+O)

The table name, index name, or constraint name specified in one of the following SQL statements is already in use: <SQLSTATE: 42I13>

ALTER TABLE statement

CREATE TABLE statement

CREATE INDEX statement

CREATE VIEW statement

This also applies to the indexes and the constraint names that HADB attempted to automatically define according to the specified uniqueness constraint definition. In addition, this also applies to the indexes that HADB attempted to define for archive range columns according to the chunk-archive specification.

aa....aa:

Schema name

bb....bb:

Table identifier, index identifier, or constraint name

cc....cc:

table: Table

index: Index

constraint: Constraint

an archive range column: Archive range column

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

If cc....cc is table, index, or constraint

Correct the table name, index name, or constraint name specified in the SQL statement.

If cc....cc is an archive range column

The index identifier specified for RANGEINDEXNAME in the chunk-archive specification is already used. Correct the specified index identifier.

KFAA30602-E

The number of columns in the table exceeds 4,000. (M+J+O)

The number of columns in the table exceeds the upper limit of 4,000. <SQLSTATE: 425C0>

S:

Ignores this SQL statement.

Action:

If there is an error in the SQL statement, correct it. Alternatively, reduce the number of columns in the table to 4,000 or fewer.

KFAA30604-E

The aa....aa of the data type "bb....bb" is invalid. (M+J+O)

The length, precision, or scale of a data type is invalid. <SQLSTATE: 42590>

aa....aa: Cause of the error

precision of the decimal number for the seconds: Fractional seconds precision

length: Length

precision: Precision

scale: Scale

bb....bb: Invalid data type

BINARY: BINARY type

CHAR: CHAR type

DECIMAL: DECIMAL type or NUMERIC type

TIME: TIME type

TIMESTAMP: TIMESTAMP type

VARBINARY: VARBINARY type

VARCHAR: VARCHAR type or STRING type

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30607-E

Definition SQL statements cannot be used on another user's aa....aa. (M+J+O)

Schema belonging to other HADB users cannot be changed. <SQLSTATE:42K14>

This message is output in the following cases:

If a schema name that does not belong to the executing HADB user was specified when a base table, viewed table, foreign table, or index is defined.

If a schema name that does not belong to the executing HADB user was specified when a base table, viewed table, foreign table, or index is deleted.

If a schema name that does not belong to the executing HADB user was specified when a viewed table is re-created.

If an attempt was made to define an index in a base table that specifies a schema name that does not belong to the executing HADB user when an index is defined.

This message is also output if the schema name specified in a definition SQL statement is different from the authorization identifier that was in use when an HADB server was connected.

aa....aa:

schema: Schema

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

If the specified schema name contains errors, correct the errors. Alternatively, check whether the authorization identifier in use when the HADB server was connected is incorrect.

KFAA30609-E

Unable to aa....aa in FIX table. (M+J+O)

The following operations cannot be performed for a FIX table: <SQLSTATE: 42I14>

Define a column of the variable-length data type.

Specify the chunk-archive specification.

Define a table as a column store table.

aa....aa: Cause of the error

define variable length column: Definition of a column of the variable-length data type

specify the "ARCHIVABLE" option: Chunk-archive specification

specify the "STORAGE FORMAT COLUMN" option: Definition of a column store table (COLUMN is specified for the STORAGE FORMAT option.)

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Check and, if necessary, revise the CREATE TABLE or ALTER TABLE statement.

When defining a FIX table, do not define or specify any of the following:

Define a column of the variable-length data type.

Chunk-archive specification

Define a column store table (Specify COLUMN for the STORAGE FORMAT option).

If any of the following conditions applies, cancel the FIX specification.

When defining a column of the variable-length data type

When specifying a chunk-archive

When defining a column store table (When specifying COLUMN for the STORAGE FORMAT option)

KFAA30612-E

The column name "aa....aa" is duplicated. (M+J+O)

A column name has been used more than once. <SQLSTATE: 42I15>

aa....aa:

The column name that caused the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

If this message is output when column definitions are omitted in the CREATE FOREIGN TABLE statement, take one of the following corrective actions:

The column names in the schema information of the PARQUET format foreign data files are duplicated. Change the column names to ensure there are no duplicates in the foreign data.

The column names included in the metadata of the referenced Iceberg table are duplicated. Change the column names to ensure there are no duplicates.

KFAA30613-E

A column cannot be aa....aa a table(reason = bb....bb). (M+J+O)

You cannot use the ALTER TABLE statement to add or delete a column. <SQLSTATE: 53021>

aa....aa: Operation that resulted in an error

added to: Addition of a column by a ALTER TABLE statement

deleted from: Deletion of a column by a ALTER TABLE statement

bb....bb: Reason why the column cannot be added or deleted

A fix table in which data was stored at least once:

You cannot add or delete a column for a FIX table to which row storage segments have been allocated.

A table in which data has been stored at least once and for which BRANCH ALL option is specified:

You cannot add or delete a column for a base table for which BRANCH ALL is specified in the CREATE TABLE statement, and to which segments for storing rows are assigned

An archivable multi-chunk table:

You cannot delete columns for archivable multi-chunk tables.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take one of the following corrective actions:

If aa....aa is added to

See When a column cannot be added to a base table in the HADB Setup and Operation Guide to add a column.

If aa....aa is deleted from

Take one of the following actions:

A fix table in which data was stored at least once

See Deleting a column after deleting all rows in a base table in Deleting columns of a base table in the manual HADB Setup and Operation Guide and delete the column.

A table in which data has been stored at least once and for which BRANCH ALL option is specified

See Deleting a column after deleting all rows in a base table in Deleting columns of a base table in the manual HADB Setup and Operation Guide and delete the column.

An archivable multi-chunk table

See Deleting a column in a archivable multi-chunk table in Deleting columns of a base table in the manual HADB Setup and Operation Guide and delete the column.

KFAA30614-E

A B-tree index cannot be created in column "aa....aa". (reason = "bb....bb") (M)

Columns of the following data types cannot be specified for B-tree indexed columns: <SQLSTATE: 42I16>

BINARY type

VARBINARY type

aa....aa:

Name of the column whose data type caused the error

bb....bb: Cause of the error

The data type of the column is BINARY: The data type of the column is BINARY.

The data type of the column is VARBINARY: The data type of the column is VARBINARY.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

A B-tree index cannot be defined for column aa....aa. Check and, if necessary, revise the column data type, indexed column, or other aspects of the database design.

KFAA30616-E

The B-tree index key length exceeded the maximum length. (M+J+O)

The length of a B-tree index key exceeds the maximum length. <SQLSTATE: 56007>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take one of the following corrective actions:

Make the page size larger for the DB area that stores the B-tree index.

Correct the B-tree index key length so that it is no greater than the maximum length.

If this message was issued while a CREATE INDEX statement was executing, check the maximum length for B-tree index keys by referencing Rules in Specification format and rules for the CREATE INDEX statement in the manual HADB SQL Reference.

If this message was issued while a CREATE TABLE statement was executing, check the maximum length of B-tree index keys corresponding to the primary key by referencing Rules in Specification format and rules for the CREATE TABLE statement in the manual HADB SQL Reference.

KFAA30617-E

The number of columns in the aa....aa exceeds 16. (M+J+O)

An error occurred in an SQL statement because the number of columns specified exceeded the maximum of 16.

aa....aa:

Cause of the error

S:

Ignores this SQL statement.

Action:

Based on the cause of the error displayed in place of aa....aa, take one of the following corrective actions.

Cause of the error displayed for aa....aa

Cause of the error and corrective action to take

SQLSTATE

index

The number of indexed columns in a multiple-column index exceeds the maximum of 16. Decrease the number of indexed columns to 16 or fewer.

425C6

primary key

The number of columns constituting a primary key exceeds the maximum of 16. Decrease the number of columns constituting the primary key to 16 or fewer.

foreign key

The number of columns constituting a foreign key exceeds the maximum of 16. Decrease the number of columns constituting the foreign key to 16 or fewer.

425CD

KFAA30619-E

Among the aa....aa columns names, column name "bb....bb" is duplicated. (M+J+O)

An error occurred in an SQL statement because a column name was specified more than once. <SQLSTATE: 42I18>

aa....aa:

Cause of the error

bb....bb: Name of the column whose name was specified more than once

If the column name cannot be output, *** is displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Based on the cause of the error displayed in place of aa....aa, take one of the following corrective actions.

Cause of the error displayed for aa....aa

Cause of the error and corrective action to take

index

A single column name has been specified more than once in an indexed column specified in a CREATE INDEX statement. Correct the indexed column specification.

primary key

A single column name has been specified more than once in the columns that constitute a primary key specified in a CREATE TABLE statement. Correct the specifications of the columns that constitute the primary key.

foreign key

A single column name has been specified more than once in the columns that constitute a foreign key specified in a CREATE TABLE statement. Correct the specifications of the columns that constitute the foreign key.

KFAA30629-E

The column cannot be deleted from the base table. (reason = aa....aa) (M+J+O)

You cannot use the ALTER TABLE statement to delete a column. <SQLSTATE:53021>

aa....aa: Reason why columns cannot be deleted

the segment for storing the row has been allocated to the table or an operation is performed after the column is added that prevents the column from being deleted:

Either of the following conditions that allows deletion of a row are not met.

The segment that stores the rows is not assigned to the base table that deletes the rows.

The column to be deleted is a column added with a ALTER TABLE statement, and no process (such as an INSERT statement or adbimport command) was executed after the column was added that would prevent the column from being deleted

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

See Deleting a column after deleting all rows in a base table in Deleting columns of a base table in the manual HADB Setup and Operation Guide and delete the column.

KFAA30630-E

A column for which NOT NULL constraint is specified cannot be added to a table in which data has been stored at least once. (M+J+O)

A column with the NOT NULL constraint specified cannot be added to a base table to which segments for storing rows are assigned. <SQLSTATE: 42IAC>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

For details about how to add columns to such tables, see When a column cannot be added to a base table in the HADB Setup and Operation Guide.

KFAA30632-E

The column cannot be deleted because only one column is defined in the table. (M+J+O)

Since there is only one column defined in the table, that column cannot be deleted with the ALTER TABLE statement. <SQLSTATE: 42I25>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

If there is only one column defined in the table, that column cannot be deleted with the ALTER TABLE statement.

If you want to delete the table, use the DROP TABLE statement.

KFAA30650-E

The number of viewed table columns is not equal to the number of columns in SELECT. (M+J+O)

There is an error in the specified CREATE VIEW statement. The number of column names specified in the column name list differs from the number of columns for the table that is derived from the query expression. <SQLSTATE: 42723>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Make sure that the number of column names specified in the column name list in the CREATE VIEW statement is the same as the number of columns for the table that is derived from the query expression.

If this message is output in either of the following cases, take the corrective action described under Procedure.

The ALTER VIEW statement is executed.

A viewed table is re-created during version upgrading of the HADB server.

For details, see Re-creation of viewed tables in the event of a version upgrade in Notes on version upgrading in the HADB Setup and Operation Guide.

Procedure

Check viewed table definition information.

Check the CREATE VIEW statement that was used when the target viewed table was defined. You can acquire viewed table definition information by searching a dictionary table. For details about examples of searching the dictionary table, see Finding out viewed table definition information in Searching a dictionary table in the HADB Setup and Operation Guide.

Delete the viewed table.

Delete the target viewed table by using the DROP VIEW statement.

Correct the information specified in the CREATE VIEW statement.

Correct the information specified in the CREATE VIEW statement you checked in step 1.

Redefine the viewed table by using the CREATE VIEW statement.

Use the CREATE VIEW statement you corrected in step 3 to redefine the viewed table deleted in step 2.

If this message is output because an asterisk (*) is specified in the selection expression for the query specification in the CREATE VIEW statement, do not specify the asterisk (*). Correct the information specified in the CREATE VIEW statement to explicitly specify the column name in the selection expression for the query specification.

KFAA30651-E

"aa....aa" cannot be specified in a view definition. (M+J+O)

The item aa....aa cannot be specified in a view definition. <SQLSTATE: 42850>

aa....aa: Item that cannot be specified

dynamic parameter: A dynamic parameter

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA30652-E

The specified DB area "aa....aa" does not exist. (M+J+O)

The DB area specified in the following SQL statements or the assumed DB area does not exist: <SQLSTATE:58005>

CREATE TABLE statement

CREATE INDEX statement

ALTER TABLE statement

aa....aa:

DB area name

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Check whether IN DB-area-name is specified in the SQL statement.

■ If the IN DB-area-name specification is omitted:

The DB area specified for the adb_sql_default_dbarea_shared operand in the server definition does not exist. Take one of the following corrective actions:

Correct the adb_sql_default_dbarea_shared operand specification in the server definition.

Add the IN DB-area-name specification in the SQL statement.

■ If IN DB-area-name is specified:

Correct the IN DB-area-name specification.

KFAA30653-E

The specified DB area "aa....aa" is not for bbbb. (M+J+O)

The specified or assumed DB area is not a data DB area. <SQLSTATE: 58006>

aa....aa:

DB area name

bbbb: Type of DB area

data: Data DB area

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Check whether IN DB-area-name is specified in the SQL statement.

■ If the IN DB-area-name specification is omitted:

The DB area specified for the adb_sql_default_dbarea_shared operand in the server definition is not a data DB area. Take one of the following corrective actions:

Specify a data DB area for the adb_sql_default_dbarea_shared operand in the server definition.

Specify a data DB area for IN DB-area-name in the SQL statement.

■ If IN DB-area-name is specified:

Specify a data DB area for IN DB-area-name in the SQL statement.

KFAA30655-E

A viewed table cannot be defined from viewed tables. (M)

A viewed table cannot be defined with another viewed table as its underlying table. <SQLSTATE: 427B3>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Make the underlying table be a table that is not a viewed table, and then define a viewed table.

KFAA30656-E

Schema "aa....aa" was not found in the system. (M+J+O)

Schema aa....aa does not exist. <SQLSTATE: 42I26>

aa....aa:

Schema name

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Define the schema.

KFAA30657-E

The size (aa....aa) of the area needed to store the row exceeds the page size (bb....bb). (M+J+O)

The CREATE TABLE or ALTER TABLE statement cannot be executed because the size of the area required to store a row exceeds the page size. <SQLSTATE: 56009>

aa....aa:

Size of the area required to store a row

bb....bb: Page size

If the page size or the size of the area required to store a row cannot be output, *** is displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take one of the following actions:

Check and, if necessary, revise the row length of the base table by referencing Rules in Specification format and rules for the CREATE TABLE statement or Specification format and rules for the ALTER TABLE statement in the manual HADB SQL Reference.

Increase the page size of the data DB area for storing the base table.

Tables with array-type columns defined cannot be stored in the DB area, which has a page size of 4,096 bytes. Store the tables in a DB area with a page size of 8,192 bytes or more.

KFAA30659-E

The value specified in the CHANGE clause of the ALTER TABLE statement is invalid. (reason = aa....aa) (M+J+O)

The data type and data length specified in the ALTER TABLE statement CHANGE clause is invalid. <SQLSTATE: 42I27>

aa....aa:

Cause of the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take corrective action as described in the following table: Then, re-execute the ALTER TABLE statement.

Information output to aa....aa

Cause of the error

Corrective action to take

the data type that cannot be changed is specified

The data type that was specified cannot be changed.

Specify the CHANGE clause so that is becomes one of the following combinations.

Specifying a VARCHAR type column with a data length of 254 bytes or less as the column name in the CHANGE clause

For the data type after the change, specify the VARCHAR type with a data length of 255 bytes or less.

Specifying a VARCHAR type column with a data length of 256 bytes or more and 31,999 bytes or less as the column name in the CHANGE clause

For the data type after the change, specify the VARCHAR type with a data length of 32,000 bytes or less.

the specified data length after the change is shorter than the data length before the change

The data length of the changed data type is specified to be shorter than the data length before the change.

The data length of the data type after the change must be longer than the data length before the change.

KFAA30661-E

Index "aa....aa"."bb....bb" with the same structure already exists. (M+J+O)

An index with the same structure already exists. <SQLSTATE: 42I29>

aa....aa:

Schema name

bb....bb:

Index identifier

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Check the content of the CREATE INDEX statement specification, and then correct the SQL statement, if necessary.

KFAA30664-E

The specified schema "aa....aa" already exists. (M+J+O)

A schema with the same name already exists. <SQLSTATE: 42I30>

aa....aa:

Schema name

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the schema name.

KFAA30665-E

The ALTER TABLE statement could not be used to change the column attributes, because the current aa....aa and the new aa....aa are the same. (M+J+O)

Because the specified values before and after changing are the same, it is not possible to change the column attributes (maximum number of elements or data length) using the ALTER TABLE statement. <SQLSTATE: 42I31>

aa....aa: Invalid specification

maximum number of elements: The maximum number of elements

data length: The data length

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take one of the following corrective actions:

If aa....aa is maximum number of elements

Re-execute the ALTER TABLE statement with a value greater than the maximum number of elements before the change.

If aa....aa is data length

Re-execute the ALTER TABLE statement with a value greater than the data length before the change as the data length of the changed data type.

KFAA30667-E

The maximum number of elements specified in the CHANGE clause of the ALTER TABLE statement is invalid. (reason = aa....aa) (M+J+O)

The maximum number of elements specified in the CHANGE clause of the ALTER TABLE statement are invalid. <SQLSTATE: 42I32>

aa....aa: Cause of the error

the new value is less than the current value:

An attempt was made to make the maximum number of elements smaller than before the change.

the data type of the target column is not the array type:

An attempt was made to change the maximum number of elements in a column that is not an array type.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take one of the following corrective actions based on the cause of the error that is output:

If the new value is less than the current value

Re-execute the ALTER TABLE statement with a value greater than the maximum number of elements before the change.

If the data type of the target column is not the array type

Specify the array-type column name in the CHANGE clause and re-execute the ALTER TABLE statement.

KFAA30670-E

There is an error in the bb....bb processing of aa....aa. (M+J+O)

bb....bb cannot be performed on aa....aa. <SQLSTATE: 42870>

aa....aa: Target table

read only viewed table: Read-only viewed table

bb....bb: Operation attempted

insert: INSERT statement

update: UPDATE statement

delete: DELETE statement

S:

Ignores this SQL statement.

Action:

Make sure that the target table is correct.

KFAA30673-E

"aa....aa" in the bb....bb statement is duplicated. (M+J+O)

An option was illegally specified more than once in a table or index definition. <SQLSTATE: 425D4>

aa....aa: Option specified more than once

BRANCH: BRANCH ALL specification

CORRECTIONRULE: Notation-correction-search text-index specification

EMPTY: Specifies unfinished status

EXCLUDE NULL VALUES: Null-value exclusion specification

INDEXTYPE: Index type specification

PCTFREE: Unused index area or unused table area specified

PRIMARY KEY: Uniqueness constraint definition

DELIMITER: Text-index delimiter specification

STORAGE FORMAT: Table-storage-format specification

bb....bb: Invalid SQL statement

CREATE INDEX

CREATE TABLE

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30677-E

aa....aa cannot be executed for bb....bb. (M+J+O)

The processing indicated by aa....aa cannot be performed on table bb....bb.

The TRUNCATE TABLE statement cannot be executed on a viewed table or foreign table. <SQLSTATE: 427B3>

The PURGE CHUNK statement cannot be executed on a single-chunk table, viewed table, or foreign table. <SQLSTATE:427B4>

aa....aa: Processing that is not permitted

purge chunk: PURGE CHUNK statement

truncate table: TRUNCATE TABLE statement

bb....bb: Table to be processed

viewed table: Viewed table

foreign table: Foreign table

no multi chunk table: Single-chunk table

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA30678-E

No column definition is specified in the aa....aa. (M+J+O)

No column definition is specified in the aa....aa statement. <SQLSTATE: 425D0>

aa....aa: SQL statement that caused the error

CREATE TABLE statement: A CREATE TABLE statement

CREATE FOREIGN TABLE statement: A CREATE FOREIGN TABLE statement

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Specify a column definition in the CREATE TABLE statement.

KFAA30692-E

Execution is not possible because table "aa....aa"."bb....bb" is in use. (M+J+O)

A definition SQL statement cannot be executed because the table definition information for table bb....bb is in use. <SQLSTATE: 53024>

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Wait for the transaction to terminate, and then re-execute the SQL.

KFAA30695-E

The aa....aa, which has a defined bb....bb, cannot be deleted because "RESTRICT" is specified. (M+J+O)

An SQL statement was executed with RESTRICT specified for the drop behavior, but the SQL statement resulted in an error for one of the following reasons. <SQLSTATE: 42I44>

An attempt was made to delete base tables for which indexes or constraints were defined.

An attempt was made to delete schemas for which tables were defined.

An attempt was made to delete a table on which viewed tables depend.

An attempt was made to delete columns for which indexes or constraints were defined.

An attempt was made to delete a column of a table on which viewed tables depend.

An attempt was made to delete a foreign server used in a foreign table.

An attempt was made to delete a foreign table on which viewed tables depend.

Note

Because range indexes are always defined for archivable multi-chunk tables, deleting an archivable multi-chunk table results in error for reason 1 above.

aa....aa: SQL statement that caused the error

table: DROP TABLE statement

schema: DROP SCHEMA statement

viewed table: DROP VIEW statement

column of table: Deleting a column by ALTER TABLE statement

foreign server: DROP SERVER statement

foreign table: DROP FOREIGN TABLE statement

bb....bb: Defined object

table: Table

index: Index

viewed table: Viewed table

constraint: Constraint

foreign table: A foreign table

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Identify the object that caused the error from the following table. Make sure that no problems occur if tables, indexes, or constraints are deleted (or viewed tables are deleted or invalidated) during execution of the SQL statement output in aa....aa. If there are no problems, re-execute the SQL statement with CASCADE specified for the drop behavior or without specifying the drop behavior.

Information output to aa....aa

Information output to bb....bb

Error cause object

table

index

The indexes defined in the table to be deleted (including the range indexes defined in the archive range column of the archivable multi-chunk table)

constraint

Constraint defined in the table to be deleted

viewed table

Viewed table that uses the table to be deleted as its underlying table or that depends on the table to be deleted

schema

table

Tables, viewed tables, and indexes defined in the schema to be deleted

viewed table

viewed table

Viewed table that uses the viewed table to be deleted as its underlying table or that depends on the viewed table to be deleted

column of table

index

Index defined in the column to be deleted

constraint

Constraint defined in the column to be deleted

viewed table

Viewed table dependent on the table deleting columns

foreign server

foreign table

Foreign table using a foreign server to be deleted

foreign table

viewed table

Viewed table dependent on the foreign table to be deleted

KFAA30704-E

The specified data type of a column "aa....aa" for column definition in the CREATE FOREIGN TABLE statement is invalid. (M+J+O)

The data type of the column aa....aa specified in the column definition of the CREATE FOREIGN TABLE statement is invalid. <SQLSTATE:42I91>

aa....aa:

The column name that caused the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The following data type cannot be specified for the column definition in the CREATE FOREIGN TABLE statement.

When PARQUET is specified for the foreign data format specification#1

TIME(0), TIME(12)

TIMESTAMP(0), TIMESTAMP(12)#2

A STRUCT that includes one of the above as a field data type, or an ARRAY that includes one of the above as an element data type.

When CSV is specified for the foreign data format specification

TIME(12)

TIMESTAMP(12)#2

UUID

STRUCT

ARRAY

When JSON is specified for the foreign data format specification

TIME(12)

TIMESTAMP(12)#2

UUID

A STRUCT that includes one of the above as a field data type, or an ARRAY that includes one of the above as an element data type.

When ICEBERG is specified for the foreign data format specification#3

TIME(0), TIME(3), TIME(9), TIME(12)

TIMESTAMP(0), TIMESTAMP(3), TIMESTAMP(9), TIMESTAMP(12)#2

A STRUCT that includes one of the above as a field data type, or an ARRAY that includes one of the above as an element data type.

Specify a fractional seconds precision other than the one mentioned above or another data type. For details about the CREATE FOREIGN TABLE statement, see CREATE FOREIGN TABLE (defining a foreign table) in the manual HADB SQL Reference.

#1

If the column definition specification is omitted, the HADB server automatically generates the column definition. If the data type of the generated column corresponds to a data type that cannot be specified as described here, the CREATE FOREIGN TABLE statement will result in an error.

#2

This applies to both TIMESTAMP WITHOUT TIME ZONE type and TIMESTAMP WITH TIME ZONE type.

#3

If ICEBERG is specified in the foreign data format specification, the HADB server automatically generates the column definition. If the data type of the generated column corresponds to a data type that cannot be specified as described here, the CREATE FOREIGN TABLE statement will result in an error.

KFAA30705-E

The value aa....aa of option "bb....bb" in statement cc....cc is outside the specified range. (M+J+O)

A value outside the valid range was specified for a table option in the CREATE TABLE or ALTER TABLE statement, or for an index option in the CREATE INDEX statement. <SQLSTATE: 425D5>

aa....aa: Invalid specification value

If it cannot be output, *** is displayed.

bb....bb: Name of option for which the out-of-range value was specified

PCTFREE

CHUNK

cc....cc: Executed SQL statement

ALTER TABLE

CREATE TABLE

CREATE INDEX

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the table or index option for which the out-of-range value was specified.

KFAA30706-E

The number of defined indexes in table "aa....aa"."bb....bb" exceeded 64. (M+J+O)

The number of indexes that can be defined for a single table has exceeded the upper limit of 64. <SQLSTATE: 5600B>

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Reduce the number of indexes that are defined for the table.

KFAA30720-E

An error occurred in the client library. (file = "aa....aa", location = bb....bb) (M+J+O)

An internal conflict occurred in a client library. <SQLSTATE: 5C011>

aa....aa:

Name of the source file that detected the error

bb....bb:

Position where error was detected

S:

Terminates processing.

Action:

Re-execute the application program. If this message is output, it means that the connection to the HADB server has been closed; you must restore the connection before executing. If reconnecting does not resolve the problem, make a backup of the client message log file, and then contact the customer support center.

KFAA30722-E

A communication error occurred. (reason = "aa....aa") (M+J+O)

A communication error that prevents continued processing has occurred during SQL statement processing.

aa....aa: Cause of the error

CONNECTION CLOSED: The connection to the HADB server was closed. <SQLSTATE: 52320>

INVALID DATA: Invalid data was received from the HADB server. <SQLSTATE: 52321>

S:

Terminates processing. Closes connection to HADB server.

Action:

Re-execute the application program or command. If this message is output, the connection with the HADB server has been closed. To re-execute the application program, therefore, you must first restore the connection with the HADB server.

If the cause of the error is CONNECTION CLOSED and the HADB server cannot be re-connected, it might have shut down. Check whether the HADB server has shut down.

If the HADB server is running but connection cannot be established, the HADB server and client versions might be different. If a message was output to the server message log file indicating that the connection to the HADB server was rejected, check the versions of the HADB server and the HADB client, and make sure that they are the same.

KFAA30723-E

Communication with the server failed. (reason = "aa....aa") (M+J+O)

An error occurred during communication with the HADB server. Another possibility is that the HADB server terminated abnormally.

aa....aa:

Cause of the failure

Value of aa....aa

Meaning

SQLSTATE

SERVER NOT UP

The HADB server is not running.

08004

HOST NAME

The address of the target host cannot be acquired.

52322

NETWORK

One of the following failures was detected:

A failure occurred on the network.

The connection was blocked by the local firewall rules.

The HADB server terminated abnormally and the connection was closed.

The connection was closed because the HADB client version differs from the HADB server version.

52324

SecurityException

A security violation occurred in the JDBC driver.

52325

TIMEOUT

A timeout occurred during connection to the HADB server or data transmission.

52326

SYSTEM CALL ERROR

A system call error occurred during communication processing.

52328

DESCRIPTOR

A descriptor shortage occurred.

53040

INSUFFICIENT NETWORK PORT

Allocation of communication port numbers failed.

53041

CLIENT MEMORY

A memory shortage occurred in a client library.

53201

S:

Terminates processing.

Action:

Re-execute the application program. If this message is output, it means that the connection to the HADB server has been closed; you must restore the connection before re-executing.

If CLIENT MEMORY is indicated as the cause of the failure, use the following procedure to resolve the memory shortage:

Check for any unnecessary processes. If any unnecessary processes are running, shut them down. Then, re-execute the command or SQL statement.

If there is not enough memory after performing step 1, restart the OS. Then, re-execute the command or SQL statement.

If there is not enough memory after performing step 2, change the kernel parameter setting to increase the amount of memory that processes can use. Restart the OS, and then re-execute the command or SQL statement.

If HOST NAME is displayed as the cause of the failure, carefully review the values specified in the client definition's adb_clt_rpc_srv_host operand, the hosts file, the settings of the DNS server, and so on.

If SERVER NOT UP is displayed even though the HADB server is running, check whether either of the following applies:

Has the host name specified in the client definition's adb_clt_rpc_srv_host operand correctly resolved to the IP address of the host on which the HADB server is running?

Is the same port number specified in the client definition's adb_clt_rpc_srv_port operand and the server definition's adb_rpc_port operand?

If neither of these resolves the problem, check the network settings, such as the firewall settings.

If SecurityException is displayed as the cause of the failure, enable a connect to the server host with java.net.SocketPermission, or disable the security manager. Also make sure that the server host name can be resolved.

KFAA30724-E

An environment variable is invalid. (variable = "aa....aa", reason = "bb....bb") (E+M+J+O)

The specified environment variable is invalid. <SQLSTATE: 42932>

aa....aa:

Environment variable name

bb....bb: Reason

INVALID CHAR: An invalid character was specified for the environment variable value.

NO VALUE: No environment variable value was specified.

OUT OF RANGE: The path name specified as the environment variable value is too long. Another possibility is that the environment variable value has exceeded the range that can be specified.

INVALID IDENTIFIER: The environment variable value is invalid.

NOT DEFINE: The environment variable value has not been defined.

FAILED TO ACCESS: The file or directory specified as the environment variable value does not exist.

INVALID PATH FORMAT: The format of the environment variable value is invalid.

LENGTH ERROR: The character string specified as the environment variable value is too long.

INVALID LETTER: A character that cannot be specified was specified as the environment variable value.

S:

Terminates processing.

Action:

Carefully review the environment variable names and values.

KFAA30727-E

An SQL statement cannot be executed because the HADB system is starting or terminating. (M+J+O)

No SQL statements can be executed because the HADB server is being started or terminated. <SQLSTATE: 52004>

S:

Terminates processing.

Action:

Start the HADB server, and then retry the operation.

KFAA30732-E

No response can be received from the HADB server because processing on the HADB server timed out. (M+J+O)

An error occurred in the application program or command because HADB server processing did not terminate when the timeout period expired. <SQLSTATE: 52330>

S:

Terminates processing.

Action:

If this message is output during execution of an application program

Make sure that the appropriate timeout period is specified.

If the timeout period is appropriate, re-execute the application program.

If the timeout period is not appropriate, change the timeout period, and then re-execute the application program.

If this message is output, it means that the connection to the HADB server has been closed. You must restore the connection when re-executing the application program.

The timeout period is specified in the following operands of the client definition:

• adb_clt_rpc_sql_wait_time

• adb_clt_rpc_con_wait_time

If you are using the JDBC driver, the timeout period is specified in the properties having the same names as the above or with a method such as setQueryTimeout.

If this message is output during execution of a command

If an error message is output after the KFAA30732-E message, take the appropriate action for that message.

If no error message is output after the KFAA30732-E message, re-execute the command. At this time, make sure that the timeout period specified for the command is appropriate. If the timeout period is not appropriate, change it, and then re-execute the command.

KFAA30733-E

The received data is invalid. (information 1 = aa....aa, information 2 = bb....bb) (M+J+O)

Invalid data was received from the HADB server. <SQLSTATE: 5C015>

aa....aa:

Maintenance information 1

bb....bb:

Maintenance information 2

S:

Ignores this SQL statement.

Action:

Make a backup of the client message log file.

Then, contact the customer support center.

KFAA30742-E

A foreign key "aa....aa"."bb....bb" cannot be defined because the referenced table "cc....cc"."dd....dd" does not have a primary key. (M+J+O)

A foreign key cannot be defined because no primary key has been defined for the referenced table. <SQLSTATE: 42I53>

aa....aa:

Foreign key schema name

bb....bb:

Foreign key constraint name

cc....cc:

Referenced table schema name

dd....dd:

Table identifier of referenced table

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement so that a table that has a primary key defined is specified as the referenced table.

KFAA30743-E

The structure of foreign key "aa....aa"."bb....bb" is different from that of the primary key of "cc....cc"."dd....dd". (M+J+O)

The structure of a foreign key is different from the structure of the primary key that the foreign key references. <SQLSTATE: 42I54>

aa....aa:

Foreign key schema name

bb....bb:

Foreign key constraint name

cc....cc:

Schema name of the table for which the primary key is defined

dd....dd:

Identifier of the table in which the primary key is defined

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Check the structure (the following items) of the foreign key and of the primary key that the foreign key references, and then correct the SQL statement.

Number of columns

Data type of each column

Data length of each column

KFAA30744-E

A foreign key "aa....aa"."bb....bb" for "cc....cc"."dd....dd" cannot be defined because ee....ee. (M+J+O)

A foreign key cannot be defined for one of the following reasons: <SQLSTATE: 42I55>

The referenced table specified is not a base table.

The referenced table is the same as the referencing table.

aa....aa:

Foreign key schema name

bb....bb:

Foreign key constraint name

cc....cc:

Referenced table schema name

dd....dd:

Table identifier of the referenced table

ee....ee:

Cause of the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The following explains how to handle this:

If the referenced table is not a real table is displayed for ee....ee

The referenced table specified is not a base table. Specify a base table for the referenced table.

If the referenced table is the same as the referencing table is displayed for ee....ee

The referenced table is the same as the referencing table. Foreign keys cannot be defined using the same referenced table and referencing table, so correct or delete the referential constraint definition.

KFAA30748-E

The number of foreign keys that reference the primary key of "aa....aa"."bb....bb" exceeds 255. (M+J+O)

The number of foreign keys that reference a primary key exceeded 255. <SQLSTATE: 5600C>

aa....aa:

Schema name of the table for which the primary key is defined

bb....bb:

Identifier of the table in which the primary key is defined

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Delete unnecessary foreign keys.

KFAA30752-E

A connection is already established. (M+O)

A connection to the HADB server has already been established. Connection processing cannot be re-executed while there is a connection to the HADB server. <SQLSTATE: 08002>

S:

Ignores this SQL statement.

Action:

Carefully review the locations where connection processing to the HADB server occurs in the application program.

KFAA30756-E

DB area pages are insufficient. DB area = "aa....aa" (M+J+O)

No more pages can be created because the DB area file cannot be expanded. <SQLSTATE: 40503>

aa....aa:

DB area name

S:

Invalidates this transaction.

Action:

Expand the storage region in the DB area file. If the storage region cannot be expanded, change the DB area file's storage location. For more information, see Problems related to free space on the disk in the HADB Setup and Operation Guide.

If this message is output when you execute the adbreorgsystemdata command, take action as follows.

When the system table is reorganized

Execute the adbreorgsystemdata command for all system tables (base tables) except for those that could not be reorganized.

Re-execute the adbreorgsystemdata command for the system tables (base tables) that could not be reorganized.

If this message is output again after the adbreorgsystemdata command is executed in step 2, free disk space for storing the system-table DB area is insufficient. Estimate the size of the system-table DB area, and then increase the amount of free space for storing the system-table DB area. For details, see Estimating the size of the system-table DB area and When a free space shortage is caused by an increase in the size of the DB area files in the HADB Setup and Operation Guide.

When the dictionary table is reorganized

Execute the adbreorgsystemdata command for all dictionary tables (base tables) except for those that could not be reorganized.

Re-execute the adbreorgsystemdata command for the dictionary tables (base tables) that could not be reorganized.

If this message is output again after the adbreorgsystemdata command is executed in step 2, free disk space for storing the dictionary DB area is insufficient. Estimate the size of the dictionary DB area, and then increase the amount of free space for storing the dictionary DB area. For details, see Estimating the size of the dictionary DB area and When a free space shortage is caused by an increase in the size of the DB area files in the HADB Setup and Operation Guide.

KFAA30758-E

The EXCLUDE NULL VALUES option cannot be specified because aa....aa. (M+J+O)

The null-value exclusion specification (EXCLUDE NULL VALUES) cannot be specified due to one of the following reasons: <SQLSTATE: 42I60>

The null-value exclusion specification is specified for an index that is not a B-tree index.

The indexed columns include a column for which the NOT NULL constraint is specified.

aa....aa: Cause of the error

the index is not a B-tree index: The null-value exclusion specification is specified for an index that is not a B-tree index.

there is a NOT NULL column in the indexed columns: The indexed columns include a column for which the NOT NULL constraint is specified.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Delete the null-value exclusion specification.

KFAA30798-E

Invalid usage of DEFAULT clause for aa....aa "bb....bb". (reason = "cc....cc") (M+J+O)

A DEFAULT clause specification is invalid. <SQLSTATE: 42I72>

aa....aa: Type of error

column: Column

bb....bb:

Column name

cc....cc: Cause of the error

the specified default option cannot be assigned to the data type of the specified string

The specified default option cannot be assigned to the data type of the column for which the DEFAULT clause is specified.

a null value cannot be specified for a column having the NOT NULL constraint

NULL is specified for a column for which NOT NULL constraint is defined.

the length of the specified default option is invalid

The length of the default value is invalid.

the DEFAULT clause cannot be specified for an array-type column

The DEFAULT clause is specified for the array-type column.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the specification of the DEFAULT clause.

KFAA30800-E

Division by zero occurred in an arithmetic operation for the "aa....aa" data type. (M+J+O)

An attempt was made to divide by 0 in arithmetic operations with data type aa....aa. <SQLSTATE: 22012>

aa....aa: Data type that generated the division by 0

BIGINT: BIGINT type

INTEGER: INTEGER type

DECIMAL: DECIMAL type or NUMERIC type

DOUBLE PRECISION: DOUBLE PRECISION type or FLOAT type

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement so that division by 0 does not occur.

KFAA30801-E

An overflow occurred in aa....aa of the "bb....bb" data type. (M+J+O)

One of the following errors occurred:

An overflow occurred in operation aa....aa using numeric data type bb....bb. <SQLSTATE: 22003>

An overflow occurred in operation aa....aa using datetime data type bb....bb. <SQLSTATE: 22008>

aa....aa: Type of operation that generated the overflow

addition: Addition

subtraction: Subtraction

multiplication: Multiplication

division: Division

bb....bb: Data type that generated the overflow

BIGINT: BIGINT type

INTEGER: INTEGER type

DECIMAL: DECIMAL type or NUMERIC type

DOUBLE PRECISION: DOUBLE PRECISION type or FLOAT type

DATE: DATE type

TIME: TIME type

TIMESTAMP: TIMESTAMP type

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement so that no overflow occurs.

Note that this error message may be output when the scalar function TIMESTAMPADD is executed. In that case, aa....aa will output addition and bb....bb will output the data type of the result of the scalar function TIMESTAMPADD. However, if QUARTER or WEEK is specified for the datetime unit and an overflow occurs in the multiplication before the added value is added, aa....aa will output multiplication and bb....bb will output INTEGER.

KFAA30802-E

An overflow occurred for the "bb....bb" data type during processing of the function "aa....aa". (M+J+O)

An overflow occurred while a set function or a window function was executing.

If aa....aa is LISTAGG <SQLSTATE:22001>

The data length of the aggregated data exceeded the maximum length of the LISTAGG result character string.

If aa....aa is COUNT <SQLSTATE:22003>

The number of target data items exceeded the maximum value for the BIGINT type.

If aa....aa is SUM <SQLSTATE:22003>

An overflow occurred when the data being handled was added.

If aa....aa is AVG <SQLSTATE:22003>

One of the following errors occurred:

• An overflow occurred when the target data was added.

• The number of target data items exceeded the maximum value for the BIGINT type.

If aa....aa is STDDEV_POP, STDDEV_SAMP, VAR_POP, or VAR_SAMP <SQLSTATE:22003>

One of the following errors occurred:

• An overflow occurred when the target data or the square of the target data was added.

• The number of target data items exceeded the maximum value for the BIGINT type.

• An overflow occurred when the target data was multiplied.

• An overflow occurred when the result of a function was obtained from the sum of the target data, the sum of the squares of the target data, and the number of target data items.

If aa....aa is PERCENTILE_CONT or MEDIAN <SQLSTATE:22003>

One of the following errors occurred:

• The number of target data items exceeded the maximum value for the BIGINT type.

• An overflow occurred when the result of a function was obtained from The number of target data items and the function's argument values.

If aa....aa is PERCENTILE_DISC <SQLSTATE:22003>

The number of target data items exceeded the maximum value for the BIGINT type.

If aa....aa is RANK, DENSE_RANK, CUME_DIST, or ROW_NUMBER <SQLSTATE:22003>

The number of target data items exceeded the maximum value for the BIGINT type.

If aa....aa is ARRAY_AGG <SQLSTATE:2202F>

The number of target data items exceeded the maximum number of elements for an array-type column, which is 30,000.

aa....aa:

Name of the function resulting in an error

bb....bb: Data type that generated the overflow

BIGINT: BIGINT type

INTEGER: INTEGER type

SMALLINT: SMALLINT type

DECIMAL: DECIMAL type or NUMERIC type

DOUBLE PRECISION: DOUBLE PRECISION type or FLOAT type

REAL: REAL type

VARCHAR: VARCHAR type

STRING: STRING type

ARRAY: Array type

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

If aa....aa is LISTAGG

Re-execute the SQL statement by specifying TRUNCATE for the LISTAGG set function overflow behavior. For details about overflow behavior, see LISTAGG in the manual HADB SQL Reference.

If aa....aa is other than LISTAGG

Eliminate the cause of the overflow by taking an action such as reducing the number of data items handled by the operation. For details about the maximum and minimum values for each data type, see List of data types in the manual HADB SQL Reference.

KFAA30803-E

Key values on a unique index are duplicated. index ID = aa....aa (M+J+O)

An attempt was made to update or add data that would have resulted in key values of a unique index being duplicated. <SQLSTATE: 23504>

aa....aa:

Index ID

S:

Invalidates this transaction.

Action:

Check for errors in the data being updated or added.

Note that you can use an index ID as a key to identify the names of the table and column in which column value duplication exists. For details about how to do this, see Searching a dictionary table in the HADB Setup and Operation Guide.

KFAA30805-E

An invalid statement handle was specified. (M+J+O)

An invalid statement handle was specified. The possible causes are as follows: <SQLSTATE: 56020>

The statement handle used during execution of the definition SQL statement was released after normal termination of that SQL statement. Therefore, it is not necessary to release the statement handle.

When a COMMIT or ROLLBACK is executed, the statement handle is released, so it is not necessary to release the statement handle.

When a ROLLBACK is generated by an error, the statement handle is released, so it is not necessary to release the statement handle. Use EndTran in the SQL result information to determine whether a ROLLBACK was generated by an error.

S:

Ignores this SQL statement.

Action:

Correct the application program. Correct the statement handle, or delete the release processing for the statement handle.

KFAA30808-E

The row length of the work table exceeds aa....aa bytes. (M+J+O)

The row length of the work table exceeds aa....aa bytes. <SQLSTATE: 40518>

aa....aa:

Maximum row length of the work table

S:

Invalidates this transaction.

Action:

Correct the SQL statement to reduce the columns of the work table so that the row length of the work table is aa....aa bytes or fewer. For details about columns of the work table, see Work tables created when SQL statements are executed in the HADB Application Development Guide.

If you cannot reduce the columns of the work table, you might be able to prevent this error by changing the page size of the work table DB area. To change the page size of the work table DB area, temporarily terminate the HADB server by using the adbstop command, and then change the value specified for the adb_dbarea_wrk_page_size operand in the server definition. Then, execute the adbstart command to start the HADB server.

For details about the relationship between the page size of the work table DB area and the maximum row length of the work table, see Maximum row length of work table in Maximum and minimum values related to database in the HADB Setup and Operation Guide.

KFAA30811-E

The number of aa....aa exceeded the definable maximum. (M+J+O)

The number of base tables, foreign tables, indexes, viewed tables, or HADB users has exceeded the maximum number that can be defined for the system. <SQLSTATE: 40900>

aa....aa: Item whose maximum number was exceeded

tables: Total number of base tables and foreign tables

indexes: Indexes

views: Viewed tables

users: HADB users

S:

Invalidates this transaction.

Action:

Delete unnecessary base tables, foreign tables, indexes, viewed tables, and HADB users.

If this message was issued while you were upgrading the HADB server, restore the previous version of the HADB server, and then reduce the number of schemas to 30,000 or fewer. After that, upgrade the HADB server again. For details about the procedure, see Steps to take when the KFAA30811-E message is output in Steps to take when version upgrading fails in the HADB Setup and Operation Guide.

KFAA30812-E

No more aa....aa can be defined because the number of aa....aa in the DB area "cc....cc" has reached the maximum bbb. (M+J+O)

The number of tables or indexes has exceeded the maximum that can be stored in a single DB area. <SQLSTATE: 40910>

aa....aa: Object that exceeds the upper limit

tables: Tables

indexes: Indexes

bbb:

The maximum number of tables or indexes that can be stored

cc....cc:

DB area name

S:

Invalidates this transaction.

Action:

Delete unneeded tables or indexes in the DB area.

KFAA30821-E

The SQL statement length exceeds 16,000,000 bytes or is invalid. (M+J+O)

The SQL statement length has exceeded the upper limit of 16,000,000 bytes, or the length is invalid. <SQLSTATE: 5600E>

S:

Ignores this SQL statement.

Action:

Correct the SQL statement length.

KFAA30824-E

Analysis of the client definitions failed. (M+O)

An analysis of the client definitions has failed. <SQLSTATE: 54006>

S:

Ignores this SQL statement.

Action:

Eliminate the cause of the error based on the message that was output immediately prior to this message.

KFAA30873-E

The batch update facility can be used only on prepared statement handles of DELETE, INSERT, and UPDATE. (M+J+O)

The following functions cannot be used on statement handles prepared for execution of statements other than DELETE, INSERT, and UPDATE: <SQLSTATE: 54012>

Batch update functionality of the JDBC driver

Update using batch binding of dynamic parameters of the CLI function (a_rdb_SQLBindArrayParams())

S:

Ignores this SQL statement.

Action:

Perform preprocessing of the DELETE, INSERT, and UPDATE statements, and then perform batch binding or batch update of dynamic parameters.

KFAA30879-E

The index (number aa....aa in DB area "bb....bb") must be rebuilt to access the table. (M+J+O)

An attempt was made to access an index that was in unfinished status. <SQLSTATE: 40508>

aa....aa:

Index ID of the index that was in unfinished status

bb....bb:

Name of the DB area that stores the index that was in unfinished status

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

If this message is output to a HADB client

Ask the HADB administrator to check the HADB server, or contact an OS user who belongs to the HADB administrators group.

If this message is output to the HADB server

If, on a table for which the target index is defined, an adbimport or adbidxrebuild command is suspended, re-execute the suspended command.

Otherwise, re-create the index in unfinished status by using the adbidxrebuild command.

Note that you can use an index ID as a key to identify the name of the index in unfinished status and the name of the table in which that index is defined. For details about how to do this, see Searching a dictionary table in the HADB Setup and Operation Guide.

KFAA30889-E

The command must be re-executed to access the table. (table ID = aa....aa, command =bb....bb) (M+J+O)

An attempt was made to access a table that is in non-updateable status due to a suspended command. <SQLSTATE: 4050D>

aa....aa:

Table ID of table that is in non-updateable status

bb....bb:

Suspended command

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

If this message is output to a HADB client

Ask the HADB administrator to check the HADB server, or contact an OS user who belongs to the HADB administrators group.

If this message is output to the HADB server

Re-execute the command displayed for bb....bb.

For details about the status in which a table cannot be updated, see Steps to take when a base table becomes non-updatable in the HADB Setup and Operation Guide.

Note that you can use a table ID as a key to identify the name of a table that cannot be updated. For details about how to do this, see Searching a dictionary table in the HADB Setup and Operation Guide.

KFAA30901-E

Execution was requested for an SQL statement for which preparation was not complete. (M+J+O)

Execution of an SQL statement was requested before preprocessing of the SQL statement had terminated normally. <SQLSTATE: 54009>

S:

Ignores this SQL statement.

Action:

Wait for preprocessing of the SQL statement to terminate normally, and then execute the application program. When a rollback occurs after preprocessing of an SQL statement has terminated normally, wait for preprocessing of the SQL statement to terminate normally again, and then execute the application program.

KFAA30913-E

An error occurred during lock processing. (M+J+O)

An error occurred during lock processing. <SQLSTATE: 4050G>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Re-execute the SQL statement.

KFAA30914-E

Lock processing timed out. (M+J+O)

Processing to reserve a lock timed out. <SQLSTATE: 4050P>

S:

Ignores this SQL statement.

Action:

Re-execute the SQL statement.

KFAA30918-E

Global buffer undefined. (M+J+O)

No global buffer has been assigned to the DB area. <SQLSTATE: 40602>

S:

Invalidates this transaction.

Action:

If this message was output to an HADB client

Ask the HADB administrator to check the HADB server, or contact an OS user who belongs to the HADB administrators group.

If this message was output to the HADB server

Perform the following procedure to take action.

Temporarily terminate the HADB server by using the adbstop command.

Check the KFAA41200-E message (concerning global buffers) that was output prior to this message, and then correct the server definition's adbbuff operand.

Execute the adbstart command to start the HADB server.

Retry the operation that caused an error.

KFAA30919-E

Insufficient buffer. (reason = aa....aa) (M+J+O)

Processing cannot continue because there are not enough buffer sectors. <SQLSTATE: 40701>

aa....aa: Cause of the error

SERVER: Server definition

COMMAND: Command option

CLIENT: Client definition

S:

Invalidates this transaction.

Action:

If this message was output to an HADB client

Take corrective action as described in the following table:

Cause of the error output for aa....aa

Corrective action

SERVER

Ask the HADB administrator to check the HADB server.

CLIENT

Increase the value specified in the client definition's adb_dbbuff_wrktbl_clt_blk_num operand.

If this message was output to the HADB server

See the corrective action for the KFAA41201-E message that was output before this message.

KFAA30930-E

Memory to execute SQL is insufficient. (memory type = aa....aa, request size = bb....bb) (M+J+O)

An attempt to acquire enough memory to execute the SQL statement has failed. <SQLSTATE: 53201>

aa....aa: Type of memory that is insufficient

PROCESS: There is a shortage of process common memory to be used to execute the SQL statement.

THREAD: There is a shortage of real thread private memory to be used to execute the SQL statement.

HEAP: Heap memory is insufficient.

SHARE: Shared memory is insufficient.

bb....bb:

Size of memory area you attempted to acquire (bytes)

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take one of the following corrective actions, and then re-execute the SQL statement or the command.

Re-estimate the amount of memory required, and then carefully review the value specified in the server definition.

Temporarily terminate the HADB server by using the adbstop command, and then change the value specified in the server definition. Then, execute the adbstart command to start the HADB server.

Allocate sufficient available memory as instructed in Steps to take when a memory shortage occurs during execution of an SQL statement or command in the HADB Setup and Operation Guide.

KFAA30931-E

The number of statement handles exceeded the maximum. (M+J+O)

The number of statement handles has exceeded the upper limit of 4,095. <SQLSTATE: 56033>

S:

Ignores this SQL statement.

Action:

Executing COMMIT releases statement handles, so increase the number of times COMMIT is invoked.

KFAA30932-E

No more connection can be established. (M+J+O)

No more connections can be established to the HADB server because the number of connections has reached the maximum for simultaneous connections. <SQLSTATE: 08620>

S:

Ignores this SQL statement.

Action:

Disconnect other application programs from the HADB server, and then connect to the HADB server.

KFAA30953-E

The global buffer is currently unusable. (reason = aa....aa) (M+J+O)

The global buffer cannot be used for the reason indicated by aa....aa. <SQLSTATE: 40704>

aa....aa: Reason why the global buffer is unavailable

buffer is busy: The load on the global buffer is too high.

S:

Invalidates this transaction.

Action:

The global buffer is temporarily unavailable due to contention, resulting in global buffer locking. Wait until the load on the global buffer decreases, and then perform the processing again.

If the KFAA41202-E message was displayed before this message, also see the action to be taken for the KFAA41202-E message.

KFAA30955-E

SQL or command processing was canceled and the transaction was rolled back. (information 1 = aa....aa, information 2 = bb....bb) (M+J+O)

Processing of the SQL statement or command was canceled and the transaction was rolled back. <SQLSTATE: 5B002>

When a transaction is forced to terminate using the adbcancel command, the application program is disconnected from the HADB server. Check in the SQL results information whether the application program has been disconnected from the HADB server, and then check whether a KFAA70001-I message was output immediately afterwards.

aa....aa:

Troubleshooting information 1

bb....bb:

Troubleshooting information 2

S:

Ignores this SQL statement.

Action:

Carefully review the SQL statement, and then re-execute it.

This message is also displayed if processing of the command timed out. In such a case, take one of the following corrective actions:

Increase the timeout period of the command.

Increase the value specified for the --timeout option, and then re-execute the command.

Stop the SQL statement or command that places the command in wait status.

Release the command from the wait status.

■ adbreorgsystemdata command

For details about how to stop the SQL statement or command that caused the wait status, see Reorganization of dictionary tables and system tables, and lock control in the HADB Setup and Operation Guide. Then, re-execute the adbreorgsystemdata command.

■ Other than adbreorgsystemdata command

The following steps should be taken to suspend the SQL statement or command that is causing the wait status. Once this is done, re-execute the timed-out command.

Check the locked resource allocated by the command that timed out.

For details about the locked resources that the command reserves, see Locked resources that are reserved and their lock modes in the HADB Setup and Operation Guide.

Use the adbls -d lock command to confirm the connection ID that secures the locked resource confirmed in Step 1.

If there is no corresponding connection ID, please re-execute the timed-out command.

Use the adbcancel command to terminate the connection ID that you confirmed in Step 2.

KFAA30959-E

The operation on the file or directory "aa....aa" failed. errno = bb....bb, file = cc....cc (M+J+O)

An error occurred in processing on a directory or one of the following files. <SQLSTATE: 40528>

DB area file

System file

Directory

CSV file that will be the input data file of the ADB_CSVREAD function

Audit trail file that will be the input data of the ADB_AUDITREAD function

File used for synonym search (synonym list definition file, dictionary creation file, dictionary deletion file, synonym dictionary file, or temporary work file)

aa....aa:

Name of invalid system call

bb....bb:

Error number or 0

cc....cc:

File name or asterisk (* or ***)

S:

Invalidates this transaction.

Action:

Take one of the following corrective actions:

●If a file name or three asterisks (***) is displayed in place of cc....cc

If bb....bb is not 0

In the OS documentation, check the system call name indicated by aa....aa and the error number indicated by bb....bb, and then eliminate the cause of the error.

If aa....aa is aio_read, also check system call read. If aa....aa is aio_write, also check system call write.

If an error occurred in a symbolic link file, check the link target files in addition to that file.

For details about how to take action for each cause of the error, see Troubleshooting in the HADB Setup and Operation Guide. If this message is output during command execution, also see Command-related problems in the HADB Setup and Operation Guide.

If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If a KFAA41200-E message was output immediately prior to this message, carefully review the settings of the file displayed in place of cc....cc.

If bb....bb is 0

Re-execute the transaction. If re-executing the transaction results in the same error, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If this message is output during execution of an SQL statement with the scalar function CONTAINS (with the synonym-search specification) specified, check whether a file name that begins with a synonym dictionary name is displayed for cc....cc. If a file name that begins with a synonym dictionary name is displayed, the synonym dictionary file might not exist. Check in the OS documentation for the system call name and error number that are displayed. If the error is caused by the absence of a synonym dictionary file, re-register the synonym dictionary and re-create the synonym dictionary file.

● If an asterisk (*) is displayed in place of cc....cc

Check and, if necessary, revise the aio-max-nr kernel parameter value by referencing Estimating the kernel parameters in the HADB Setup and Operation Guide. Alternatively, check and, if necessary, revise the following settings:

If this message was issued while the adbimport command was executing

Specify a smaller value in the import option adb_import_buff_blk_num.

If this message was issued while the adbidxrebuild command was executing

Reduce the value of the adb_idxrebuild_buff_blk_num index rebuild option.

If this message was issued while the adbexport command was executing

Reduce the value of the adb_export_wrktbl_blk_num export option.

If this message was issued while the adbmergechunk command was executing

Reduce the value of the adb_mergechunk_buff_blk_num merge chunk option.

If this message was issued while the adbunarchivechunk command was executing

Specify a smaller value in the unarchived chunk option adb_unarcv_buff_blk_num.

If this message was issued while an SQL statement was executing

Specify a smaller value in the client definition's adb_dbbuff_wrktbl_clt_blk_num operand.

KFAA30984-E

The HADB client cannot connect to the HADB server because the versions of the HADB client and HADB server are different. (HADB client version = "aa....aa", HADB server version = "bb....bb") (M+J+O)

The HADB client cannot connect to the HADB server because the versions of the HADB client and HADB server are different. <SQLSTATE: 0860C>

aa....aa:

Version of the HADB client

bb....bb:

Version of the HADB server

S:

Ignores this SQL statement.

Action:

Match the version of the HADB client to that of the HADB server.

KFAA30990-E

The character encodings of the HADB client and HADB server are different. (client = "aa....aa", server = "bb....bb") (M+O)

The character encoding of the HADB server and client do not match. <SQLSTATE: 08605>

aa....aa:

Character encoding of the HADB client

bb....bb:

Character encoding of the HADB server

S:

Ignores this SQL statement.

Action:

Check whether the environment variable ADBCLTLANG matches the character encoding of the HADB server.

KFAA31120-E

The window function "bb....bb" is specified in argument of aa....aa. (M+J+O)

The window function bb....bb cannot be specified in aa....aa. <SQLSTATE: 427H3>

aa....aa: Item that cannot be specified

set function: Set function

window function: Window function

bb....bb:

Window function name

S:

Ignores this SQL statement.

Action:

Correct the SQL statement, and then re-execute it.

KFAA31121-E

The CREATE VIEW statement length exceeds 64,000 bytes. (M+J+O)

The length of a CREATE VIEW statement exceeds 64,000 bytes. <SQLSTATE: 5600E>

S:

Ignores this SQL statement.

Action:

Correct the SQL statement length, and then retry the operation.

KFAA31123-E

Sort keys are duplicated in the "ORDER BY" clause. (sort key No: aa, bb) (M+J+O)

Columns used as sort keys specified in the ORDER BY clause are duplicated. <SQLSTATE: 42736>

aa:

Number indicating the location of the first occurrence of the duplicated sort key

bb:

Number indicating the location of the second occurrence of the duplicated sort key

S:

Ignores this SQL statement.

Action:

Correct the sort keys specification in the ORDER BY clause. The sort keys specified at positions aa and bb are duplicated.

Example message that is displayed:

KFAA31123-E Sort keys are duplicated in the "ORDER BY" clause. (Sort key No: 1, 2)

If the above message is displayed, the first and the second sort keys in the ORDER BY clause are the same.

KFAA31124-E

The number of sort keys specified in aa....aa exceeds 1. (M+J+O)

No more than one sort key can be specified in aa....aa. <SQLSTATE: 427B7>

aa....aa: Type of function

inverse distribution function: Inverse distribution function

LISTAGG set function: LISTAGG set function

ARRAY_AGG set function: ARRAY_AGG set function

S:

Ignores this SQL statement.

Action:

Specify only one sort key.

KFAA31125-E

The number of window functions specified in the query specification or "ORDER BY" clause exceeds 64. (query number = aa....aa) (M+J+O)

The number of window functions specified in the query specification or the ORDER BY clause exceeds 64. <SQLSTATE: 427H4>

aa....aa: Position number of the query that specified the window function

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement.

Action:

Decrease the number of window functions specified.

KFAA31126-E

"Null ordering" cannot be specified in the "sorting specification list" of aa....aa. (function name = bb....bb) (M+J+O)

The null-value sort order cannot be specified in the sort specification list in aa....aa. <SQLSTATE: 427A5>

aa....aa: Location where the sort specification list is specified

within group specification: WITHIN group specification

ARRAY_AGG set function: ARRAY_AGG set function

bb....bb: Set function name

If aa....aa is ARRAY_AGG set function, three asterisks (***) are displayed.

S:

Ignores this SQL statement.

Action:

Delete the specification of the null-value sort order.

KFAA31127-E

The specification method of inverse distribution functions is invalid. (function name = "aa....aa", reason = bb....bb, query number = cc....cc) (M+J+O)

The specified inverse distribution function is invalid.

aa....aa:

Inverse distribution function name

bb....bb: Cause of the error

different column name: Two or more inverse distribution functions with different column names specified in the aggregated argument are specified. <SQLSTATE: 427B9>

value expression: A value expression other than a single column specification has been specified as the aggregated argument of the inverse distribution function, but multiple inverse distribution functions have been specified in the same query specification. <SQLSTATE: 427BA>

different sort specification: Multiple inverse distribution functions that contain different sort order specifications in the sort specification of a WITHIN group specification are specified. <SQLSTATE:427BB>

cc....cc: Position number of the query that specified the inverse distribution function

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA31128-E

The specification of the "FULL OUTER JOIN" is invalid. (reason = aa....aa , details = bb....bb) (M+J+O)

A FULL OUTER JOIN specification has one of the following errors.

The table defining the array-type column specified for the table reference in FULL OUTER JOIN or the specified location of that array-type column is incorrect. For details, see Rules in Specification format and rules for joined tables in the manual HADB SQL Reference. <SQLSTATE:427I1>

A FULL OUTER JOIN table reference specification has one of the following errors. For details, see Rules in Specification format and rules for joined tables in the manual HADB SQL Reference. <SQLSTATE:427I2>

A table reference on both sides of a FULL OUTER JOIN specifies a table in which all columns are array-type columns or STRUCT type columns.

When a table that defines an array-type column or STRUCT type column for a table reference on either side of a FULL OUTER JOIN, the array-type column or STRUCT type column is specified in an other item than the ON search condition of the FULL OUTER JOIN.

An external reference column whose reference destination is a table reference specified in FULL OUTER JOIN was specified. For details, see Common rules for subqueries in Rules in Specification format and rules for subqueries in the manual HADB SQL Reference. <SQLSTATE:427I8>

aa....aa: Cause of the error

array-type column: Incorrect position specified for array-type column

correlated subqueries: An external reference column was specified.

array-type or struct-type column: Incorrect position specified for array-type column or STRUCT type column

bb....bb: Error detail message

There is an error in the table that defines the array-type column specified in the table reference of FULL OUTER JOIN, or the specified position of the array type column is invalid:

Table defining the array type specified in the table reference of FULL OUTER JOIN, or the specified position of that array-type column.

The column which refers to "Table Reference" in "FULL OUTER JOIN":

Column referencing a table reference specified in FULL OUTER JOIN

There is an error in the table that defines the array-type or struct-type column specified in the table reference of FULL OUTER JOIN, or the specified position of the array type or struct-type column is invalid:

Table defining the array type or STRUCT type specified in the table reference of FULL OUTER JOIN, or the specified position of that array-type column or STRUCT type column.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31129-E

The specified number of aa....aa exceeds the maximum of bb....bb. (M+J+O)

The number of aa....aa that were specified exceeds the maximum bb....bb. <SQLSTATE:425CK>

aa....aa: Specification that exceeded maximum

FULL OUTER JOIN: FULL OUTER JOIN specification for joined table

bb....bb:

Maximum number of specifications

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the number of aa....aa specified to be bb....bb or fewer.

KFAA31131-E

A delimited identifier which contains left parentheses or right parentheses can be specified only in the first query specification except for a WITH clause in the SELECT statement. (M+J+O)

A delimited identifier that contains left or right parentheses can be specified only in the first query specification in the SELECT statement. However, a delimited identifier that contains left or right parentheses cannot be specified for a query specification in the WITH clause. <SQLSTATE: 425CL>

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

Note that, for the following locations, single-byte left or right parentheses can be specified at the beginning of the name.

The column name of the "selection expression AS column name" within the first query specification, excluding query specifications within the WITH clause of the SELECT statement.

The column name in the "selection expression AS column name" within the first query specification of the COPY statement.

The column name in the ORDER BY clause (excluding ORDER BY clauses specified within subqueries).

KFAA31132-E

NULL can be specified as the selection expression of a SELECT statement only in the outermost query excluding WITH clauses and provided that the query is not the target of set operators. (M+J+O)

Although NULL is specified in the selection expression in a query specification, an error occurred in the SELECT statement because the following conditions are not met. <SQLSTATE: 425CM>

NULL can be specified only in the selection expression for the outermost query specification in the SELECT statement.

NULL cannot be specified in the selection expression for a query specification that is the target of the set operation.

NULL cannot be specified in the selection expression for a query specification in the WITH clause.

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA31135-E

The specification of the maximum number of recursion is invalid. (reason = aa....aa, with list number = bb....bb) (M+J+O)

The specification of the maximum-number-of-recursions specification is invalid. <SQLSTATE: 425Q0>

aa....aa: Cause of the error

value is incorrect: The specified value is invalid.

bb....bb:

List number of the WITH list for which the maximum-number-of-recursions specification is specified

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31137-E

There is an error in the specified syntax format. (reason = aa....aa) (M+J+O)

There is an error in the specification format of the specified syntax. <SQLSTATE: 425Q2>

aa....aa: Cause of the error

TABLE cannot be specified in the derived table of a table function where the ADB_GENERATE_SERIES function is specified

TABLE cannot be specified for a table function derived table that specifies the ADB_GENERATE_SERIES function.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The table function derived table that specifies the ADB_GENERATE_SERIES function is specified in the format TABLE(ADB_GENERATE_SERIES-function). Correct it as follows:

Incorrect:

FROM TABLE(ADB_GENERATE_SERIES(...))

Correct:

FROM ADB_GENERATE_SERIES(...)

KFAA31201-E

The grouping column name for the grouping specification that specified "AS column name" cannot be referenced from a subquery in a aa....aa. (M+J+O)

If AS column-name is specified in the GROUP BY clause, the grouping column name cannot be referenced from a subquery in aa....aa. <SQLSTATE: 427I5>

aa....aa: Location of specification in which the error occurred

"HAVING" clause: HAVING clause

selection expression: Selection expression

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31202-E

If you specify "AS column name" as the grouping column in the "GROUP BY" clause, a value expression other than a column specification must be included. (M)

If AS column-name is specified in the GROUP BY clause, a value expression containing only column specifications cannot be specified in the GROUP BY clause. <SQLSTATE: 427I0>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31203-E

The aa....aa cannot be specified because of a restriction. (reason = bb....bb) (M+J+O)

aa....aa cannot be specified. <SQLSTATE: 427A3>

aa....aa: Item that cannot be specified

special register "CURRENT_USER_IS_DBA"

bb....bb: Reason why the item cannot be specified

being used by the system: The item is being used by the system.

S:

Ignores this SQL statement.

Action:

Enclose CURRENT_USER_IS_DBA in double quotation marks (").

KFAA31204-E

An invalid item (aa....aa) was specified for the "WITH" clause. (M+J+O)

A dynamic parameter is specified in the WITH clause. <SQLSTATE: 427D3>

aa....aa: Items that cannot be specified in the WITH clause:

dynamic parameter: A dynamic parameter

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31205-E

The data type or length of aa....aa column is invalid. (query number = bb....bb) (M)

The data type or length of column aa....aa is invalid.

A value expression whose result has a data length of 0 was specified. <SQLSTATE: 42705>

aa....aa:

viewed table: A viewed table

derived table: A derived table

query name: A query name

bb....bb: Position number of the query that specified the invalid column

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31206-E

The aa....aa is invalid. (reason = bb....bb) (M+J+O)

The aa....aa specified is invalid. <SQLSTATE: 427A4>

aa....aa: Location of invalid specification

insert value: Insertion value specified in an INSERT statement

bb....bb: Cause of the error

specified identifier: An identifier was specified.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31207-E

The table name of the table reference for the query cannot be referenced from a subquery in an "ORDER BY" clause. (M+J+O)

Table names of table references specified in the query specification cannot be referenced from subqueries in ORDER BY clauses. <SQLSTATE: 427I7>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31208-E

The index specification is invalid. (table name="aa....aa"."bb....bb" as "cc....cc" reason = dd....dd) (M+J+O)

The index specification is invalid for table aa....aa.bb....bb (correlation name cc....cc).

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc: Correlation name

If no correlation name is specified, *** is displayed.

dd....dd: Cause of the error

query name: An index is specified for a query name. <SQLSTATE: 428F0>

viewed table: An index is specified for a viewed table. <SQLSTATE: 428F1>

foreign table: An index is specified for a foreign table. <SQLSTATE:428F2>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31209-E

The chunk ID specification method is invalid. (reason = aa....aa) (M+J+O)

The specification of the chunk ID is invalid.

aa....aa: Cause of the error

predicate kind: The predicate type is invalid. <SQLSTATE: 42767>

specified position: The specified position is invalid. <SQLSTATE: 42768>

no multi chunk table: The specified table is not a multi-chunk table. <SQLSTATE: 42769>

table kind: The table type is invalid. <SQLSTATE: 42769>

subquery: A subquery is specified. <SQLSTATE:4276B>

logical operator: A logical operator (AND, OR, or NOT) is specified. <SQLSTATE: 4276C>

comparison partner: The comparison partner is invalid. <SQLSTATE: 4276D>

value expression: A value expression is specified. <SQLSTATE: 4276E>

statement kind: The SQL statement type is invalid. <SQLSTATE: 4276F>

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA31210-E

The number of set operations with an EXCEPT or INTERSECT operator in the SQL statement exceeds 63. (M+J+O)

The number of set operations specified in an SQL statement that include EXCEPT or INTERSECT exceeds the maximum of 63 that can be specified. <SQLSTATE: 427A6>

S:

Ignores this SQL statement.

Action:

Specify 63 or fewer set operations.

KFAA31212-E

The datetime format specified in the scalar function is not compatible with the "TIME" data. (argument number = aaa, function name = "bb....bb", query number = cc....cc) (M+J+O)

The datetime format specified in the scalar function bb....bb is not compatible with the time data. <SQLSTATE: 42787>

aaa:

Argument number

bb....bb:

Scalar function name

cc....cc: Position number of the query that specified bb....bb

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the datetime format. Specify a datetime format (that specifies hours, minutes, or seconds) that is compatible with the time data.

KFAA31213-E

The format specification is invalid in a scalar function. (function name = aa....aa, reason = bb....bb, query number = cc....cc) (M+J+O)

The format specification is invalid in scalar function "aa....aa".

aa....aa:

Scalar function name

bb....bb: Cause of the error

value: The specified value is invalid. <SQLSTATE: 2250G>

data type: The data type specified in the format specification is invalid. <SQLSTATE: 42789>

data length: The data length specified in the format specification is invalid. <SQLSTATE: 4278A>

not literal: A non-literal is specified. <SQLSTATE: 4278B>

combination: A combination error occurred. <SQLSTATE: 4278C>

sequence: A sequence error occurred. <SQLSTATE: 4278D>

cc....cc: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the format specification.

KFAA31214-E

There are no format elements in the format specification of a scalar function. (function name = aa....aa, information = bb....bb, query number = cc....cc) (M+J+O)

A required element is missing from the format specification of scalar function "aa....aa". <SQLSTATE: 2250G>

aa....aa:

Scalar function name

bb....bb: Element required for the format specification:

YEAR: Year

MONTH: Month

DAY: Day

HOUR: Hour

MINUTE: Minute

SECOND: Second

NUMERIC: Numeric element

cc....cc: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the format specification.

KFAA31215-E

The PURGE CHUNK statement is invalid. (reason = aa....aa) (M+J+O)

The specified PURGE CHUNK statement is invalid.

aa....aa: Cause of the error

The chunk ID is not specified: The chunk ID is not specified in the search conditions. <SQLSTATE:427B5>

The column name in a table of a delete target is specified: A column in the table from which chunks are to be deleted is specified in the search conditions. <SQLSTATE:427BC>

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA31216-E

The specification of the "LIMIT" clause is invalid. (reason = aa....aa) (M+J+O)

The specified LIMIT clause is invalid.

aa....aa: Cause of the error

correlated subqueries: The LIMIT clause is specified for a derived table that has an external reference beyond the derived table for which the LIMIT clause is specified. For details, see Explanation of specification format in Specification format and rules for subqueries in the manual HADB SQL Reference. <SQLSTATE: 427I3>

specified position: The position of the specified LIMIT clause is invalid. <SQLSTATE: 427I4>

specified position of offset: The position at which the offset of the first row to return is specified is invalid. <SQLSTATE: 427I6>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31217-E

The data lengths of the arguments specified in aa....aa are not the same. (M+J+O)

The data lengths of the arguments specified in the scalar function "aa....aa" are different. <SQLSTATE: 2250I>

aa....aa:

a scalar function "BITAND": Scalar function BITAND

a scalar function "BITOR": Scalar function BITOR

a scalar function "BITXOR": Scalar function BITXOR

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31218-E

The total size of dynamic parameters exceeds 32,000,000 bytes. (M+J+O)

The total data length of dynamic parameters exceeds 32,000,000 bytes. <SQLSTATE: 56034>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

If you are specifying a dynamic parameter that is assumed to be of STRING type, use the scalar functions CAST or CONVERT to convert the assumed data type of the dynamic parameter to VARCHAR with the minimum required data length. The following shows an example of converting the assumed data type of a dynamic parameter to VARCHAR(100) by using the scalar functions CAST and CONVERT.

Example using the scalar function CAST

CAST(? AS VARCHAR(100))

Example using the scalar function CONVERT

CONVERT(?, VARCHAR(100))

KFAA31219-E

A viewed table whose view level is aa....aa cannot be specified in the CREATE VIEW statement. (M+J+O)

A viewed table whose view level is aa....aa cannot be specified in the CREATE VIEW statement. <SQLSTATE: 42737>

aa....aa:

View level of the viewed table specified in the SQL statement

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31223-E

The subquery method specification is invalid. (reason = aa....aa, query number = bb....bb) (M+J+O)

The specified subquery processing method specification is invalid. <SQLSTATE: 428F5>

aa....aa: Cause of the error

specified in a subquery of a derived table

The subquery processing method specification is specified for a table subquery of a derived table.

specified in a subquery of multiset value constructor by query

The subquery processing method specification is specified for a table subquery of a multiset value constructor by query.

bb....bb: Position number of the query that specified the subquery processing method specification

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31224-E

The specification method of a LISTAGG set function is invalid. (reason = aa....aa, query number = bb....bb) (M+J+O)

The specified LISTAGG set function is invalid.

aa....aa: Cause of the error

the length of the LISTAGG separator character string exceeds the maximum length of the LISTAGG result character string

The length of the LISTAGG separator character string exceeds the specified maximum length of the LISTAGG result character string. <SQLSTATE:4271A>

the value specified as the maximum length of the LISTAGG result character string is outside the valid range

The specified value of the maximum length of the LISTAGG result character string is outside the specifiable range. <SQLSTATE:4271B>

the length of the trailing character string to be truncated exceeds the maximum length of the LISTAGG result character string

The length of the truncated string suffix exceeds the specified maximum length of the LISTAGG result character string. <SQLSTATE: 4271C>

bb....bb: Position number of the query that specified the LISTAGG set function

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31226-E

The scalar function "LTDECODE" is specified incorrectly. (reason = aa....aa, query number = bb....bb) (M+J+O)

The specified scalar function LTDECODE contains an error. <SQLSTATE: 4278S>

aa....aa: Cause of the error

a dynamic parameter by itself cannot be specified for all of the target data and comparison data

Parameters cannot be specified so that all of the following conditions are satisfied.

Only a single dynamic parameter is specified for the target data.

Only a single dynamic parameter is specified for all of the comparison data.

a dynamic parameter by itself or NULL cannot be specified for all of the return value and predefined return value

Parameters cannot be specified so that all of the following conditions are satisfied.

Only a single dynamic parameter is specified for all of the return values, or NULL is specified.

Only a single dynamic parameter is specified for the predefined return value, or NULL is specified.

bb....bb: Query position number

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31227-E

The scalar function "TIMESTAMPADD" is specified incorrectly. (reason = aa....aa, query number = bb....bb) (M+J+O)

The specified scalar function TIMESTAMPADD is invalid.

The combination of the data type of the target data and the date/time unit designation is invalid. <SQLSTATE:4278T>

A value that is outside the specification range is specified in the add value. <SQLSTATE: 4278U>

aa....aa: Cause of the error

the combination of the data type of the target data and the datetime unit is invalid

The combination of the data type of the target data and the date/time unit designation is invalid.

the addition value is outside the valid range

A value that is outside the specification range is specified in the add value.

The following shows the combinations of range of numeric data values that can be specified for the date and time units and add value.

YEAR: -9,998 to 9,998

QUARTER: -39,995 to 39,995

MONTH: -119,987 to 119,987

DAYOFYEAR: -3,652,058 to 3,652,058

DAY: -3,652,058 to 3,652,058

WEEK: -521,722 to 521,722

HOUR: -87,649,415 to 87,649,415

MINUTE: -5,258,964,959 to 5,258,964,959

SECOND: -315,537,897,599 to 315,537,897,599

MILLISECOND: -315,537,897,599,999 to 315,537,897,599,999

MICROSECOND: -315,537,897,599,999,999 to 315,537,897,599,999,999

NANOSECOND: -9,223,372,036,854,775,807 to 9,223,372,036,854,775,807

PICOSECOND: -9,223,372,036,854,775,807 to 9,223,372,036,854,775,807

bb....bb: Query position number

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31234-E

The scalar function "aa....aa" is specified incorrectly. (reason = bb....bb) (M+J+O)

The specified scalar function "aa....aa" is invalid.

aa....aa:

Scalar function name

bb....bb: Cause of the error

predicate kind: The predicate type is invalid. <SQLSTATE: 4278O>

specified position: The specified position is invalid. <SQLSTATE: 4278P>

comparison partner: The comparison partner is invalid. <SQLSTATE:4278Q>

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA31235-E

There is an error in the specification method of a scalar function argument. (function name = "aa....aa", reason = bb....bb, query number = cc....cc) (M+J+O)

The specification method of the aa....aa scalar function is invalid.

aa....aa:

Name of the scalar function in which the error occurred

bb....bb: Cause of the error

the identification number is outside the valid range

The value of the identification number exceeds the range that can be specified. <SQLSTATE: 4278J>

the total number of the types of scalar functions specified in the SQL statement exceeds 1,000

The total number of the types of identification numbers for the aa....aa scalar function that can be specified in the SQL statement exceeds 1,000. <SQLSTATE: 4278K>

specified position is invalid

The aa....aa scalar function is specified in an invalid position. <SQLSTATE: 4278M>

the specification of scalar functions that have the same identification number is invalid

The specification method of aa....aa scalar functions that have the same identification number is invalid. <SQLSTATE: 4278N>

cc....cc: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

However, if the value of SQLSTATE for bb....bb is 4278K, three asterisks (***) are displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Check the rules for the scalar function displayed for aa....aa in the manual HADB SQL Reference, and then correct the SQL statement.

If bb....bb is the specification of scalar functions that have the same identification number is invalid, take one of the following actions:

If aa....aa is RANDOMCURSOR

Correct the RANDOMCURSOR scalar functions specified with the same identification number in the SQL statement by using one of the following methods:

Specify minimum and maximum values for only one RANDOMCURSOR scalar function (do not specify those values for any other RANDOMCURSOR scalar functions).

Do not specify minimum and maximum values for any RANDOMCURSOR scalar functions.

If aa....aa is RANDOMROW

Correct the RANDOMROW scalar functions specified with the same identification number in the query specification by using one of the following methods:

Specify minimum and maximum values for only one RANDOMROW scalar function (do not specify these values for any other RANDOMROW scalar functions).

Do not specify minimum and maximum values for any RANDOMROW scalar functions.

KFAA31239-E

The specification of the table function column list is invalid. (reason = aa....aa, query number = bb....bb) (M+J+O)

The table function column list specified in the table function derived table is invalid. <SQLSTATE: 427JA>

aa....aa: Cause of the error

the table function column list cannot be specified for the system-defined function "ADB_AUDITREAD"

If the ADB_AUDITREAD function is specified in the table function derived table, the table function column list cannot be specified.

the table function column list is not specified for the system-defined function "ADB_CSVREAD"

If the ADB_CSVREAD function is specified in the table function derived table, the table function column list must be specified.

the table function column list cannot be specified for the system-defined function "ADB_GENERATE_SERIES"

If the ADB_GENERATE_SERIES function is specified in the table function derived table, the table function column list cannot be specified.

bb....bb: Position number of the query that specified the table function derived table

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31240-E

The specification of the table function derived table that includes the system-defined function "aa....aa" is invalid. (reason = bb....bb, detail = cc....cc, query number = dd....dd) (M)

The specification of the table function derived table with the system-defined function aa....aa specified is invalid.

aa....aa:

System-defined function name

bb....bb: Cause of the error

specified position: The specified position is invalid. <SQLSTATE: 427K0>

cc....cc: Details about the error

the table cannot be specified in correlated subqueries: The table function derived table cannot be specified in a subquery that includes an external reference column.

the table cannot be specified in a multiset value expression: The table function derived table cannot be specified in a multiset value expression.

dd....dd: Position number of the query that specified the table function derived table

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31241-E

The argument specified in the system-defined function "aa....aa" is invalid. (argument number = bb....bb, reason = cc....cc, query number = dd....dd) (M+J+O)

The argument specified in the system-defined function aa....aa is invalid.

aa....aa:

System-defined function name

bb....bb:

Number of the argument that contains the error in the system-defined function

cc....cc:

Cause of the error

data type is incorrect

The data type is invalid. <SQLSTATE: 427K1>

the argument cannot be omitted in a multi-node configuration

If the multi-node function is used, a required argument is omitted. <SQLSTATE: 427K2>

dd....dd: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31242-E

A multiset value constructor by query cannot be specified as an argument of the system-defined function "ADB_AUDITREAD". (query number = aa....aa) (M+J+O)

A multiset value constructor by query cannot be specified as an argument of the ADB_AUDITREAD function. <SQLSTATE: 427K5>

aa....aa: Position number of the query that specified the ADB_AUDITREAD function

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31243-E

The set of audit trail file path names is invalid as a result of applying special characters in the audit file path names specified as the argument of the system-defined function "ADB_AUDITREAD". (reason = aa....aa, query number = bb....bb) (M+J+O)

There is a problem with the audit trail file path names (that contain special characters) specified as the argument of the ADB_AUDITREAD function.

aa....aa: Cause of the error

no audit trail file path is specified for the input data

There is no audit trail file that will be the input data. <SQLSTATE: 427K6>

the input data includes more than 65535 audit trail file path names

The number of audit trail files that will be the input data exceeds 65,535. <SQLSTATE: 427K7>

bb....bb: Position number of the query that specified the ADB_AUDITREAD function

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take the corrective action for the cause of the error displayed for aa....aa.

Cause of the error displayed for aa....aa

Specification of arguments in the ADB_AUDITREAD function

Corrective action to take

no audit trail file path is specified for the input data

Argument specified

Correct the audit trail file path names containing special characters specified as the argument of the ADB_AUDITREAD function. (Correct the audit trail file path names so that audit trail files that will be the input data of the ADB_AUDITREAD function exist.)

Note that the current audit trail file will not be the input data of the ADB_AUDITREAD function.

If you want to view an audit trail in the current audit trail file, swap the current audit trail file, and then execute the SELECT statement with the ADB_AUDITREAD function specified.

Argument not specified

An audit trail file other than the current one does not exist under the audit trail directory. Therefore, there is no audit trail file that will be the input data of the ADB_AUDITREAD function. If you want to view an audit trail in the current audit trail file, swap the current audit trail file, and then execute the SELECT statement with the ADB_AUDITREAD function specified.

If you want to view an audit trail file stored in a place that is not under the audit trail directory, specify the path name of that audit trail file in the ADB_AUDITREAD function.

the input data includes more than 65535 audit trail file path names

Argument specified

Correct the audit trail file path names containing special characters specified as the argument of the ADB_AUDITREAD function. Make sure that the number of audit trail files that will be the input data of the ADB_AUDITREAD function does not exceed 65,535.#

Argument not specified

Make sure that the number of audit trail files under the audit trail directory does not exceed 65,535.# For example, move audit trail files to the audit trail storage directory.

#

The current audit trail file is not subject to counting.

Note

The audit trail directory is the directory specified in the adb_audit_log_path operand in the server definition.

For details about how to swap the current audit trail file, see Swapping the current audit trail file in the HADB Setup and Operation Guide.

KFAA31245-E

There is an error in the specification method of an array element reference. (reason = aa....aa, query number = bb....bb) (M+J+O)

The specified array element reference is invalid.

aa....aa: Invalid cause

Value of aa....aa

Description

SQLSTATE

the array value expression is not array data

The array value expression is not array data.

427P1

a dynamic parameter is specified in an array value expression

A dynamic parameter has been specified in an array value expression

427P2

specified position of the array element reference is invalid

The specified position for the array element reference is invalid.

427P3

column specifications of different table references are specified in a predicate that includes an array element reference for which ANY is specified

A different table reference column specification is being specified for a predicate that includes an array element reference with ANY specified.

427P4

a scalar subquery is specified in a predicate that includes an array element reference for which ANY is specified

A scalar subquery is specified for a predicate containing an array element reference with ANY specified.

427P5

column specifications of different table references are specified for an array element reference that has the same identification number and for which ANY is specified

A column specification for an array element reference that specifies ANY with the same identification number is specified for a column specification of a different table reference.

427P6

more than 255 types of identification numbers of array element references for which ANY is specified

The total number of the specified array element reference identification numbers specifying ANY specified in the SQL statement exceeds 255.

427P7

bb....bb: Position number of the query that specified the array element reference

For details about query position numbers, see 1.5 Query position numbers.

However, if the value of SQLSTATE for aa....aa is 427P7, three asterisks (***) are displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

See Specification format and rules for array element references in the manual HADB SQL Reference and correct the SQL statement.

KFAA31255-E

Struct data cannot be specified in aa....aa. (query number = bb....bb) (M+J+O)

Structure data cannot be specified in aa....aa. <SQLSTATE:427MC>

aa....aa: Invalid specification

sort key: Sort key

select expression of the outermost query for a set operation:

Selection expression of the outermost query specification for a set operation

select expression of the outermost query specification in statements other than COPY and CREATE VIEW:

Selection expression for the outermost query specification (except in the COPY and CREATE VIEW statements)

select expression of scalar subquery: Selection expression of scalar subquery

grouping column: Grouping column

row value constructor element: Row value constructor element

IN predicate: An IN predicate

QUANTIFIED predicate: A quantified predicate

CASE expression: A CASE expression

bb....bb: Query position number

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31256-E

Struct data cannot be specified in aa....aa that includes DISTINCT. (query number = bb....bb) (M+J+O)

Structure data cannot be specified in aa....aa with DISTINCT specified. <SQLSTATE:427MD>

aa....aa: Invalid specification

select expression: Selection expression

set function: Set function

bb....bb: Query position number

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31257-E

The specification method of the field reference is invalid (reason = aa....aa, query number = bb....bb) (M+J+O)

The specification method of the field reference is invalid. <SQLSTATE:427ME>

aa....aa: Reason for error

the parameter cannot be specified in a struct value expression:

Dynamic parameters cannot be specified in a structure value expression.

the struct value expression is not struct data:

The structure value expression is not structure data.

the field name is not included in struct data:

The field name is not included in the structure data.

bb....bb: Query position number

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31260-E

The numbers of row value constructor elements of the row value constructors specified for the table value constructor are not the same. (query number = aa....aa) (M+J+O)

The numbers of row value constructor elements specified in the row value constructors do not match. <SQLSTATE: 427L0>

aa....aa: Position number of the query that specified the table value constructor

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31261-E

A row value constructor element specified for the row value constructor is invalid. (reason = aa....aa, query number = bb....bb) (M+J+O)

The specified row value constructor element is invalid. <SQLSTATE: 427M0>

aa....aa: Cause of the error

invalid argument in a scalar function "CAST": The argument specified in the scalar function CAST is invalid.

invalid argument in a scalar function "CONVERT": The argument specified in the scalar function CONVERT is invalid.

bb....bb: Position number of the query that specified the row value constructor

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31262-E

Dynamic parameters cannot be specified for the row value constructor elements of row value constructors specified for the table value constructor. (query number = aa....aa) (M+J+O)

A dynamic parameter alone cannot be specified in a row value constructor element. <SQLSTATE: 427M1>

aa....aa: Position number of the query that specified the table value constructor

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31263-E

There is an error in the specification method of aa....aa predicate for which a row value constructor is specified. (reason = bb....bb, query number = cc....cc) (M+J+O)

The specification method of the aa....aa that specified a row value constructor is invalid.

aa....aa: Type of predicate that contains error

COMPARISON: A comparison predicate

IN: An IN predicate

bb....bb: Reason for error

Value of bb....bb

Description

SQLSTATE

a row value constructor can be compared with other row value constructors only

Row value constructors and non-row value constructors are compared. Row-value constructors can only be compared to row-value constructors.

427M2

the specified value of the row value constructor element is invalid

The specified value of the row value constructor element is invalid.

427M3

the specified position of the predicate is invalid

The specified position of the predicate is invalid.

427M4

the comparison operator is invalid

A comparison operator is invalid.

427M5

cc....cc: Position number of the query that specified the predicate

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31264-E

There is an error in the specification method of aa....aa in the bb....bb. (reason = cc....cc) (M+J+O)

The specification method of aa....aa of bb....bb is invalid. <SQLSTATE:427M6>

aa....aa: Location of invalid specification

access key string: Access key string

secret key string: Secret key string

endpoint string: Endpoint string

foreign server option: Foreign server option

ALTER SERVER option: Foreign server definition modification option

bb....bb: Invalid SQL statement

ALTER SERVER statement: ALTER SERVER statement

CREATE SERVER statement: CREATE SERVER statement

cc....cc: Reason for the error

The reason for the error and an example of how this message is output are shown below.

Value of cc....cc

Description

Example of how this message is output

the data length exceeds the range that can be specified

The data length has exceeded the range that can be specified.

The data length of the access key string, secret key string, or endpoint string exceeds 100 bytes.

the specified option is duplicated

The specified option is specified more than once.

The same foreign server option (underlined) is specified in the CREATE SERVER statement as follows.

Example:

CREATE SERVER "S001" OPTIONS (

ACCESS_KEY 'ACCESS1'

,SECRET_KEY 'SECRET1'

,SECRET_KEY 'SECRET2')

the ALTER SERVER options for a different operation cannot be specified

When multiple foreign server definition modification options are specified, different operations cannot be specified.

Different operations (underlined) are specified in the foreign server definition modification option of the ALTER SERVER statement as follows.

Example:

ALTER SERVER "S001" OPTIONS (

ADD ACCESS_KEY 'ACCESS1'

,SET SECRET_KEY 'SECRET1')

the same option with ALTER SERVER options cannot be specified

When multiple foreign server definition modification options are specified, the same foreign server option cannot be specified.

The same foreign server option (underlined) is specified in the foreign server definition modification option of the ALTER SERVER statement as follows.

Example:

ALTER SERVER "S001" OPTIONS (

SET SECRET_KEY 'SECRET1'

,SET SECRET_KEY 'SECRET2')

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31265-E

There is an error in the specification method of aa....aa in the CREATE FOREIGN TABLE statement. (reason = bb....bb) (M+J+O)

The specification method for aa....aa of the CREATE FOREIGN TABLE statement is invalid. <SQLSTATE:427M7>

aa....aa: Location of invalid specification

foreign table option: Foreign table option

foreign data directory path string: Foreign data directory path string

template directory path string: Template directory path string

delimiter character: Delimiter character

enclosing character: Enclosing character

enumeration string: Enumeration string

minimum value string or integer: Minimum value string or minimum value integer

maximum value string or integer: Maximum value string or maximum value integer

datetime format string: Date and time format string

interval value: Interval value

digit value: Number of digits

catalog namespace: Catalog namespace

catalog endpoint string: Catalog endpoint string

catalog region: Catalog region name

catalog ID: Catalog ID

warehouse name: Warehouse name

token URI: Token URI

client ID: Client ID

client secret: Client secret

allowed scope string: Allowed scope string

bb....bb: Cause of the error

the data length exceeds the range that can be specified

The data length exceeds the range that can be specified.

the value exceeds the range that can be specified

The value exceeds the range of values that can be specified.

the specified option is duplicated

The specified option is specified more than once.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31266-E

There is an error in the specification method of aa....aa. (reason = bb....bb, query number = cc....cc) (M+J+O)

The specification method of aa....aa is invalid. <SQLSTATE:427M8>

aa....aa: Location of invalid specification

foreign table: Table name of the foreign table

time travel specification: Time travel specification

bb....bb: Cause of the error

the specified position

The specified position is invalid.

the time travel specification is not specified for a foreign table that references an Iceberg table

The aa....aa can only be specified for a foreign table that references an Iceberg table.

the specified value for the snapshot ID is invalid

The specified value for the snapshot ID specification is invalid.

the specified value for the timestamp specification is invalid

The specified value for the timestamp specification is invalid.

cc....cc: Position number of the query

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31267-E

There is an error in the specification method of aa....aa in the COPY statement. (reason = bb....bb) (M+J+O)

The specification method of aa....aa of the COPY statement is invalid. <SQLSTATE:427MA>

aa....aa: Location of invalid specification

output location string: Output location string

delimiter character: Delimiter character

COPY option: COPY option

bb....bb: Cause of the error

the data length exceeds the range that can be specified

The data length exceeds the range that can be specified.

the same type of option is duplicated

The option specified in the COPY option is specified more than once.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31268-E

There is an error in the specification method of aa....aa in the COPY statement. (reason = bb....bb) (M+J+O)

The specification method of aa....aa of the COPY statement is invalid. <SQLSTATE: 427MB>

aa....aa: Position of error

output location string: Output location string

COPY option: COPY option

delimiter character specification: Delimiter character specification

header specification: Header specification

output data compression format specification: Output data compression format specification

the column derived from the result of the query expression body: The column derived from the result of the query expression body

bb....bb: Cause of the error

's3://' or 'file://' is not specified at the beginning of the string

s3:// or file:// is not specified at the beginning of the string.

If the data output destination is object storage, the output location string must start with s3://.

If the data output destination is file storage, the output location string must start with file://.

the specification cannot be specified when the output data format is CSV

Cannot be specified if the output data format is CSV format.

the specification cannot be specified when the output data format is not CSV

The specification cannot be specified when the output data format is not CSV.

the data type of the derived column is invalid

The data type of the derived column is invalid.

a foreign server cannot be specified when the output location string is specified in FILE URI format (when the output destination of the file is file storage)

When the output location string is specified in FILE URI format (i.e., when the data output destination is file storage), the foreign server cannot be specified.

a foreign server cannot be omitted when the output location string is specified in S3 URI format (when the output destination of the file is object storage)

When the output location string is specified in S3 URI format (i.e., when the data output destination is object storage), the foreign server must be specified.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

If bb....bb is the data type of the derived column is invalid, then the column derived from the result of the query expression body of the COPY statement corresponds to one of the following data types. Therefore, the COPY statement resulted in an error.

When the output data format is PARQUET format

TIME(0)

TIME(12)

TIMESTAMP(0)#

TIMESTAMP(12)#

An ARRAY type with one of the above data types specified as the element data type, or a STRUCT type with one of the above data types specified as the field data type.

When the output data format is CSV format

TIME(12)

TIMESTAMP(12)#

UUID

ARRAY

STRUCT

Correct the query expression body of the COPY statement so that the column derived from the result of the COPY statement query expression body is of a data type other than the above.

#

This applies to both TIMESTAMP WITHOUT TIME ZONE type and TIMESTAMP WITH TIME ZONE type.

KFAA31269-E

The derived column list cannot be specified for aa....aa. (M+J+O)

The derived column list cannot be specified in aa....aa. <SQLSTATE: 4275B>

aa....aa:

the table function derived table that specifies the system-defined function ADB_AUDITREAD

The table function derived table with the ADB_AUDITREAD function specified

the table function derived table that specifies the system-defined function ADB_CSVREAD

The table function derived table with the ADB_CSVREAD function specified

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31270-E

There is an error in the specification method of aa....aa in the system-defined function ADB_GENERATE_SERIES. (reason = bb....bb) (M+J+O)

The specification of aa....aa in the ADB_GENERATE_SERIES function is invalid. <SQLSTATE: 4275C>

aa....aa: Location of invalid specification

start value: Start value

end value: End value

step value: Interval value

argument: Argument

function: Function

bb....bb: Cause of the error

the data type is invalid

The data type is incorrect.

a dynamic parameter by itself cannot be specified

The dynamic parameter cannot be specified by itself.

the combination of arguments is invalid

The combination of arguments is incorrect.

the specification cannot be omitted

The specification cannot be omitted.

the interval value cannot be 0

A value of 0 cannot be specified for the interval value.

only a constant can be specified for a labeled duration

Only literals can be specified for labeled durations.

the specification of the labeled duration modifier is invalid

There is an error in the specification of the labeled duration qualifier.

the arguments are of data types that cannot be compared

The data type of the argument is not a comparable data type.

the specified column is not from a table that is comma joined with the system-defined function ADB_GENERATE_SERIES, or the column is from a joined table

The column is not from a comma-joined table with the ADB_GENERATE_SERIES function, or it is from a joined table.

columns from different tables are being specified

Columns from different tables are specified.

a subquery of the specified in the argument is correlated subquery

An external reference column is specified.

the system-defined function ADB_GENERATE_SERIES is specified more than once in the query specification

Two or more ADB_GENERATE_SERIES functions are specified in the query specification.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31271-E

The column definition information for the foreign table "aa....aa" in the view definition during definition of the view table differs from the information during retrieval of the view table. (reason = "bb....bb") (M+J+O)

The column definitions of the foreign table aa....aa specified in the CREATE VIEW statement differ between when the view table was defined and when the view table was retrieved. <SQLSTATE: 4275D>

aa....aa:

Name of the foreign table

bb....bb:

Name of the column or field that caused the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The column definition of the column or field bb....bb differs between when the view table was defined and when the view table was searched. One of the following is different.

Name

Data type

Data length

Maximum number of elements

Number of columns

Number of fields

Recreate the view table, which uses the foreign table aa....aa as its underlying table, in ascending view level order using the ALTER VIEW statement or similar. For details about the ALTER VIEW statement, see ALTER TABLE (alter table definition) in the manual HADB SQL Reference.

Note that this message may be output when retrieving a view table that meets all of the following conditions.

A view table is defined using a foreign table that has a STRUCT type column as its underlying table in HADB server version 06-00.

The HADB server has been upgraded to version 06-01 or later.

KFAA31280-E

The specified SQL statement is invalid. (reason = aa....aa) (M)

The SQL statement specification contains an error.

aa....aa: Cause of the error

a column store table or a viewed table for which a column store table is specified in the outermost query in the viewed table definition, cannot be deleted, inserted, or updated

The following tables cannot be specified as target tables for deletion, insertion, or updating. <SQLSTATE: 42875>

Column store table

A viewed table that is defined by specifying a column store table in the outermost query specification

a table that defines the array-type columns cannot be deleted, inserted, or updated

The following tables cannot be specified as target tables for deletion, insertion, or updating. <SQLSTATE: 42875>

Table defining array-type columns

a LISTAGG set function cannot be specified in the window function

A LISTAGG set function cannot be specified in the window function. <SQLSTATE:42876>

an ARRAY_AGG set function cannot be specified in the window function

A ARRAY_AGG set function cannot be specified in the window function. <SQLSTATE:42877>

an array-type column cannot be specified as an external reference column

An array-type column cannot be specified as an external reference column. <SQLSTATE:42878>

rows cannot be deleted, inserted or updated using the cloud storage facility

When using the cloud storage facility, the INSERT, UPDATE, and DELETE statements cannot be executed. <SQLSTATE:42879>

the position of the "ORDER BY" clause specified in the subquery is invalid

A ORDER BY clause specified in the subquery is specified at an invalid location. <SQLSTATE:4287A>

the "LIMIT" clause must be specified when the "ORDER BY" clause is specified in the subquery or the with list element

If an ORDER BY clause is specified for a subquery or WITH list element, the LIMIT clause must also be specified. <SQLSTATE:4287B>

a struct-type column cannot be specified as an external reference column

A STRUCT-type column cannot be specified as an external reference column. <SQLSTATE:4287C>

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA31301-E

The aa....aa is incorrectly specified. (reason = bb....bb) (M+J+O)

The specified LIMIT clause or window frame border is invalid.

A value specified in the window frame value specification for a window frame border is invalid. <SQLSTATE: 22013>

The value specified for row-count or offset in the LIMIT clause is invalid. <SQLSTATE: 22510>

The data type of row-count or offset in the LIMIT clause is invalid. <SQLSTATE: 429D9>

aa....aa: Invalid specification

limit row count: The maximum number of rows to return (row-count) as specified in the LIMIT clause

offset row count: The offset of the first row to return (offset) as specified in the LIMIT clause

window frame bound: Window frame border

bb....bb: Cause of the error

value: The specified value is invalid.

data type: The specified data type is invalid.

S:

Ignores this SQL statement.

Action:

Correct the SQL statement.

KFAA31306-E

The number a argument in the CLI function "bb....bb" is invalid.(number = cc....cc, reason = dd....dd) (M+J+O)

The ath argument of CLI function bb....bb is invalid. <SQLSTATE: 54001>

a:

Order number of argument

bb....bb:

CLI function

cc....cc:

Specification sequence of ColumnInfo or ParameterInfo

dd....dd:

Cause of the error

S:

Ignores this SQL statement.

Action:

The following table shows the corrective action to take:

Value of a

Value of bb....bb

Value of cc....cc

Value of dd....dd

Corrective action to take

3

a_rdb_SQLBindArrayParams

0

ARRAY COUNT

The value specified in the argument ArrayCount is invalid. Specify a value of 1 or higher.

4

a_rdb_SQLBindArrayParams

0

PARAMETER COUNT

The value specified in the argument ParameterCount is invalid. Specify the number of dynamic parameters acquired with a_rdb_SQLNumParams().

5

a_rdb_SQLBindArrayParams

0 or more

PARAMETER INFO

If the value of cc....cc is 0, the address specified in the argument ParameterInfo is invalid.

If the value of cc....cc is 1 or more, the address specified in the cc....ccth place of the address array specified in the argument ParameterInfo is invalid.

In either case, specify a correct address.

5

a_rdb_SQLBindArrayParams

0 or more

PARAMETER VALUE

The address of a member of ParameterValue in one of the following ParameterInfo structures is invalid:

Array number of a ParameterInfo structure that includes the invalid ParameterValue:

Value of cc....cc divided by the argument ParameterCount

Position of a ParameterInfo structure that includes the invalid ParameterValue:

Remainder of cc....cc divided by the argument ParameterCount + 1

If a value other than the one specified in a_rdb_SQL_NULL_DATA was specified in the member Ind of the ParameterInfo structure, specify a valid address.

3

a_rdb_SQLBindCols

0

COLUMN COUNT

The value set is different from the column count returned by a_rdb_SQLNumResultCols(). Set the same value.

4

a_rdb_SQLBindCols

0

COLUMN INFO

The address specified in the argument ColumnInfo is invalid. Set the correct address.

4

a_rdb_SQLBindCols

1 or more

BUFFER LENGTH

The value of member BufferLength of the ColumnInfo structure specified in the cc....ccth position does not match the column length of the cc....ccth column found by the search. Guided by the column information returned by a_rdb_SQLDescribeCols(), set a valid value.

4

a_rdb_SQLBindCols

1 or more

TARGET VALUE

The address of member TargetValue of the ColumnInfo structure specified in the cc....ccth position is invalid. Set the correct address.

4

a_rdb_SQLBindCols

0

ARRAY TYPE

Column binds cannot be performed on search item columns of array type. Correct the SQL statement so that the data type of the search item column does not become an array type.

3

a_rdb_SQLBindParams

0

PARAMETER COUNT

The value set is different from the parameter count returned by a_rdb_SQLNumParams(). Set the same value.

4

a_rdb_SQLBindParams

0

PARAMETER INFO

The address specified in the argument ParameterInfo is invalid. Set the correct address.

4

a_rdb_SQLBindParams

1 or more

PARAMETER VALUE

The address of member ParameterValue of the ParameterInfo structure specified in the cc....ccth position is invalid. If a value other than a_rdb_SQL_NULL_DATA was set in the member Ind of the ParameterInfo structure, set a valid address.

3

a_rdb_SQLDescribeCols

0

COLUMN COUNT

The value set is different from the column count returned by a_rdb_SQLNumResultCols(). Set the same value.

4

a_rdb_SQLDescribeCols

0

COLUMN INFO

The address specified in the argument ColumnInfo is invalid. Set the correct address.

4

a_rdb_SQLDescribeCols

1 or more

NAME BUFFER LENGTH

The value of BufferLength in the ColumnNameInfo structure indicated by member NameInfo of the ColumnInfo structure specified in the cc....ccth position is too small. Increase the value.

4

a_rdb_SQLDescribeCols

1 or more

NAME

The address specified in Name in the ColumnNameInfo structure indicated by member NameInfo of the ColumnInfo structure specified in the cc....ccth position is invalid. Set the correct address.

3

a_rdb_SQLDescribeParams

0

PARAMETER COUNT

The value set is different from the parameter count returned by a_rdb_SQLNumParams(). Set the same value.

4

a_rdb_SQLDescribeParams

0

PARAMETER INFO

The address specified in the argument ParameterInfo is invalid. Set the correct address.

3

a_rdb_SQLNumResultCols

0

COLUMN COUNT

The address specified in the argument ColumnCount is invalid. Set the correct address.

3

a_rdb_SQLNumParams

0

PARAMETER COUNT

The address specified in the argument ParameterCount is invalid. Set the correct address.

KFAA31307-E

At least one dynamic parameter does not have a set value. (M+J+O)

There is a dynamic parameter for which no value is set. <SQLSTATE: 24512>

S:

Ignores this SQL statement.

Action:

Take one of the following corrective actions:

Set a value for the dynamic parameter in the SQL statement using a_rdb_SQLBindParams or a_rdb_SQLBindArrayParams.

If a dynamic parameter was specified in an SQL statement specified by a_rdb_SQLExecDirect, either correct it to an SQL statement that does not specify a dynamic parameter, or re-execute the SQL statement with a_rdb_SQLExecute. However, if re-executing using a_rdb_SQLExecute, after the SQL statement preprocessing is completed, set a value for the dynamic parameter in the SQL statement using a_rdb_SQLBindParams or a_rdb_SQLBindArrayParams.

KFAA31310-E

An error has already occurred in the opened cursor. (M+J+O)

An error has already occurred in the opened cursor. Close the cursor. <SQLSTATE: 24513>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Eliminate the cause of the error generated previously for the query whose cursor is open, and then re-execute the SQL statement.

KFAA31371-E

The SQL statement cannot be executed because a required resource is locked. (name = aa....aa, object = bb....bb) (M+J+O)

The SQL statement cannot be executed because another SQL statement or command has locked a resource that the SQL statement needs to execute. <SQLSTATE: 52401>

aa....aa: Name of locked resource

DBAREA: DB area

TABLE: Table

bb....bb: Locked resource to be acquired

If aa....aa is DBAREA

"cc....cc"

If aa....aa is TABLE

"dd....dd"."ee....ee"

cc....cc:

DB area name

dd....dd:

Schema name

ee....ee:

Table name

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Wait for the other SQL statement or command that has locked the resource to terminate, and then re-execute the SQL statement. For details about locked resources acquired during SQL statement and command execution, see Locked resources that are reserved and their lock modes in the HADB Setup and Operation Guide.

KFAA31372-E

An error occurred during execution of an SQL statement that uses hash tables. (information1 = aa....aa, information2 = bb....bb, information3 = cc....cc, information4 = dd....dd) (M+J+O)

An error occurred when an SQL statement that uses hash tables was executing. <SQLSTATE: 5100J>

aa....aa: Cause of the error

INSUFFICIENT MEMORY: The adb_sql_exe_hashtbl_area_size operand value (hash table area size) is too small for the executed SQL statement.

bb....bb:

Maintenance information

cc....cc:

Maintenance information

dd....dd:

Maintenance information

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Specify a larger value in the adb_sql_exe_hashtbl_area_size operand in the server or client definition.

If the error still occurs, take the following correction action:

If the error occurs when executing a SQL statement that specifies a GROUP BY clause, use a grouping method specification. For details about grouping method specifications, see Specification format and rules for GROUP BY clauses in the manual HADB SQL Reference.

KFAA31373-E

There is an error in the specification method of a scalar function argument. (function name = "aa....aa", reason = "bb....bb") (M+J+O)

There is an error in the specification format of scalar function aa....aa.

aa....aa:

Scalar function name

bb....bb: Cause of the error

data length insufficient: The result data is too short. <SQLSTATE: 22001>

overflow: An overflow occurred. <SQLSTATE: 22003>

format: There is an error in the character string format of the data to be converted. <SQLSTATE: 22018>

value: The value of the data to be converted is invalid. <SQLSTATE: 22018>

out of range: A value outside of the range that can be converted to the elements specified in the format specification is specified in the target data. <SQLSTATE: 22522>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

Note that this error might be output by a CONVERT scalar function that was generated internally when viewed tables defined prior to upgrading the version are searched after the version is upgraded. If this occurs, re-define the viewed table. For details about the conditions that generate the scalar function CONVERT, see Notes on version upgrading in Upgrading the HADB server version in Building a System of the HADB Setup and Operation Guide.

KFAA31375-E

The argument of the aggregate function "aa....aa" is invalid. (M+J+O)

There is an error in the range of the argument value for set function aa....aa. <SQLSTATE: 22003>

aa....aa:

Set function name

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31376-E

The aa....aa cannot be executed because one or more update chunks contains an archived chunk. (chunk ID = bb....bb) (M+J+O)

An attempt to execute the DELETE statement for the archivable multi-chunk table caused an error because the specified search condition did not meet the execution condition of the DELETE statement.

Alternatively, an attempt to execute the UPDATE statement for the archivable multi-chunk table caused an error because the specified search condition did not meet the execution condition of the UPDATE statement. <SQLSTATE: 5100K>

aa....aa: SQL statement that caused the error

DELETE statement: DELETE statement

UPDATE statement: UPDATE statement

bb....bb:

Chunk ID of the chunk subject to execution of the SQL statement

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Confirm that the search condition specified in the UPDATE statement or DELETE statement is appropriate. For details, see the following parts in the manual HADB SQL Reference:

Rules in Specification format and rules for the DELETE statement

Rules in Specification format and rules for the UPDATE statement

If you want to delete data in an archived chunk, release the chunk bb....bb from the archived state, and then execute the DELETE statement.

If you want to update data in an archived chunk, release the chunk bb....bb from the archived state, and then execute the UPDATE statement.

KFAA31377-E

The number of recursions in the recursive query exceeds the maximum (aa....aa). (M+J+O)

The number of recursions in the recursive query exceeds the maximum number of recursions aa....aa. <SQLSTATE: 5100L>

aa....aa:

Maximum number of recursions

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement according to the following actions:

The number of recursions in the recursive query exceeds the maximum number of recursions. Increase the maximum number of recursions.

An infinite loop might have occurred in the recursive query. Revise the termination condition of the recursive query, and then eliminate the infinite loop.

KFAA31378-E

An error occurred during the execution of SQL statements by using SQL parallel execution. (SQL main node number = aa....aa, error node number = bb....bb, error = "cc....cc") (M+J+O)

An error occurred when executing the SQL statement with the SQL parallel execution function applied. <SQLSTATE: 5100M>

aa....aa:

Node number of the SQL main node

bb....bb:

Node number of the node where the error occurred

cc....cc:

Portion of the error message of the error that occurred

The entire KFAA31378-E message (the message text portion not including the message output destination), in the range of 490 bytes. If the end of cc....cc is in the middle of a multibyte character, the character before that will be output.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Refer to the cc....cc error message and eliminate the cause of the error. After that, re-execute the SQL statement with the SQL parallel execution function applied.

Due to the cc....cc error message being cut off in the middle, it may not be possible to check the contents of the error message. In that case, check the relevant error message in the message log of the node with the node number output to bb....bb. The relevant error message should be identified from the following information when the KFAA31378-E message is output to the message log.

Time

Connection sequence number

KFAA31379-E

An error occurred in the communication between nodes during the execution of SQL statements by using SQL parallel execution. (error node number = aa....aa) (M+J+O)

A failure occurred in communication between nodes when executing the SQL statements with the SQL parallel execution function applied. <SQLSTATE: 5100N>

aa....aa:

Node number of the node where the error occurred

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

A communication error occurred on the node with node number aa....aa. Check the following for the node with node number aa....aa and eliminate the cause of the error.

Communication line status

Server process status

Message log

KFAA31380-E

An error occurred during execution of string concatenation. (info1 = aa....aa, info2 = bb....bb, info3 = cc....cc) (M+J+O)

An error occurred during string concatenation. The result of the scalar function CONCAT or the concatenation operation exceeded the maximum data length (cc....cc bytes) of the result. <SQLSTATE:22001>

aa....aa: Function or operation that generated the error

function: Scalar function CONCAT

operator: Concatenation operation

bb....bb: Cause of the error 1

data length: The result of concatenating strings exceeded the maximum data length of the result.

cc....cc: Cause of the error 2

If bb....bb is data length, the maximum data length of the result is output.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement so that the result of the scalar function CONCAT or the concatenation operation does not exceed the maximum data length (cc....cc bytes) of the result.

KFAA31405-E

The specified data type (aa....aa) and value (bb....bb) conflict. (query number = cc....cc) (M+J+O)

The value specified for labeled duration is invalid. <SQLSTATE: 42703>

The value resulting from the multiplication for labeled duration is outside the range that can be specified for the labeled duration.

aa....aa: Cause of the error

value: The value specified for labeled duration or the value resulting from the multiplication for labeled duration is not in the specifiable range. The specifiable ranges are as follows:

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): -87,649,415 to +87,649,415

MINUTE(S): -5,258,964,959 to +5,258,964,959

SECOND(S): -315,537,897,599 to +315,537,897,599

MILLISECOND(S): -315,537,897,599,999 to +315,537,897,599,999

MICROSECOND(S): -315,537,897,599,999,999 to +315,537,897,599,999,999

NANOSECOND(S): -9,223,372,036,854,775,807 to +9,223,372,036,854,775,807

PICOSECOND(S): -9,223,372,036,854,775,807 to +9,223,372,036,854,775,807

bb....bb: Specification that generated the error

LABELED DURATION: A labeled duration

cc....cc: Position number of the query

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31420-E

The data length of an argument specified in the scalar function "aa....aa" is longer than bb....bb bytes. (query number = cc....cc) (M+J+O)

The data length of an argument specified in the scalar function "aa....aa" exceeds bb....bb bytes. <SQLSTATE: 42819>

aa....aa: Scalar function name

BIN: Scalar function BIN

HEX: Scalar function HEX

bb....bb: Maximum byte length

4,000: Maximum byte length that can be specified for an argument of the scalar function BIN

16,000: Maximum byte length that can be specified for an argument of the scalar function HEX

cc....cc: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

If aa....aa is BIN, make sure that the maximum data length of an argument in the scalar function BIN is 4,000 bytes or less.

If aa....aa is HEX, make sure that the maximum data length of an argument in the scalar function HEX is 16,000 bytes or less.

KFAA31424-E

The length of the regular expression character string of "LIKE_REGEX" predicate is wrong. (M+J+O)

The length of the regular expression character string specified in the LIKE_REGEX predicate is invalid. <SQLSTATE: 4278R>

S:

Ignores this SQL statement.

Action:

Correct the length of the regular expression character string.

KFAA31425-E

An invalid argument was specified in a scalar function. (function name = aa....aa, argument = bb....bb, query number = cc....cc) (M+J+O)

The specified scalar function is invalid.

The data type of bb....bb is invalid in the LTRIM scalar function. <SQLSTATE: 42788>

The data type of bb....bb is invalid in the RTRIM scalar function. <SQLSTATE: 42788>

The data type of bb....bb is invalid in the TRIM scalar function. <SQLSTATE: 42788>

The data length of bb....bb is invalid in the REPLACE scalar function. <SQLSTATE: 4278E>

aa....aa:

Scalar function name

bb....bb: Argument of the scalar function

object data: Target data

erase character: Deletion character

cc....cc: Position number of the query that specified aa....aa

For details about query position numbers, see 1.5 Query position numbers.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31436-E

The aa....aa privilege specified as "RESTRICT" cannot be revoked. (reason = bb....bb) (M+J+O)

The aa....aa privilege cannot be revoked because RESTRICT is specified for the drop behavior. <SQLSTATE: 42K26>

aa....aa: Privilege that cannot be revoked

SELECT: SELECT privilege

REFERENCES: REFERENCES privilege

ACCESS: Access privilege

bb....bb: Reason why it cannot be revoked

viewed table exists:

There is a viewed table that was defined using the SELECT privilege whose revocation was attempted.

referential constraints exist:

There is a referential constraint that was defined using the REFERENCES privilege whose revocation was attempted.

dependent privileges exist:

The access privilege whose revocation was attempted has dependent privileges.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take one of the following corrective actions:

Re-execute the SQL statement with CASCADE specified for the drop behavior.

Take one of the following corrective actions, and then re-execute the SQL statement with RESTRICT specified for the drop behavior.

If bb....bb is viewed table exists

Delete the viewed table defined using the SELECT privilege to be revoked.

If bb....bb is referential constraints exist

Delete the referential constraint defined using the REFERENCES privilege to be revoked.

If bb....bb is dependent privileges exist

Delete the dependent privileges of the access privilege to be revoked.

KFAA31470-E

The aa....aa is specified in the recursive member. (with list number = bb....bb, query number = cc....cc) (M+J+O)

aa....aa is specified in the recursive member. <SQLSTATE: 427N0>

aa....aa: Item that cannot be specified

SELECT DISTINCT: SELECT DISTINCT

"GROUP BY" clause: GROUP BY clause

"HAVING" clause: HAVING clause

"LIMIT" clause: LIMIT clause

set function: Set function

LEFT OUTER JOIN: LEFT OUTER JOIN

RIGHT OUTER JOIN: RIGHT OUTER JOIN

FULL OUTER JOIN: FULL OUTER JOIN

more than one recursive query name: Multiple recursive query names

bb....bb:

List number of the WITH list element for which the recursive member is specified

cc....cc: Position number of the query that specified predicate aa....aa

For details about query position numbers, see 1.5 Query position numbers.

If aa....aa is "LIMIT" clause and the LIMIT clause is specified in the query expression body that contains the set operation, the position number of the first query specification in the query expression body is displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31471-E

The data types of the columns derived from the anchor member and the recursive member are different. (with list number = aa....aa, column list number = bb....bb, anchor member data type = cc....cc, recursive member data type = dd....dd) (M+J+O)

The data type and data length of the column derived from the anchor member are different from those of the column derived from the recursive member. <SQLSTATE: 427N1>

aa....aa:

List number of the WITH list element that caused the error

bb....bb:

List number of the derived column that caused the error

cc....cc:

Data type of the derived column of the anchor member

dd....dd:

Data type of the derived column of the recursive member

The following information is output for cc....cc and dd....dd:

BIGINT: BIGINT type

INTEGER: INTEGER type

SMALLINT: SMALLINT type

DECIMAL(m,n): DECIMAL type or NUMERIC type (m indicates the precision, and n indicates scaling.)

DOUBLE PRECISION: DOUBLE PRECISION type or FLOAT type

REAL: REAL type

CHAR(n): CHAR type (n indicates the length of the character string.)

VARCHAR(n): VARCHAR type (n indicates the maximum length of the character string.)

STRING: STRING type

DATE: DATE type

TIME(p): TIME type (p indicates the fractional seconds precision.)

TIMESTAMP(p) WITHOUT TIME ZONE: TIMESTAMP type without time zone (p indicates the fractional seconds precision.)

TIMESTAMP(p) WITH TIME ZONE: TIMESTAMP type with time zone (p indicates the fractional seconds precision.)

BINARY(n): BINARY type (n indicates the binary data length.)

VARBINARY(n): VARBINARY type (n indicates the maximum length of binary data.)

BOOLEAN: BOOLEAN type

UUID: UUID type

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31476-E

An error occurred during execution of the scalar function "aa....aa". (details = bb....bb) (M+J+O)

One of the following errors occurred while scalar function aa....aa was executing:

The character string returned by scalar function TRANSLATE exceeded the permitted data length for execution results. <SQLSTATE: 22001>

The character string returned by scalar function REPLACE exceeded the permitted data length for execution results. <SQLSTATE: 22001>

An error occurred during data conversion:

• The target data type is character string data. <SQLSTATE: 22001>

• The target data type is numeric data. <SQLSTATE: 22003>

• The target data type is datetime data. <SQLSTATE: 22018>

An overflow error occurred in numeric data. <SQLSTATE: 22003>

An overflow error occurred in datetime data. <SQLSTATE: 22008>

A division by zero error occurred. <SQLSTATE: 22012>

An out-of-range value was specified in the LN scalar function. <SQLSTATE: 2201E>

An out-of-range value was specified in the POWER or SQRT scalar function. <SQLSTATE: 2201F>

An out-of-range value was specified in a scalar function. <SQLSTATE: 2250H>

aa....aa:

Scalar function name

bb....bb: Error detail message

data length insufficient: The returned value cannot be stored due to the limit on the data length for scalar function execution results.

division by zero error: A division by zero error occurred.

domain error: An out-of-range value was specified in a scalar function.

overflow error: An overflow occurred.

transform error: An error occurred during data conversion.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The following table shows the corrective action to take:

Error detail message

(bb....bb)

Corrective action to take

data length insufficient

Correct the SQL statement to increase the data length for scalar function execution results. If this message was issued when scalar function TRANSLATE was executing, see Rules in TRANSLATE in the manual HADB SQL Reference.

division by zero error

Correct the SQL statement so that the division by zero error will not occur.

For details about the condition that results in a division by zero error, see Scalar Functions in the manual HADB SQL Reference (see the details of the scalar function displayed in place of aa....aa).

domain error

Correct the SQL statement so that an out-of-range value will not be passed to the scalar function.

For details about the value range permitted for the scalar function, see description of the scalar function displayed in place of aa....aa under Scalar Functions in the manual HADB SQL Reference.

overflow error

Correct the SQL statement so that an overflow error will not occur.

transform error

Correct the SQL statement so that the target data can be stored in the data type of the scalar function's execution results.

KFAA31515-E

The cursor is not closed. (M+J+O)

The cursor has not been closed. <SQLSTATE: 24511>

S:

Ignores this SQL statement.

Action:

Close the cursor, and then re-execute the SQL statement.

KFAA31524-E

The SQL statement cannot be executed, because the transaction access mode is "READ_ONLY". (M+J+O)

The SQL statement could not be executed because the transaction access mode is read-only. <SQLSTATE: 25006>

S:

Ignores this SQL statement.

Action:

When the transaction access mode is read-only, the only SQL statements that can be executed are retrieval SQL statements. Use one of the following methods to change the transaction access mode to read/write, and then re-execute the SQL statement.

For the setReadOnly method of the JDBC driver's Connection interface, specify false.

For the Attribute argument of the ODBC driver's SQLSetConnectAttr, specify SQL_ATTR_ACCESS_MODE, and for the ValuePtr argument, specify SQL_MODE_READ_WRITE.

For the JDBC driver's adb_clt_trn_access_mode property (system property, user property, or property for connection URL), specify READ_WRITE.

For the Attribute argument of the CLI function a_rdb_SQLSetConnectAttr(), specify a_rdb_SQL_ATTR_ACCESS_MODE, and for the Value argument, specify a_rdb_SQL_ACCESS_MODE_READ_WRITE.

For the client definition's adb_clt_trn_access_mode operand, specify READ_WRITE.

KFAA31550-E

The name of the DB area for the index in ARCHIVABLE clause must be specified. (M+J+O)

The chunk-archive specification in the CREATE TABLE statement or ALTER TABLE statement is invalid. In the chunk-archive specification, a DB area must be specified to store the range index that is automatically defined by the HADB server. <SQLSTATE: 42IBA>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take one of the following actions:

■ Correct the SQL statement.

You must specify IN DB-area-name for the chunk-archive specification in the following cases:

When you execute the CREATE TABLE statement

When you execute the ALTER TABLE statement (if a range index is not specified in the column specified as an archive range column)

■ Specify the adb_sql_default_dbarea_shared operand in the server definition.

For the adb_sql_default_dbarea_shared operand, specify the DB area name that is assumed if the IN DB-area-name specification is omitted in the chunk-archive specification.

KFAA31551-E

aa....aa in ARCHIVABLE clause must not be specified. (M+J+O)

The chunk-archive specification in the ALTER TABLE statement is invalid. Neither IN DB-area-name nor RANGEINDEXNAME can be specified in the chunk-archive specification in the following case: <SQLSTATE: 42IBB>

A range index has already been specified on the column specified as an archive range column.

aa....aa: Invalid part

The name of the DB area for the index

The specified name of the DB area that stores the range index (IN DB-area-name) is invalid.

The index identifier

The specification of RANGEINDEXNAME in the chunk-archive specification is invalid.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

If aa....aa is The name of the DB area for the index

Delete the specification of IN DB-area-name from the chunk-archive specification.

If aa....aa is The index identifier

Delete the specification of RANGEINDEXNAME from the chunk-archive specification.

KFAA31552-E

The NOT NULL constraint must be specified for the archive range column. (M+J+O)

The NOT NULL constraint (NOT NULL) is not defined on the column specified for RANGECOLUMN in the chunk-archive specification in the ALTER TABLE statement. The NOT NULL constraint (NOT NULL) must be defined on the column specified as the archive range column. <SQLSTATE: 42IBC>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Specify, as the archive range column, a column on which the NOT NULL constraint (NOT NULL) is defined.

KFAA31553-E

The ARCHIVABLE clause cannot be specified for a table that is not a multi-chunk table in ALTER TABLE. (M+J+O)

The chunk-archive specification in the ALTER TABLE statement cannot be specified for a single-chunk table. <SQLSTATE: 42IBD>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

A single-chunk table cannot be changed to an archivable multi-chunk table by using the ALTER TABLE statement. To change a single-chunk table to an archivable multi-chunk table, see Changing a single-chunk table to a multi-chunk table in the HADB Setup and Operation Guide.

KFAA31554-E

The ALTER TABLE statement could not be used to change the column names, because the current column names and the desired column names are the same. (M+J+O)

The column name cannot be changed by using the ALTER TABLE statement because the current column name is the same as the new column name. <SQLSTATE: 42IBE>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the new column name specified for RENAME COLUMN in the ALTER TABLE statement.

KFAA31555-E

The UNARCHIVABLE option cannot be specified in ALTER TABLE statement, because aa....aa. (M+J+O)

The archivable multi-chunk table could not be changed to a regular multi-chunk table because an error occurred in the ALTER TABLE statement. <SQLSTATE: 42IBF>

aa....aa: Cause of the error

the table has an archived chunk

The archivable multi-chunk table that contains an archived chunk is specified in the ALTER TABLE statement.

the table is not an archivable multi-chunk table

A table that is not an archivable multi-chunk table is specified in the ALTER TABLE statement.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

If aa....aa is the table has an archived chunk

Execute the adbunarchivechunk command to release the chunk from the archived state. Then, execute the ALTER TABLE statement.

Note that if there is a deletion-pending chunk in the archived state, delete the target chunk by using the PURGE CHUNK statement, and then execute the ALTER TABLE statement.

If aa....aa is the table is not an archivable multi-chunk table

Confirm that the table name specified in the ALTER TABLE statement is correct.

KFAA31556-E

The specified foreign server "aa....aa" does not exist. (M+J+O)

The specified foreign server does not exist. <SQLSTATE:427C5>

aa....aa:

Foreign server name

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31557-E

The specified foreign server "aa....aa" is already defined. (M+J+O)

The specified foreign server is already defined. <SQLSTATE:427C6>

aa....aa:

Foreign server name

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31558-E

A foreign server defined by another HADB user is specified. (M+J+O)

A foreign server defined by another HADB users is specified. <SQLSTATE:427C7>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement to specify the foreign server defined by you (the HADB user who executed the SQL statement).

KFAA31562-E

There is an error in the specification method in the ALTER SERVER statement. (reason = aa....aa) (M+J+O)

The specification method of the ALTER SERVER statement is invalid. <SQLSTATE:42I7A>

aa....aa: Invalid cause

the value for the option cannot be omitted

The value for the foreign server option (access key string, etc.) cannot be omitted.

an option that is not defined by a CREATE SERVER statement cannot be changed by an ALTER SERVER statement

A foreign server option that is not defined by a CREATE SERVER statement cannot be changed by an ALTER SERVER statement.

the option is already defined

The specified foreign server option is already defined.

the endpoint string does not start with 'http://' or 'https://'

The endpoint string does not start with http:// or https://.

only one of either the access key or the secret key cannot be added

Only one of either the access key or the secret key cannot be added.

only one of either the access key or the secret key cannot be deleted

Only one of either the access key or the secret key cannot be deleted.

a value was specified for an option for which values cannot be specified

A value cannot be specified for the specified foreign server option.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31563-E

There is an error in the specification method in the CREATE SERVER statement. (reason = aa....aa) (M+J+O)

The specification method of the CREATE SERVER statement is invalid. <SQLSTATE:42I7B>

aa....aa: Cause of the error

only one of either the ACCESS_KEY or SECRET_KEY options is specified

Only one of either the ACCESS_KEY or SECRET_KEY options is specified.

the endpoint string does not start with 'http://' or 'https://'

The endpoint string does not start with http:// or https://.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31564-E

There is an error in the specification method of aa....aa in the CREATE FOREIGN TABLE statement. (reason = bb....bb) (M+J+O)

The specification method for aa....aa of the CREATE FOREIGN TABLE statement is invalid. <SQLSTATE:42I7C>

aa....aa: Location of invalid specification

foreign data directory path string: Foreign data directory path string

foreign table option: Foreign table option

partition key column option specification: Optional partitioning key column specification

partition key column specification: Partition key column specification

attribute property: Property

enumeration string: Enumeration string

minimum value string or integer: Minimum value string or minimum value integer

maximum value string or integer: Maximum value string or maximum value integer

datetime format string: Date and time format string

template directory path string: Template directory path string

catalog type specification: Catalog type specification

catalog URI specification: Catalog URI specification

catalog namespace specification: Catalog namespace specification

catalog region specification: Catalog region specification

catalog ID specification: Catalog ID specification

warehouse name specification: Warehouse name specification

Iceberg option: Iceberg option

token URI specification: Token URI specification

client ID specification: Client ID specification

client secret specification: Client secret specification

allowed scope specification: Allowed scope specification

column definition: Column definition

bb....bb: Cause of the error

Value of bb....bb

Description

's3://' or 'file://' is not specified at the beginning of the string

s3:// or file:// is not specified at the beginning of the string.

If the storage location of the foreign data is object storage, the directory path string of the foreign data must start with s3://.

If the storage location of the foreign data is file storage, the directory path string of the foreign data must start with file://.

'/' is not specified to the tail of string

/ is not specified at the tail of the string.

neither the foreign data format nor the foreign data directory path, or both, have been specified

The following two required specifications are not provided. Either both specifications are missing, or only one of the specifications is present:

Specification of the data format for the foreign data

Specification of the directory path for the foreign data

the option cannot be specified when the foreign data format is not CSV

The specified option can be specified only when the data format of the foreign data is CSV format.

the option can only be specified when the foreign data format is ICEBERG

The specified option can be specified only when ICEBERG is specified in the foreign data format specification.

the option cannot be specified when the foreign data format is ICEBERG

The specified option cannot be specified when ICEBERG is specified in the foreign data format specification.

an option that must be specified when the foreign data format is ICEBERG is not specified

An option that is required when ICEBERG is specified in the foreign data format specification has not been specified.

the partition key column must be specified when the partition key column option is specified

When specifying the optional partitioning key column specification, the partition key column specification must be specified.

the partition key column cannot be specified when the partition key column option is omitted

If the optional partitioning key column specification is omitted, the partition key column specification cannot be specified.

the same attribute property cannot be specified for the same column name

The same type of property cannot be specified for the same column name.

the column name specified in the attribute property must be the same as the column name of the partition key column

The column name specified for the property must be the same as the column name of the partition key column specification.

the combination of the attribute property is invalid

The combination of properties that can be specified is invalid.

an attribute property that must be specified is not specified

A property that needs to be specified is not specified.

the data length of the value that can be specified for the enumeration string exceeds the upper limit

Among the strings specified in the enumeration string, there are strings that exceed the maximum data length.

the number of values that can be specified for the enumeration string exceeds the upper limit

The number of strings specified in the enumeration string exceeds the limit.

the value of the minimum value string or integer is higher than the value of the maximum value string or integer

The value of the minimum value string is greater than the value of the maximum value string. Or, the minimum integer value is greater than the maximum integer value.

the minimum value string or maximum value string cannot be converted to a date-time value by using the datetime format string

Could not convert the minimum or maximum value string to a datetime value according to the specified datetime format string.

the header of the template directory path string must be the same as the foreign data directory path string

The beginning of the template directory path string must be the same as the foreign data directory path string.

the data type for the partition key column cannot be specified

A data type that cannot be specified for the data type of the partition key column is specified.

the data length is over

The maximum data length is exceeded.

the combination of the time unit and the specified value for the TYPE is invalid

The combination of the specified value of TYPE and the specified value of time unit is invalid.

values for each element in the enumeration string, minimum value integer, maximum value integer, a minimum value string or a maximum value string cannot be converted to the value for the data type of the partition key column

Each string in the enumerated string, the minimum integer, the maximum integer, the minimum value string, or the maximum value string could not be converted to the data type of the partition key column.

the variables for all partition key columns are not specified in the template directory path string

The variables corresponding to all partition key columns are not specified in the template directory path string.

a foreign server cannot be omitted when the foreign data directory path string is specified in S3 URI format (when external data is stored in object storage)

When the directory path string of foreign data is specified in S3 URI format (i.e., when the foreign data is stored in object storage), the foreign server must be specified.

a foreign server cannot be specified when the foreign data directory path string is specified in FILE URI format (when external data is stored in file storage)

When the directory path string of foreign data is specified in FILE URI format (i.e., when the foreign data is stored in file storage), the foreign server cannot be specified.

the string does not start with 'http://' or 'https://'

The string does not start with either http:// or https://.

the option cannot be specified when the catalog type is GLUE

An option that cannot be specified when GLUE is designated as the catalog type has been specified.

the Iceberg option that must be specified when the catalog type is GLUE is not specified

An Iceberg option that is required when GLUE is designated as the catalog type has not been specified.

the option cannot be specified when the catalog type is REST

An option that cannot be specified when REST is designated as the catalog type has been specified.

the Iceberg option that must be specified when the catalog type is REST is not specified

An Iceberg option that is required when REST is designated as the catalog type has not been specified.

the token URI specification, client ID specification, client secret specification, and allowed scope specification must be all specified or all omitted

Token URI specification, client ID specification, client secret specification, and allowed scope specification must either all be specified or all be omitted.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31565-E

The field name "aa....aa" is duplicated. (M+J+O)

A field name has been used more than once. <SQLSTATE:42ICD>

aa....aa:

Field name resulting in the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement to avoid duplicate field names.

If this message is output when column definitions are omitted in the CREATE FOREIGN TABLE statement, take one of the following corrective actions:

The field names in the schema information of the PARQUET format foreign data files are duplicated. Change the field names to ensure there are no duplicates in the foreign data.

The field names included in the metadata of the referenced Iceberg table are duplicated. Change the field names to ensure there are no duplicates.

KFAA31566-E

Processing to generate column definitions for the foreign table failed. (reason = "aa....aa") (M+J+O)

An attempt to generate the column definitions for the foreign table failed. <SQLSTATE:42I7D>

aa....aa:

Cause of the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take the following action depending on the cause of error output to aa....aa.

Value of aa....aa

Cause of the error

Corrective action to take

the foreign data format is not PARQUET or ICEBERG

A value other than PARQUET or ICEBERG is specified in the foreign data format specification.

Specify PARQUET or ICEBERG in the foreign data format specification in the CREATE FOREIGN TABLE statement.

the foreign data does not exist in the directory from which data is to be retrieved

The PARQUET format foreign data files do not exist under the target directory for foreign data search (including subdirectories).

Store the foreign data files under the target directory for foreign data search.

the column name in the foreign data is invalid

The column names of the foreign data do not meet the conditions of the naming rules for the columns of the foreign table.

The column names included in the metadata of the Iceberg table# do not meet the conditions of the naming rules for foreign tables.

Make sure that the column names of the foreign data meet the following conditions. Also, check whether the column names included in the Iceberg table metadata meet the following conditions. If they do not, the CREATE FOREIGN TABLE statement will result in an error.

The first character of the column name is a halfwidth uppercase letter (A to Z, #, @, \, _), halfwidth lowercase letter, halfwidth katakana character, or fullwidth character.

Each character of the column name is a halfwidth uppercase letter (A to Z, #, @, \, _), digit, halfwidth lowercase letter, halfwidth katakana character, halfwidth space, hyphen, halfwidth vertical bar, or fullwidth character.

The column name does not contain any fullwidth spaces.

The length of the column name is 100 bytes or less.

For details, see column-name in Rules for characters that can be used in names of Specifying names in the manual HADB SQL Reference.

the data type of the foreign data is not compatible with the data types supported by HADB

The data type of the foreign data column is not compatible with the HADB data type.

The data type of the columns included in the Iceberg table# metadata is not compatible with the HADB data type.

Check whether the following conditions are met.

Change the data type of the foreign data columns to a type compatible with the HADB data type. Alternatively, change the data type of the columns included in the Iceberg table metadata to a type compatible with the HADB data type.

If the foreign data is of type DECIMAL(precision=m, scale=n), then m and n must satisfy 1 ≤ m ≤ 38, 0 ≤ n ≤ 38, and n ≤ m.

The data length of the binary data in the foreign data is between 1 and 32,000 bytes.

The element data type of the LIST type in the foreign data specifies a data type that is compatible with the HADB data type.

The maximum number of elements for the LIST type in the foreign data is between 2 and 30,000.

The total number of fields contained in the STRUCT type of the foreign data is 1,000 or less.

If the elements of the LIST type in the foreign data are nested with STRUCT type, the repetition count of the LIST type and STRUCT type is 8 or less.

If the elements of the STRUCT type in the foreign data are nested with STRUCT type or LIST type, the repetition count of the LIST type and STRUCT type is 8 or less.

For details, see the following tables in Specification format and rules for the CREATE FOREIGN TABLE statement in the manual HADB SQL Reference:

The table Correspondence between the data type of each column of foreign data in PARQUET format and the HADB data type in Rules

The table Correspondence between the data types of the columns included in the metadata of the Iceberg table and the HADB data types in If ICEBERG is specified in the foreign data format specification under Rules for omitting the column definition specification

unsupported foreign data was detected

There are columns in the foreign data with data types not supported by HADB.

There are columns in the Iceberg table# metadata with data types not supported by HADB.

Delete columns with data types not supported by HADB from the foreign data.

Alternatively, delete columns with data types not supported by HADB from the Iceberg table metadata.

the field name in the foreign data is invalid

The field names of the foreign data do not meet the conditions of the naming rules for the field names of the STRUCT type columns in the foreign table.

The field names included in the metadata of the Iceberg table# do not meet the conditions of the naming rules for the field names of STRUCT columns in the foreign table.

Check whether the field names of the foreign data meet the following conditions. If they do not, the CREATE FOREIGN TABLE statement will result in an error.

The first character of the field name is a halfwidth uppercase letter (A to Z, #, @, \, _), halfwidth lowercase letter, halfwidth katakana character, or fullwidth character.

The characters in the field name include halfwidth uppercase letters (A to Z, #, @, \, _), digits, halfwidth lowercase letters, halfwidth katakana characters, halfwidth spaces, hyphens, halfwidth vertical bar, or fullwidth characters.

The field name does not contain fullwidth spaces.

The length of the field name is 100 bytes or less.

For details, see field-name in Rules for characters that can be used in names of Specifying names in the manual HADB SQL Reference.

the number of columns in the table exceeds maximum number

The number of columns in the table exceeds the limit.

If this message is output when defining a foreign table

When column definitions are omitted, the total number of columns in the referenced PARQUET format foreign data files and the number of partition key columns must be 4,000 or less.

If this message is output when retrieving a foreign table

The total number of columns included in the metadata of the Iceberg table referenced by the foreign table to be retrieved must be 4,000 or less.

#

If this message is output when retrieving a foreign table, there is a problem with the columns or fields in the metadata of the Iceberg table referenced by the foreign table to be retrieved. If a time travel specification is used when retrieving the foreign table, there is a problem with the columns or fields in the metadata at the snapshot point.

KFAA31600-E

Unable to aa....aa. (reason = bb....bb) (M+J+O)

aa....aa cannot be done because of bb....bb. <SQLSTATE: 42I75>

aa....aa: Operation resulting in an error

define index: Index definition

alter table: Changing table definitions

create table: Table definition

create foreign table: Defining a foreign table

bb....bb: Cause of the error

not specify "EMPTY":

If the EMPTY option was not specified

DEFAULT clause:

The DEFAULT clause is specified

the length of varchar column exceeds 32,000 bytes:

A VARCHAR-type column whose defined length exceeds 32,000 bytes is specified

an array-type column cannot be defined in a row store table:

An array-type column is defined in the row store table

a unique constraint cannot be defined in a table that defines array-type columns:

Uniqueness constraints are defined on tables that defines array-type columns.

an array-type column cannot be added to a row store table:

An attempt was made to add an array-type column to a row store table.

an array-type column cannot be added to a table that defines a B-tree index:

An attempt was made to add an array-type column to a table with a B-tree index defined.

a B-tree index cannot be defined in a table that defines array-type columns:

An attempt was made to define a B-tree index on a table that has an array-type column defined.

an archivable multi-chunk table cannot be defined using the cloud storage facility:

When using the cloud storage facility, an attempt was made to define an archivable multi-chunk table.

a text index cannot be defined using the cloud storage facility:

When using the cloud storage facility, an attempt was made to define a text index.

the struct data is specified:

The STRUCT type is specified

the string data is specified:

The STRING type is specified.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

If bb....bb is not specify "EMPTY"

Re-execute the CREATE INDEX statement with the EMPTY option specified.

If bb....bb is DEFAULT clause

Delete the specified DEFAULT clause. The DEFAULT clause cannot be specified in an ALTER TABLE statement.

If bb....bb is the length of varchar column exceeds 32,000 bytes

In the ALTER TABLE statement, CREATE TABLE statement, or CREATE FOREIGN TABLE statement, a VARCHAR type column cannot be specified if the defined column length exceeds 32,000 bytes. Correct the SQL statement.

If bb....bb is an array-type column cannot be defined in a row store table

When defining an array-type column, the table must be defined as a column store table. You cannot define an array-type column in the row store table. Correct the CREATE TABLE statement.

If bb....bb is a unique constraint cannot be defined in a table that defines array-type columns

Uniqueness constraints cannot be defined when defining array-type columns. Correct the CREATE TABLE statement.

If bb....bb is an array-type column cannot be added to a row store table

Array-type columns can only be added to a column store table. Array-type columns cannot be added to the row store table. Correct the ALTER TABLE statement.

If bb....bb is an array-type column cannot be added to a table that defines a B-tree index

Array-type columns cannot be added to tables with B-tree indexes defined. Correct the ALTER TABLE statement.

If bb....bb is a B-tree index cannot be defined in a table that defines array-type columns

B-tree indexes cannot be defined for tables with array-type columns defined. Correct the CREATE INDEX statement.

If bb....bb is an archivable multi-chunk table cannot be defined using the cloud storage facility

If you are using the cloud storage facility, you cannot define an archivable multi-chunk table. Correct the ALTER TABLE or CREATE TABLE statements.

If bb....bb is a text index cannot be defined using the cloud storage facility

If you are using the cloud storage facility, you cannot define a text index. Correct the CREATE INDEX statement.

If bb....bb is the struct data is specified

Columns of the STRUCT type cannot be added or defined. Correct the ALTER TABLE or CREATE TABLE statements.

If bb....bb is the string data is specified

Columns of the STRING type cannot be added or defined. Correct the ALTER TABLE or CREATE TABLE statements.

Note

For details about the CREATE INDEX statement, see CREATE INDEX (defining an index) in the manual HADB SQL Reference.

For details about the ALTER TABLE statement, see ALTER TABLE (alter table definition) in the manual HADB SQL Reference.

For details about the CREATE TABLE statement, see CREATE TABLE (define a table) in the manual HADB SQL Reference.

For details about the CREATE FOREIGN TABLE statement, see CREATE FOREIGN TABLE (defining a foreign table) in the manual HADB SQL Reference.

KFAA31602-E

The multiple referential constraints which reference the same primary key cannot be defined. (M+J+O)

Multiple referential constraints that access the same primary key cannot be defined from the same column or from the same group of multiple columns (even if the column order is different). <SQLSTATE: 42I77>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the referential constraint definition. Make sure that only one referential constraint accesses the same primary key from the same column or from the same group of multiple columns (even if the column order is different).

KFAA31603-E

Unable to aa....aa. (reason = bb....bb) (M+J+O)

The data type of a column by ALTER TABLE statement cannot be changed. <SQLSTATE: 42I75>

aa....aa: Operation resulting in an error

change the data type of the column by ALTER TABLE statement

Changing the data type of a column using the ALTER TABLE statement

bb....bb:

Cause of the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take corrective action as described in the following table: Then, re-execute the ALTER TABLE statement.

Information output to bb....bb

Cause of the error

Corrective action to take

the specified column comprises a multiple-column B-tree index in which the total data length of the indexed columns exceeds 255 bytes

When changing the data type of a column of type VARCHAR with a data length of 254 bytes or less, the column whose data type is to be changed is an index component column of a multiple-column index, and the total length of the columns in an index of the multiple-column index after the data type change is 256 bytes or more after changing the data type.

See How to change the data type of a column in a base table (how to increase the data length of a column of type VARCHAR) in the manual HADB Setup and Operation Guide and change the data type of the column.

the total data length of the column comprising the B-tree index which is determined by the changed data length exceeds the maximum length

When changing the data type of a VARCHAR column with a data length greater than 256 bytes and less than 31,999 bytes, the column whose data type is being changed is a constituent column of the B-tree index, and the total data length of the constituent columns of the changed B-tree index exceeds the upper limit.

Take one of the following actions to ensure that the total data length of the columns in the B-tree index after the change satisfies the conditions described in Changing the data type (VARCHAR data length) of the base table columns in Specification format and description of the Specification format and rules for the ALTER TABLE statement in the manual HADB SQL Reference.

Reduce the data length after the change

Make the page size larger for the data DB area that stores the B-tree index

To increase the page size of the data DB area, you need to delete the data DB area using the adbmodarea command and then recreate it. For how to recreate a data DB area, see Steps to take when a data DB area can no longer be expanded in the HADB Setup and Operation Guide.

the specified column defines a text index

A text index is defined for the column you are trying to change the data type of.

See How to change the data type of a column in a base table (how to increase the data length of a column of type VARCHAR) in the manual HADB Setup and Operation Guide and change the data type of the column.

the specified column comprises a foreign key

The column whose data type is to be changed is the column comprising the foreign key.

the specified column comprises a primary key that is referenced from a foreign key

The column whose data type is to be changed is the constituent column of a primary key that is referenced by a foreign key in another table.

KFAA31648-E

The dictionary (base table) cannot be accessed because a transaction is using the dictionary (base table). (M)

The dictionary table (base table) cannot be accessed because a transaction is using the dictionary table (base table). <SQLSTATE: 52402>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Wait for the transaction that is accessing the dictionary table (base table) to terminate, and then re-execute the SQL statement.

KFAA31650-E

A aa....aa index cannot be defined because "bb....bb" is specified. (M+J+O)

An index cannot be defined because the bb....bb option is specified. <SQLSTATE: 42IA6>

aa....aa: Index type

range: Range index

text: Text index

bb....bb: The option specified

UNIQUE: UNIQUE was specified.

ASC: ASC was specified.

DESC: DESC was specified.

PCTFREE: PCTFREE was specified.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Execute the CREATE INDEX statement without specifying the option output in bb....bb

KFAA31651-E

A aa....aa index cannot be defined because multiple indexed columns are specified. (M+J+O)

An index cannot be defined because multiple indexed columns are specified. <SQLSTATE: 42IA7>

aa....aa: Index type

range: Range index

text: Text index

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

A range index and text index cannot be changed to a multiple-column index. Change the database design (the specification for the indexed columns).

If you want to define range indexes for all indexed columns specified in CREATE INDEX statements, execute multiple CREATE INDEX statements specifying columns one at a time rather than specifying multiple columns with a single CREATE INDEX statement.

KFAA31652-E

A range index cannot be defined in column "aa....aa". (reason = bb....bb) (M+J+O)

A range index cannot be defined for the following columns: <SQLSTATE: 42IA8>

A column whose type is CHAR and whose length exceeds 32 bytes

A column whose type is VARCHAR

A column whose type is BINARY

A column whose type is VARBINARY

A column whose type is UUID

aa....aa:

Column name

bb....bb: Reason why range index cannot be defined

data type is CHAR and data length is longer than 32 bytes: The data type of the column is CHAR and the data length exceeds 32 bytes.

data type is VARCHAR: The data type of the column type is VARCHAR.

data type is BINARY: The data type of the column type is BINARY.

data type is VARBINARY: The data type of the column type is VARBINARY.

data type is UUID: The data type of the column type is UUID.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

A range index cannot be defined for the column aa....aa, so change the database design (column data type, indexed columns, index type, and so on).

KFAA31653-E

aa....aa index cannot be defined. (reason = "bb....bb") (M+J+O)

A table for which an index cannot be defined is specified.

You cannot define aa....aa for a multi-chunk table. <SQLSTATE: 42IA9>

You cannot define aa....aa for a column store table. <SQLSTATE: 42IC1>

aa....aa: Index type

A unique: Unique index

A text: Text index

bb....bb: Reason why an index cannot be defined

the table in the CREATE INDEX statement is a multi-chunk table:

An attempt is made to define a unique index for a multi-chunk table.

the table in the CREATE INDEX statement is a column store table:

The table for which you are attempting to define a text index is a column store table.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take one of the following corrective actions:

If bb....bb is the table in the CREATE INDEX statement is a multi-chunk table

Revise the database design so as not to define a unique index or to remove the chunk specification from the table definition.

If bb....bb is the table in the CREATE INDEX statement is a column store table

You cannot define a text index for a column store table. Revise the database design (including the options to be specified for tables, and index design).

KFAA31654-E

The maximum number of chunks of a table without the CHUNK option specified cannot be changed. (M+J+O)

The maximum number of chunks was not specified in the chunk specification when the base table was defined by using the CREATE TABLE statement. Therefore, the ALTER TABLE statement cannot be used to change the maximum number of chunks. <SQLSTATE: 42IAD>

S:

Ignores this SQL statement.

Action:

If you want to specify the maximum number of chunks, delete the table definition and then re-define the table. For details about the procedure, see Changing a single-chunk table to a multi-chunk table in the HADB Setup and Operation Guide.

If you do not need to specify the maximum number of chunks, delete the specification of the maximum number of chunks and then re-execute the ALTER TABLE statement.

KFAA31655-E

In the CHUNK option, no value was specified for the maximum number of chunks that can be created. Alternatively, the ARCHIVABLE clause was not specified. (M+J+O)

The specified ALTER TABLEstatement is invalid. Neither the maximum number of chunks nor the chunk-archive specification is specified. <SQLSTATE: 42IAE>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the specification of the ALTER TABLE statement. That is, specify the maximum number of chunks or the chunk-archive specification.

KFAA31656-E

The operation cannot be executed because a required resource (aa....aa) is locked. (M)

The specified operation could not be performed because the locked resource aa....aa is being used by another operation.

aa....aa:

Name of locked resource

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Wait for termination of the operation that is using the locked resource aa....aa, and then retry the operation. For details about the allocation of locked resources, see Locked resources that are reserved and their lock modes in the HADB Setup and Operation Guide.

KFAA31657-E

A primary key cannot be defined.(reason = "aa....aa") (M+J+O)

If the chunk specification is specified, a primary key cannot be defined. Conversely, if a primary key is defined, the chunk specification cannot be specified. <SQLSTATE: 42IAF>

aa....aa: Cause of the error

the table is a multi-chunk table: The base table for which a primary key will be defined also contains the chunk specification.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The chunk specification and a primary key cannot be defined together. Review the database design.

KFAA31658-E

The index corresponding to aa....aa cannot be deleted. (M+J+O)

The DROP INDEX statement cannot be used to delete the B-tree indexes that correspond to the primary key.

Also, the DROP INDEX statement cannot be used to delete the range indexes that are automatically defined for archive range columns. <SQLSTATE: 42IB0>

aa....aa: Index that was attempted to be deleted

the primary key: B-tree index corresponding to the primary key

an archive range column: Range index automatically defined for an archive range column

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

To delete the B-tree indexes that correspond to the primary key, use the DROP TABLE statement to delete them for each base table.

To delete the range indexes automatically defined for archive range columns, use the DROP TABLE statement to delete the base table for the range indexes.

KFAA31659-E

A text index cannot be defined in column "aa....aa". (reason = bb....bb) (M+J+O)

A text index cannot be defined for the following columns: <SQLSTATE: 42IB2>

Columns whose data type is not CHAR or VARCHAR

aa....aa:

Column name

bb....bb: Cause of the error

data type is not CHAR or VARCHAR: An attempt is made to define a text index for a column whose data type is neither CHAR nor VARCHAR.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Revise the column for which to define the text index.

KFAA31660-E

The aa....aa option cannot be specified because the index is not a text index. (M+J+O)

The following index option cannot be specified for an index other than a text index: <SQLSTATE: 42IB3>

Notation-correction-search text-index specification

aa....aa:

CORRECTIONRULE: Notation-correction-search text-index specification

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Delete the index option specification indicated by aa....aa, and then execute the CREATE INDEX statement.

KFAA31661-E

Table definition information of a aa....aa node cannot be invalidated. (reason = "bb....bb", node_id = cc....cc) (M+J+O)

The table-definition information for a aa....aa node could not be invalidated. <SQLSTATE:53026>

aa....aa: Node type

secondary: Secondary node

worker: Worker node

bb....bb: Cause of the error

communication to the secondary node

Inter-node communication between the primary and secondary nodes failed.

communication to the worker node

Inter-node communication between the primary and worker nodes failed.

processing on the secondary node

Failed to process secondary node.

processing on the worker node

Failed to process worker node.

cc....cc: Node ID

If the node ID cannot be output, three asterisks (***) are displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

If bb....bb is communication to the secondary node

Access the message log files of the primary node and of the secondary node indicated by the node ID. Eliminate the cause of the failure of communication between nodes, as indicated by the messages that were output.

If bb....bb is communication to the worker node

Access the message log files of the primary node and of the worker node indicated by the node ID. Eliminate the cause of the failure of communication between nodes, as indicated by the messages that were output.

If bb....bb is processing on the secondary node

Access the message log files of the secondary node indicated by the node ID. Eliminate the cause of the processing failure on the secondary node, as indicated by the messages that were output.

If bb....bb is processing on the worker node

Access the message log files of the worker node indicated by the node ID. Eliminate the cause of the processing failure on the worker node, as indicated by the messages that were output.

KFAA31662-E

The SQL statement cannot be executed because a aa....aa table is being manipulated in a transaction. (M+J+O)

The SQL statement cannot be executed because the aa....aa table is being referenced in the same transaction. <SQLSTATE: 53027>

If a definition SQL statement cannot be executed, either of the following tables is being referenced in the same transaction:

Dictionary table that will be referenced and updated in an extension of the definition SQL statement

Table that will be changed and deleted by the definition SQL statement

If the TRUNCATE TABLE statement or PURGE CHUNK statement cannot be executed, the operation target table is being referenced.

aa....aa: Table being referenced in the transaction

dictionary: Dictionary table that will be referenced and updated in an extension of the definition SQL statement

user: Table that will be changed and deleted by the definition SQL statement, or the table specified in the TRUNCATE TABLE statement or PURGE CHUNK statement

S:

Invalidates this transaction.

Action:

Re-execute the SQL statement.

KFAA31663-E

The operation cannot be executed because a required resource is locked. (name = aa....aa, object = bb....bb) (M+J+O)

The SQL statement or the command cannot be executed due to contention of the locked resource. <SQLSTATE: 53028>

aa....aa: Locked resource name

PREPARE TABLE: Pre-processing table

DBAREA: DB area

TABLE: Table

bb....bb: Locked resource to be acquired

A table name or DB area name is displayed.

The table name is displayed in the format "schema-name"."table-identifier".

If the schema name, table identifier, or DB area name cannot be output, three asterisks (***) are displayed.

S:

For the SQL statement:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

For the command:

Stops execution of the command.

Action:

Wait for termination of the SQL statement or command that is acquiring the locked resource, and then re-execute the SQL statement or command. For details about locked resources acquired by the SQL statement or command, see Locked resources in Locking in Architecture in the HADB Setup and Operation Guide.

KFAA31664-E

The definition SQL statement cannot be executed because there is a ResultSet object. (M+J+O)

The definition SQL statement cannot be executed because a ResultSet object exists. <SQLSTATE: 53029>

S:

Invalidates this transaction.

Action:

Re-execute the definition SQL statement.

KFAA31665-E

The data type of an archive range column is invalid. (M+J+O)

Columns of the following data types cannot be specified as archive range columns. <SQLSTATE: 42IB4>

CHARACTER type with a definition length of 33 or more bytes

VARCHAR type

TIMESTAMP WITH TIME ZONE type

BINARY type

VARBINARY type

BOOLEAN type

UUID type

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Revise database design such as selection of archive range columns and column data types.

KFAA31666-E

The archive directory is specified incorrectly. (reason = aa....aa) (M+J+O)

The specified archive directory is invalid.

aa....aa: Cause of the error

The length of the archive directory path is out of range: The length of the path name of the specified archive directory is not in the range from 1 to 400 bytes. <SQLSTATE: 42IB5>

The archive directory is not an absolute path: The specified archive directory is not an absolute path. <SQLSTATE: 42IB6>

The archive directory does not exist: A directory that does not exist is specified as an archive directory. <SQLSTATE: 5302A>

The directory cannot be specified as an archive directory: A directory that cannot be specified as an archive directory is specified. <SQLSTATE: 5302B>

The HADB administrator does not have read, write, and execute permissions for the archive directory: A directory for which the HADB administrator does not have read, write, and execution permissions is specified as an archive directory. Alternatively, the archive directory path contains a directory for which the HADB administrator does not have execution permission. <SQLSTATE: 5302C>

One or more symbolic link destinations specified in the archive directory cannot be acquired: Link destinations for the symbolic link specified in the archive directory cannot be acquired. <SQLSTATE: 5302D>

system call error(errno = bb....bb): An error occurred in a system call. <SQLSTATE: 5302E>

bb....bb:

Error number

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take the corrective action for the cause of the error indicated by aa....aa, and then revise the archive directory specification. For details about the rules for specifying an archive directory, see the explanation of ARCHIVEDIR in chunk-specification in Explanation of specification format in Specification format and rules for the CREATE TABLE statement in the manual HADB SQL Reference.

If aa....aa indicates a system call error and bb....bb indicates an error number, check the error number in the OS documentation, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the displayed error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA31667-E

The CORRECTIONRULE option cannot be specified because the character encoding to be used on the HADB server is Shift-JIS (ADBLANG=SJIS). (M+J+O)

The notation-correction-search text-index specification (CORRECTIONRULE) cannot be specified because the character encoding used on the HADB server is Shift-JIS (if the value specified for the environment variable ADBLANG is SJIS). <SQLSTATE: 42IB7>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Delete the notation-correction-search text-index specification (CORRECTIONRULE) , and then re-execute the CREATE INDEX statement.

KFAA31668-E

The ALTER TABLE statement cannot be executed when both the ARCHIVABLE clause and the maximum number of chunks to be created are specified in the CHUNK option. (M+J+O)

The specified ALTER TABLE statement is invalid. Change of the maximum number of chunks and the chunk-archive specification cannot be specified at the same time. <SQLSTATE: 42IB8>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Specify either of the following, and then, execute the ALTER TABLE statement.

Change of the maximum number of chunks

Chunk-archive specification

KFAA31669-E

The ARCHIVABLE clause in the CHUNK option cannot be specified for the archivable multi-chunk table in ALTER TABLE. (M+J+O)

The chunk-archive specification in the ALTER TABLE statement cannot be specified for an archivable multi-chunk table. <SQLSTATE: 42IB9>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

The table specified in the ALTER TABLE statement is an archivable multi-chunk. Check the table name specified in the ALTER TABLE statement.

KFAA31670-E

The aa....aa privilege and the bb....bb privilege cannot be granted to the same user. (M+J+O)

aa....aa and bb....bb cannot be granted to the same HADB user. <SQLSTATE: 42K30>

aa....aa: Privilege type

DBA: DBA privilege

AUDIT ADMIN: Audit admin privilege

bb....bb: Privilege type

AUDIT ADMIN: Audit admin privilege

CRYPTO ADMIN: CRYPTO ADMIN privilege

S:

Ignores this SQL statement.

Action:

Grant aa....aa and bb....bb to different HADB users.

KFAA31673-E

The password of the auditor (aa....aa) cannot be changed by other users. (M+J+O)

The password of an HADB user who has the audit privilege cannot be changed by other HADB users. <SQLSTATE: 42K33>

aa....aa:

Authorization identifier of the HADB user who has the audit privilege

S:

Ignores this SQL statement.

Action:

Ensure that the password of an HADB user who has the audit privilege is changed by that HADB user.

KFAA31675-E

The operation "aa....aa" cannot be executed, because you do not have the bb....bb privilege. (M+J+O)

The aa....aa operation cannot be performed because you do not have the required privilege. <SQLSTATE: 42K35>

aa....aa: Operation that could not be performed

CREATE AUDIT: Defining an audit target

DROP AUDIT: Deleting an audit target definition

REVOKE AUDIT ADMIN: Revoking the audit admin privilege

REVOKE AUDIT VIEWER: Revoking the audit viewer privilege

audit trail search by using the system-defined function ADB_AUDITREAD: Searching for an audit trail by using the ADB_AUDITREAD function

adbmkdmk command: Creating HADB encryption key

adbupddmk command: Updating HADB encryption key

bb....bb: Privilege required to perform the operation

AUDIT ADMIN: Audit admin privilege

AUDIT VIEWER: Audit viewer privilege

CRYPTO ADMIN: CRYPTO ADMIN privilege

S:

Ignores this SQL statement.

Action:

Ensure that an HADB user with the bb....bb privilege performs aa....aa.

KFAA31678-E

The audit target specified in CREATE AUDIT is already defined. (M+J+O)

The audit target specified in the CREATE AUDIT statement is already defined. <SQLSTATE: 42K38>

S:

Ignores this SQL statement.

Action:

Because the audit target is already defined, there is no need to execute the CREATE AUDIT statement.

KFAA31679-E

The audit target specified in DROP AUDIT has not been defined. (M+J+O)

The audit target definition specified in the DROP AUDIT statement does not exist. <SQLSTATE: 42K39>

S:

Ignores this SQL statement.

Action:

Because the specified audit target definition does not exist, there is no need to execute the DROP AUDIT statement.

KFAA31684-E

The table option "aa....aa" cannot be specified. (reason = bb....bb) (M+J+O)

Table option aa....aa cannot be specified. <SQLSTATE: 42IAA>

aa....aa: Table option that cannot be specified

BRANCH ALL

PCTFREE

CHUNK ARCHIVABLE

bb....bb: Reason why table option cannot be specified

FIX table: The table is a FIX table.

column store table: The table is a column store table.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31685-E

aa....aa cannot be specified. (reason = bb....bb) (M+J+O)

aa....aa cannot be specified. <SQLSTATE: 42IAB>

aa....aa: Invalid option

BRANCH: BRANCH specification

COMPRESSION TYPE: Compression-type specification

CHUNK ARCHIVABLE: Chunk-archive specification

bb....bb: Reason it cannot be specified

A data type is not VARCHAR or VARBINARY

The data type of the column is not VARCHAR or VARBINARY

The table option BRANCH ALL is specified

The table option BRANCH ALL is specified.

The table option STORAGE FORMAT COLUMN is specified

COLUMN is specified for the table option STORAGE FORMAT.

The table option STORAGE FORMAT COLUMN is not specified

COLUMN is not specified for the table option STORAGE FORMAT.

The table option BRANCH ALL was specified when the table was defined

The table option BRANCH ALL was specified when the table was defined.

The table is a column store table

The table is a column store table.

The table is a row store table

The table is a row store table.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take corrective action as described in the following table:

Information output to bb....bb

Description

Action to take

A data type is not VARCHAR or VARBINARY

You cannot specify branch specification for a column whose data type is other than the VARCHAR type or the VARBINARY type.

Use one of the following methods to correct the SQL statement:

If you want to use a data type other than the VARCHAR type or the VARBINARY type for the column:

Delete the branch specification from the SQL statement.

If you want to specify branch specification:

Change the data type of the column to the VARCHAR type or the VARBINARY type.

The table option BRANCH ALL is specified

You cannot specify branch specification for a table column that is defined by specifying the table option BRANCH ALL.

Use one of the following methods to correct the SQL statement:

If you want to specify the table option BRANCH ALL:

Delete the branch specification from the SQL statement.

If you want to specify branch specification:

Delete the table option BRANCH ALL from the SQL statement.

The table option STORAGE FORMAT COLUMN is specified

You cannot specify branch specification for a table column that is defined with the table option STORAGE FORMAT COLUMN specified.

Use one of the following methods to correct the SQL statement:

If you want to define the table as a column store table:

Delete the branch specification from the SQL statement.

If you want to specify branch specification:

Define the table as a row store table instead of a column store table:

The table option STORAGE FORMAT COLUMN is not specified

You cannot specify compression-type specification for a table column that is defined without the table option STORAGE FORMAT COLUMN specified.

Use one of the following methods to correct the SQL statement:

If you want to define the table as a row store table:

Delete the compression-type specification from the SQL statement.

If you want to specify compression-type specification for a column:

Specify the table option STORAGE FORMAT COLUMN to define the table as a column store table.

The table option BRANCH ALL was specified when the table was defined

You cannot add a column for which branch specification is specified to a base table for which BRANCH ALL was specified when the table was defined.

Delete the branch specification from the SQL statement.

The table is a column store table

You cannot add a column for which branch specification is specified to a column store table.

Delete the branch specification from the SQL statement.

You cannot specify chunk-archive specification for a column store table.

A column store table cannot be changed to an archivable multi-chunk table by using the ALTER TABLE statement.

If you need an archivable multi-chunk table, change the column store table to a row store table. For details about how to change a column store table to a row store table, see Changing a column store table to a row store table in the HADB Setup and Operation Guide.

If you change the column store table to a row store table, specify chunk-archive specification when you execute the CREATE TABLE statement to define the table as an archivable multi-chunk table.

The table is a row store table

You cannot add a column for which compression-type specification is specified to a row store table.

Delete the compression-type specification from the SQL statement.

KFAA31686-E

The DELIMITER option cannot be specified because the index type is not TEXT WORDCONTEXT. (M+J+O)

TEXT WORDCONTEXT is not specified for the index type. Therefore, a text-index delimiter specification cannot be specified. <SQLSTATE: 42IC0>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the SQL statement.

KFAA31687-E

The authentication method for the user of the specified authorization identifier cannot be changed to aa....aa authentication. (reason = bb....bb) (M+J+O)

The user authentication method of the HADB user having the specified authorization identifier cannot be changed. <SQLSTATE: 42K44>

aa....aa: User authentication method

PAM: PAM authentication

Keycloak: Keycloak authentication

bb....bb:

Cause of the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take corrective action as described in the following table:

Information output to bb....bb

Cause of the error

Corrective action to take

the user already uses the specified authentication method

The specified user authentication method is already in use.

There is no need to change the user authentication method for the specified HADB user.

the user is the auditor

The user authentication method for HADB users with audit privilege cannot be changed.

After revoking the audit privilege of the specified HADB user, please change the user authentication method. An HADB user who has the audit admin privilege must revoke the audit privilege.

the user has the CRYPTO ADMIN privilege

The user authentication method for HADB users with a CRYPTO ADMIN privilege cannot be changed.

After revoking the CRYPTO ADMIN privilege of the specified HADB user, please change the user authentication method. An HADB user who has the DBA privilege must revoke the CRYPTO ADMIN privilege.

the user is the last user who has both DBA and CONNECT privileges and who uses database authentication

At least one HADB user with DBA and CONNECT privileges is required, using database authentication as the user authentication method. Therefore, when there is only one such HADB user, the user authentication method for that HADB user cannot be changed.

After confirming that there are two or more HADB users who satisfy both of the following conditions, change the user authentication method for the specified HADB users.

Has both the DBA privilege and the CONNECT privilege

Uses database authentication for user authentication method

KFAA31688-E

User authentication by using aa....aa authentication failed. (reason = bb....bb) (M+J+O)

User authorization using aa....aa failed. <SQLSTATE:28503>

aa....aa: User authentication method

PAM: PAM authentication

Keycloak: Keycloak authentication

bb....bb:

Cause of the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take corrective action as described in the following table: Then, run user authorization.

Information output to bb....bb

Cause of the error

Corrective action to take

the specified user does not exist

There is no external user (e.g., OS user) corresponding to the specified authorization identifier.

Verify that there is an external user (e.g., OS user) corresponding to the specified authorization identifier. After that, specify the authorization identifier and password corresponding to the external user (e.g., OS user) that exists.

the specified password has expired

The specified password has expired.

Update the password expiration date for the external user (e.g., OS user) corresponding to the specified authorization identifier.

the specified user account has expired

The specified user account has expired.

Update the expiration date of the account of the external user (e.g., OS user) corresponding to the specified authorization identifier.

authentication failed

Authentication failed.

The following describes the causes for the user authorization failure and the corrective action to take.

Common to PAM authentication and Keycloak authentication:

The password is invalid

Check that the password is correct and enter the correct password.

In the case of PAM authentication:

The PAM configuration file (/etc/pam.d/hadb) does not exist

Check whether the PAM configuration file exists on the server machine. If the PAM configuration file does not exist, refer to PAM Settings in PAM Authentication Preferences of the manual HADB Setup and Operation Guide to store the PAM configuration file on the server machine and set permissions.

Permissions in the PAM configuration file (/etc/pam.d/hadb) are invalid

Check that the permissions for the PAM configuration file are correct. If the PAM configuration file permissions are invalid, refer to PAM Settings in PAM Authentication Preferences of the manual HADB Setup and Operation Guide to set the appropriate permissions.

If the above solution does not resolve the problem, please refer to the OS manual on PAM authentication errors and eliminate the cause of the error.

In the case of Keycloak authentication:

Detailed information about the error cause is output in the immediately preceding error message. Follow this detailed information to take appropriate action.

password decryption failed

Failed to decrypt password.

Specify the path name of the correct public key file in the client definition's adb_clt_passwd_pubkey_path operand using an absolute path.

If an error occurs when executing the command, specify the path name of the correct public key file in the server definition's adb_cmd_passwd_pubkey_path operand using an absolute path.

the access token is invalid

The access token is invalid.

The following causes are possible. Review your settings.

The access token has expired.

The issuer of the access token is incorrect.

A token signature algorithm not supported by HADB is being used.

The hostname is not specified in the Keycloak configuration file.

If the adb_auth_clt_keyc_endpoint operand is specified in the server definition and the hostname is not specified in the Keycloak configuration file, the issuer of the access token may be considered incorrect. For details about specifying hostname, see Specifying the configuration file of Configuration on the Keycloak server under Environment settings for Keycloak authentication in the manual HADB Setup and Operation Guide. After specifying the hostname, restart the Keycloak server.

an error occurred in the attempt to call a PAM library function

An error occurred while calling a PAM library function.

Eliminate the cause of the error based on the message that was output immediately prior to this message.

an error occurred in the attempt to call an OpenSSL library function

An error occurred while calling an OpenSSL library function.

an error occurred in the attempt to call a libcurl library function

An error occurred during the call to the libcurl library function.

an error occurred in the attempt to call a jansson library function

An error occurred during the call to the jansson library function.

an error occurred in the attempt to call a cjose library function

An error occurred during the call to the cjose library function.

KFAA31696-E

The DB area for data is not specified. (M+J+O)

The data DB area for storing tables or indexes is not specified in the CREATE TABLE or CREATE INDEX statement. <SQLSTATE: 58024>

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take one of the following actions:

■ Correct the SQL statement.

If the CREATE TABLE statement resulted in an error, add either or both of the following specifications to the CREATE TABLE statement.

Specification of IN DB-area-name that specifies the DB area in which defined tables are to be stored

Specification of IN DB-area-name in a uniqueness constraint definition

For details about the IN DB-area-name specification, see Explanation of specification format in Specification format and rules for the CREATE TABLE statement in the manual HADB SQL Reference.

If the CREATE INDEX statement resulted in an error, add the following specification to the CREATE INDEX statement.

Specification of IN DB-area-name that specifies the DB area in which defined indexes are to be stored

For details about the IN DB-area-name specification, see Explanation of specification format in Specification format and rules for the CREATE INDEX statement in the manual HADB SQL Reference.

■ Specify the adb_sql_default_dbarea_shared operand in the server definition.

For the adb_sql_default_dbarea_shared operand, specify the DB area name that is assumed if the IN DB-area-name specification is omitted.

KFAA31711-E

The number of user logfiles exceeded the maximum. (M+J+O)

The number of user log files has reached its upper limit. <SQLSTATE: 40820>

S:

Invalidates this transaction.

Action:

See the description of the expression that calculates the number of user log files in Determining the number of user log files in the HADB Setup and Operation Guide. Then, take one of the following actions so that the conditions in the expression are satisfied:

Increase the value of the adb_log_usrfile_num operand in the server definition (increase the number of user log files).

Decrease the number of real threads that perform update processing.

To decrease the number of real threads that perform update processing, decrease the values of the options in the expression that calculates the number of user log files.

KFAA31713-E

There was a conflict between attempts to update rows. table ID = aa....aa, AP name = bb....bb (M+J+O)

An attempt was made to update or delete a row that is being updated or deleted by another transaction. <SQLSTATE: 4050Q>

aa....aa:

Table ID (decimal)

bb....bb: An identifier that indicates the application that is deleting or updating the target row.

Note that *** is displayed when no application identifier can be output.

S:

Invalidates this transaction.

Action:

Wait for the executing transaction to terminate, and then re-execute the new transaction.

Note that you can use a table ID as a key to identify the name of the table that an attempt was made to update or delete. For details about how to do this, see Searching a dictionary table in the HADB Setup and Operation Guide.

KFAA31714-E

The SQL statement cannot be executed, because the unique constraint for the B-tree index "aa....aa"."bb....bb" was violated between SQL preparation and SQL execution. (M+J+O)

The SQL statement cannot be executed because a uniqueness constraint violation occurred on B-tree index "aa....aa"."bb....bb" between the time the preprocessing of the SQL statement began and the time the SQL statement was executed. <SQLSTATE: 52020>

aa....aa: Schema name

Schema name of the B-tree index on which a uniqueness constraint violation occurred

bb....bb: Index identifier

Index identifier of the B-tree index on which a uniqueness constraint violation occurred

S:

Invalidates this transaction.

Action:

Re-execute the SQL statement.

KFAA31719-E

A transaction cannot be executed because the command is being executed or the transaction by AP is being executed. (M+J+O)

This transaction cannot be executed because a command is executing or because a transaction is being executed by an application program. <SQLSTATE: 54017>

S:

Ignores this SQL statement.

Action:

Wait for the executing command or transaction to terminate, and then re-execute the new transaction.

KFAA31727-E

A table or index cannot be aa....aa because the number of chunks created in the "bb....bb" DB area exceeds cc....cc. (M+J+O)

No new table or index can be defined in the data DB area because the maximum number of chunks that can be managed in one data DB area has been exceeded. Another possibility is that the value set for the maximum number of chunks in a table defined in the data DB area cannot be increased. <SQLSTATE: 40801>

aa....aa: Operation attempted

defined: Defining tables or indexes

changed: Changing table definitions

bb....bb:

DB area name

cc....cc:

Number of chunks that exceeded the maximum

S:

Invalidates this transaction.

Action:

Reduce the value set for the maximum number of chunks based on the number of chunks that exceeded this maximum (value of cc....cc), and then re-execute the SQL statement.

However, if all the following conditions are satisfied, this message might be output again after the maximum number of chunks is reduced. In such a case, further reduce the maximum number of chunks.

changed is displayed for aa....aa.

The table to be changed and the index defined for that table are stored in the same DB area.

If the value set for the maximum number of chunks cannot be reduced, take the action that is appropriate to the operation to be performed, as described below.

Operation attempted (information displayed as aa....aa)

Corrective action

defined

Define the table or index in another DB area.

Delete any unneeded tables and indexes from this DB area.

Reduce the value set for the maximum number of chunks in another table in the same DB area.#

changed

Delete any unneeded tables and indexes from this DB area.

Reduce the value set for the maximum number of chunks in another table in the same DB area.#

#

For details about how to change the maximum number of chunks, see Changing the maximum number of chunks in Performing operations on multi-chunk tables in Unscheduled Operations in the HADB Setup and Operation Guide.

KFAA31728-E

A chunk of the chunk ID aa....aa was not found in the "bb....bb"."cc....cc" table. (M)

The specified chunk ID does not exist in the table. <SQLSTATE: 40802>

aa....aa:

Chunk ID

bb....bb:

Schema name

cc....cc:

Table identifier

S:

Invalidates this transaction.

Action:

Retrieve the STATUS_CHUNKS system table to check for the chunk IDs existing in the table. For details about how to retrieve the STATUS_CHUNKS table, see Searching system tables in the HADB Setup and Operation Guide.

KFAA31729-E

The chunk ID of the current chunk cannot be specified for aa....aa. (M+J+O)

The chunk ID of the current chunk cannot be specified in the PURGE CHUNK statement. <SQLSTATE: 40803>

aa....aa:

SQL statement

S:

Invalidates this transaction.

Action:

The current chunk cannot be deleted.

Retrieve the STATUS_CHUNKS system table to determine whether the chunk ID specified in the PURGE CHUNK statement is correct. For details about how to retrieve the STATUS_CHUNKS table, see Searching system tables in the HADB Setup and Operation Guide.

KFAA31730-E

After the change, the created number of chunks exceeds the maximum number of chunks. (created number of chunks = aa....aa) (M+J+O)

The ALTER TABLE statement cannot be executed because the maximum number of chunks specified in the ALTER TABLE statement is less than the number of chunks that have already been created in the table. <SQLSTATE: 40804>

aa....aa:

Number of chunks that have already been created in the table

S:

Invalidates this transaction.

Action:

Specify aa....aa or a greater value as the maximum number of chunks in the ALTER TABLE statement.

KFAA31733-E

The page being recovered for the primary node promotion was accessed. (M+J+O)

The page being recovered for database update processing was accessed during the primary node switchover processing. <SQLSTATE: 40920>

S:

Invalidates this transaction.

Action:

Wait for the primary node switchover processing to terminate, and then re-execute the SQL statement or command that caused the error.

KFAA31734-E

The path of the input data file of the system-defined function aa....aa is invalid. (reason = bb....bb) (M+J+O)

An error occurred during check of the path name of the file that will be the input data of the system-defined function aa....aa.

aa....aa: System-defined function name

ADB_AUDITREAD

ADB_CSVREAD

bb....bb: Cause of the error

INVALID PATH FORMAT: The specification format of the path name is invalid.

LENGTH ERROR: The specified path name is too long.

INVALID PATH: The file of the specified path cannot be used as the input data of the system-defined function.

S:

Invalidates this transaction.

Action:

Take the following action depending on the executed system-defined function and the displayed cause of error.

Executed system-defined function (aa....aa)

Cause of the error (bb....bb)

Corrective action to take

SQLSTATE

ADB_AUDITREAD

INVALID PATH FORMAT

Specify the path name of the audit trail file by using an absolute path.

Also, make sure that the special character is correctly specified in the audit trail file path.

2252A

LENGTH ERROR

Reduce the length of the audit trail file path name (excluding leading and trailing spaces) to 1,024 bytes or less.

If the audit trail file path name contains a special character, reduce the length of the target audit trail file path name to 1,024 bytes or less.

2252B

INVALID PATH

The path to the current audit trail file cannot be specified in the ADB_AUDITREAD function. Specify an audit trail file other than the current file.

2252C

ADB_CSVREAD

INVALID PATH FORMAT

Specify the path name of the CSV file by using an absolute path.

22523

LENGTH ERROR

Reduce the length of the CSV file path name (excluding leading and trailing spaces) to 510 bytes or less.

22524

KFAA31735-E

The file format of the input data file of the system-defined function aa....aa is invalid. (file = bb....bb) (M+J+O)

The data format of the file that will be the input data of the system-defined function aa....aa is invalid. <SQLSTATE: 22525>

aa....aa: System-defined function name

ADB_AUDITREAD

ADB_CSVREAD

bb....bb:

Path name of the file with an invalid data format

S:

Invalidates this transaction.

Action:

■ If aa....aa is ADB_AUDITREAD

Make sure that the file indicated by bb....bb is either of the following files:

Audit trail file

Audit trail file that has been compressed by the OS's gzip command

■ If aa....aa is ADB_CSVREAD

Check the following:

Make sure that the file indicated by bb....bb is a regular file.

If GZIP is specified for the compression format option COMPRESSION_FORMAT, make sure that the file indicated by bb....bb satisfies either of the following conditions:

The file has been compressed by the OS's gzip command.

The file is a compressed file exported by using the adbexport command.

If this message is output when you access an archivable multi-chunk table, the file indicated by bb....bb (archive file) has been corrupted. In this case, see Recovering the database from the backup in the HADB Setup and Operation Guide, and then recover the database.

KFAA31736-E

An error occurred in the input data file of the system-defined function ADB_CSVREAD. (reason = aa....aa, file = bb....bb, row = cc....cc, field = dd....dd) (M+J+O)

An error occurred in the file that will be the input data of the ADB_CSVREAD function. The location of the error can be identified based on bb....bb, cc....cc, and dd....dd.

aa....aa: Cause of the error

DATA CONVERSION ERROR: An error occurred during file conversion processing. <SQLSTATE: 22527>

NO FIELD: Field data does not exist. <SQLSTATE: 22528>

INVALID ENCLOSING CHARACTER: Invalid enclosing characters exist in the data. <SQLSTATE: 22529>

bb....bb:

Path name of the file in which the error occurred

cc....cc:

Row number of data in the file

dd....dd:

Field data number in the file

S:

Invalidates this transaction.

Action:

Make sure that the compression format of the file indicated by bb....bb matches the specification of the compression format option COMPRESSION_FORMAT of the ADB_CSVREAD function.

If they match, identify the field data that caused the error based on the information indicated by cc....cc and dd....dd. Then, take the corrective action for the cause of the error indicated by aa....aa.

If aa....aa is DATA CONVERSION ERROR

The data type specified for the table function column list is not compatible with the data type of the field data. Correct the data type specified for the table function column list.

If the error occurred at the end of the row, check that the row ends with a linefeed in the file indicated by bb....bb.

If aa....aa is NO FIELD

Add field data.

Alternatively, make sure that the field data number is specified correctly for the specification column option.

If aa....aa is INVALID ENCLOSING CHARACTER

Correct the invalid enclosing characters.

Alternatively, make sure that the enclosing character specification option is specified correctly.

If this message is output when you access an archivable multi-chunk table, the file indicated by bb....bb (archive file) has been corrupted. In this case, see Recovering the database from the backup in the HADB Setup and Operation Guide, and then recover the database.

KFAA31737-E

The size (aa....aa) of the area needed to store the row exceeds the capacity of one segment (bb....bb). (M+J+O)

The size of the area required to store a row exceeds the capacity of one segment. Therefore, the CREATE TABLE or ALTER TABLE statement can be executed. <SQLSTATE:52021>

aa....aa: Size of the area required to store a row (unit: byte)

If the size of the area required to store a row cannot be output, *** is displayed.

bb....bb: Capacity of one segment (unit: byte)

If the capacity of one segment cannot be output, *** is displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take one of the following corrective actions:

If this message is output during execution of a CREATE TABLE statement

Make sure to meet the condition expression of the capacity of one segment explained in IN DB-area-name [Common] in Explanation of specification format in Specification format and rules for the CREATE TABLE statement in the manual HADB SQL Reference. To satisfy the condition expression, one or more of the following actions must be taken.

Decrease the specified value of the data length of the element data type of an array-type column.

Decrease the specified value of the maximum number of elements in an array-type column.

Reduce the specified value of data length for non-array-type columns.

If the above actions are not possible, increase the capacity of one segment of the data DB area.

If this message is output during execution of a ALTER TABLE statement

Make sure to meet the condition expression of the capacity of one segment explained in Rules in Specification format and rules for the ALTER TABLE statement in the manual HADB SQL Reference. To satisfy the condition expression, one of the following actions is required.

If this message is output when a column was added

The specified value for the data length of the additional column is too large. Reduce the specified value for the data length of the additional column.

Note that when adding an array-type column, the specified value of data length of element data type is too large or the specified value of maximum number of elements is too large. Make at least one of the specified values smaller.

If this message is output when the data type of a column was changed

The specified value of the data length of the changed data type is too large for the column whose data type was changed. Reduce the specified value of the data length of the changed data type.

If this message is output when the maximum number of elements in an array-type column is increased

The specified value for the maximum number of elements after the change is too large. Reduce the specified value for the maximum number of elements after the change.

If the above actions are not possible, increase the capacity of one segment of the data DB area.

For details about the appropriate value for the capacity of one segment of the data DB area, see Points to consider when determining the capacity of one segment in data DB areas in the HADB Setup and Operation Guide.

Note that to increase the capacity of one segment of the data DB area, the data DB area must be deleted once using the adbmodarea command and then recreated. For how to recreate a data DB area, see Steps to take when a data DB area can no longer be expanded in the HADB Setup and Operation Guide.

KFAA31738-E

Processing cannot continue because the aa....aa operation failed. (operation = bb....bb, object key = "cc....cc") (M+J+O)

Processing cannot continue because the S3 bucket or container operation has failed. <SQLSTATE:40529>

aa....aa: Operation target

S3 bucket: S3 bucket

Container: Container

bb....bb: Operation failed

get_async: Asynchronous GET request

put_async: Asynchronous PUT request

delete_async: Asynchronous DELETE request

delete_all: Synchronous DELETE ALL request

head_async: Asynchronous HEAD request

list_init_async: Asynchronous LIST INIT request

list_exec_async: Asynchronous LIST EXEC request

list_term_async: Asynchronous LIST TERM request

cc....cc: Object key

If it cannot be output, * is displayed.

S:

Terminates processing.

Action:

If this message was output to the HADB server

Operation for S3 bucket or container failed. Check the KFAA41236-E message or KFAA41237-E message that was output before and after this message, and eliminate the cause of the error.

If this message was output to an HADB client

Ask the HADB administrator to check the HADB server, or contact an OS user who belongs to the HADB administrators group.

KFAA31739-E

An Apache Arrow API error occurred. (cause = "aa....aa", details = "bb....bb") (M+J+O)

An Apache Arrow API error occurred. <SQLSTATE:5100R>

aa....aa:

Apache Arrow status code

bb....bb:

Detailed information set by the Apache Arrow API

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Refer to the information output in aa....aa and bb....bb to remove the cause of the error. For information on Apache Arrow status codes, see Programming Support in the Apache Arrow documentation.

bb....bb may contain position information that indicates the location that caused the foreign data access error. However, the meaning of the position information may differ between foreign data access errors and DB area access errors. For example, if the position information is a row number, the row number output in case of a foreign data access error starts from 0, but the row number output in case of a DB area access error starts from 1. Therefore, if there is no problem at the location indicated in the position information, review the surrounding locations as well.

This error message may appear when the size of a single row of data in a foreign data file in CSV or JSON format exceeds 64 megabytes.

This error message might also be output if each JSON object in the JSON-format foreign data file is delimited by a comma instead of a newline character.

For rules on foreign data files, see Rules in Specification format and rules for the CREATE FOREIGN TABLE statement in the manual HADB SQL Reference.

If you cannot determine the corrective action to take based on the information that was output, execute the adbinfoget command, collect troubleshooting information, and then contact the customer support center.

Note

This error message may be output when the pathname of the data output destination specified in the COPY statement is too long.

KFAA31740-E

The data included in the column "aa....aa" derived from the result of the outermost query in the query expression body of the COPY statement is invalid. (reason = bb....bb) (M+J+O)

The data contained in the column "aa....aa" derived by the outermost query specification in the query expression body of the COPY statement is invalid. <SQLSTATE:5100P>

aa....aa:

Column name or its field name

bb....bb: Cause of the error

The data exceeds the range of values that can be handled by the TIMESTAMP column type.

The data exceeds the range of values that can be handled by the TIMESTAMP column type.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take one of the following corrective actions, and then re-execute the SQL statement.

Ensure that the data in the derived column are within the range of the TIMESTAMP column type.

Change the data type of the derived column.

For data that can be handled by the COPY statement, see COPY (output search results to a file) in the HADB SQL Reference manual.

KFAA31741-E

An attempt to acquire the memory required to access the foreign server failed. (details = "aa....aa") (M+J+O)

An attempt to acquire enough memory to access the foreign server has failed. <SQLSTATE:53201>

aa....aa:

Detailed error information

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Refer to the detailed error information output to aa....aa to make sure that there is enough memory available for the following procedure. Then, re-execute the SQL statement or command.

Detailed error information includes error messages generated by Apache Arrow and exception information from the standard library. Detailed error information may include error messages from AWS and other sources.

Check whether there are any unneeded processes or shared memory. If there are any unneeded processes or shared memory, terminate or delete them.

If there is not enough memory after performing step 1, terminate the HADB server once with the adbstop command. Then, execute the adbstart command to start the HADB server.

If there is not enough memory after performing step 2, restart the OS. Then, execute the adbstart command to start the HADB server.

If there is not enough memory after performing step 3, change the kernel parameter setting to increase the amount of memory that processes can use. After restarting the OS, start the HADB server with the adbstart command.

KFAA31742-E

An error was detected when accessing the data file of the foreign table. (cause = "aa....aa", details = "bb....bb") (M+J+O)

An error was detected when accessing the foreign data file.

aa....aa:

Cause of the error

bb....bb:

Detailed error information

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take the following action depending on the cause of error output to aa....aa.

Value of aa....aa

Cause of the error

Corrective action to take

SQLSTATE

Field not found

No field corresponding to the column to be searched was found.

The column name to be searched does not match the field name of the foreign data. The field name of the foreign data will be output to bb....bb. Based on this, change the column name in the foreign table.

The column and field names should match, down to the uppercase and lowercase letters.

2252D

Data type incompatibility

Data type is incompatible.

Data cannot be retrieved because the data type of the columns in the foreign table and the field in the foreign data are incompatible. The data type code of the column and the data type name of the field will be output to bb....bb. Based on this, change the data type of the column in the foreign table to a compatible data type.

Note that if the data type of a column in an foreign table is an array-type column, no data type code is output to bb....bb. It is output as ARRAY.

For details about data type codes, see Types of data types in the HADB SQL Reference manual.

See the Apache Arrow documentation for the data type names of the fields.

For details about data type compatibility, see CREATE FOREIGN TABLE (defining a foreign table) in the HADB SQL Reference manual.

2252E

Outside the range of the numeric data type

There are values in the foreign data that exceed the range that can be handled as numeric data.

Change the data type of the columns in the foreign table to numeric data that can handle a wider range. For example, if a SMALLINT column type caused the error, change it to an INTEGER column type.

Note that values exceeding the maximum range of data types supported by HADB cannot be retrieved. Please take the following actions to avoid errors.

Specify values within the range of the column data type for the search condition.

Exclude the column that caused the error from the projection column.

The column names and data type codes of the foreign table will be output to bb....bb. In the case of DECIMAL column type, precision is also output.

For details about data type codes, see Types of data types in the HADB SQL Reference manual.

Defined column length exceeded

There is data in the foreign data that exceeds the defined length of the columns in the foreign table.

There is foreign data that is greater than the defined length of the columns in the foreign table. The length of the column definitions in the foreign table and the data length of the foreign data will be output to bb....bb. Based on this, increase the length of the column definitions in the foreign table.

The number of array elements exceeded the maximum number of elements

There is array type data in the foreign data in which the number of array elements exceeds the maximum number of elements.

The maximum number of elements specified in the column definition and the number of elements in the foreign data will be output to bb....bb. Based on this, increase the maximum number of elements in the array-type column.

Unsupported data

There is data in the foreign data that is not supported by HADB.

In bb....bb, there is data in the foreign data that is not supported by HADB. Based on this, delete the relevant foreign data.

DECIMAL scale mismatch

The column of the foreign table and the field of the foreign data do not match the scale of the DECIMAL type.

The column and field scale will be output to bb....bb. Based on this, match the scale.

KFAA31743-E

An Apache Arrow API error occurred during the execution of the COPY statement. (SQL serial no = aa....aa, column name = "bb....bb", cause = "cc....cc", detail = "dd....dd") (M+J+O)

An Apache Arrow API error occurred while executing the COPY statement. <SQLSTATE:5100P>

aa....aa:

SQL statement sequence number since the connection was established

bb....bb: Column name or field name that caused the error

The column or field names displayed are those derived from the outermost query specification in the query expression body of the COPY statement.

If no column name or the field name of that column can be output, three asterisks (***) are displayed.

cc....cc:

Apache Arrow status code

dd....dd:

Detailed information set by the Apache Arrow API

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Refer to the information output in cc....cc and dd....dd to remove the cause of the error. For information on Apache Arrow status codes output for cc....cc, see Programming Support in the Apache Arrow documentation. If the output content of dd....dd is cut off in the middle, also check the KFAA51292-E message.

The detailed information of the Apache Arrow API output for dd....dd may contain position information that indicates the location that caused the error. However, the meaning of the position information may differ from the HADB errors. For example, if the position information is a column number, the column number output in case of the Apache Arrow API detailed information starts from 0, but the column number output in case of HADB starts from 1. Therefore, if there is no problem at the location indicated in the position information, review the surrounding locations as well.

If you cannot determine the corrective action to take based on the information that was output, execute the adbinfoget command, collect troubleshooting information, and then contact the customer support center.

KFAA31744-E

Failed to establish a connection to the foreign server. (details = "aa....aa") (M+J+O)

A connection could not be established to the foreign server. <SQLSTATE:5100S>

aa....aa:

Detailed error information

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Review the various settings by referring to the detailed error information output to aa....aa.

Detailed error information will be output in the error messages generated by Apache Arrow. Detailed error information may include error messages from AWS and other sources.

The following describes the cause of the error and the corrective action to take.

Cause of the error

Corrective action

Authentication information to access foreign servers are invalid

Set the correct authentication information. Authentication information can be configured for the foreign servers in the following ways.

Set an access key and secret key for each foreign server.

Set IAM roles for each instance.

Set up an authentication information file for each instance.

For details, see the following section.

How to define a foreign server in the manual HADB Setup and Operation Guide.

CREATE SERVER (defining a foreign server) in the manual HADB SQL Reference

Privileges required to operate foreign servers are insufficient

Bind the appropriate IAM policy with the authentication information you are using. For details, see How to define a foreign server in the manual HADB Setup and Operation Guide.

Endpoint on foreign servers is invalid

Set the correct endpoints. For details, see CREATE SERVER (defining a foreign server) in the manual HADB SQL Reference.

Communication to the foreign servers is blocked

Check the network settings.

KFAA31820-E

An Apache Iceberg API error occurred. (cause = "aa....aa", details = "bb....bb") (M+J+O)

An Apache Iceberg API error has occurred. <SQLSTATE:5100R>

aa....aa:

The classification set by the Apache Iceberg API

bb....bb:

Detailed information set by the Apache Iceberg API

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Refer to the information output in aa....aa and bb....bb to remove the cause of the error.

The main causes of the error and their corrective actions are shown below.

There is an error in the definition of the foreign server.

Redefine the foreign server and foreign table. For details on defining foreign servers and foreign tables, see CREATE SERVER (define a foreign server) and CREATE FOREIGN TABLE (define a foreign table) in the manual HADB SQL Reference.

There is an error in the definition of the foreign table.

Redefine the foreign table. For details on defining foreign tables, see CREATE FOREIGN TABLE (define a foreign table) in the manual HADB SQL Reference.

KFAA31821-E

The Iceberg table includes an unsupported file format "aa....aa". (M+J+O)

An unsupported file format is included in the Iceberg table. <SQLSTATE:2252E>

aa....aa:

Data format that caused the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Correct the Iceberg table to ensure that no files other than those in Parquet format are included.

KFAA31822-E

An error was detected when accessing the Iceberg catalog. (cause = "aa....aa", details = "bb....bb") (M+J+O)

An error was detected when accessing the Iceberg catalog. No resource corresponding to the search target was found. <SQLSTATE:2252D>

aa....aa: Cause of the error

Not Found: The resource was not found.

bb....bb:

Detailed information about error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Refer to the detailed error information output in bb....bb (such as the resource name that caused the error) and take appropriate action.

If aa....aa shows Not Found

The resource corresponding to the search target was not found in the Iceberg catalog. Correct the definition of the foreign table. The resource name that was not found is output in bb....bb.

Note that the resource name must match exactly, including case sensitivity of uppercase and lowercase alphabetic characters.

KFAA31893-E

The AP cannot connect to HADB servers on aa....aa versions not supported by HADB. (M+O)

An application program cannot connect to the HADB server on a kernel or OS version that is not supported by HADB. <SQLSTATE: 5201F>

aa....aa: Cause of the error

kernel: Kernel

operating system: OS

S:

Ignores this SQL statement.

Action:

Upgrade the kernel or OS to a version supported by HADB.

KFAA31894-E

An error occurred in the connection, and the transaction was rolled back. (statement handle = aa....aa, error message = "bb....bb") (M+J+O)

The transaction was rolled back because an error occurred in one of the statement handles used in the transaction. <SQLSTATE: 5C03A>

aa....aa:

Statement handle

bb....bb:

Error message for the error that occurred in another statement handle

S:

Ignores this SQL statement.

Action:

Check the action to be taken for the error message indicated by bb....bb, and then take the action. Then, retry the operation.

KFAA31895-E

Invalid data was received from an HADB client (with the JDBC driver) or from a command. (information 1 = aaaa, information 2 = bbbb) (M+J+O)

Invalid data was received from an HADB client (including a JDBC driver) or command. <SQLSTATE: 5C034>

aaaa:

Maintenance information 1

bbbb:

Maintenance information 2

S:

Ignores this SQL statement.

Action:

Make a backup of the client message log file. Then, contact the customer support center.

KFAA31896-E

An SQL statement cannot be executed. (reason = aa....aa) (M)

An SQL statement cannot be executed due to one of the following reasons:

The server message log file is full. <SQLSTATE: 53030>

The client message log file is full. <SQLSTATE: 53031>

aa....aa: Cause of the error

message log is full: The server message log file is full.

client log is full: The client message log file is full.

S:

Ignores this SQL statement.

Action:

Disconnect from the HADB server, and then terminate the application program. Next, take the following corrective action, corresponding to the cause of the error:

If the server message log file is full

Shut down the HADB server, and then allocate space on the disk where the server message log file is stored.

If the client message log file is full

Allocate space on the disk where the client message log file is stored.

KFAA31897-E

The aa....aa cannot be set. (reason = bb....bb) (M+J+O)

aa....aa cannot be set.

aa....aa: Item that cannot be set

transaction isolation level: Transaction isolation level

sql order mode: Character string data sort order

sql order mode(ISO): Character string data sort order (ISO)

transaction access mode: Transaction access mode

audit trail information: Additional user information

bb....bb:

Cause of the error

S:

Ignores this SQL statement.

Action:

Take one of the following corrective actions based on the cause of the error that is output:

Cause of the error (bb....bb)

Error description

Corrective action

SQLSTATE

connection is not established

No connection has been established.

Set the following items after a connection is established:

Transaction isolation level

Sort order of character string data

Transaction access mode

Additional user information

54203

transaction is already started

The transaction has already started.

Set the following items after the transaction is committed with COMMIT or ROLLBACK:

Transaction isolation level

Sort order of character string data

Transaction access mode

Additional user information

54204

character encodings of the HADB client is not Unicode(UTF-8)

The character encoding used by the HADB client is not Unicode (UTF-8).

Specify BYTE for the character string data sort order.

54205 (when connected, 08622)

character encodings of the HADB server is not Unicode(UTF-8)

The character encoding used by the HADB server is not Unicode (UTF-8).

54205 (when connected, 08607)

cursor is already opened

The cursor is already opened.

Close the ResultSet object that is generated by the target Connection object. Then, set the following items:

Transaction isolation level

Sort order of character string data

Transaction access mode

Additional user information

54206

KFAA31898-E

aa....aa. (reason = bb....bb, connection identifier = cc....cc) (M+J+O)

aa....aa cannot be performed for reason bb....bb.

aa....aa: Process in which an error occurred

The definition SQL cannot be executed: Execution of a definition SQL statement

The retrieval SQL cannot be executed: Execution of a retrieval SQL statement

The update SQL cannot be executed: Execution of an update SQL statement

The CONNECT statement cannot be executed: Execution of a CONNECT statement

The command cannot be executed: Execution of a command

The transaction cannot be started: Start of transaction

The retrieval SQL applying SQL parallel execution cannot be executed: Execution of a retrieval SQL statement with SQL parallel execution function applied

bb....bb:

Cause of the error

cc....cc:

Connection ID

S:

Ignores this SQL statement.

Action:

Take one of the following corrective actions based on the cause of the error that is output:

Cause of the error (bb....bb)

Error description

Corrective action

SQLSTATE

A command that cannot be executed at the same time as other commands or applications is currently being executed

A command is running that cannot be executed concurrently with another command or application.

After the executing command has terminated, re-execute this command.

08608

The HADB server operation mode is "OFFLINE"

The CONNECT statement cannot be executed because the HADB server is in offline mode.

Change the HADB server operation mode to normal, and then re-execute the SQL statement.

08609

A command cannot be executed because the HADB server operation mode is offline mode.

Change the HADB server operation mode to normal, and then re-execute the command.

However, for the adbupddmk command, change the HADB server operation mode to maintenance mode, and then re-execute the command.

None

A connection is being established directly on a secondary node

The CONNECT statement cannot be executed because a direct connection is being established to the HADB server for the secondary node.

Change the application's connection target to the alias IP address that indicates the primary node, and then re-execute the SQL statement.

0860A

A connection is being established directly on a worker node

The CONNECT statement cannot be executed because a direct connection is being established to the HADB server for the worker node.

Take one of the following corrective actions. Then, re-execute the SQL statement.

Multi-node configuration with HA Monitor

Change the application program's connection target to the alias IP address that indicates the primary node.

Multi-node configuration without HA Monitor

Change the application program's connection target to the IP address of the primary node.

0860A

An attempt to connect to the port for communication between HADB servers is in progress

The CONNECT statement cannot be executed because an attempt to establish a connection to an HADB server-dedicated communication port is in progress.

In adb_clt_rpc_srv_port in the client definition, specify the port number specified by the server definition's adb_rpc_port operand, and then re-execute the SQL statement.

0860B

The HADB client or command belongs to a client group whose maximum number of concurrent connections is zero

A connection to the HADB server cannot be established because the client or command belongs to a client group or command group whose maximum number of concurrent connections is zero.

Take one of the following corrective actions. Then, re-execute the SQL statement or command.

Action 1

For the adb_clt_group_name operand in the client definition, specify a group name for which a value other than 0 is specified for the -m option of the adbcltgrp operand in the server definition.

Action 2

In the server definition, revise the value of the adbcltgrp operand's -m option corresponding to the group name specified for the adb_clt_group_name operand in the client definition.

This error also occurs if, in the server definition, the sum of the values specified for -u options of the adbcltgrp operands equals the value of the adb_sys_max_users operand. In this case, revise the value specified for each -u option of the adbcltgrp operand.

0860D

The HADB server operation mode is "MAINTENANCE"

The CONNECT statement cannot be executed because the HADB server operation mode is maintenance mode.

Change the HADB server operation mode to normal, and then re-execute the CONNECT statement.

0860E

A command cannot be executed because the HADB server operation mode is maintenance mode.

Change the HADB server operation mode to normal, and then re-execute the command.

None

The HADB client execution environment is invalid

The CONNECT statement cannot be executed because the HADB client execution environment is invalid.

Take the corrective action given for the error message that was output preceding this message.

08623

SQL is already being executed on the same connection

An SQL statement is already executing on the connection.

Wait for the SQL statement executing on the connection to finish, and then re-execute this SQL statement.

54013

Wait for the SQL statement executing on the connection to finish, and then re-execute this retrieval SQL statement with SQL parallel execution function applied.

54025

The read-only transaction is already being executed on the HADB server in the multi-node configuration

Transactions cannot be started because a read-only transaction is being executed on an HADB server in a multi-node configuration.

Execute the SQL statement or command again after all read-only transactions being performed are completed on an HADB server in a multi-node configuration.

54014 or None

The read/write transaction or the command is already being executed on the HADB server in the multi-node configuration

Transactions cannot be started because a read/write transaction or command is being executed on an HADB server in a multi-node configuration.

Execute the SQL statement again after all read/write transactions and commands being performed are completed on an HADB server in a multi-node configuration.

54016

The HADB server operation mode is "QUIESCENCE"

An update SQL statement or definition SQL statement cannot be executed because the HADB server operation mode is quiescence mode.

Change the HADB server operation mode to normal, and then re-execute the SQL statement.

54018

A command cannot be executed because the HADB server operation mode is quiescence mode.

Change the HADB server operation mode to normal, and then re-execute the command.

However, for the adbupddmk command, change the HADB server operation mode to maintenance mode, and then re-execute the command.

None

An attempt to access a DB area that is being accessed by an update SQL statement in a different transaction while another retrieval SQL statement is being executed in the same transaction

If the multi-node function is used, the retrieval SQL statements that satisfy all the following conditions cannot be executed:

An attempt is made to concurrently execute retrieval SQL statements by using multiple statement handles in the same transaction.

A retrieval SQL statement is accessing the data DB area.

Another retrieval SQL statement attempts to access the data DB area being accessed by an update SQL statement (this retrieval SQL statement results in an error).

For details about the conditions in which an error occurs, see Nodes on which SQL statements are executed in Nodes on which transactions and commands are executed in the HADB Setup and Operation Guide.

Take one of the following corrective actions:

Action 1

Wait for termination of the running retrieval SQL statement in condition 2 on the left.

Action 2

Wait for termination of the transaction that uses the update SQL statement in condition 3 on the left.

Then, re-execute the SQL statement that resulted in an error.

54020

The number of concurrent SQL parallel executions exceeded the maximum number

Because the number of concurrent executions of the SQL parallel execution function applied to the retrieval SQL statement has exceeded the maximum number of concurrent executions specified in the server definition adb_sys_max_parallel_exec_num operand, no more SQL parallel execution function applied to the retrieval SQL statement can be executed.

Re-execute the retrieval SQL statement with the SQL parallel execution function after the other retrieval SQL statements with the SQL parallel execution function have been completed.

54024

The retrieval SQL is already being executed as part of SQL parallel execution on the same connection

The SQL statement cannot be executed because a retrieval SQL statement that has already applied the SQL parallel execution function is being executed on the same connection.

Wait for the SQL statement executing on the connection to finish, and then re-execute this retrieval SQL statement with SQL parallel execution function applied.

54025

No SQL sub node could be allocated

Because none of the SQL sub nodes could be allocated, the SQL parallel execution function cannot be applied to the retrieval SQL statement.

The following describes the causes of why not a single SQL sub node could be allocated and the corrective action to take.

The specified values of the operands in the server definition do not match

When using the SQL parallel execution function, there are server definition operands whose specified values must match at each node.

Check that the specified values of the operands in the server definitions for each node match. If there are nodes with different specified values for the server definition operands, terminate the HADB server and set the specified values for the server definition operands to be the same. After that, start the HADB server and then re-execute the retrieval SQL statement with the SQL parallel execution function applied.

For details about the server definition operands that require the specification value at each node to match, see Preparatory Work When Using the SQL Parallel Execution Function in Specifying the Server Definition in the HADB Setup and Operation Guide.

There is no node in the multi-node configuration that can become an SQL sub node

Check for deleted worker nodes or disconnected secondary nodes.

Add a worker node that can become a SQL sub node or return the secondary node and then re-execute the retrieval SQL statement with the SQL parallel execution function applied.

There is no room in the processing thread to execute SQL statements on each node

After the execution of the SQL statement or command being executed on each node is completed, re-execute the retrieval SQL statement with the SQL parallel execution function applied.

Alternatively, you can terminate the multi-node configuration HADB server and specify a value for the server definition adb_sys_rthd_num operand that is greater than or equal to "adb_sys_max_users-operand-specified-value × adb_sql_exe_max_rthd_num-operand-specified-value". After that, start the multi-node configuration HADB server and re-execute the retrieval SQL statement with the SQL parallel execution function applied.

54026

A read/write transaction or specific command is being executed on the primary node

Cannot execute the retrieval SQL statement that uses the SQL parallel execution function because a read/write transaction or a specific command is being executed on the primary node.

Re-execute the retrieval SQL statement with the SQL parallel execution function applied after the read/write transaction or command that is running on the primary node has completed.

54027

The command was executed on a secondary node

This command cannot be executed on a secondary node.

Re-execute the command on a primary node.

None

The command was executed on a worker node

This command cannot be executed on a worker node.

Re-execute the command on a primary node.

None

A node other than the primary node is running

The command cannot be executed because a node other than the primary node is activated.

Terminate the HADB server on the secondary node and worker node, and then re-execute the command.

None

The HADB server operation mode is "NORMAL"

A command cannot be executed because the HADB server operation mode is normal mode.

Change the HADB server operation mode to maintenance mode, and then re-execute the command.

None

Other command or AP is currently being executed

Reorganization of the dictionary table by using the adbreorgsystemdata command cannot be executed because other commands or applications are running.

Re-execute the reorganization of the dictionary table by using the adbreorgsystemdata command after other commands or applications have finished.

None

KFAA31899-E

Failed to read the public key file. (file = aa....aa, reason = bb....bb) (M+J+O)

An attempt to load the public key file failed. <SQLSTATE:08625>

aa....aa: Path name of the public key file

The path name of the public key file is displayed as an absolute path. However, if the path name of the public key file cannot be displayed, asterisks (***) are displayed.

Even if the public key file specified in the client or server definition is not a regular file, the path name of the specified public key file is displayed as an absolute path.

In addition, if the absolute path name of the public key file exceeds 256 bytes, it will be displayed right-aligned.

bb....bb:

Cause of the error

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take corrective action as described in the following table:

Information output to bb....bb

Cause of the error

Corrective action to take

the public key file does not exist

The public key file specified in the client or server definition does not exist.

Specify the path name of the existing public key file in the client definition's adb_clt_passwd_pubkey_path operand using an absolute path.

If an error occurs when executing the command, store the public key file in the path specified in the adb_cmd_passwd_pubkey_path operand of the server definition.

the public key file is not a regular file

The public key file specified in the client or server definition is not a regular file.

Specify the path name of the regular file public key file in the client definition's adb_clt_passwd_pubkey_path operand using an absolute path.

If an error occurs when executing the command, specify the path name of the regular file public key file in the server definition's adb_cmd_passwd_pubkey_path operand using an absolute path.

the permission for the public key file is invalid

The permissions for the public key file specified in the client or server definition is invalid.

Grant read permission for the public key file specified in the adb_clt_passwd_pubkey_path operand of the client definition to the OS user managing the HADB client.

If an error occurs when executing the command, grant read permission for the public key file specified in the adb_cmd_passwd_pubkey_path operand in the server definition to the HADB administrator and OS user belonging to the HADB administrators group.

the format of the public key file is invalid

The format of the public key file specified in the client or server definition is invalid.

Specify the path name of the correct format public key file in the client definition's adb_clt_passwd_pubkey_path operand using an absolute path.

If an error occurs when executing the command, store the correct format public key file in the path specified in the adb_cmd_passwd_pubkey_path operand of the server definition.

the public key file was not specified

No public key file is specified in the client definition.

Add the adb_clt_passwd_pubkey_path operand to the client definition and specify in this operand the absolute path name of the public key file used to encrypt the password.

the specification of a public key file is not necessary

There is no need to specify a public key file in the client definition.

The password cannot be encrypted because no private key file is specified in the adb_auth_passwd_privkey_path operand of the server definition. Therefore, there is no need to specify the adb_clt_passwd_pubkey_path operand in the client definition (do not specify it).

KFAA32000-I

SQL statement execution has finished. (M)

SQL statement execution has finished. <SQLSTATE: 00000>

S:

Continues processing.

KFAA32100-I

There are no rows that match the search condition, or row fetching has finished. (M)

No rows match the conditions. Another possibility is that row fetching has terminated. <SQLSTATE: 02000>

S:

Continues processing.

KFAA32390-I

The SQL execution node will now be changed. (before = a, after = b) (M)

The node in which to execute SQL statements is changed. <SQLSTATE: 00000>

a:

Node number of the secondary node or worker node before the change

b:

Node number of the primary node after the change

S:

Continues processing.

KFAA34002-E

There is an error in the specification method of a scalar function "CONTAINS" argument. (reason = aa....aa) (M+J+O)

The specified scalar function CONTAINS contains an error.

aa....aa: Cause of the error

correction format: The notation-correction-search specification or simple-string specification is invalid. <SQLSTATE: 428T0>

correction value: The specified search string is invalid. <SQLSTATE: 428T1>

synonym format: The synonym-search specification is invalid. <SQLSTATE: 428TA>

synonym value: The synonym dictionary name is invalid. <SQLSTATE: 428TB>

word-context format: The word-context search specification is invalid. <SQLSTATE: 428TC>

S:

Ignores this SQL statement.

Action:

The possible errors are as follows.

■ If aa....aa is correction format:

An invalid character string might be specified in the notation-correction-search specification. Check whether a character string other than IGNORECASE or SORTCODE is specified.

The following errors might exist:

- The simple-string specification in the notation-correction-search specification is not enclosed in parentheses (( and )).

- Parentheses (( and )) are not paired correctly.

- A character exists between ( and a simple-string specification.

- A character exists between a simple-string specification and ).

The specification format of the simple-string specification might be invalid. Make sure that a double quotation mark (") is specified at the beginning.

■ If aa....aa is correction value:

Make sure that the simple-string specification ends with ".

■ If aa....aa is synonym format:

An invalid character string might be specified in the synonym-search specification. Check whether a character string other than SYNONYM is specified.

The following errors might exist:

- The synonym-search specification does not contain parentheses (( and )).

- Parentheses (( and )) are not paired correctly.

- A character exists between ) and a simple-string specification.

- A character exists between ) and a notation-correction-search specification.

The specified synonym dictionary name might be invalid. Make sure that a double quotation mark (") is specified at the beginning. Also, check whether a character is specified between " at the end of the synonym dictionary name and a comma (,) .

■ If aa....aa is synonym value:

Make sure that the specified synonym dictionary name ends with ".

Check whether characters that cannot be used are specified in the synonym dictionary name.

Make sure that the length of the synonym dictionary name does not exceed 120 bytes.

Make sure that the synonym dictionary name is specified. Make sure that an empty string (0 bytes) is not specified.

■ If aa....aa is word-context format:

The character string might be specified in the word-context search specification might be invalid. Make sure that a character string other than WORDCONTEXT or WORDCONTEXT_PREFIX is not specified.

Make sure that a synonym-search specification is not contained in WORDCONTEXT_PREFIX specified in the word-context search specification.

Make sure that the word-context search specification contains parentheses (( and )).

Make sure that the parentheses (( and )) in the word-context search specification are paired correctly.

Make sure that no character exists between ) and a simple-string specification.

Make sure that no character exists between ) and a notation-correction-search specification.

Make sure that no character exists between ) and a synonym-search specification.

KFAA34003-E

A correction search cannot be specified as a scalar function "CONTAINS" argument, because the character encoding to be used on the HADB server is Shift JIS. (ADBLANG = SJIS) (M+J+O)

A notation-correction-search specification cannot be specified because the character encoding used by the HADB server is Shift-JIS (if the value specified for the environment variable ADBLANG is SJIS). <SQLSTATE: 428T2>

S:

Ignores this SQL statement.

Action:

Take one of the following corrective actions:

Delete the notation-correction-search specification from the scalar function CONTAINS.

Change the value of the environment variable ADBLANG to Unicode (UTF-8), and then create the database again by using the adbinit command.

KFAA34004-E

A regular expression specified for a regular expression string that has the "LIKE_REGEX" predicate is incorrect. (details = aa....aa) (M+J+O)

A regular expression specified for a regular expression character string in the LIKE_REGEX predicate is invalid.

aa....aa: Cause of the error

Invalid regular expression: The specified regular expression is invalid. <SQLSTATE: 428T3>

Invalid quantifier: The specified quantifier (such as + and *) is invalid. <SQLSTATE: 428T4>

Unmatched parenthesis: Pairing of parentheses is invalid. <SQLSTATE: 428T5>

Unmatched square bracket: Pairing of square brackets is invalid. <SQLSTATE: 428T6>

S:

Ignores this SQL statement.

Action:

The possible errors are as follows.

▪ If aa....aa is Invalid regular expression:

A special character in character enumeration might be invalid.

An undefined character set identifier might be specified in a character set identifier specification.

▪ If aa....aa is Invalid quantifier:

Two quantifiers might be specified in succession.

The specified repetition factor might contain the following errors:

- Values other than numeric values might be specified for the maximum and minimum values (for example, a comma specification error or missing closing parenthesis).

- The following condition might not be satisfied: 0 ≤ lower limit ≤ upper limit ≤ 256.

■ If aa....aa is Unmatchedparenthesis:

The right parenthesis ()) corresponding to the left parenthesis (() might not be specified.

■ If aa....aa is Unmatchedsquare bracket:

A right square bracket (]) might not be specified after a left square bracket ([).

A right curly bracket (}) might be specified in an inappropriate position.

A right square bracket (]) might be specified in an inappropriate position.

For details about the rules for specifying regular expressions, see LIKE_REGEX predicate in the manual HADB SQL Reference.

KFAA34005-E

The synonym dictionary (aa....aa) specified by the scalar function "CONTAINS" is not registered in the system. (M+J+O)

The synonym dictionary specified in the scalar function CONTAINS does not exist. <SQLSTATE: 428T7>

aa....aa:

Name of the synonym dictionary specified in the scalar function CONTAINS

S:

Ignores this SQL statement.

Action:

Specify the correct synonym dictionary name in the scalar function CONTAINS.

KFAA34006-E

The synonym dictionary (aa....aa) specified by the scalar function "CONTAINS" cannot be used for a correction search. (M+J+O)

The synonym dictionary specified in the scalar function CONTAINS does not support a correction search. The synonym dictionary created by specifying CASESENSITIVE for the notation-correction option does not support a correction search. <SQLSTATE: 428T8>

aa....aa:

Synonym dictionary name specified in the scalar function CONTAINS

S:

Ignores this SQL statement.

Action:

Take one of the following actions:

Correct the specification of the scalar function CONTAINS to disable the correction search.

Re-create the synonym dictionary that supports a correction search.

KFAA34007-E

The synonym dictionary cannot be used by an HADB server in a multi-node configuration. (M)

A synonym search cannot be performed if the multi-node function is used. <SQLSTATE: 428T9>

S:

Ignores this SQL statement.

Action:

Correct the specification of the scalar function CONTAINS. The following shows a correction example.

Before change:

CONTAINS("DOC",'SYNONYM("TERM","PC")') > 0

After change:

CONTAINS("DOC",'"PC"') > 0 OR
CONTAINS("DOC",'"personal computer"' ) > 0 OR
CONTAINS("DOC",'"microcomputer"') > 0

As shown above, use the logical operator OR to specify all the synonyms to be searched for.

KFAA34008-E

The synonym-dictionary-file aa....aa operation failed. (node number = bb....bb, IP address = cc....cc, server definition = dd....dd, file = ee....ee, errno = ff....ff) (M+J+O)

An error occurred during operation on the synonym dictionary file. <SQLSTATE: 53050>

aa....aa: Name of the system call that caused the error

close: Closing the file

lseek: Moving a pointer on the file

open: Opening the file

read: Reading the file

bb....bb: Node number of the node where the error occurred

If a multi-node configuration is not used, * is displayed.

cc....cc: IP address of the node where the error occurred

If a multi-node configuration is not used, * is displayed.

dd....dd: Server definition operand that specifies the directory containing the file in which the error occurred

adb_syndict_storage_path

adb_syndict_node_storage_path

ee....ee:

Name of the file in which the error occurred

ff....ff:

Error number

S:

Ignores this SQL statement.

Action:

An error occurred during operation of the synonym dictionary file ee....ee under the directory specified by the dd....dd operand. Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the displayed system call name and error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

However, if one of the following conditions is met, also perform the corrective action appropriate for the condition.

If this message is output during execution of an SQL statement with the scalar function CONTAINS (with the synonym-search specification) specified

Check whether a file name that begins with a synonym dictionary name is displayed for ee....ee. If a file name that begins with a synonym dictionary name is displayed, the synonym dictionary file might not exist. Check in the OS documentation for the system call name and error number that are displayed. If the error is caused by the absence of a synonym dictionary file, re-register the synonym dictionary and re-create the synonym dictionary file.

For details about how to re-create a synonym dictionary file, see Steps to take if synonym dictionary files or their storage directory is accidentally deleted in the HADB Setup and Operation Guide.

If the error number is 0

An attempt to allocate memory failed during processing to read the synonym dictionary file. Check for any unnecessary processes. If there are any unnecessary processes, stop or delete them. Then, re-execute the adbsyndict command.

KFAA34009-E

The text index must be rebuilt to access the table. (index ID = "aa....aa") (M+J+O)

Data retrieval by using the text index aa....aa is not available. Alternatively, the text index aa....aa cannot be updated. <SQLSTATE: 53051>

aa....aa:

Index ID

S:

Ignores this SQL statement. If this message is issued during execution of the command, processing terminates.

Action:

Execute the adbidxrebuild command to rebuild the text index aa....aa. Identify the table name and index name that must be specified for executing the adbidxrebuild command from the index ID displayed by aa....aa. For details about how to identify the table name and index name from the index ID, see When identifying the name of a table for which an index is defined from an index ID and When identifying the index name from an index ID in Searching a dictionary table in the HADB Setup and Operation Guide.

Note

If you upgrade the HADB server to version 04-00 or later, text indexes defined in version 03-06 (text indexes with text-index-word-context search specification) cannot be used for a search. Note also that those text indexes cannot be updated. To allow the text indexes to be searched and updated, you need to rebuild them.

2.2 Messages from KFAA40000 to KFAA49999

KFAA40000-E

The HADB server terminated abnormally because corrupted management information was detected in the area of memory used by HADB. (information 1 = aa....aa, information 2 = bb....bb) Save troubleshooting information by the "adbinfoget" command, and then contact customer service. (M)

Management information within a memory area has been corrupted. Therefore, the HADB server is terminated abnormally.

aa....aa:

Information for investigating memory corruption 1

bb....bb:

Information for investigating memory corruption 2

S:

Terminates the HADB server abnormally.

Action:

If this message was output to the server message log file

Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If this message was output to the client message log file

Make a backup of the client message log file, and then contact the customer support center.

KFAA40001-E

Resources for asynchronous I/O execution are insufficient. (M)

Sufficient resources could not be allocated for execution of asynchronous I/O.

S:

Terminates processing.

Action:

There are two possible causes:

The values specified in the server definition's adb_sys_max_users, adb_sys_rthd_num, and adb_sys_uthd_num operands are too large.

Kernel parameter aio-max-nr is too small.

Check the server definition, and then carefully review the values specified for each operand. If a specified value is too large, decrease it.

Next, carefully review the value of kernel parameter aio-max-nr. If the specified value is too small, increase it.

Once you have taken the above corrective actions, start the HADB server with the adbstart command, and then re-execute the processing.

KFAA40002-E

An error occurred during access to the HADB system shared memory. (information = aa....aa) (M)

An error occurred when shared memory was accessed.

aa....aa: Cause of the error

System call error, system call = "bb....bb", errno = cc....cc

A system call error has occurred.

bb....bb: Name of system call in which the error occurred

cc....cc: Error number

Shared memory management table overflow

The amount of shared memory managed by HADB has exceeded the preset limit.

Shared memory address is not 4096 boundery

The top address of the acquired shared memory area does not fall on a 4,096 byte boundary.

The system does not have the capability to use HugePages

The system does not have the capability to use HugePages.

The system can not use HugePages

The system cannot use HugePages.

RLIMIT_MEMLOCK error

The size of shared memory that the HADB server attempted to obtain exceeds the value of kernel parameter RLIMIT_MEMLOCK. Alternatively, the user does not have privileges necessary to obtain the shared memory.

The value of adb_sys_memory_limit in the server definition exceeds the size of shared memory that is available as HugePages

The value specified for the adb_sys_memory_limit operand in the server definition exceeds the size of shared memory to be allocated as HugePages.

S:

Terminates processing.

Action:

Eliminate the error based on the cause of the error aa....aa that is output in the message. Then, re-execute the command.

If the cause of the error indicated by aa....aa is System call error, system call = "bb....bb", errno = cc....cc

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error.

This message might be displayed if a command is executed while the HADB server is starting or terminating. If this is the case, re-execute the command.

If this message is output when executing the adbstart command, even though you responded Y to the KFAA91104-Q message, execute the adbinfosweep command and then execute the adbstart command again.

If shmat is output for the system call name and EINVAL is output for the error number in an environment that uses HugePages, check the server definition's adb_sys_shm_huge_page_size operand. Check whether the value specified for this operand is an even multiple of the page size of HugePages as specified in the OS.

If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If the cause of the error indicated by aa....aa is Shared memory management table overflow

The HADB server has acquired too much shared memory.

There might be too many global buffers. Carefully review the number of server definition adbbuff operands and the values specified for these options.

If the cause of the error indicated by aa....aa is Shared memory address is not 4096 boundery

Specify a multiple of 4,096 for kernel parameter SHMLBA.

If the cause of the error indicated by aa....aa is The system does not have the capability to use HugePages

Specify the group ID of the group for the HugePages user for kernel parameter hugetlb_shm_group.

If the cause of the error indicated by aa....aa is The system can not use HugePages

Carefully review whether the environment can use HugePages, the kernel version, and the appropriate settings.

If aa....aa is RLIMIT_MEMLOCK error

Revise the value of kernel parameter memlock.

If the cause of the error indicated by aa....aa is The value of adb_sys_memory_limit in the server definition exceeds the size of shared memory that is available as HugePages

Change the value specified for the adb_sys_memory_limit operand in the server definition so it is equal to or smaller than value-specified-for-kernel-parameter-vm.nr_hugepages × single-page-size-in-HugePages. Alternatively, increase the value specified for the kernel parameter vm.nr_hugepages.

For details about kernel parameters, see Estimating the kernel parameters in the HADB Setup and Operation Guide.

KFAA40003-E

An error occurred during the creation of a server process. (information = aa....aa) (M)

An error occurred during the creation of a server process.

aa....aa: Cause of the error

System call error, system call = "bb....bb", errno = cc....cc

A system call error has occurred.

bb....bb: Name of system call in which the error occurred

cc....cc: Error number

S:

Terminates processing.

Action:

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA40004-E

The DB directory is already in use. (M)

The DB directory is already in use.

S:

Terminates processing.

Action:

A DB directory cannot be simultaneously accessed from multiple HADB servers. Carefully review the path name of the DB directory specified in the server definition's adb_db_path operand.

KFAA40005-E

There is contention for a locked resource "aa....aa". (M)

There is contention for a locked resource.

aa....aa: Locked resource in contention

SCON: Single connection

DIC: Dictionary

DBAREA: DB area

TABLE: Table

PREPARE TABLE: Pre-processing table

S:

Terminates processing.

Action:

Open the message log file and check the messages that were output after this message. Eliminate the source of the lock, and then retry the operation.

KFAA40006-E

An unavailable locale was specified. (E)

An unsupported locale was specified.

S:

Terminates processing.

Action:

Check whether a locale that cannot be used in the following environment variables is specified.

LANG

LC_ALL

LC_COLLATE

LC_CTYPE

LC_MESSAGES

LC_MONETARY

LC_NUMERIC

LC_TIME

Specify a usable locale in each environment variable. After confirming that the setting of that environment variable is correct, retry the operation.

KFAA40007-E

Memory to execute the HADB system is insufficient. (memory type = aa....aa, request size = bb....bb, thread no = cc....cc, information1 = dd....dd, information2 = ee....ee) (M)

There is not enough memory to run the HADB server, and an attempt to allocate memory failed.

aa....aa: Type of memory that is insufficient

PROCESS: Process common memory used by the HADB server

THREAD: Real thread private memory used by the HADB server

HEAP: Heap memory

SHARE: Shared memory

bb....bb:

Size of memory you attempted to acquire (bytes)

cc....cc:

If aa....aa is PROCESS, HEAP, or SHARE

0 is displayed.

If aa....aa is THREAD

The real thread number is displayed.

dd....dd:

Maintenance information

ee....ee:

Maintenance information

S:

Terminates processing.

Action:

Take appropriate action as described in Memory-related problems in Troubleshooting in the HADB Setup and Operation Guide. Then, re-execute the command or SQL statement.

If the HADB server is running, execute the adbstop command to terminate the HADB server, and then take corrective action.

KFAA40008-E

An error occurred while accessing the core files storage directory. (serverdef = adb_core_path, information = aa....aa) (M)

An error occurred when attempting to access the error information (core file) output directory.

aa....aa: Cause of the error

System call error, system call = "bb....bb", errno = cc....cc

A system call error has occurred.

bb....bb: Name of system call in which the error occurred

cc....cc: Error number

NOT EXIST

The directory specified in the adb_core_path operand in the server definition does not exist.

INVALID PATH FORMAT

The specification format of the directory path specified in the adb_core_path operand in the server definition is invalid.

LENGTH ERROR

The path of the directory specified in the adb_core_path operand in the server definition is too long.

INVALID LETTER

An invalid character is specified in the adb_core_path operand in the server definition.

NO PERMISSION

No permission has been granted to access the directory specified in the adb_core_path server definition operand.

S:

Terminates processing.

Action:

Eliminate the error based on the cause of the error aa....aa that is output in the message.

If aa....aa is System call error, system call = "bb....bb", errno = cc....cc

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If aa....aa is NOT EXIST

Correct the adb_core_path operand specification or create the directory specified in the adb_core_path operand.

If aa....aa is INVALID PATH FORMAT, LENGTH ERROR, or INVALID LETTER

Correct the path name specified in the adb_core_path operand.

If aa....aa is NO PERMISSION

Specify a directory that the HADB administrator is authorized to access (read, write, and execute) in the adb_core_path operand or grant access permissions (read, write, and execute) to the HADB administrator by executing the chmod OS command on the directory specified in the adb_core_path operand.

KFAA40009-E

An error occurred during the creation of a real thread. (number of requests = aaaa, number of created real threads = bbbb) (M)

An error occurred during creation of a real thread.

aaaa:

Number of real threads that needed to be created

bbbb:

Number of real threads that were created

S:

Terminates processing.

Action:

Using the following procedure, carefully review all kernel parameters, and then re-execute:

Using the OS's ulimit -u command, carefully review whether the value specified for nproc is sufficient.

If the value specified for nproc is sufficient and an error still occurs, carefully review the value specified for threads-max.

KFAA40010-E

The aa....aa real threads were forcibly terminated during processing. (M)

A real thread has been forced to terminate during processing.

aa....aa:

Type of real thread

S:

Continues processing.

KFAA40011-E

Commands cannot be executed on kernel versions not supported by HADB. (HADB supported kernel versions = "aa....aa" or later, execution environment kernel versions = "bb....bb") (E)

Commands cannot be executed on kernel versions that are not supported by HADB.

aa....aa:

Kernel version required by HADB

bb....bb:

Kernel version used in the command execution environment

S:

Terminates processing.

Action:

Upgrade the OS to a kernel version that is supported by HADB.

KFAA40012-I

HADB system shared memory was acquired. (shmid = aa....aa, sysid = bb....bb) (M)

The shared memory was acquired.

aa....aa:

Identifier of the shared memory segment

bb....bb:

Sequence number assigned to the shared memory that the HADB server is using

S:

Continues processing.

KFAA40013-E

An error occurred during a semaphore operation. (information = aa....aa) (M)

An error occurred during semaphore operation.

aa....aa: Cause of the error

System call error, system call = "bb....bb", errno = cc....cc

A system call error has occurred.

bb....bb: Name of system call in which the error occurred

cc....cc: Error number

S:

Terminates processing.

Action:

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If this message is output when executing the adbstart command, even though you responded Y to the KFAA91104-Q message, execute the adbinfosweep command and then execute the adbstart command again.

If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA40014-I

A HADB dump file was output. (M)

An HADB dump file was output.

S:

Continues processing.

KFAA40015-E

An error occurred while trying to output a HADB dump file. (information = aa....aa) (M)

An attempt to output an HADB dump file resulted in an error.

aa....aa: Cause of the error

write error. errno = bbb: An error occurred during output operations to the HADB dump file.

bbb: Error number

multiple exceptions were detected: Multiple exceptions were detected.

S:

Continues processing.

Action:

If information is write error.errno = bbb, check in the OS documentation for the error number that is displayed, and then eliminate the cause of the error.

If information is multiple exceptions were detected, take the appropriate action based on the message indicating the cause of error that was output immediately prior to this message.

KFAA40016-E

An attempt to open a HADB dump file failed. (information = aa....aa) (M)

An attempt to open an HADB dump file failed.

aa....aa: Cause of the error

open error. errno = bb....bb

bb....bb: Error number

S:

Continues processing.

Action:

Check in the OS documentation for the error number that is displayed, and then eliminate the cause of the error.

KFAA40017-I

HADB system shared memory was attached. (shmid = aa....aa, sysid = bb....bb, address = cc....cc) (M)

Shared memory was attached.

aa....aa:

ID of shared memory segment

bb....bb:

Serial number allocated to shared memory being used by HADB server

cc....cc:

Address attached

S:

Continues processing.

KFAA40018-I

A wait for the release of a locked resource "aa....aa" occurred. (M)

The process of allocating the locked resource was placed in wait status.

aa....aa: Name of locked resource

DIC: Dictionary

DBAREA: DB area

TABLE: Table

PREPARE TABLE: Pre-processing table

S:

Continues processing.

KFAA40019-I

A wait for the release of a locked resource "aa....aa" was resolved. (M)

The process of allocating the locked resource has been released from wait status.

aa....aa: Name of locked resource

DIC: Dictionary

DBAREA: DB area

TABLE: Table

PREPARE TABLE: Pre-processing table

S:

Continues processing.

KFAA40020-W

The number of concurrent connections to the HADB server has reached or exceeded aa....aa% of the maximum number of concurrent connections. (number of connections = bb....bb, cc....cc = dd....dd) (L+M)

The number of connections to the HADB server has reached aa....aa % of the maximum number of concurrent connections.

aa....aa: Output trigger of a warning message regarding the maximum number of concurrent connections (%)

If a client group has not been defined

The value specified for the adb_sys_max_users_wrn_pnt operand in the server definition is displayed.

If a client group has been defined

The value specified for the -w option of the adbcltgrp in the server definition applied to the client group is displayed.

bb....bb: Current number of connections to the HADB server

If a client group has been defined, the number of connections for that client group is displayed.

cc....cc:

One of the following is displayed:

adb_sys_max_users

This is displayed if a client group has not been defined.

adbcltgrp(-g: client group name, -m)

This is displayed if a client group has been defined.

dd....dd: Maximum number of concurrent connections

If a client group has not been defined

The value specified for the adb_sys_max_users operand in the server definition is displayed.

If a client group has been defined

The value specified for the -m option of the adbcltgrp operand in the server definition applied to the client group is displayed.

S:

Continues processing.

Action:

See Checking the application or command processing status in the HADB Setup and Operation Guide, and check whether an application or command has established unauthorized connections.

If this message is frequently output, revise the following values:

If a client group has not been defined

adb_sys_max_users_wrn_pnt operand or adb_sys_max_users operand in the server definition

If a client group has been defined

adbcltgrp operand's -w option or adbcltgrp operand's -m option in the server definition

Once output, this message will not be output again until the number of connections to the HADB server (or that number in the client group if defined) is below the trigger level to reset the warning message output status.

KFAA40021-W

The amount of memory used by the HADB server has reached or exceeded aa....aa% of the maximum amount that can be used by the HADB server. (memory used = bb....bb MB, adb_sys_memory_limit = cc....cc MB) (L+M)

The amount of memory used by the HADB server has reached aa....aa% of the maximum size of memory that the HADB server can use (value specified for the adb_sys_memory_limit operand).

aa....aa: Output trigger of a warning message regarding the amount of memory used by the HADB server (%)

The value specified for the adb_sys_memory_limit_wrn_pnt operand in the server definition is displayed.

bb....bb:

Current memory usage by the HADB server (MB)

cc....cc: Maximum size of memory that the HADB server can use (MB)

The value specified for the adb_sys_memory_limit operand in the server definition is displayed.

S:

Continues processing.

Action:

See Checking the memory usage status for each real thread in the HADB Setup and Operation Guide, and then check the usage of memory.

If this message is frequently output, revise the values specified for the following operands in the server definition:

adb_sys_memory_limit_wrn_pnt

adb_sys_memory_limit

Once output, this message will not be output again until the amount of memory used by the HADB server reaches or drops below the trigger level to reset the warning message output status.

KFAA40022-W

The value specified for the server definition aa....aa contains an error. The specified value bb....bb will be changed to cc....cc. (M)

Because the value specified for the aa....aa operand in the server definition contains an error, the value to be applied in the system will be changed from bb....bb to cc....cc.

aa....aa:

Operand name in the server definition

bb....bb:

Value before the change (value specified for the operand)

cc....cc:

Value after the change (value applied in the system)

S:

Continues processing.

Action:

Take one of the following actions:

If aa....aa is adb_sys_max_users_wrn_pnt

Correct the value specified for the adb_sys_max_users_wrn_pnt operand. Specify the value so that output-trigger-of-a-warning-message-relating-to-the-maximum-number-of-concurrent-connections is equal to or larger than reset-trigger-of-the-warning-message-output-status.

If aa....aa is adb_sys_memory_limit_wrn_pnt

Correct the value specified for the adb_sys_memory_limit_wrn_pnt operand. Specify the value so that output-trigger-of-a-warning-message-relating-to-the-amount-of-memory-used-by-the-HADB-server is equal to or larger than reset-trigger-of-the-warning-message-output-status.

KFAA40023-I

The warning message output status was reset because the number of concurrent connections to the HADB server decreased to aa....aa% or less of the maximum number of concurrent connections. (number of connections = bb....bb, cc....cc = dd....dd) (M)

The number of connections to the HADB server has decreased to aa....aa % or less of the maximum number of concurrent connections. The warning message output status is reset.

aa....aa: Reset trigger of the warning message output status (%)

If a client group has not been defined

The value specified for the adb_sys_max_users_wrn_pnt operand in the server definition is displayed.

If a client group has been defined

The value specified for the -w option of the adbcltgrp operand in the server definition applied to the client group is displayed.

bb....bb: Current number of connections to the HADB server

If a client group has been defined, the number of connections for that client group is displayed.

cc....cc:

One of the following is displayed:

adb_sys_max_users

This is displayed if a client group has not been defined.

adbcltgrp(-g: client group name, -m)

This is displayed if a client group has been defined.

dd....dd: Maximum number of concurrent connections

If a client group has not been defined

The value specified for the adb_sys_max_users operand in the server definition is displayed.

If a client group has been defined

The value specified for the -m option of the adbcltgrp operand in the server definition applied to the client group is displayed.

S:

Continues processing.

KFAA40024-I

The warning message output status was reset because the amount of memory used by the HADB server decreased to aa....aa% or less of the maximum amount that can be used by the HADB server. (memory used = bb....bb MB, adb_sys_memory_limit = cc....cc MB) (M)

The amount of memory used by the HADB server has decreased to aa....aa% or less of the maximum size of memory that the HADB server can use (value specified for the adb_sys_memory_limit operand). The warning message output status is reset.

aa....aa: Reset trigger of the warning message output status (%)

The value specified for the adb_sys_memory_limit_wrn_pnt operand in the server definition is displayed.

bb....bb:

Current memory usage by the HADB server (MB)

cc....cc: Maximum size of memory that the HADB server can use (MB)

The value specified for the adb_sys_memory_limit operand in the server definition is displayed.

S:

Continues processing.

KFAA40025-W

The message log file is in fall-back mode because the disk on which the aa....aa is stored is full. (L+M)

There is not enough free space on the disk where the message log file for the HADB server or HADB client is stored. Therefore, the message log file is placed in fall-back mode.

aa....aa: Message log file that is placed in fall-back mode

server message log: Server message log file

client message log: Client message log file

S:

Continues processing.

Action:

Take one of the following corrective actions:

If aa....aa is server message log

Check the amount of free space on the disk where the server message log file is stored. For details about how to check, see Releasing the message log file from fall-back mode in the HADB Setup and Operation Guide.

In addition, allocate free space of at least twice the value specified for the ADBMSGLOGSIZE environment variable by, for example, deleting unnecessary work files from the disk where the server message log file is stored.

If aa....aa is client message log

Check the amount of free space on the disk in which the client message log file is stored. For details about how to check, see Releasing the message log file from fall-back mode in the HADB Setup and Operation Guide.

In addition, allocate free space of at least twice the value specified for the ADBMSGLOGSIZE environment variable by, for example, deleting unnecessary work files from the disk where the client message log file is stored.

KFAA40026-E

A deadlock was detected. (M)

A deadlock was detected.

S:

Terminates processing.

Action:

After this message is output, the KFAA40005-E message is output, informing that the locked resource to be allocated when a deadlock is detected could not be allocated. Eliminate the cause of the lock, and then re-execute the process.

A deadlock may be detected only if the adb_sys_lck_conflict_behavior operand in the server definition has WAIT specified.

KFAA40203-E

Memory is insufficient for processing. (M)

The HADB server is not able to allocate sufficient process common memory.

S:

Terminates processing.

Action:

Use the procedure below to resolve the shortage of process common memory. Then, re-execute the command.

If necessary, restore the database before re-executing the command. For details, see the corrective action to take when a command terminates abnormally in the manual HADB Command Reference.

Check for any unnecessary processes. If there are any unnecessary processes, shut them down.

If there is not enough process common memory after performing step 1, restart the OS. Then, execute the adbstart command to start the HADB server.

If there is not enough process common memory after performing step 2, change the kernel parameter setting to increase the amount of memory that processes can use. After restarting the OS, execute the adbstart command to start the HADB server.

KFAA40204-E

An error occurred in aa....aa processing on the file bb....bb. (M)

An error occurred in I/O involving a file.

aa....aa: Processing that generated the error

open: An error occurred when opening a file.

read: An error occurred when reading a file.

write: An error occurred when writing to a file.

close: An error occurred when closing a file.

reopen: An error occurred when re-opening a file.

bb....bb:

Name of file or directory where the error occurred

S:

Terminates processing.

Action:

Check the messages that were output before and after this message in the message log file, and eliminate the cause of the error. Then, re-execute the command.

If necessary, restore the database, and then re-execute the command. For details about how to restore the database, see the corrective action to take when a command terminates abnormally in the manual HADB Command Reference.

For details about what action to take for each error cause, see Troubleshooting in the HADB Setup and Operation Guide. If this message is output during command execution, also see Command-related problems in the HADB Setup and Operation Guide.

When no message indicating the cause of the error is output to the message log file, the following factors relating to file bb....bb are possible explanations:

Permissions required for accessing file bb....bb might not have been set up.

The disk area for storing the bb....bb file might be full.

An I/O error might have occurred.

The size of the input data file was changed while data was being imported.

KFAA40205-E

A file I/O error occurred. (reason = aa....aa, func = bb....bb, errno = cc....cc, (dd....dd)) (M)

An error occurred in I/O involving a file.

aa....aa: Reason the error occurred

Details are shown in the following table.

Value of aa....aa

Description

File-lock

The affected file is in use by another program. Wait until the file operations of the other program have terminated, and then retry the operation.

Invalid-parameter

An internal processing conflict was found. Contact the customer support center.

Invalid-path

The following are possible causes:

The path name is invalid. Check for problems with the path name.

An operation such as a delete or update was performed on the file while an application program was executing.

Invalid-permission

The following are possible causes:

The permission (for access) for the specified file is invalid. Carefully review the permissions for possible problems.

The file specified at the write destination is a read-only file. Check whether the write destination file is correct.

A file already opened by another application program was specified.

File-format

The following are possible causes:

The specified file format differs from the actual file format.

If the row length (length to the linefeed) actually input from a file is longer than the input file row length calculated from the specified option values, this error might result.

Suppose that the file format of the input data file is CSV format and the -r option (column structure information file) is specified for the adbimport command, the maximum value for field data number can be specified for this option. In this case, the maximum field data number specified for the column structure information option is added to the input file row length calculated from the option specification.

The format of the file that specifies the table name or index identifier is invalid.

File-sequence

The multivolume file sequence is invalid.

Invalid-device

The entry type (attribute) of the specified file is invalid. If the entry type can be identified, it is displayed as a single alphabetic character in parentheses.

Carefully review whether the locations where the directory name and file name were specified are correct.

No-file

There is no file to read. Another possibility is that the file was deleted during writing.

No-space

There is not enough space in the file to be written to.

No swap-file

There is no swap file for the multivolume file. Carefully review the capacity. Alternatively, specify a multivolume file.

Same-file

The file specified as the multivolume file is the same as the file just processed. Another possibility is that an attempt was made, when writing to a multivolume file, to overwrite the current volume onto a previous volume.

Unmatch-entry

The entry in the header does not match the specification of the control information file, for a file that has a header. The name of the entry that does not match is displayed in parentheses.

no-data

The quantity of data items that were recorded at the synchronization point does not exist in the specified file.

bb....bb: Name of system call in which the error occurred

The name of the system call is displayed when the OS detects an error. Otherwise, *** is displayed.

cc....cc:

Error number

dd....dd:

The source file name and row number where the failure was detected.

S:

Terminates processing.

Action:

Based on the reason the error was generated, the system call name, and the error number, eliminate the cause of the error. Then, re-execute the command.

If necessary, restore the database before re-executing the command. For details about how to restore the database, see the corrective action to take when a command terminates abnormally in the manual HADB Command Reference.

For details about what action to take for each error cause, see Troubleshooting in the HADB Setup and Operation Guide. If this message is output during command execution, also see Command-related problems in the HADB Setup and Operation Guide.

If using the multi-node function:

For details about the corrective action to take if a running command is interrupted and the table to be processed becomes non-updatable, see the following: Releasing a base table from non-updatable status (when the multi-node function is being used) in Base table operations (when the multi-node function is being used) in the HADB Setup and Operation Guide.

KFAA40207-E

An error occurred in aaaa processing. (func = bb....bb, return code = cc....cc) (M)

An error occurred during aaaa processing.

aaaa:

Program name

bb....bb:

Name of function where the error occurred

cc....cc:

Error code of function where the error occurred

S:

Terminates processing.

Action:

Take the corrective action that corresponds to the error code output to cc....cc, as indicated in the following table.

Check whether the database needs to be restored before re-executing the command. For details about how to restore the database, see the corrective action to take when a command terminates abnormally in the manual HADB Command Reference.

Error code

Reason the error occurred

Corrective action to take

-202

Memory is insufficient.

Use the following procedure to resolve the shortage of process common memory:

Check for any unnecessary processes. If there are any unnecessary processes, shut them down.

If there is not enough memory after performing step 1, restart the OS. Then, execute the adbstart command to start the HADB server.

If there is not enough memory after performing step 2, change the kernel parameter setting to increase the amount of memory that processes can use. After restarting the OS, execute the adbstart command to start the HADB server.

-210

-230

There is not enough available space in the work directory that stores temporary work files.

The corrective action to take differs depending on whether the -w option was specified when the command was executed.

If the -w option was specified

Specify a directory that has sufficient free disk space allocated, and then retry the operation.

If the -w option was not specified

Specify a directory that has sufficient free disk space allocated, using the -w option, and then retry the operation.

Alternatively, allocate sufficient free space on the disk that stores the DB directory, and then retry the operation without specifying the -w option.

For details about the corrective action to take, also see Command-related problems in the HADB Setup and Operation Guide.

-290

The sort buffer is not big enough.

Take one of the following actions:

Increase the value specified in import option adb_import_sort_buff_size.

Increase the value specified in index rebuild option adb_idxrebuild_sort_buff_size.

Increase the value specified in merge chunk option adb_mergechunk_sort_buff_size.

Increase the value specified in unarchived chunk optionadb_unarcv_sort_buff_size.

Other error codes

An error occurred during sort processing.

Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA40208-E

An error occurred in aaaa processing. (func = bb....bb, errno = cc....cc) (M)

An error occurred during aaaa processing.

aaaa:

Program name

bb....bb:

Name of the function where the error occurred

cc....cc:

Error code of the function where the error occurred

S:

Terminates processing.

Action:

Take the corrective action according to the error code indicated by cc....cc.

Before re-executing the command, check whether the database needs to be restored. For details about how to restore the database, see the corrective action to take when a command terminates abnormally in the manual HADB Command Reference.

Error code

Cause of the error

Corrective action to take

-202

Memory is insufficient.

Use the following procedure to resolve the shortage of memory.

Check for any unnecessary processes. If there are any unnecessary processes, stop them.

If there is still not enough memory after performing step 1, restart the OS. Then, execute the adbstart command to start the HADB server.

If there is still not enough memory after performing step 2, change the kernel parameter setting to increase the maximum amount of memory that processes can use. After restarting the OS, execute the adbstart command to start the HADB server.

-210

-230

There is not enough available space in the work directory in which to store temporary work files.

The corrective action to take differs depending on whether the -w option was specified when the command was executed.

If the -w option was specified

Specify a directory that has sufficient free disk space allocated, and then retry the operation.

If the -w option was not specified

Use the -w option to specify a directory that has sufficient free disk space allocated, and then retry the operation.

Alternatively, allocate sufficient free space on the disk where the DB directory is stored, and then retry the operation without specifying the -w option.

-290

The sort buffer size is insufficient.

Take one of the following actions:

Increase the value specified for the import option adb_import_sort_buff_size.

Increase the value specified for the index rebuild option adb_idxrebuild_sort_buff_size.

Increase the value specified for the merge chunk option adb_mergechunk_sort_buff_size.

Increase the value specified for the unarchived chunk option adb_unarcv_sort_buff_size.

Error codes other than the above

An error occurred during sort processing.

Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA40212-E

Memory is insufficient. (size of the insufficient memory = aa....aa, part number = bb....bb, part code = cc....cc) (M)

A memory shortage occurred.

aa....aa:

Size of the attempted allocation of memory

bb....bb:

Maintenance information 1

cc....cc:

Maintenance information 2

S:

Terminates processing.

Action:

Refer to the corrective action of the KFAA40007-E message.

If necessary, restore the database before re-executing the command. For details about how to restore the database, see the corrective action to take when a command terminates abnormally in the manual HADB Command Reference.

When this message is output, also consider the following corrective actions:

Check whether the memory of the environment to be executed can allocate the amount of memory indicated by aa....aa.

If this message is output during execution of the adbimport command, check whether the defined length of the column of the table to be imported is longer than the maximum length of data to be stored. If it is, consider reducing the defined length of the column.

KFAA40213-E

An attempt to perform aa....aa processing for the file bb....bb has failed. (M)

An attempt to delete a file failed.

aa....aa: Processing that failed to execute

unlink: Deletion processing

bb....bb:

File name

S:

Terminates processing.

Action:

The file has not been deleted. If the file is not necessary, delete it manually.

KFAA40214-E

An error occurred in a system call. (func = aa....aa, errno = bb....bb) (M)

A system call error occurred.

aa....aa:

Name of system call in which the error occurred

bb....bb:

Error number

S:

Terminates processing.

Action:

If the system call name (function) is malloc, the HADB server is not able to allocate sufficient process common memory. Use the following procedure to resolve a shortage of process common memory:

Check for any unnecessary processes. If there are any unnecessary processes, shut them down.

If there is not enough process common memory after performing step 1, restart the OS. Then, execute the adbstart command to start the HADB server.

If there is not enough process common memory after performing step 2, change the kernel parameter setting to increase the amount of memory that processes can use. After restarting the OS, execute the adbstart command to start the HADB server.

If other error messages are also displayed, check those messages and eliminate the cause of the error. Then, re-execute the command.

For details about the corrective action to take, also see Command-related problems in the HADB Setup and Operation Guide.

If necessary, restore the database before re-executing the command. For details about how to restore the database, see the corrective action to take when a command terminates abnormally in the manual HADB Command Reference.

KFAA40215-E

An error occurred during a statistics log file operation. (file name = aa....aa, system call = bb....bb, reason = cc....cc) (M)

An error occurred during statistics log file operation.

aa....aa:

Name of the statistics log file in which the error occurred

bb....bb:

System call name

cc....cc:

Cause of the error

S:

Terminates processing.

Action:

Take the corrective action for the cause of the error indicated by cc....cc.

Cause of the error indicated by cc....cc

Description

Action

no permission

The user does not have privileges for the statistics log file and the storage directory of the statistics log file.

Grant the following privileges to the HADB administrator. Then, start the HADB server.

Statistics log file

Grant write privileges to the HADB administrator.

Statistics log file storage directory

Grant read, write, and execution privileges to the HADB administrator.

not found directory

The storage directory of the statistics log file does not exist.

Make sure that the path name specified for the adb_sta_log_path operand in the server definition is correct.

If the storage directory of the statistics log file does not exist, create that directory. Then, start the HADB server.

not directory

The storage directory of the statistics log file is not a directory.

Specify a directory for the adb_sta_log_path operand in the server definition.

Then, start the HADB server.

KFAA40216-E

An error occurred during access to the storage directory of the statistics log file. (serverdef = adb_sta_log_path, information = aa....aa) (M)

An error occurred during access to the storage directory of the statistics log file.

aa....aa:

Cause of the error

S:

Terminates processing.

Action:

Take the corrective action for the cause of the error displayed for aa....aa.

Cause of the error displayed for aa....aa

Description

Action

invalid path format

The specification format of the path specified for the adb_sta_log_path operand in the server definition is invalid.

Correct the path name specified for the adb_sta_log_path operand in the server definition. Then, start the HADB server.

length error

The path specified for the adb_sta_log_path operand in the server definition is too long.

invalid letter

Invalid characters are specified for the adb_sta_log_path operand in the server definition.

KFAA40220-E

An error occurred during a statistics log file operation. (file name = aa....aa, system call = bb....bb, errno = cc....cc) (M)

An error occurred when a statistics log file was manipulated.

aa....aa:

File name

bb....bb:

System call name

cc....cc:

Error number

S:

Terminates processing.

Action:

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error.

If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA40289-E

To execute the bb....bb command, you need at least aa....aa threads. (E+M)

At least aa....aa threads are required to execute the bb....bb command.

aa....aa:

Minimum number of threads needed to execute a command

bb....bb:

Command name

S:

Terminates processing.

Action:

If you omit the options shown in the following table when specifying the corresponding commands, the value specified for the adb_sql_exe_max_rthd_num operand in the server definition is assumed as the number of threads used by the commands. The commands, however, cannot be executed, because the value specified for the adb_sql_exe_max_rthd_num operand is less than the minimum number of threads required by each command. Specify a value equal to or greater than the minimum number of threads required (a value equal to or greater than aa....aa) for the command options shown in the following table, and execute the command again.

Command name

Command option name

Minimum number of threads required

adbimport

adb_import_rthd_num

2

adbidxrebuild

adb_idxrebuild_rthd_num

3

adbgetcst

adb_getcst_rthd_num

2

adbexport

adb_export_rthd_num

3

adbmergechunk

adb_mergechunk_rthd_num

3

adbarchivechunk

adb_arcv_rthd_num

3

adbunarchivechunk

adb_unarcv_rthd_num

2

KFAA40290-E

The number of threads that can be used is insufficient. (required no. of threads = aaaa, available no. of threads = bbbb, command = cc....cc) (E+M)

The number of threads is insufficient to execute the cc....cc command.

aaaa:

Number of threads to be used by the command cc....cc

bbbb:

Available number of processing real threads

cc....cc:

Name of the command for which the number of threads is insufficient

S:

Terminates processing.

Action:

The number specified for the option# of the command cc....cc (the number specified as the number of threads to be used for the command) has exceeded either of the following specified values.

The value specified for the adb_sys_rthd_num operand in the server definition

The value specified for the -r option of the adbcltgrp operand in the server definition (the value specification of the command group)

In such a case, take one of the following corrective actions:

For the option# of the command cc....cc, set a smaller number of threads to be used for command execution.

Specify a larger value for the adb_sys_rthd_num operand or for the -r option of the adbcltgrp operand in the server definition.

Make sure that number-of-threads-to-be-used-by-command is equal to or less than available-number-of-processing-real-threads. Once this is done, re-execute the command.

#

The following tables shows the relevant option of each command and the minimum number of threads required for command execution.

Command name

Command option name

Minimum number of threads required

adbimport

adb_import_rthd_num

2

adbidxrebuild

adb_idxrebuild_rthd_num

3

adbgetcst

adb_getcst_rthd_num

2

adbexport

adb_export_rthd_num

3

adbmergechunk

adb_mergechunk_rthd_num

3

adbarchivechunk

adb_arcv_rthd_num

3

adbunarchivechunk

adb_unarcv_rthd_num

2

KFAA40291-W

A value larger than aaaa is specified for a value in the server definition adb_cmd_rthd_num. The specified value is ignored and the value of aaaa to is changed the assumed value of the number of processing real threads used by the command, and then processing will continue. (adb_cmd_rthd_num = bbbb, adb_sys_rthd_num = cccc) (M)

A value has been specified for the server definition's adb_cmd_rthd_num operand that is larger than the value calculated using the following formula.

Formula

(value-of-server-definition-adb_sys_rthd_num-operand - 2) ÷ 2

The system ignores the specification of the adb_cmd_rthd_num operand, changes the provisional value for number of processing real threads a command uses into the value calculated using the above formula, and then continues processing.

When the value specified for the adb_sys_rthd_num operand is 3 or less, the provisional value for number of processing real threads a command will use changes to 1.

aaaa:

Value found with the above formula

bbbb:

Provisional value for number of processing real threads a command will use specified in the adb_cmd_rthd_num operand

cccc:

Number of processing real threads specified in the adb_sys_rthd_num operand

S:

Continues processing.

Action:

Change the value of the adb_cmd_rthd_num operand to be no more than the value calculated in the formula above.

KFAA40292-E

An error occurred in aa....aa processing. (func = bb....bb, return code = cc....cc, file = dd....dd) (M)

An error occurred during file compression or decompression processing.

aa....aa: Processing in which the error occurred

compression: File compression processing

decompression: File decompression processing

bb....bb:

Name of the zlib function where the error occurred

cc....cc:

Return value of the zlib function

dd....dd:

Path name of the file in which the error occurred

S:

Terminates processing.

Action:

If cc....cc is 2:

A preset dictionary request error occurred during file decompression processing. Files compressed by using a preset dictionary cannot be decompressed. Use a file that has been compressed without using a preset dictionary.

If cc....cc is not 2:

If the adbimport command caused the error

If aa....aa is decompression, perform the following procedure.

1. Check whether the OS's gzip command or the adbexport command that compressed dd....dd terminated abnormally.

2. If the command terminated abnormally, take the corrective action for the cause, and then re-execute the OS's gzip command or the adbexport command.

3. Re-execute the adbimport command.

If aa....aa is not decompression, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If a command other than the adbimport command caused the error

Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA40293-E

A memory shortage occurred in aa....aa processing. (func = bb....bb, return code = cc....cc, file = dd....dd) (M)

A memory shortage occurred during file compression or decompression processing.

aa....aa: Processing in which the error occurred

compression: File compression processing

decompression: File decompression processing

bb....bb:

Name of the zlib function where the error occurred

cc....cc:

Maintenance information

dd....dd:

Path name of the file in which the error occurred

S:

Terminates processing.

Action:

Take one of the following actions:

Make sure that unnecessary processes do not exist. If there are any unnecessary processes, shut them down, and then execute the command.

If there is still not enough memory after performing step 1, restart the OS. Then, start the HADB server, and then execute the command.

If there is still not enough memory after performing step 2, increase the value specified for the kernel parameter that sets the maximum amount of memory that processes can use, and then restart the OS. Then, start the HADB server, and then execute the command.

KFAA41000-W

The value of the aa option in the client group (bb....bb) will be changed from cc....cc to dd....dd. (M)

The value specified for the aa option of the client group bb....bb will be changed from cc....cc to dd....dd.

aa:

Option name of the adbcltgrp operand in the server definition

bb....bb:

Client group name or command group name

cc....cc:

Value specified for the aa option of the adbcltgrp operand in the server definition

dd....dd:

Value after change (value assumed by the HADB server)

S:

Continues processing.

Action:

If aa is -m

Revise the value specified for the -m option of the adbcltgrp operand in the server definition. If the value of the -m option is greater than the value obtained by the following calculation, change the value of the option to be equal to or smaller than the calculated value.

If aa is -r

Revise the value specified for the -r option of the adbcltgrp operand in the server definition. If the value of the -r option is greater than the value obtained by the following calculation, change the value of the option to be equal to or smaller than the calculated value.

If aa is -w

Revise the value specified for the -w option of the adbcltgrp operand in the server definition. Specify the value so that output-trigger-of-a-warning-message-relating-to-the-maximum-number-of-concurrent-connections-for-the-specified-client-group is equal to or larger than reset-trigger-of-the-warning-message-output-status.

For details about the value specification for each option, see the description of the adbcltgrp operand in Operands and options related to the client-group facility (command format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide.

KFAA41001-E

The operation failed. (operation = aa....aa, errno = bb....bb) (M)

The aa....aa operation failed.

aa....aa: Name of the system call that caused the error

popen

This is called when the monshow command is executed to monitor the status of HA Monitor.

bb....bb:

Error number

S:

Terminates this transaction.

Action:

In the OS documentation, check the system call name indicated by aa....aa and the error number indicated by bb....bb, and then eliminate the cause of the error.

KFAA41100-W

The value of adb_sql_exe_max_rthd_num is invalid. The value must be less than or equal to the value of adb_sys_rthd_num. The adb_sql_exe_max_rthd_num value will be changed to the value of adb_sys_rthd_num. (adb_sql_exe_max_rthd_num = aaaa, adb_sys_rthd_num = bbbb) (M)

A value was specified for the maximum number of SQL processing real threads that is larger than the number of processing real threads. The specified value is ignored, and processing continues using the value specified for the number of processing real threads as the maximum number of SQL processing real threads.

aaaa:

The maximum number of SQL processing real threads specified in the server definition's adb_sql_exe_max_rthd_num operand

bbbb:

The number of processing real threads specified in the server definition's adb_sys_rthd_num operand

S:

Continues processing.

Action:

Carefully review the specified values so that the value specified for the server definition's adb_sql_exe_max_rthd_num operand is less than or equal to the value of the adb_sys_rthd_num operand.

For details about the operands, see the topic Operands related to performance (set format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide.

KFAA41101-W

The value of adb_sql_exe_hashgrp_area_size is invalid. A value from 1 to 3 cannot be specified. The value of adb_sql_exe_hashgrp_area_size will be set to 4. (adb_sql_exe_hashgrp_area_size = b) (M)

A value smaller than 4 (between 1 and 3) was specified for the hash group area size. The specified value is ignored, and the hash group area size is changed to 4.

b:

Value of the hash group area size specified in the server definition's adb_sql_exe_hashgrp_area_size operand.

S:

Continues processing.

Action:

Carefully review the setting so that the specified value of the server definition's or client definition's adb_sql_exe_hashgrp_area_size operand is either 0 or in the range 4-1,000,000.

For details about the adb_sql_exe_hashgrp_area_size operand, see the following: If the operand is in the server definition, see the topic Operands related to performance (set format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide. If the operand is in the client definition, see the topic Operands related to performance in Contents of operands in the client definition in Designing Client Definitions in the HADB Application Development Guide.

KFAA41103-W

The value of aa....aa in the client definition is invalid. The value must be less than or equal to the value specified in the server definition. The value of aa....aa in the client definition will be changed to the value specified in the server definition. (client definition = bb....bb, server definition = cc....cc) (M)

For the aa....aa operand, the value specified in the client definition is being ignored and the value specified in the server definition is being used, because the value specified in the client definition is greater than the value specified in the server definition.

aa....aa: Name of the target operand:

adb_sql_exe_max_rthd_num: Maximum number of SQL processing real threads

adb_sql_exe_hashtbl_area_size: Size of the hash table area

adb_sql_exe_hashflt_area_size: Size of the hash filter area

bb....bb:

Value of the aa....aa operand specified in the client definition

cc....cc:

Value of the aa....aa operand specified in the server definition

S:

Continues processing.

Action:

Evaluate the aa....aa operand values, and set the value specified in the client definition to be equal to or less than the value specified in the server definition.

For details about the target operand, see the following: If the operand is in the server definition, see the topic Operands related to performance (set format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide. If the operand is in the client definition, see the topic Operands related to performance in Contents of operands in the client definition in Designing Client Definitions in the HADB Application Development Guide.

KFAA41105-W

The value of adb_sql_exe_max_rthd_num in the client definition must be less than or equal to the maximum number of processing real threads usable in SQL execution. The value of adb_sql_exe_max_rthd_num in the client definition will be changed to aa....aa. (client definition = bb....bb) (M)

The value specified for the adb_sql_exe_max_rthd_num operand in the client definition is greater than the maximum number of processing real threads that can be used during execution of the SQL statement. As a result, the value specified for the client definition will be invalidated and changed to aa....aa.

aa....aa:

Value of the adb_sql_exe_max_rthd_num operand in the client definition after change

bb....bb:

Value specified for the adb_sql_exe_max_rthd_num operand in the client definition

S:

Continues processing.

Action:

Review the value specified for the adb_sql_exe_max_rthd_num operand in the client definition to be equal to or smaller than the maximum number of processing real threads that can be used by a HADB client.

For details about the adb_sql_exe_max_rthd_num operand in the client definition, see the topic Operands related to performance in Contents of operands in the client definition in Designing Client Definitions in the HADB Application Development Guide.

If the client-group facility is used, the maximum number of processing real threads that can be used by a HADB client varies depending on whether the HADB client belongs to a group. For details, see Points to consider when specifying the number of processing real threads for a group in the HADB Setup and Operation Guide.

KFAA41106-W

The value specified by the aa....aa method of the JDBC driver was out of range. The value will be changed to a system-specified value. (before the change = bb....bb, after the change = cc....cc) (M)

The value bb....bb specified for the aa....aa method of the JDBC driver is invalidated, and then the value cc....cc is applied.

aa....aa:

Executed method name

bb....bb:

Value specified for the aa....aa method

cc....cc:

Applied value

S:

Continues processing.

Action:

A value outside the specifiable range is specified for the aa....aa method. Correct the specified value of the aa....aa method. For details about the values that can be specified for the aa....aa method, see the description of the following operands in Operands related to performance in the HADB Application Development Guide:

adb_sql_exe_max_rthd_num

adb_sql_exe_hashtbl_area_size

adb_sql_exe_hashflt_area_size

KFAA41200-E

This buffer is undefined. (DB area = aa....aa, page type = b) (M)

This global buffer has not been defined.

aa....aa:

Affected DB area name

b: Page type

d: Directory page

w: Work table page

t: Data page

h: Upper page

f: Leaf page

r: Row ID directory page

s: Row ID list page

a: Range index page

i: String control page

p: Position control page

S:

Invalidates this transaction.

Action:

If the affected DB area aa....aa is not specified in the server definition's adbbuff operand

Allocate a new global buffer to the affected DB area aa....aa. When you do so, specify a value of 1 or more in the -p option.

If the affected DB area aa....aa is specified in the server definition's adbbuff operand

Take corrective action as described in the following table:

Page type displayed for b

Corrective action

-a option specified

-a option omitted

The page type displayed is a.

Specify 1 or a greater value in the -a option of the adbbuff operand.

Specify 1 or a greater value in the -p option of the adbbuff operand.

The page type displayed is not a.

Specify 1 or a greater value in the -p option of the adbbuff operand.

KFAA41201-E

This buffer is insufficient. (DB area = aa....aa, page type = b, buffer type = cc....cc) (M)

Processing cannot continue because there are not enough global buffer sectors.

aa....aa:

Affected DB area name

b: Page type

d: Directory page

w: Work table page

t: Data page

h: Upper page

f: Leaf page

r: Row ID directory page

s: Row ID list page

a: Range index page

cc....cc: Buffer type

COMMAND: Buffer for commands

GLOBAL WORK: Global buffer for global work tables

LOCAL WORK: Buffer for local work tables

GLOBAL: Global buffer

S:

Invalidates this transaction.

Action:

The corrective action to take differs depending on whether the server definition's adbbuff operand is defined.

If no adbbuff operand that includes the DB area name output in aa....aa is defined

Define the adbbuff operand. If the -p option specification was omitted, specify a value in the -p option that is larger than the default value.

If an adbbuff operand that includes the DB area name output in aa....aa is defined

Take corrective action as described in the following table:

Type of buffer output in cc....cc

Corrective action

COMMAND

If this message was output while the adbimport command was executing

Increase the value specified in the import option adb_import_buff_blk_num.

If this message was output while the adbidxrebuild command was executing

Increase the value specified in the index rebuild option adb_idxrebuild_buff_blk_num.

If this message was output while the adbmergechunk command was executing

Increase the value specified in the merge chunk option adb_mergechunk_buff_blk_num.

GLOBAL WORK

Increase the value in the server definition's adb_dbbuff_wrktbl_glb_blk_num operand.

LOCAL WORK

Increase the value specified in the client definition's adb_dbbuff_wrktbl_clt_blk_num operand.

If this message was output while the adbexport command was executing, increase the value specified in the export option adb_export_wrktbl_blk_num.

GLOBAL

The page type displayed for b is a.

-a option specified.

Increase the value specified in the -a option of the adbbuff operand.

-a option omitted.

Increase the value specified in the -p option of the adbbuff operand.

The page type displayed for b is not a.

Increase the value specified in the -p option of the adbbuff operand.

KFAA41202-E

Processing cannot continue because the global buffer is busy. (DB area = aa....aa, buffer = bb....bb) (M)

Processing cannot continue because the load on the global buffer bb....bb allocated to the DB area aa....aa is too high.

aa....aa:

DB area name

bb....bb:

Global buffer name

S:

Invalidates this transaction.

Action:

Take one of the following corrective actions:

Re-execute the processing after any application programs that are causing a high load on the global buffer bb....bb have terminated.

Cancel any application programs causing a high load on the global buffer bb....bb, and then re-execute the processing.

One of the application programs executing an SQL statement on a table or index stored in the DB area aa....aa might be causing a high load on the global buffer bb....bb.

KFAA41205-E

The operation on the file or directory "aa....aa" failed. (operation = bb....bb, errno = cc....cc) (M)

The operation on the file or directory indicated by aa....aa failed.

aa....aa:

File name or directory name

An asterisk (*) or asterisks (***) might be displayed.

bb....bb:

Name of the system call in which the error occurred

cc....cc:

Error number

S:

Terminates this transaction.

Action:

Take one of the following corrective actions:

▪ If a file name, directory name, or three asterisks (***) are displayed in place of aa....aa:

Check in the OS documentation for the system call name displayed for bb....bb and the error number displayed in place of cc....cc, and then eliminate the cause of the error. If an error occurred in a symbolic link file, check the link target files in addition to that file.

If this message is output when starting the HADB server in a multi-node configuration or when adding a worker node to a multi-node configuration

Check whether an error occurred during open processing of the DB area file.

The file name displayed for aa....aa is the symbolic link name for the DB area file.

The system call name displayed for bb....bb is open.

The error number displayed for cc....cc is ENOENT.

If all the above conditions exist, an error occurred during open processing of the DB area file. In this case, the DB directory of the node that output this message is an invalid status. If this message is output when starting the HADB server in a multi-node configuration, execute the adbinit command on the secondary node where this message was output to recreate the DB directory, and then start the multi-node configuration HADB server normally. If this message appears when adding a worker node to a multi-node configuration, execute the adbinit command on the worker node where this message appears to recreate the DB directory, then start the HADB server on the worker node with the adbstart command and add the worker node to the multi-node configuration. For details, see the following section in the HADB Setup and Operation Guide.

Adding, deleting, or expanding data DB areas (when the multi-node function is being used)

If you cannot start a multi-node configuration HADB server normally in Problems related to starting or stopping a multi-node configuration HADB server

If this message is output when you use the table function derived table or access an archivable multi-chunk table

Check the existence of the file or directory indicated by aa....aa.

If this message is output during execution of a command

See Problems related to commands in the HADB Setup and Operation Guide.

If the file name displayed in aa....aa is a cache file or a reuse information file

In addition to the cache file or reuse information file displayed in aa....aa, also check the cache file storage directory and the file system status.

If the system call name displayed in bb....bb is write or aio_write, and the error number displayed in cc....cc is 0

There is a possibility that the writing has been interrupted by aa....aa, so re-execute the operation. As a result, if the same error occurs, it is due to insufficient disk space, so make sure there is enough free space in the area where aa....aa is located.

If the error number displayed for cc....cc is EIO

An error occurred in I/O involving a file. If a file name has been output, make sure that you can access the file system or disk where the file is stored.

If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

▪ If an asterisk (*) is displayed in place of aa....aa:

If this message was issued while the adbimport command was executing

Specify a smaller value in the import option adb_import_buff_blk_num.

If this message was issued while the adbidxrebuild command was executing

Specify a smaller value in the index rebuild option adb_idxrebuild_buff_blk_num.

If this message was issued while the adbexport command was executing

Specify a smaller value in the export option adb_export_wrktbl_blk_num.

If this message was issued while the adbmergechunk command was executing

Specify a smaller value in the merge chunk option adb_mergechunk_buff_blk_num.

If this message was issued while the adbunarchivechunk command was executing

Specify a smaller value in the unarchived chunk option adb_unarcv_buff_blk_num.

If this message was issued while an SQL statement was executing

Specify a smaller value in the client definition's adb_dbbuff_wrktbl_clt_blk_num operand.

KFAA41206-I

An operation on file "aa....aa" failed. (operation = bb....bb, errno = cc....cc) (M)

An operation on the file aa....aa failed.

aa....aa:

File name

bb....bb:

Name of system call in which the error occurred

cc....cc:

Error number

S:

Continues processing.

Action:

If an error message is output immediately after this message, check in the OS documentation for the system call name displayed for bb....bb and the error number displayed for cc....cc, and then eliminate the cause of the error.

If the error number output for cc....cc is EIO, a file I/O error occurred. If a file name has been output for aa....aa, check whether you can access the file system or disk where the file is stored. If this error occurs repeatedly, a hardware failure might have occurred. Check the hardware status.

If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA41207-E

An operation on file "aa....aa" failed. (operation = bb....bb, reason = "cc....cc") (M)

An operation on the file aa....aa failed.

aa....aa:

File name

bb....bb:

Failed operation

aio_read: Asynchronous file read

aio_write: Asynchronous file write

cc....cc:

Cause of the error

too short

Asynchronous input/output processing of data that was shorter than the requested read size or write size was performed.

S:

Terminates this transaction.

Action:

Re-execute the transaction. If this error occurs repeatedly, a hardware failure might have occurred. Check the hardware status.

If you cannot determine the corrective action to take, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA41208-W

An operation on file "aa....aa" failed. (operation = bb....bb, reason = "cc....cc") (M)

An operation on the file aa....aa failed.

aa....aa:

File name

bb....bb:

Failed operation

aio_read: Asynchronous file read

aio_write: Asynchronous file write

cc....cc:

Cause of the error

too short

Asynchronous input/output processing of data that was shorter than the requested read size or write size was performed.

S:

Continues processing.

Action:

If this error occurs repeatedly, a hardware failure might have occurred. Check the hardware status.

KFAA41210-E

The number of user logfiles exceeded the maximum. (M)

The number of user log files has reached its upper limit.

S:

Invalidates this transaction.

Action:

See the description of the expression that calculates the number of user log files in Determining the number of user log files in the HADB Setup and Operation Guide. Then, take one of the following actions so that the conditions in the expression are satisfied:

Increase the value of the adb_log_usrfile_num operand in the server definition (increase the number of user log files).

Decrease the number of real threads that perform update processing.

To decrease the number of real threads that perform update processing, decrease the values of the options in the expression that calculates the number of user log files.

If this message was output while the HADB server was being upgraded, take the appropriate action by referencing Steps to take when the KFAA41210-E message is output in Steps to take when version upgrading fails in the HADB Setup and Operation Guide.

KFAA41212-I

The size of the user log file was reduced. (file name = aa....aa, size = bb....bb MB) (M)

The size of the user log file was reduced.

aa....aa:

Name of the user log file

When the system directory support option for cloud storage facility is enabled, the name of the first S3 object in the group of S3 objects that contain the user log files is output, instead of the user log file names.

bb....bb:

Size before the file was reduced (rounded up in megabytes)

S:

Continues processing.

Action:

If this message is output during normal operation, we recommend that you increase the value specified for the adb_log_usrfile_size operand (initial-size-of-user-log-file or trigger-for-reducing-size-of-user-log-file) in the server definition. For details, see Working with the system log files in the HADB Setup and Operation Guide.

KFAA41213-W

The value of the second argument of the server definition adb_log_usrfile_size must be greater than or equal to the first argument of adb_log_usrfile_size. The value of the second argument of adb_log_usrfile_size will be changed to cc....cc. (adb_log_usrfile_size = aa....aa, bb....bb) (M)

The following values specified for the adb_log_usrfile_size operand in the server definition are invalid. Therefore, the default value (initial size of user log files x 2) is assumed as the trigger for reducing the size of the user log file.

initial-size-of-user-log-file

trigger-for-reducing-size-of-user-log-file

aa....aa: Initial size of user log files specified for the adb_log_usrfile_size operand

If you are using the multi-node function, the largest of the initial sizes of user log files specified on the primary node and secondary node is displayed.

bb....bb: Trigger for reducing the size of the user log file specified for the adb_log_usrfile_size operand

If you are using the multi-node function, the largest of the triggers for reducing the size of the user log file specified on the primary node and secondary node is displayed.

cc....cc: Value assumed for the trigger for reducing the size of the user log file

The value twice the value of aa....aa (initial size of user log files) is displayed.

S:

Continues processing.

Action:

Specify the adb_log_usrfile_size operand so that the following condition is satisfied:

trigger-for-reducing-size-of-user-log-file > initial-size-of-user-log-file

KFAA41220-W

Processing to start input/output control for the files used by the updated-row columnizing facility failed. (M)

Processing to start input/output control for the files used by the updated-row columnizing facility failed.

S:

Continues processing.

Action:

No matter whether the updated-row columnizing facility is enabled, processing to start input/output control for the files used by the updated-row columnizing facility is performed when the HADB server starts. Therefore, if this message is output when the updated-row columnizing facility is not enabled, check the message indicating the cause of the error that was output prior to this message, and then eliminate the cause of the error.

If this message is output when the updated-row columnizing facility is enabled, perform the following procedure to take action:

Execute the adbcolumnize --stop command to disable the updated-row columnizing facility.

A message indicating the cause of the error was output prior to this message. Eliminate the cause of the error according to the corrective action shown in that message.

Execute the adbcolumnize --start command to enable the updated-row columnizing facility.

KFAA41221-I

A system call error occurred. (func = "aa....aa", errno = bb....bb, file = "cc....cc") (M)

An error has occurred during execution of system call aa....aa.

aa....aa:

Name of system call in which the error occurred

bb....bb:

Error number

cc....cc:

File identifier

S:

Continues processing.

Action:

Take the following actions if necessary.

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the displayed system call name and error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Note that if aa....aa is a system call relating to file operations, cc....cc indicates the file identifier in one of the following formats. If the system call does not relate to file operations, nothing is indicated by cc....cc.

File name only

Absolute path

Relative path from the DB directory

KFAA41222-I

There is not enough free disk space to create the files used by the updated-row columnizing facility. (L+M)

There is not enough free disk space to create files to be used by the updated-row columnizing facility.

S:

Continues processing.

Action:

Increase free space in the file system to which the spool directory under the server directory belongs. To create the files to be used by the updated-row columnizing facility, at least 130 MB of free space is required.

KFAA41223-I

The file "aa....aa" must be a regular file, but it is not a regular file. (M)

File aa....aa must be a regular file, but file aa....aa is not.

aa....aa:

File identifier

S:

Continues processing.

Action:

A regular file having the same name as aa....aa cannot be created. Therefore, rename the file aa....aa so that a regular file named aa....aa can be created. aa....aa indicates the file identifier in one of the following formats:

File name only

Absolute path

Relative path from the DB directory

KFAA41230-W

The usage rate of DB area for data have reached aa....aa%. (DB area name = "bb....bb") (M)

The data DB area "bb....bb" usage rate reached aa....aa%.

aa....aa:

Data DB area usage rate (unit: %)

bb....bb:

Data DB area name

S:

Continues processing.

Action:

Expand the data DB area capacity as needed.

For details about expanding the data DB area capacity, see the following sections in the manual HADB Setup and Operation Guide.

If the multi-node function is not used

Expanding a data DB area (adding a data DB area file)

If the multi-node function is used

Expanding a data DB area (adding a data DB area file) in Adding, deleting, or expanding data DB areas (when the multi-node function is being used)

KFAA41235-E

Storage capacity became insufficient during operations on the cache file used by the cloud storage facility. Processing cannot continue because the storage capacity available for cache files used by the cloud storage facility is below the lower limit. (lower limit = aa....aa) (M)

There was insufficient storage capacity while operating the cache file. Processing cannot continue because the storage capacity required to operate the cache file is less than the lower limit.

aa....aa:

Lower storage space limit required for cache file operation (in gigabytes)

S:

Terminates processing.

Action:

Ensure that the storage capacity required for cache file operation is greater than the lower limit value output in aa....aa. Then, restart the HADB server.

If this message is output during execution of the adbinit command, take the corrective action above and then re-execute the adbinit command.

This message may also be output by an insufficient number of i nodes in the file system, even if there is ample storage capacity. In that case, instead of allocating storage capacity, allocate a i node.

KFAA41236-E

The operation on the aa....aa failed. (object key = "bb....bb", error type = cc....cc, msg = "dd....dd", exception name = ee....ee, response code = ff....ff, request id = gg....gg, ipaddress = hh....hh) (M)

Failed to operate S3 bucket.

aa....aa: Operation target

S3 bucket: S3 bucket

bb....bb: Object key

If it cannot be output, * is displayed.

cc....cc:

Error type

dd....dd: Message

If it cannot be output, * is displayed.

ee....ee: Exception name

If it cannot be output, * is displayed.

ff....ff:

Response code

gg....gg: Request ID

If it cannot be output, * is displayed.

hh....hh: IP address of remote host

If it cannot be output, * is displayed.

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the information output in this message. This message will output the information returned from AWS.

Note that if ee....ee is InternalError it indicates an error due to a temporary AWS problem. In this case, there is nothing for the user to do.

KFAA41237-E

The operation on the aa....aa failed. (object key = "bb....bb", status code = cc....cc, error code = dd....dd, msg = "ee....ee", request id = ff....ff) (M)

The container operation failed.

aa....aa: Operation target

Container: Container

bb....bb: Object key

If it cannot be output, * is displayed.

cc....cc: Status code

If it cannot be output, * is displayed.

dd....dd: Error code

If it cannot be output, * is displayed.

ee....ee:

Message

ff....ff: Request ID

If it cannot be output, * is displayed.

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the information output in this message. This message will output the information returned from Azure.

KFAA41238-W

The storage capacity for creating the file is insufficient. (file category = "aa....aa", file name = "bb....bb", size = cc....cc) (M)

Not enough storage capacity for creating the "aa....aa" file.

aa....aa: Type of file

reuse information file (in the cache file storage directory)

Reuse information file stored in the cache file storage directory

bb....bb:

File name

cc....cc:

Size of the file you attempted to create (unit: bytes)

S:

Continues processing.

Action:

The reuse information file is stored in the cache file storage directory and managed by the default cache group. Increase the storage capacity of the cache file storage directory so that the default cache group does not run out of capacity.

KFAA41239-E

The storage capacity for cache files used by the cloud storage function is insufficient. (number of cache groups = aa....aa, lower limit = bb....bb MB, free space = cc....cc MB, size of reused cache files = dd....dd MB) (M)

There is not enough storage capacity to store the cache file.

aa....aa:

Number of cache groups

bb....bb:

Lower limit of storage capacity for storing cache files (unit: megabytes)

cc....cc:

Free storage capacity (unit: megabyte)

dd....dd:

Total size of reused cache files (unit: megabytes)

S:

Terminates processing.

Action:

Each cache group requires at least 1 gigabyte of storage capacity.

However, if the system directory cache group's capacity limit is less than 1 gigabyte, that value becomes the minimum required capacity for that cache group.

This message is displayed when the total of the free capacity in the storage (cc....cc value) and the total size of the reused cache files (dd....dd value) is less than the lower limit storage capacity for storing cache files (bb....bb value).

Take one of the following corrective actions: Then, restart the HADB server.

Allocate free storage capacity

Ensure that there is enough free capacity to meet the following conditions: "bb....bb value - dd....dd value".

cc....cc value + dd....dd value ≥ bb....bb value

Reduce the number of cache groups defined in the adbcachegrp operand of the server definition.

If this message is output during execution of the adbinit command, take the corrective action above and then re-execute the adbinit command.

KFAA41241-E

An Apache Arrow API error occurred. (cause = "aa....aa", details = "bb....bb", resource = "cc....cc") (M)

An Apache Arrow API error occurred.

aa....aa:

Apache Arrow status code

bb....bb:

Detailed information set by the Apache Arrow API

cc....cc: Resource information about the error

Information about the resource associated with this error, such as foreign table names, URIs, and endpoints, is output.

If no information to output exists, one asterisk (*) is displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Refer to the information output in aa....aa and bb....bb to remove the cause of the error. For information on Apache Arrow status codes, see Programming Support in the Apache Arrow documentation.

bb....bb may contain position information that indicates the location that caused the foreign data access error. However, the meaning of the position information may differ between foreign data access errors and DB area access errors. For example, if the position information is a row number, the row number output in case of a foreign data access error starts from 0, but the row number output in case of a DB area access error starts from 1. Therefore, if there is no problem at the location indicated in the position information, review the surrounding locations as well.

If you cannot determine the corrective action to take based on the information that was output, execute the adbinfoget command, collect troubleshooting information, and then contact the customer support center.

KFAA41600-E

An Apache Iceberg API error occurred. (cause = "aa....aa", details = "bb....bb", resource = "cc....cc") (M)

An Apache Iceberg API error has occurred.

aa....aa:

The classification set by the Apache Iceberg API

bb....bb:

Detailed information set by the Apache Iceberg API

cc....cc:

Resource information about the error

Information about resources associated with this error, such as file paths, is output.

If there is no information to output, * is displayed.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Refer to the information output in aa....aa and bb....bb to remove the cause of the error.

If you cannot determine the corrective action to take based on the information that was output, execute the adbinfoget command, collect troubleshooting information, and then contact the customer support center.

2.3 Messages from KFAA50000 to KFAA59999

KFAA50000-E

An analysis file cannot be opened. (analysis file = aa....aa, error number = bb....bb) (M)

An analysis file used to analyze definition information (a file that the system uses) cannot be opened.

aa....aa:

Analysis file name

bb....bb: Error number

An error number of 0 indicates that the path name description is invalid.

S:

Terminates processing.

Action:

Check in the OS documentation for the error number that is displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the error number that is displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA50001-E

A value specified for a variable is invalid. (file = aa....aa, line = bb....bb, operand = cc....cc) (M)

An operand stated in the definition file is invalid.

aa....aa:

Definition file name

bb....bb:

Line that generated the error

cc....cc:

Operand name

S:

Terminates processing.

Action:

Check the format in which the operand is stated, and correct the operand if it is invalid. Then, retry the operation.

KFAA50002-E

A command name is invalid. (file = aa....aa, line = bb....bb, command = cc....cc) (M)

An operand of the command format stated in the definition file is invalid.

aa....aa:

Definition file name

bb....bb:

Line that generated the error

cc....cc:

Operand name

S:

Terminates processing.

Action:

Check the format in which the operand is stated, and correct any options that are invalid. Then, retry the operation.

KFAA50003-E

An option name is invalid. (file = aa....aa, line = bb....bb, option = ccc) (M)

The option name of an operand described in the definition file is invalid.

aa....aa:

Definition file name

bb....bb:

Line that generated the error

ccc:

Option name

S:

Terminates processing.

Action:

Check the format in which the option name of the operand is stated, and correct the option if it is invalid. Then, retry the operation.

KFAA50004-E

An option is specified more than once. (file = aa....aa, line = bb....bb, option = ccc) (M)

An option is specified more than once in a command-format operand stated in a definition file.

aa....aa:

Definition file name

bb....bb:

Line that generated the error

ccc:

Option name

S:

Terminates processing.

Action:

Check the format in which the operand is stated, and correct the option if it is specified more than once. Then, retry the operation.

KFAA50005-E

An argument of an option is invalid. (file = aa....aa, line = bb....bb, option = ccc) (M)

The value specified in an option of an operand stated in the definition file is invalid.

aa....aa:

Definition file name

bb....bb:

Line that generated the error

ccc:

Option name

S:

Terminates processing.

Action:

Check the format in which the option of the operand is stated, and correct the value specified if it is invalid. This message might be output, for example, if a character string is specified in the argument of an option for which only numeric values can be specified.

KFAA50006-E

A definition file cannot be analyzed because memory is insufficient. (required memory = aa....aa) (M)

A memory shortage has occurred in analysis processing of a definition file.

aa....aa:

Required memory when error occurred (bytes)

S:

Terminates processing.

Action:

Delete any unnecessary processes, and then retry the operation. If there are no unnecessary processes, memory is insufficient. Take corrective action to add memory, and then retry the operation.

KFAA50007-E

An I/O error occurred. (file = aa....aa) (M)

An error occurred during reading of a definition file.

aa....aa:

Definition file name

S:

Terminates processing.

Action:

Determine whether there are any errors in the definition file.

If the definition file name is server.def, the server definition might have been corrupted. Delete the server definition and create a new one. Then, retry the operation.

KFAA50008-E

A definition file cannot be opened. (definition file = aa....aa, error number = bb....bb) (M)

A definition file could not be opened.

aa....aa:

File name

bb....bb: Error number

An error number of 0 indicates that the path name description is invalid.

S:

Terminates processing.

Action:

Check in the OS documentation for the error number that is displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the error number that is displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA50009-E

The length of a record exceeds the maximum. (file = aa....aa, line = bb....bb) (M)

A line stated in a definition file exceeds 4,000 bytes.

aa....aa:

File name

bb....bb:

Line that generated the error

S:

Terminates processing.

Action:

Check the length of the line that generated the error in the definition file.

The maximum number of characters that can be stated in a line of a definition file is 4,000 bytes worth. If a line contains more than 4,000 bytes worth of characters, break it into multiple lines. To continue a line, enter the continuation character \ at the end of the line, and follow it immediately with a linefeed. For details about continuing lines, see Syntax rules for the server definition in the HADB Setup and Operation Guide.

Note that, for multi-byte characters, lines that have a length no greater than 4,000 bytes in a text editor might be recognized as having more than 4,000 bytes, since a single character might be converted into 2 or more bytes.

KFAA50010-E

A specified variable name is invalid. (file = aa....aa, line = bb....bb) (M)

The specified set format operand name cannot be analyzed because it contains one of the following errors:

There is no description of a set format operand name.

The specified set format operand name contains an error. Another possibility is that an unsupported set format operand name has been specified.

aa....aa:

Definition file name

bb....bb:

Line that generated the error

S:

Terminates processing.

Action:

Specify a valid set format operand name. Alternatively, carefully review the relationship between the definition file and the definition contents.

KFAA50011-E

The format of aa....aa is invalid. (file = bb....bb, line = cc....cc) (M)

The format in which a definition file is stated contains an error.

aa....aa:

Name of definition that generated the error

bb....bb:

Definition file name

cc....cc:

Line that generated the error

S:

Terminates processing.

Action:

There is no equal sign (=) between the affected definition name and the specification value, so add one.

KFAA50012-E

A required definition is not specified. (file = aa....aa, operand = bb....bb) (M)

A required operand is not specified in the definition file.

aa....aa:

Definition file name

bb....bb:

Operand name

S:

Terminates processing.

Action:

Check whether a required adb_db_path operand has been specified or not. If it has not, or it has been specified incorrectly, specify it again.

KFAA50013-E

A required option is not specified. (file = aa....aa, line = bb....bb, command = cc....cc, option = ddd) (M)

An option that cannot be omitted was not specified in a definition file.

aa....aa:

Definition file name

bb....bb:

Line that generated the error

cc....cc:

Operand name

ddd:

Option name

S:

Terminates processing.

Action:

Check whether the required option was specified or not.

KFAA50014-W

A definition is repeated. The first definition will be used and processing will continue. (file = aa....aa, line = bb....bb, operand = cc....cc) (M)

An operand was specified more than once in a definition file. The first operand value specified takes effect.

aa....aa:

Definition file name

bb....bb:

Number of lines that specify the definition after the first instance

cc....cc:

Name of operand specified more than once

S:

Continues processing.

Action:

Check the first operand value specified. If there is no problem with the specified value, delete the duplicate operands. If there is a problem with the specified value, leave only the desired operand and delete all duplicate operands. Then, retry the operation.

KFAA50015-E

The specified DB directory does not exist. (M)

The DB directory specified in the server definition does not exist.

S:

Terminates processing.

Action:

Check the path name of the DB directory specified in the server definition's adb_db_path operand. If an error is found, correct it. Then, execute the adbstart command to restart the HADB server.

KFAA50016-E

The DB directory contents are invalid. (M)

The DB directory contents are invalid.

S:

Terminates processing. Alternatively, the system abnormally terminates the HADB server.

Action:

Check whether the correct path name of the DB directory has been specified in the server definition's adb_db_path operand. Then, execute the adbstart command to restart the HADB server.

If this message is output even though the correct DB directory path name is specified, take one of the following corrective actions:

Restore the database from the backup.

Execute the adbinit command to initialize the DB directory.

KFAA50017-E

The specified DB directory path is invalid. (information = aa....aa) (M)

The DB directory path name is invalid.

aa....aa: Cause of the error

INVALID PATH FORMAT: The format in which the path name is specified is invalid.

INVALID LETTER: An invalid character has been specified.

S:

Terminates processing.

Action:

Check the path name of the DB directory specified in the server definition's adb_db_path operand. If the specification format is incorrect or disallowed characters were used, correct the errors. Then, execute the adbstart command to restart the HADB server.

If INVALID PATH FORMAT was output as the cause of the error, check for the following mistakes:

The first character is not a forward slash (/).

A character string of length 0 was specified.

There is a space at the start or end of the path.

KFAA50018-E

An error occurred while accessing to the message catalog file. (information = aa....aa) (E)

An error occurred while a message catalog file was being accessed.

aa....aa: Cause of the error

FAILED TO GET THE PATH NAME OF THE CATALOG FILE

An attempt to get the name of a message catalog file has failed.

System call error, system call = "bb....bb", errno = cc....cc

A system call error has occurred.

bb....bb: Name of system call in which the error occurred

cc....cc: Error number

S:

Terminates processing.

Action:

Eliminate the error based on the cause of the error aa....aa that is output in the message.

When aa....aa is FAILED TO GET THE PATH NAME OF THE CATALOG FILE

Carefully review the values specified for environment variables ADBDIR and ADBCLTDIR. Also carefully review the storage directory of the message catalog file#.

#

• HADB server: $ADBDIR/lib

• HADB client for Windows: %ADBCLTDIR%\lib

• HADB client for Linux: $ADBCLTDIR/lib

When aa....aa is System call error, system call = "bb....bb", errno = cc....cc

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

After taking corrective action, execute the adbstart command to restart the HADB server.

KFAA50019-E

An error occurred while accessing to the message log file. (information = aa....aa) (E)

An error has occurred while accessing a message log file.

aa....aa: Cause of the error

FAILED TO GET THE PATH NAME OF THE MESSAGE LOG FILE

An attempt to get the name of a server message log file failed.

FAILED TO GET THE PATH NAME OF THE CLIENT MESSAGE LOG FILE

An attempt to get the name of a client message log file failed.

System call error, system call = "bb....bb", errno = cc....cc

A system call error has occurred.

bb....bb: Name of system call in which the error occurred

cc....cc: Error number

S:

Terminates processing.

Action:

Eliminate the error based on the cause of the error aa....aa that is output in the message.

If aa....aa is FAILED TO GET THE PATH NAME OF THE MESSAGE LOG FILE

Carefully review both the server message log file's storage directory ($ADBDIR/spool/) and the value specified in environment variable ADBDIR.

If aa....aa is FAILED TO GET THE PATH NAME OF THE CLIENT MESSAGE LOG FILE

Carefully review both the client message log file's storage directory# and the value specified in environment variable ADBCLTDIR.

#

• HADB client for Windows: %ADBCLTDIR%\spool

• HADB client for Linux: $ADBCLTDIR/spool

If aa....aa is System call error, system call = "bb....bb", errno = cc....cc

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

After taking corrective action, execute the adbstart command to restart the HADB server.

KFAA50020-E

The character encodings used for the specified database and for the database used by HADB are different. (database encoding = "aa....aa", HADB encoding = "bb....bb") (M)

The character encoding used by the database does not match the character encoding that the HADB server uses in its database.

aa....aa: Character encoding used by the database

This is the character encoding that was specified in the environment variable ADBLANG when the adbinit command was executed.

bb....bb: Character encoding that the HADB server uses in its database

This is the character encoding that is specified in the environment variable ADBLANG.

S:

Terminates processing.

Action:

Check whether the path name of the DB directory specified in the server definition's adb_db_path operand and the character encoding specified in environment variable ADBLANG are correct.

Specify the correct DB directory path name and the correct character encoding in environment variable ADBLANG, and then re-start the HADB server.

Also, if unsupported is returned in aa....aa, the databases might be corrupted. Initialize the DB directory with an adbinit command. If a backup is necessary, make a copy with the OS's cp command or the like prior to initialization.

KFAA50021-E

The HADB system cannot terminate because it is connected to an application. (M)

The HADB server cannot terminate because there is a connected application program or executing command.

S:

Terminates processing.

Action:

Take one of the following actions:

Wait until the connected application program disconnects from the HADB server and the executing command terminates, and then re-execute the adbstop command. Alternatively, execute the adbstop --wait connection command.

If you want to wait until the current transaction is completed and the executing command terminates before you terminate the HADB server, execute the adbstop --wait transaction command.

If you can cancel the current transaction and executing command, execute the adbstop --cancel command.

For details about the adbstop command options, see Terminating the HADB server in Starting and terminating the HADB server and its operation modes in Scheduled Operations in the HADB Setup and Operation Guide. Alternatively, see adbstop (Terminate the HADB Server) in the manual HADB Command Reference.

KFAA50022-E

An error occurred while accessing the status file. (information = aa....aa) (M)

An error occurred while a status file was being accessed.

aa....aa: Cause of the error

System call error, system call = "bb....bb", errno = cc....cc

A system call error has occurred.

bb....bb: Name of system call in which the error occurred

cc....cc: Error number

Cloud storage I/O error

An I/O error has occurred in the cloud storage facility.

S:

Terminates processing.

Action:

When aa....aa is System call error, system call = "bb....bb", errno = cc....cc

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

When aa....aa is Cloud storage I/O error

Check the cloud storage messages output prior to this message and eliminate the cause of the error.

KFAA50023-E

The HADB server terminated abnormally because an error occurred during the start or end processing for a transaction. (M)

The HADB server terminated abnormally because an error occurred during processing to start or end a transaction.

S:

Terminates the HADB server abnormally.

Action:

Eliminate the cause of the error according to the corrective action for the message that was output immediately prior to this message. Then, start the HADB server.

KFAA50024-E

The HADB system cannot be restarted because the following server definitions are different from the last time the system was started. (M)

The HADB system cannot be restarted because the server definitions are different from the last time the system was started.

S:

Terminates processing.

Action:

Message KFAA50025-E is output after this message. Take the corrective action indicated for the KFAA50025-E message.

KFAA50025-E

A value specified in the server definition aa....aa the last time the HADB system was started was bb....bb. The value is now cc....cc. (M)

The HADB system cannot be restarted because a server definition is different from the last time the system was started.

aa....aa: Server definition operand name that is different from the value specified at the last startup

adb_sys_max_users operand

adb_sys_rthd_num operand

adb_sys_memory_limit operand

adb_sys_rthd_area_max operand

adb_sys_proc_area_max operand

bb....bb:

Value specified at last startup

If no value has been specified, "unspecified" is displayed.

cc....cc:

Value specified at this startup

If no value has been specified, "unspecified" is displayed.

S:

Terminates processing.

Action:

Match the specified value of the server definition operand name aa....aa (which is different from the value specified at last startup) to the specified value bb....bb at last startup, and then re-execute the adbstart command.

KFAA50026-I

The following values were specified for the aa....aa. (M)

A value is specified for aa....aa.

A message indicating the specified value is output after this message.

aa....aa:

server definitions: Server definition

client definitions: Client definition

adbinit control-file: Initialization option file

adbmodarea control-file: DB area addition and modification option file

adbimport options: Import option

adbexport options: Export option

adbidxrebuild options: Index rebuild option

adbgetcst options: Cost information collection-options

adbmergechunk options: Merge chunk option

adbmodbuff options: Buffer-modifying option

adbimport column-structure-information-file: Column structure information file

adbarchivechunk options: Archived chunk option

adbunarchivechunk options: Unarchived chunk option

client-managing definitions: Client-managing definition

adbchgchunkstatus batch-changes-of-chunk-statuses-option-file: Configuration file for changing chunk statuses in a batch

S:

Continues processing.

KFAA50027-I

aa....aa bb....bb (M)

bb....bb was specified for the aa....aa operand in the server definition.

aa....aa:

Operand name in the server definition

bb....bb: Value specified for the operand

For operands in the set format

An equal sign (=) is displayed at the beginning.

If the format of the value specified for the operand is an integer suffixed by the unit, the value is output after conversion to the numeric value that is assumed when the unit is omitted. In this case, no unit is output.

(Example) When adb_sys_memory_limit = 192GB (196,608 MB) is specified in the server definition

KFAA50027-I adb_sys_memory_limit = 196608

For operands in the command format

All option names that were specified in the aa....aa operand and the specified values of their arguments are displayed in the format option-name∆value-specified-for-option-argument. (The Δ symbol indicates a space.)

S:

Continues processing.

KFAA50028-E

An error occurred while accessing the shared memory ID file. (information = aa....aa) (M)

An error occurred while a shared memory ID storage file ($ADBDIR/spool/.adbshmid) was being accessed.

aa....aa: Cause of the error

System call error, system call = "bb....bb", errno = cc....cc

A system call error has occurred.

bb....bb: Name of system call in which the error occurred

cc....cc: Error number

I/O retry count over flow

The shared memory ID storage file is busy.

S:

Terminates processing.

Action:

Eliminate the error based on the cause of the error aa....aa that is output in the message.

If aa....aa is System call error, system call = "bb....bb", errno = cc....cc

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If aa....aa is I/O retry count over flow

Wait a while, and then re-execute the command.

KFAA50029-E

An error occurred while accessing the shared memory dump file. (information = aa....aa) (M)

An error occurred while a shared memory dump file was being accessed.

aa....aa: Cause of the error

System call error, system call = "bb....bb", errno = cc....cc

A system call error has occurred.

bb....bb: Name of system call in which the error occurred

cc....cc: Error number

I/O retry count over flow

The shared memory dump file is busy.

S:

Terminates processing.

Action:

Eliminate the error based on the cause of the error aa....aa that is output in the message.

If aa....aa is System call error, system call = "bb....bb", errno = cc....cc

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If aa....aa is I/O retry count over flow

Wait a while, and then re-execute the command.

KFAA50030-E

An error occurred while accessing the DB directory. (information = aa....aa) (M)

An error occurred while a DB directory was being accessed.

aa....aa: Cause of the error

System call error, system call = "bb....bb", errno = cc....cc

A system call error has occurred.

bb....bb: Name of system call in which the error occurred

cc....cc: Error number

S:

Terminates processing.

Action:

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA50032-E

The HADB server cannot be started because the specified value of the following server definition, client-managing definition or environment variable is different from other specified node values. (M)

The HADB server cannot be started because the value specified in the server definition, client-managing definition, or environment variable is different from the values specified for other nodes.

S:

Terminates processing.

Action:

After this message is output, message KFAA50033-E will be output. Take the corrective action indicated for message KFAA50033-E.

KFAA50033-E

The HADB server cannot be started because the specified value of the aa....aa(bb....bb) is different from other specified node values. (local node = cc....cc, other node = dd....dd) (M)

The HADB server could not start because the specified value of bb....bb differs from the value specified on another node.

aa....aa: Location where the value is specified

server definition: Server definition

client-managing definition: Client-managing definition

environment variable: Environment variable

bb....bb:

The name of the server definition operand, client-managing definition operand, or environment variable in which the value that was different from the value specified on the other node was specified

cc....cc:

Value specified on the local node

If no value has been specified, "unspecified" is displayed.

If bb....bb is adbclientmang, an asterisk (*) is displayed.

dd....dd:

Value specified on the other node

If no value has been specified, "unspecified" is displayed.

If bb....bb is adbclientmang, an asterisk (*) is displayed.

S:

Terminates processing.

Action:

If aa....aa is server definition or environment variable

Make the specified value of bb....bb the same for all nodes.

If the operand name of the server definition shown below is displayed in bb....bb, make sure that the specified value of bb....bb is the same on the primary node and secondary node.

adb_sql_default_dbarea_shared

adb_rpc_port

adb_syndict_storage_path

adb_cmd_dvbix_rthd_use

adb_cmd_ixrec_file_use

adb_auth_keyc_endpoint

adb_auth_clt_keyc_endpoint

adb_auth_keyc_realm

adb_auth_keyc_clt_id

If aa....aa is client-managing definition

Make the specified value of bb....bb the same for the primary node and secondary node.

KFAA50034-E

Startup wait processing for other nodes timed out. (timeout process = aa....aa) (M)

The wait for startup processing to complete on other nodes timed out.

aa....aa: Timed-out process

Awaiting the communication establishment with other nodes

Waiting for communication to be established between this server and the HADB servers on other nodes

Awaiting the monbegin command of the HA monitor execute

Waiting for HA Monitor's monbegin command to execute

Awaiting the HADB server start completion of other nodes

Waiting for startup of the HADB servers on other nodes to complete

S:

Terminates processing.

Action:

Increase the server definition's adb_sys_node_start_wait_time operand value.

If a time-out occurs even after the operand value is increased, check the HADB server statuses and HA Monitor statuses of other nodes, and remove the cause of the time-out of the processing described in the message output. Then, retry the operation.

Note that if aa....aa fails with Awaiting the communication establishment with other nodes during the addition of a worker node, the following transaction or command may be in progress on the primary node.

Read/write transaction

adbimport command

adbidxrebuild command

adbgetcst command

adbmergechunk command

adbchgchunkcomment command

adbchgchunkstatus command

adbarchivechunk command

adbunarchivechunk command

adbreorgsystemdata command

adbsyndict command

adbaudittrail command (except when the --swap option or -d option is specified)

If you wish to give priority to adding worker nodes, cancel any transactions or commands that are being executed on the primary node. Once this is done, re-execute adding the worker node.

KFAA50035-E

A value specified for server definition "adb_sys_multi_node_info" or "adb_sys_multi_worker_node_info" is invalid. (reason = aa....aa) (M)

The specified value of one of the operands in the server definition is invalid.

adb_sys_multi_node_info operand

adb_sys_multi_worker_node_info operand

aa....aa:

Cause of the error

S:

Terminates processing.

Action:

Take corrective action depending on the cause of the error that was output.

No.

Display of aa....aa

Cause of the error

Corrective action to take

1

The same IP address is specified multiple times

The same IP address is specified multiple times.

Correct the duplicate IP address specification with the host name specified in the adb_sys_multi_node_info and adb_sys_multi_worker_node_info operands in the server definition.

2

Multiple nodes are specified with the same combination of IP address and port number

The IP address and port number combination is duplicated.

Any of the node IP address and port number combinations specified in the adb_sys_multi_node_info operand and the adb_sys_multi_worker_node_info operand of the server definition is duplicated. Correct the IP address or port number specification for the node with duplicate specified values.

3

Information for the local node is not specified

The information for the local node has not been specified.

Specify the host name and port number of the local node in the adb_sys_multi_node_info or adb_sys_multi_worker_node_info operand in the server definition.

This message is also output when the host name of the worker node is specified in the adb_sys_multi_node_info operand instead of the adb_sys_multi_worker_node_info operand in the server definition, when the worker node is the local node. In this case, specify the host name and port number of the local worker node in the adb_sys_multi_worker_node_info operand.

4

The value specified for the local node port number in server definition adb_sys_multi_node_info or adb_sys_multi_worker_node_info and the value specified for server definition adb_rpc_port are the same value

The port number of the local node specified in the server definition's adb_sys_multi_node_info operand or adb_sys_multi_worker_node_info operand is the same as the port number specified in the server definition's adb_rpc_port operand.

Change one of the following.

The value specified for the adb_rpc_port operand in the server definition

The port number of the local node specified in the adb_sys_multi_node_info or adb_sys_multi_worker_node_info operand in the server definition

5

Only one host name is specified

Only one host name is specified in the adb_sys_multi_node_info operand in the server definition.

Specify two or more host names in the adb_sys_multi_node_info operand from the server definition.

KFAA50036-E

The aa....aa command cannot be executed on bb....bb. (M)

The aa....aa command cannot be executed on bb....bb.

aa....aa:

Name of the command that cannot be executed

bb....bb: Execution node

secondary nodes: Secondary nodes

worker nodes: Worker nodes

S:

Terminates processing.

Action:

Execute command aa....aa on the primary node.

KFAA50037-E

An error occurred while accessing the semaphore ID file. (information = aa....aa) (M)

An error occurred while accessing the semaphore set ID storage file.

aa....aa: Cause of the error

System call error, system call = "bb....bb", errno = cc....cc

A system call error has occurred.

bb....bb: Name of system call in which the error occurred

cc....cc: Error number

I/O retry count over flow

The semaphore set ID storage file is busy.

S:

Terminates processing.

Action:

Eliminate the error based on the cause of the error aa....aa that is output in the message.

If aa....aa is System call error, system call = "bb....bb", errno = cc....cc

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If aa....aa is I/O retry count over flow

Wait a while, and then re-execute the command.

KFAA50038-E

The database cannot be upgraded because aa....aa. (M)

The database cannot be upgraded for reason aa....aa.

aa....aa: Cause of the error

of an abnormal termination the last time it ended

The HADB server's previous termination mode was abnormal termination or forced termination.

the adbstart command was never been executed in previous versions

The previous version of HADB server has never been started.

of using the multiple node facility

The HADB server is using the multi-node function.

S:

Terminates processing.

Action:

See Steps to take when the KFAA50038-E message is output in Steps to take when version upgrading fails in the HADB Setup and Operation Guide.

If aa....aa is of using the multiple node facility, see Notes on version upgrading in the HADB Setup and Operation Guide, and then take action according to the following procedure.

Delete the adb_sys_multi_node_info operand from the server definition to stop the use of the multi-node function.

Start the HADB server and upgrade the database.

Wait until the operation in step 2 terminates normally, and then terminate the HADB server.

Add the adb_sys_multi_node_info operand to the server definition to use the multi-node function. Then start the HADB server in the multi-node configuration.

KFAA50039-E

The HADB server cannot be started because the HADB version is older than the database version. (HADB version = "aa....aa", database version = "bb....bb") (M)

The HADB server cannot be started because the HADB server's version is earlier than the database version.

aa....aa:

HADB server version

bb....bb:

Database version

S:

Terminates processing.

Action:

Make sure that the HADB server version matches the database version. For details about how to upgrade HADB server, see Upgrading the HADB server version in the HADB Setup and Operation Guide.

KFAA50040-E

ISO cannot be specified for the sorting order, because the character encoding to be used on the HADB server is not Unicode (UTF-8). (ADBLANG = aa....aa, adb_sql_order_mode = bb....bb) (M)

ISO cannot be specified as the sort order because the character encoding used in the HADB server is not Unicode (UTF-8).

aa....aa: Value of the ADBLANG environment variable

SJIS: Shift-JIS is specified as the character encoding used by the HADB server.

bb....bb: adb_sql_order_mode operand value

ISO: ISO is specified as the sort order.

S:

Terminates processing.

Action:

Specify BYTE in the adb_sql_order_mode operand in the server definition. Then, execute the adbstart command to start the HADB server.

Alternatively, change the value of the ADBLANG environment variable to Unicode (UTF-8), and then re-create the database using the adbinit command.

KFAA50041-E

aa....aa during the bb....bb standby processing. (M)

aa....aa occurred during bb....bb wait status

aa....aa: Cause of the error

A timeout occurred: A timeout occurred.

A cancel was detected: A cancellation was detected.

bb....bb: Process during wait status

termination: Termination process

S:

Terminates processing.

Action:

If the cause of the error is A timeout occurred

If this message was output while the adbstop --wait connection command was executing, wait until the connected application program disconnects from the HADB server and the executing command terminates, and then re-execute the adbstop --wait connection command. Alternatively, increase the timeout value specified in the -t option, and then re-execute the adbstop --wait connection command.

If this message was output while the adbstop --wait transaction command was executing, wait until all transaction processing and command execution finishes, and then re-execute the adbstop --wait transaction command. Alternatively, increase the timeout value specified in the -t option, and then re-execute the adbstop --wait transaction command.

If the cause of the error is A cancel was detected

If this message is output during execution of the adbstop --wait connection or adbstop --wait transaction command, execute the adbstop --cancel command to terminate the HADB server.

KFAA50042-W

The user does not have permission to access the specified directory in the server definition adb_core_path. (M)

The user does not have the privileges to access the directory specified in the server definition's adb_core_path operand.

S:

Continues processing.

Action:

Terminate the HADB server normally, and then grant access privileges for the directory specified in the server definition's adb_core_path operand to the HADB administrator. Then, execute the adbstart command to start the HADB server.

KFAA50043-E

An HADB server could not be returned to a multi-node configuration because aa....aa. (M)

The node cannot be returned to the multi-node configuration.

aa....aa:

Cause of the error

bb....bb:

Specified value of the operand in the server definition before change

cc....cc:

Specified value of the operand in the server definition after change

S:

Terminates processing.

Action:

Take corrective action for the cause of the error displayed for aa....aa.

Display of aa....aa

Cause of the error

Corrective action to take

one of the HADB servers that composes the multi-node configuration is performing termination processing

One of the HADB servers in the multi-node configuration is performing termination processing.

Wait for completion of termination processing of the HADB server, and then perform the operation to return the node.

the primary node is performing switchover processing

Primary node switchover processing is in progress.

Wait for completion of primary node switchover processing, and then perform the operation to return the node.

another HADB server is being returned to the multi-node configuration

Another node is being returned to the multi-node configuration.

Wait for completion of processing to return to the multi-node configuration, and then perform the operation to return the node.

an application or a command is connected to the HADB server

An application program or command is being connected to the HADB server in the multi-node configuration.

Wait for the application program and command to be disconnected, and then perform the operation to return the node.

a value specified in the server definition adb_sys_rthd_num the last time the HADB server was started was bb....bb. The value is now cc....cc

The value specified for the adb_sys_rthd_num operand in the server definition is changed.

Return the value of the server definition's adb_sys_rthd_num operand to its original value, and then perform the operation to return the node.

a worker node is being added to the multi-node configuration

Another worker node is being added to the multi-node configuration.

Wait for completion of adding processing of the worker node, and then perform the operation to return the node.

KFAA50044-I

The HADB server of the connection-destination node terminated normally. (node number = aa....aa, host name = bb....bb, IP address = cc....cc) (M)

The HADB server at the connection target terminated normally.

aa....aa:

Number of the node where the HADB server terminated normally

bb....bb:

Host name of the node where the HADB server terminated normally (communication between servers)

cc....cc:

IP address of the node where the HADB server terminated normally (communication between servers)

S:

Continues processing.

KFAA50045-E

Execution of the HA Monitor command failed. (M)

Execution of an HA Monitor command failed.

S:

Terminates processing.

Action:

Check the following:

Is the HA Monitor path specified in the environment variable PATH?

Is HA Monitor installed?

Is the path specified in ADBDIR in the environment variable definition for commands (multinode.env) correct?

KFAA50046-E

The specified node type does not match the status of HA Monitor on the server. (alias = "aa....aa", HADB node type = bb....bb, HA Monitor status = cc....cc) (M)

The node type of the HADB server does not match the HA Monitor status.

aa....aa:

Server ID for HA Monitor

bb....bb: Node type of the HADB server

PRIMARY: Primary node

SECONDARY: Secondary node

cc....cc: HA Monitor status

ONLINE: Active system

STANDBY: Standby system

S:

Terminates processing.

Action:

Make sure that the servers file of HA Monitor is specified correctly and that the shell command processing is specified correctly for the actcommand operand.

They are correct if the relationship between bb....bb and cc....cc is either of the following:

bb....bb is PRIMARY and cc....cc is ONLINE

bb....bb is SECONDARY and cc....cc is STANDBY

This message might be output when a node is returned to a multi-node configuration after a failure occurs on the monitoring path of HA Monitor. In this situation, execute the monlink command of HA Monitor to recover the monitoring path.

KFAA50047-E

An error occurred on another node or an HADB server on another node was terminated during the HADB system start processing. (node number = aa....aa, host name = bb....bb, IP address = cc....cc) (M)

One of the following problems occurred during the startup process of HADB server of the multi-node configuration, so the HADB server of the multi-node configuration cannot be started.

An error occurred on another node.

An HADB server on another node terminated.

aa....aa:

Node number of the node where the problem occurred

If the process of adding a worker node fails before acquiring the node number, 0 is output.

bb....bb:

Host name of the node where the problem occurred (communication between servers)

cc....cc:

IP address of the node where the problem occurred (communication between servers)

S:

Terminates processing.

Action:

Take the corrective action on the node where the error occurred, and then start the HADB server in the multi-node configuration.

If an HADB server on another node terminated, re-execute the adbstart command to start that HADB server in the multi-node configuration.

This message may also be output in the following cases:

If an attempt is made to return a node while a node is returning

If an attempt is made to add a worker node while a node is returning

KFAA50048-E

The server definition adb_sys_memory_limit cannot be defined together with the server definition adb_sys_proc_area_max or the server definition adb_sys_rthd_area_max. (M)

In the server definition, the adb_sys_memory_limit operand cannot be specified together with the adb_sys_proc_area_max operand or adb_sys_rthd_area_max operand.

S:

Terminates processing.

Action:

To specify the adb_sys_memory_limit operand in the server definition, delete the specifications of the adb_sys_proc_area_max operand and adb_sys_rthd_area_max operand in the server definition. Then, retry the operation.

To specify the adb_sys_proc_area_max operand or adb_sys_rthd_area_max operand in the server definition, delete the specification of the adb_sys_memory_limit operand in the server definition. Then, retry the operation.

KFAA50049-E

The HADB server cannot be started because the HADB server version is different from the HADB server version of another node. (local node = aa....aa, other node = bb....bb) (M)

The HADB server cannot start because the HADB server version is different from that of another node.

aa....aa:

HADB server version of the local node

bb....bb:

HADB server version of the other node

S:

Terminates processing.

Action:

Match the HADB server versions of the relevant nodes, and then retry the operation.

If the operation for replacement with the revised version of HADB server has been performed for each node, restore the server directory from the backup. Then, see Swapping the HADB server with its revised version (when the multi-node function is used) in the HADB Setup and Operation Guide, and then re-install the revised version of HADB server.

KFAA50050-I

The extended syslog facility was used on the HADB server. (L+M)

The extended syslog function has been applied to the HADB server.

S:

Continues processing.

KFAA50051-W

The character encoding conversion facility of the extended syslog facility could not be used. (reason = aa....aa) (M)

The character encoding conversion facility of the extended syslog function could not be applied.

aa....aa:

Reason why the facility cannot be applied

S:

Continues processing.

Action:

To use the syslog character encoding conversion facility, take appropriate action for the reason indicated by aa....aa.

Display of aa....aa

Reason why the facility cannot be applied

Corrective action to take

The extended syslog facility does not support the character encoding conversion facility

The extended syslog function does not support the character encoding conversion facility.

Terminate the HADB server, and then install HA Logger Kit for Linux (extended syslog function) that supports the character encoding conversion facility. Then, start the HADB server.

For details about how to install HA Logger Kit for Linux (extended syslog function), see HA Logger Kit for Linux Instruction Manual.

Initialization of the character encoding conversion facility failed

Initialization of the character encoding conversion facility failed.

To convert syslog character encoding, Hitachi Code Converter is required as the prerequisite software.

If you have not installed Hitachi Code Converter

Terminate the HADB server and install Hitachi Code Converter. Then, start the HADB server. See the manual Hitachi Code Converter (UNIX Edition) for information on how to install Hitachi Code Converter.

If you have installed Hitachi Code Converter

The error might have been caused by insufficient memory. Terminate the HADB server, and then take the corrective action for insufficient memory. Then, start the HADB server.

If there is enough heap memory and the error was not caused by insufficient memory, terminate the HADB server, and then re-install Hitachi Code Converter. Then, start the HADB server. If the error persists, contact the customer support center.

KFAA50052-E

An HADB server could not be terminated because aa....aa. (M)

The HADB server cannot be terminated for one of the following reasons:

A node is being returned to a multi-node configuration

A worker node is being added to a multi-node configuration

aa....aa: Reason

the HADB server is being returned to a multi-node configuration

A node is being returned to a multi-node configuration.

a worker node is being added to a multi-node configuration

A worker node is being added to a multi-node configuration.

S:

Terminates processing.

Action:

If aa....aa is the HADB server is being returned to a multi-node configuration

Wait for completion of processing to return the node to the multi-node configuration, and then execute the adbstop command.

If aa....aa is a worker node is being added to a multi-node configuration

Wait for completion of processing to add a worker node to the multi-node configuration, and then execute the adbstop command.

KFAA50053-E

The HADB server terminated abnormally because an error occurred during switchover processing of the primary node. (information = aa....aa) (M)

An error occurred during primary node switchover processing. Therefore, the HADB server is terminated abnormally.

aa....aa:

Message ID

S:

Terminates the HADB server abnormally.

Action:

Take action for the message ID indicated by aa....aa. After taking action, return the node to the multi-node configuration if necessary.

KFAA50054-E

The HADB server operation mode could not be changed because aa....aa. (M)

The HADB server operation mode cannot be changed for one of the following reasons:

A node is being returned to a multi-node configuration

A worker node is being added to a multi-node configuration

aa....aa: Reason

the HADB server is being returned to a multi-node configuration

A node is being returned to a multi-node configuration.

a worker node is being added to a multi-node configuration

A worker node is being added to a multi-node configuration.

S:

Terminates processing.

Action:

If aa....aa is the HADB server is being returned to a multi-node configuration

Wait for completion of processing the node to return to the multi-node configuration, and then execute the adbchgsrvmode command.

If aa....aa is a worker node is being added to a multi-node configuration

Wait for completion of processing to add a worker node to the multi-node configuration, and then execute the adbchgsrvmode command.

KFAA50055-I

The HADB server returned to a multi-node configuration. (node number = aa....aa, host name = bb....bb, IP address = cc....cc) (M)

Processing to return to the multi-node configuration has completed.

aa....aa:

Node number of the node that returned to the multi-node configuration

bb....bb:

Host name of the node that returned to the multi-node configuration

cc....cc:

IP address of the node that returned to the multi-node configuration

S:

Continues processing.

KFAA50056-I

An error occurred during an attempt to access a syslog file that uses the extended syslog facility. (information = aa....aa) (M)

An error occurred during access to a syslog file that uses the extended syslog function.

aa....aa: Detailed information about error

Function error, function = "bb....bb", errno = cc....cc

An error occurred in a function provided by the extended syslog function.

bb....bb:

Name of the function in which the error occurred

cc....cc:

Error number

S:

Continues processing.

Action:

Check the cause of the error based on the function name indicated by bb....bb and the error number indicated by cc....cc, and then take corrective action.

KFAA50057-W

The message log file of another node was in fall-back mode. (node number = aa....aa, host name = bb....bb, IP address = cc....cc) (M)

Free disk space for storing the message log file is insufficient on a node other than the node for which this message was output.

aa....aa:

Node number of the node where free disk space is insufficient

bb....bb:

Host name of the node where free disk space is insufficient

cc....cc:

IP address of the node where free disk space is insufficient

S:

Continues processing.

Action:

The KFAA40025-W message has been output for the node where free disk space is insufficient. Take corrective action for that message.

KFAA50058-E

The HADB server cannot be started because the server definition on the local node is different from the definition on another node. (server definition = aa....aa, local node = bb....bb, other node = cc....cc) (M)

The HADB server in a multi-node configuration could not be started because the setting of whether the aa....aa operand is specified in the server definition is different between nodes.

aa....aa: Name of the server definition operand

adb_audit_log_path

adb_crypto_dmkey_path

adb_auth_passwd_privkey_path

adb_cmd_passwd_pubkey_path

bb....bb: Whether the aa....aa operand is specified in the local node

specified: The operand is specified.

unspecified: The operand is not specified.

cc....cc: Whether the aa....aa operand is specified in other nodes

specified: The operand is specified.

unspecified: The operand is not specified.

S:

Terminates processing.

Action:

Take corrective action according to the operand name of the server definition output for aa....aa. Then, restart the HADB server in the multi-node configuration.

If aa....aa is adb_auth_passwd_privkey_path

Make sure that the primary node and all secondary nodes have the same settings in regard whether the operand is specified and the specified content.

If aa....aa is adb_cmd_passwd_pubkey_path

Make sure that all nodes have the same settings in regard whether the operand is specified and the specified content.

If aa....aa is other than above

Make sure that all nodes have the same settings in regard whether the operand is specified.

KFAA50059-E

The HADB server in the multi-node configuration cannot start, because aa....aa. (M)

The HADB server in the multi-node configuration could not be started for the reason indicated by aa....aa.

aa....aa: Cause of the error

HA Monitor is not running

HA Monitor is not running.

even though only one host name is specified for the server definition adb_sys_multi_node_info, the worker node facility is not in use

Multi-node configuration with HA Monitor

Only one host name is specified in the adb_sys_multi_node_info operand from the server definition.

Multi-node configuration without HA Monitor

Even though only one host name is specified in the adb_sys_multi_node_info operand from the server definition, there is no definition for using worker nodes.

the total number of nodes is greater than 12

The number of all nodes exceed the upper limit of 12.

S:

Terminates processing.

Action:

Eliminate the error based on the cause of the error aa....aa that is output in the message.

If aa....aa is HA Monitor is not running

Start the HA Monitor by executing HA Monitor's monstart command, and then start the HADB server in the multi-node configuration.

If this message is output while HA Monitor is running, the following directory path might not be specified for the PATH environment variable of the HADB administrator. Therefore, HA Monitor's command might have failed.

Storage directory for HA Monitor's commands (/opt/hitachi/HAmon/bin)

In such cases, revise the PATH environment variable, and then start the HADB server in the multi-node configuration.

If aa....aa is even though only one host name is specified for the server definition adb_sys_multi_node_info, the worker node facility is not in use

After taking one of the following actions, start the HADB server in the multi-node configuration.

Multi-node configuration with HA Monitor

Specify two or more host names in the adb_sys_multi_node_info operand from the server definition.

Multi-node configuration without HA Monitor

To use worker nodes, add the adb_sys_multi_max_worker_nodes operand to the server definition.

If aa....aa is the total number of nodes is greater than 12

Correct the specified values of the adb_sys_multi_node_info and adb_sys_multi_max_worker_nodes operands from the server definition to meet the following formula. Then, start the HADB servers in the multi-node configuration.

(number-of-primary nodes + number-of-secondary nodes + number-of-worker nodes) ≤ 12

KFAA50060-W

An error occurred while accessing the access path search information log file. (path = aa....aa, func = "bb....bb", errno = cc....cc) (M)

An error occurred while accessing the access path search information log file.

aa....aa:

Path name of the file in which the error occurred

Either of the following file path names is output:

Access path search information log file

Management file for the access path search information log

bb....bb:

Details of the operation that caused the error (system call name)

open: Opening the file

close: Closing the file

read: Reading the file

write: Writing to the file

lseek: Changing the file offset

ftruncate: Truncating the file

fstat: Acquiring the file status

fsync: Synchronizing the files

cc....cc:

Error number

S:

Continues processing.

Action:

In the OS documentation, check the system call indicated by bb....bb and the error number indicated by cc....cc, and then eliminate the cause of the error.

KFAA50061-E

A aa....aa error occurred. (func = "bb....bb", errno = cc....cc) (M)

An error occurred in bb....bb of aa....aa.

aa....aa: Argument type that generated the error

system call

System call

library function

Library function

bb....bb:

Name of the function resulting in an error

cc....cc:

Error number

S:

Terminates processing.

Action:

Check the displayed function name error number in the OS documentation, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the displayed error number, execute the adbinfoget command to collect troubleshooting information. Then, contact the customer support center.

KFAA50063-I

A worker node was added to a multi-node configuration. (node number = aa....aa, host name = bb....bb, IP address = cc....cc) (M)

A worker node was added to the multi-node configuration.

aa....aa:

Node number of the added worker node

bb....bb:

Host name of the added worker node (communication between servers)

cc....cc:

IP address of the added worker node (communication between servers)

S:

Continues processing.

KFAA50064-E

A worker node could not be added to a multi-node configuration because aa....aa. (M)

The worker node cannot be added to the multi-node configuration.

aa....aa:

Cause of the error

S:

Terminates processing.

Action:

Take corrective action for the cause of the error displayed for aa....aa.

Display of aa....aa

Cause of the error

Corrective action to take

one of the HADB servers that composes the multi-node configuration is performing termination processing

One of the HADB servers in the multi-node configuration is performing termination processing.

Wait for completion of termination processing of the HADB server, and then perform the operation to add the worker node.

the primary node is performing switchover processing

Primary node switchover processing is in progress.

Wait for completion of primary node switchover processing, and then perform the operation to add the worker node.

another HADB server is being returned to the multi-node configuration

Another node is being returned to the multi-node configuration.

Wait for completion of processing to return to the multi-node configuration, and then perform the operation to add the worker node.

no more worker nodes can be added

An attempt was made to add more worker nodes than the maximum number of worker nodes.

After deleting the other worker nodes, execute the operation to add a worker node.

This message is also output when a worker node is added to a multi-node configuration without specifying the adb_sys_multi_max_worker_nodes operand in the server definition for the primary and secondary nodes. In this case, terminate the HADB server in the multi-node configuration once and specify the adb_sys_multi_max_worker_nodes operand in the server definition for the primary node and each secondary node. Then, start the HADB servers in the multi-node configuration and execute the operation to add a worker node.

the adbmodarea command is being executed on the primary node

The adbmodarea command is being executed on the primary node.

Wait for the completion of the adbmodarea command executing on the primary node.

Note that the DB directory configuration has been changed by executing the adbmodarea command. Therefore, execute the adbinit command to make the DB directory configuration the same as the primary node, and then execute the operation to add the worker node. For details on how to create the initialization option used when executing the adbinit command, see Notes on executing the adbinit command when adding a new secondary node in the manual HADB Setup and Operation Guide. When reading this section, replace the secondary node with a worker node.

the adbupddmk command is being executed on the primary node

The adbupddmk command is being executed on the primary node.

Wait for the completion of the adbupddmk command executing on the primary node. Then, execute the operation to add a worker node.

KFAA50068-E

The cloud storage facility cannot be used because aa....aa. (M)

Cloud storage facility is not available.

aa....aa:

Cause of the error

S:

Terminates processing.

Action:

Take the corrective action for the cause of the error displayed for aa....aa.

Display of aa....aa

Cause of the error

Corrective action

the server definition adb_sys_cld_cache_path is not specified

The adb_sys_cld_cache_path operand is not specified in the server definition even though the conditions for using the cloud storage facility are met.

Specify the adb_sys_cld_cache_path operand in the server definition. Then, restart the HADB server.

the initialization option adb_init_cld_cache_path is not specified

The adb_init_cld_cache_path operand is not specified in the initialization option even though the conditions for using the cloud storage facility are met.

Specify the adb_init_cld_cache_path operand in the initialization option. Then, re-execute the adbinit command.

multiple libraries for the cloud storage facility are installed

Multiple libraries for the cloud storage facility (HADB option) are installed.

Perform the following corrective actions:

When the cloud storage facility is used

Make sure that only the library for the cloud storage facility suitable for the environment where the HADB server is running is installed. For example, when running the HADB server in an AWS environment, only the library for the cloud storage facility for AWS should be installed. If the library for the cloud storage facility for Azure is installed, uninstall it.

When the cloud storage facility is not used

Uninstall all installed libraries for the cloud storage facility.

After performing the corrective action above, start the HADB server or re-execute the adbinit command.

due to a version mismatch between the HADB server and the library for the cloud storage facility

The versions of the HADB server and the library for the cloud storage facility (HADB option) are different.

When using the cloud storage facility, install the HADB option with the same version as the HADB server.

one or a combination of the adb_sys_cld_aws_region, adb_sys_cld_aws_bucket, and adb_sys_cld_endpoint operands is specified in the server definition even though the library for the cloud storage facility is not installed

The library for the cloud storage facility for AWS is not installed; however, one or more of the following operands related to the cloud storage facility have been specified in the server definition.

adb_sys_cld_aws_region operand

adb_sys_cld_aws_bucket operand

adb_sys_cld_endpoint operand

Perform the following corrective actions:

When the cloud storage facility is used

Install the library for the cloud storage facility for AWS and specify the following operands in the server definition.

When Amazon S3 is used:

adb_sys_cld_aws_region operand or adb_sys_cld_endpoint operand

adb_sys_cld_aws_bucket operand

When Amazon S3-compatible object storage is used:

adb_sys_cld_endpoint operand

adb_sys_cld_aws_bucket operand

If the KFAA50070-W message appears immediately before this message, the library for the cloud storage facility is installed, but the environment is not suitable for using the cloud storage facility. See the KFAA50070-W message and perform the corrective action.

If the cloud storage facility is not used

Do not specify adb_sys_cld_aws_region operand, adb_sys_cld_aws_bucket operand, and adb_sys_cld_endpoint operand in the server definition.

After performing the corrective actions above, restart the HADB server.

only one or an incorrect combination of the adb_sys_cld_aws_region, adb_sys_cld_aws_bucket, and adb_sys_cld_endpoint operands is specified in the server definition even though the library for the cloud storage facility is installed

The library for the cloud storage facility for AWS is installed; however, there is a discrepancy in the specification of the following operands related to the cloud storage facility in the server definition.

adb_sys_cld_aws_region operand

adb_sys_cld_aws_bucket operand

adb_sys_cld_endpoint operand

Perform the following corrective actions:

When the cloud storage facility is used

Specify the following operands in the server definition.

When Amazon S3 is used:

adb_sys_cld_aws_region operand or adb_sys_cld_endpoint operand

adb_sys_cld_aws_bucket operand

When Amazon S3-compatible object storage is used:

adb_sys_cld_endpoint operand

adb_sys_cld_aws_bucket operand

When the cloud storage facility is not used

Do not specify adb_sys_cld_aws_region operand, adb_sys_cld_aws_bucket operand, and adb_sys_cld_endpoint operand in the server definition.

After performing the corrective actions above, restart the HADB server.

one or a combination of the adb_init_cld_aws_region, adb_init_cld_aws_bucket, and adb_sys_cld_endpoint operands is specified for the initialization options even though the library for the cloud storage facility is not installed

The library for the cloud storage facility for AWS is not installed; however, one or more of the following operands related to the cloud storage facility have been specified in the initialization option.

adb_init_cld_aws_region operand

adb_init_cld_aws_bucket operand

adb_sys_cld_endpoint operand

Perform the following corrective actions:

When the cloud storage facility is used

Install the library for the cloud storage facility for AWS and specify the following operands in the initialization option.

When Amazon S3 is used:

adb_init_cld_aws_region operand or adb_sys_cld_endpoint operand

adb_init_cld_aws_bucket operand

When Amazon S3-compatible object storage is used:

adb_sys_cld_endpoint operand

adb_init_cld_aws_bucket operand

If the KFAA50070-W message appears immediately before this message, the library for the cloud storage facility is installed, but the environment is not suitable for using the cloud storage facility. See the KFAA50070-W message and perform the corrective action.

If the cloud storage facility is not used

Do not specify adb_init_cld_aws_region operand, adb_init_cld_aws_bucket operand, and adb_sys_cld_endpoint operand in the initialization option.

After performing the corrective action above, re-execute the adbinit command.

only one or an incorrect combination of the adb_init_cld_aws_region, adb_init_cld_aws_bucket, and adb_sys_cld_endpoint operands is specified for the initialization options even though the library for the cloud storage facility is installed

The library for the cloud storage facility for AWS is installed; however, there is a discrepancy in the specification of the following operands related to the cloud storage facility in the initialization option.

adb_init_cld_aws_region operand

adb_init_cld_aws_bucket operand

adb_sys_cld_endpoint operand

Perform the following corrective actions:

When the cloud storage facility is used

Specify the following operands in the initialization option.

When Amazon S3 is used:

adb_init_cld_aws_region operand or adb_sys_cld_endpoint operand

adb_init_cld_aws_bucket operand

When Amazon S3-compatible object storage is used:

adb_sys_cld_endpoint operand

adb_init_cld_aws_bucket operand

When the cloud storage facility is not used

Do not specify adb_init_cld_aws_region operand, adb_init_cld_aws_bucket operand, and adb_sys_cld_endpoint operand in the initialization option.

After performing the corrective action above, re-execute the adbinit command.

even though the library for the cloud storage facility is not installed, one or both of the adb_sys_cld_az_storage_account and adb_sys_cld_az_container operands are specified in the server definition or the initialization option

The library for the cloud storage facility for Azure is not installed, but one or both of the following operands are specified in the server definition or initialization option.

adb_sys_cld_az_storage_account operand

adb_sys_cld_az_container operand

If this message is output when starting the HADB server

Perform the following corrective actions:

When the cloud storage facility is used

Install the library for the cloud storage facility for Azure and specify the adb_sys_cld_az_storage_account and adb_sys_cld_az_container operands in the server definition.

If the KFAA50070-W message appears immediately before this message, the library for the cloud storage facility is installed, but the environment is not suitable for using the cloud storage facility. See the KFAA50070-W message and perform the corrective action.

If the cloud storage facility is not used

Do not specify adb_sys_cld_az_storage_account operand and adb_sys_cld_az_container operand in the server definition.

After performing the corrective actions above, restart the HADB server.

If this message is output when the command adbinit is executed

Perform the following corrective actions:

When the cloud storage facility is used

Install the library for the cloud storage facility for Azure and specify the adb_sys_cld_az_storage_account and adb_sys_cld_az_container operands in the initialization option.

If the KFAA50070-W message appears immediately before this message, the library for the cloud storage facility is installed, but the environment is not suitable for using the cloud storage facility. See the KFAA50070-W message and perform the corrective action.

If the cloud storage facility is not used

Do not specify the adb_sys_cld_az_storage_account operand and adb_sys_cld_az_container operand in the initialization option.

After performing the corrective action above, re-execute the adbinit command.

even though the library for the cloud storage facility is installed, either the adb_sys_cld_az_storage_account operand or the adb_sys_cld_az_container operand is specified in the server definition or the initialization option

The library for the cloud storage facility for Azure is installed, but only one of the following operands are specified in the server definition or initialization option.

adb_sys_cld_az_storage_account operand

adb_sys_cld_az_container operand

If this message is output when starting the HADB server

Perform the following corrective actions:

When the cloud storage facility is used

Specify the adb_sys_cld_az_storage_account operand and adb_sys_cld_az_container operand in the server definition.

When the cloud storage facility is not used

Do not specify adb_sys_cld_az_storage_account operand and adb_sys_cld_az_container operand in the server definition.

After performing the corrective actions above, restart the HADB server.

If this message is output when the command adbinit is executed

Perform the following corrective actions:

When the cloud storage facility is used

Specify the adb_sys_cld_az_storage_account operand and adb_sys_cld_az_container operand in the initialization option.

When the cloud storage facility is not used

Do not specify the adb_sys_cld_az_storage_account operand and adb_sys_cld_az_container operand in the initialization option.

After performing the corrective action above, re-execute the adbinit command.

KFAA50069-I

The library for the cloud storage facility was loaded. (library name = "aa....aa") (L+M)

The library for the cloud storage facility was loaded.

aa....aa: Type of library loaded

libadbcldstge-aws.so: Amazon S3 library or Amazon S3-compatible object storage library

libadbcldstge-azure.so: Azure Blob Storage library

S:

Continues processing.

KFAA50070-W

An attempt to load the library for the cloud storage facility failed. (reason = "aa....aa") (L+M)

Failed to load the library for the cloud storage facility.

aa....aa:

Cause for failure to load

S:

Assuming that the library for the cloud storage facility is not installed, the process continues.

Action:

For AWS environment or Amazon S3-compatible object storage environment

If the cause of the load failure is the absence of a specific shared library, take the following corrective actions.

See Checking prerequisite packages in Tasks that must be performed before HADB server installation in the HADB Setup and Operation Guide and install the required packaged for using the cloud storage facility to the instance where the HADB server is installed.

If you do not use the cloud storage facility and this message is output, remove the library for the cloud storage facility (libadbcldstge-aws.so) from under the $ADBDIR/lib directory.

For Azure environment

If the cause of the load failure is the absence of a specific shared library, take the following corrective actions.

Check the OS version of the virtual machine. If the OS version is RHEL 8 or earlier, upgrade to RHEL 9 or later.

See Checking prerequisite packages in Tasks that must be performed before HADB server installation in the HADB Setup and Operation Guide and install the required packaged for using the cloud storage facility to the virtual machine where the HADB server is installed.

If you do not use the cloud storage facility and this message is output, remove the library for the cloud storage facility (libadbcldstge-azure.so) from under the $ADBDIR/lib directory.

KFAA50071-W

The AWS CLI is not installed, or execution of the AWS CLI command failed. (L+M)

AWS CLI is not installed. Or the AWS CLI command failed to execute.

S:

Continues processing.

Action:

Take the following corrective actions:

Install the AWS CLI so that the aws command is stored in either:

/usr/local/bin/aws

/usr/bin/aws

For details about how to install AWS CLI, see Installing AWS CLI in Building a HADB server in an AWS environment in the HADB Setup and Operation Guide.

If you have already installed AWS CLI, create a symbolic link so that you can execute the aws command in the above path.

Modify the execution environment so that the following AWS CLI commands can be executed correctly

aws ec2 describe-instance-types

For details about how modify the execution environment, see Installing AWS CLI in Building a HADB server in an AWS environment in the HADB Setup and Operation Guide.

Modify the execution environment to allow the use of EC2 Instance Metadata Service (IMDSv2)

The EC2 instance metadata is obtained using IMDSv2 when the HADB server is started. Modify the execution environment so that you can use IMDSv2.

When this warning message is output, the resource cannot be utilized because it cannot perform the appropriate processing for the instance type of the instance that is starting the HADB server. As a result, performance may be affected.

KFAA50072-E

The Azure CLI is not installed. (L+M)

Azure CLI is not installed.

S:

Terminates processing.

Action:

Install Azure CLI. For details about how to install Azure CLI, see Installing Azure CLI in Building a HADB server in an Azure environment in the HADB Setup and Operation Guide.

When using cloud storage facility in an Azure environment, authentication via Azure CLI is recommended. Therefore, please configure your environment so that Azure CLI can be run correctly. For details about authentication with Azure CLI, see Setting the authentication information required to access Azure Blob Storage in Building a HADB server in an Azure environment in the HADB Setup and Operation Guide.

KFAA50073-I

aa....aa(bb....bb) is not supported. (file = cc....cc, line = dd....dd) (M)

Operands or options specified in the definition file are not supported.

aa....aa:

A command: Operand in the command format

An option: Operand option in the command format

An operand: Operand in the set format

bb....bb:

If aa....aa is A command: Operand name in the command format

If aa....aa is An option: Operand option name in the command format

If aa....aa is An operand: Operand name in the set format

cc....cc:

Definition file name

dd....dd:

Row number with unsupported operands or options specified

S:

Continues processing.

This message is output when INFORMATION os specified for the environment variable ADB_DEFFILE_UNSUPPORTED_OPERAND_BEHAVIOR. For the environment variable ADB_DEFFILE_UNSUPPORTED_OPERAND_BEHAVIOR, see the following.

Set the environment variables in the manual HADB Setup and Operation Guide

Set the environment variables in the manual HADB Command Reference

KFAA50100-E

The specified server definition value is invalid. (name = aa....aa, value = "bb....bb") (M)

The value specified in a server definition operand was invalid.

aa....aa:

Name of the server definition operand

bb....bb:

Value specified in the server definition operand

S:

Terminates processing.

Action:

Correct the value specified in the server definition operand.

KFAA50101-I

The work table DB area was initialized. (page size = aa....aa KB, file = "bb....bb") (M)

A work table DB area was initialized.

aa....aa:

Page size of the work table DB area (KB)

bb....bb: Type of the work table DB area file

ADBWRK: Regular file

Other: Block special file

S:

Continues processing.

KFAA50102-E

Initialization of the work table DB area failed. (M)

Initialization of a work table DB area failed.

S:

Terminates processing.

Action:

Check the error message output preceding this error message. Eliminate the cause of the error as indicated for that error message.

KFAA50103-E

The work table DB area information cannot be found. (M)

The information for a work table DB area cannot be found.

S:

Terminates processing.

Action:

The cause could be either of the following:

The wrong block special file was assigned to the master directory DB area

Assign the correct block special file.

The contents of the master directory DB area are corrupted

Restore the contents from back-up.

KFAA50104-E

The file "aa....aa" is invalid. (M)

The file aa....aa is invalid.

aa....aa:

File name

S:

Terminates processing.

Action:

The cause could be either of the following:

The wrong block special file was assigned

Assign the correct block special file.

The file is corrupted

Restore the file from back-up.

KFAA50105-E

The cloud object "aa....aa" does not exist. (M)

The S3 object aa....aa or BLOB aa....aa does not exist.

aa....aa:

S3 object name or BLOB name

S:

Terminates processing.

Action:

For AWS environment or Amazon S3-compatible object storage environment

The following are possible causes for the S3 bucket specified in the server definition adb_sys_cld_aws_bucket operand.

The database has not been initialized using the adbinit command.

The server definition's adb_sys_cld_aws_bucket operand specifies an invalid S3 bucket name.

Deleted intentionally or due to operational error.

For Azure environment

The following are possible causes for the container specified in the server definition adb_sys_cld_az_container operand.

The database has not been initialized using the adbinit command.

The server definition's adb_sys_cld_az_container operand specifies an invalid container name.

Deleted intentionally or due to operational error.

Eliminate the cause of the error and then re-execute the adbstart command.

KFAA50108-I

The block special file "aa....aa"(bb....bb) is initialized. (S+L+M)

The block special file aa....aa was initialized.

aa....aa:

Name of the block special file that was initialized

bb....bb: Path name of the aa....aa object

If the object path name was specified when the block special file was initialized, the path names output for aa....aa and bb....bb are the same.

S:

Continues processing.

KFAA50112-E

A system call error occurred. (func = "aa....aa", errno = bbb) (E+M)

System call aa....aa generated an error.

aa....aa:

System call that caused the error

bbb:

Error number

S:

Terminates processing.

Action:

Check the OS documentation for the displayed system call name and error number, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number, execute the adbinfoget command, collect troubleshooting information, and then contact the customer support center.

KFAA50116-E

Disk capacity is insufficient. (E+M)

There is an insufficient amount of disk capacity available.

S:

Terminates processing.

Action:

Take one of the following corrective actions, and then re-execute the command.

Increase the free space on the disk

If the disk has enough free space for initialization, check whether the file system has reached its limit or the disk quota has reached the maximum.

Reduce the initial allocation size of the file

KFAA50117-E

A path is not a regular file or a symbolic link. (name = "aa....aa") (E+M)

The path displayed in place of aa....aa is not a regular file path or symbolic link path.

aa....aa:

Path name

S:

Terminates processing.

Action:

Check and, if necessary, revise the specified DB area name and the path attribute displayed in place of aa....aa.

KFAA50122-E

The aa....aa bb....bb operation failed. (name = "cc....cc") (E+M)

The bb....bb processing of aa....aa failed.

aa....aa: Processing target

file: File

directory: Directory

DB area: DB area

encryption key: HADB encryption key or data encryption key

cloud storage: Cloud storage

bb....bb: Processing information

create: Creation processing

delete: Deletion processing

open: Open processing

close: Close processing

write: Write processing

read: Read processing

readlink: Link acquisition processing for symbolic link

initialize: Initialization processing

add: Processing to add DB area

remove: Processing to delete DB area

expand: Processing to expand DB area

cc....cc:

Name of operation target

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the corrective action given for the message that was output immediately prior to this message, and then re-execute the command.

KFAA50123-E

The aa....aa path is invalid. (reason = "bb....bb", path = "cc....cc") (E+M)

The specification for the aa....aa path is invalid.

aa....aa: Type of path

directory: Directory

file: File

bb....bb: Cause of the error

too short: The path name specified is smaller than the minimum length.

too long: The path name specified exceeds the maximum length.

not directory: The path specified is not a directory.

not exist: The path name specified does not exist.

invalid permission: Access privilege for the specified path has not been granted.

system call error: A system call generated an error.

duplicate: The path name specification is duplicated.

not block special file: The path specified is not a block special file.

cc....cc:

Path name

S:

Terminates processing.

Action:

Correct the specification of the path displayed in place of aa....aa. Then, re-execute the command.

If bb....bb is duplicate, one of the following pairs duplicate each other.

A block special file and a block special file

A DB directory, or a directory where a data DB area file will be stored, and a server directory

An initialization option file or DB area addition and modification option file and a DB area file

A location where a data DB area file will be stored and a directory under the DB directory

Any directory (other than a regular file or symbolic link) and a data DB area file

For details about the directories under the DB directory, see Directories that are created under adbinit (Initialize the Database) in the manual HADB Command Reference.

KFAA50134-E

The mounted block special file "aa....aa" is specified. (E+M)

A mounted block special file aa....aa was specified.

aa....aa:

Block special file that was specified

S:

Terminates processing.

Action:

Check whether it is okay to delete the data in the block special file. If deleting the data is okay, unmount the block special file, and then retry the operation.

If this message is output while the file is unmounted, the block special file might have been mistakenly registered in /etc/mtab. In that case, try using a method such as one of the following to restore the content of /etc/mtab:

Use the umount command to delete invalid registration.

Change the /etc/fstab settings, as necessary, and re-start the OS.

KFAA50135-E

The block special file "aa....aa" is allocated to the existing DB area file "bb....bb". (E+M)

The DB area file bb....bb has already been created in the specified block special file aa....aa.

aa....aa:

Block special file name

bb....bb:

Existing DB area file name (if it has an extension, with that extension)

S:

Terminates processing.

Action:

The DB area file to be added must be allocated to an unused block special file. Take one of the following corrective actions:

Change the specification of the block special file aa....aa that was specified in the -v option. (Specify an unused block special file.)

If the DB area created in the block special file aa....aa is not needed, delete that DB area.

KFAA50140-E

The symbolic link "aa....aa" is invalid. (reason = "bb....bb") (E+M)

A symbolic link is invalid.

aa....aa:

DB area file name (if it has an extension, with that extension)

bb....bb: Cause of the error

too long: The path name of the link target exceeds 255 bytes.

mounted: The block special file at the link target is mounted.

duplicate: A symbolic link duplicates the link target.

S:

Terminates processing.

Action:

A symbolic link might have been corrected inaccurately. Correct the symbolic link or restore the symbolic link file from backup.

KFAA50143-I

The number of segments created for each file to be initialized in the DB area "aa....aa" is bb....bb. (M)

The number of segments created for each DB area file in the DB area to be initialized is bb....bb.

aa....aa:

Name of the DB area to be initialized

bb....bb:

Number of segments created for each DB area file

S:

Continues processing.

KFAA50144-E

Initialization of the file "aa....aa" failed because of insufficient free disk space. (required free space = bb....bb KB) (M)

An error occurred during initialization of the file because of insufficient free disk space.

aa....aa:

Name of the file in which the error occurred (including extension, if any)

bb....bb:

Required free disk space (KB)

S:

Terminates processing.

Action:

Take one of the following corrective actions, and then re-execute the command.

Expand the disk space at the write destination.

Specify a smaller value for the initial allocation size of the DB area file.

For regular files, the following corrective action is also possible.

Increase the free space in the file system.

KFAA50150-I

The bb....bb processing of the DB area "aa....aa" has started on this node. (M)

The bb....bb processing of the DB area aa....aa has started on the node that output this message.

aa....aa:

DB area name

bb....bb: Processing of the DB area

add: Addition

remove: Deletion

expand: Expansion

S:

Continues processing.

KFAA50151-I

The bb....bb processing of the DB area "aa....aa" has ended on this node. (M)

The bb....bb processing of the DB area aa....aa has ended on the node that output this message.

aa....aa:

DB area name

bb....bb: Processing of the DB area

add: Addition

remove: Deletion

expand: Expansion

S:

Continues processing.

KFAA50152-I

The bb....bb processing of the DB area "aa....aa" has been canceled on this node. (M)

The bb....bb processing of the DB area aa....aa was canceled on the node that output this message.

aa....aa:

DB area name

bb....bb: Processing of the DB area

add: Addition

remove: Deletion

expand: Expansion

S:

Continues processing.

KFAA50153-E

An error occurred on node number aa....aa. (IP address = bb....bb) (M)

An error occurred on the node with node number aa....aa.

aa....aa:

Node number of the node where the error occurred

bb....bb:

IP address of the node where the error occurred

S:

Terminates processing.

Action:

See the error message output to the message log file for the node with node number aa....aa, and then take the corrective action for the cause of the error.

KFAA50154-E

DB area files cannot be created on node number aa....aa because the node is not working. (IP address = bb....bb) (M)

DB area files cannot be created on the node with node number aa....aa because the node with node number aa....aa is stopped.

aa....aa:

Node number of the stopped node

bb....bb:

IP address of the stopped node

S:

Terminates processing.

Action:

Return the stopped node displayed in aa....aa to the multi-node configuration. Then, retry the operation. For details about how to return the node to the multi-node configuration, see Returning a node to the multi-node configuration in the HADB Setup and Operation Guide.

KFAA50156-E

It is necessary to specify block special files in multi-node configurations. Block special files have not been specified to be allocated to the DB area "aa....aa". (M)

DB area files in the DB area aa....aa have not been allocated for block special files. When the multi-node function is used, DB area files must be allocated for block special files.

aa....aa:

DB area name

S:

Terminates processing.

Action:

To add or expand the DB area when the multi-node function is used, specify block special files in the adbaddarea operand or the -v option of the adbexpandarea operand.

KFAA50157-E

The block special file "bb....bb" that you are trying to allocate to the DB area file "aa....aa" on this node is different from the block special file that is allocated to the primary node. (information1 = cc....cc, information2 = dd....dd) (M)

The following two block special files are different.

Block special file bb....bb that you tried to allocate to the DB area file aa....aa on the node that output this message

Block special file allocated on the primary node

aa....aa:

DB area file name (if there is an extension, with the extension)

bb....bb:

Link target path of aa....aa

cc....cc:

Maintenance information 1

dd....dd:

Maintenance information 2

S:

Terminates processing.

Action:

Check whether bb....bb is a block special file that can be shared with all nodes.

KFAA50158-E

A block special file that cannot be shared with node number aa....aa is specified. (IP address = bb....bb) (M)

A block special file that cannot be shared with the node with node number aa....aa is specified.

aa....aa:

Node number of the node

bb....bb:

IP address of the node

S:

Terminates processing.

Action:

See the KFAA50157-E message output to the message log file for the node with node number aa....aa, and identify the block special file that cannot be shared. Then, specify a block special file that can be shared with all nodes, in place of the block special file you identified.

KFAA50159-W

An attempt to delete DB area files on node number aa....aa failed, but operation is not affected. (IP address = bb....bb) (M)

An attempt to delete DB area files failed on the node with node number aa....aa. However, operation is not affected.

aa....aa:

Node number of the node

bb....bb:

IP address of the node

S:

Continues processing.

Action:

See the KFAA96219-W message output to the message log file for the node with node number aa....aa, and determine the DB area file that failed to be deleted. Then, manually delete the DB area file.

Note that the DB area file that failed to be deleted can remain as is without affecting operation.

KFAA50160-I

The symbolic link "aa....aa"(bb....bb) was created. (M)

A symbolic link for the DB area file is created.

aa....aa:

DB area file name (if there is an extension, with the extension)

bb....bb:

Path name of the link target

S:

Continues processing.

KFAA50161-I

The result of the aa....aa processing of DB area "bb....bb" will be not applied to worker node cc....cc, because worker node cc....cc is not running. (M)

The worker node with node number cc....cc is not operating. Therefore, the results of processing aa....aa for the data DB area bb....bb will not be applied to the worker node with node number cc....cc.

aa....aa: Processing of the data DB area

addition: Addition

expansion: Expansion

bb....bb:

Data DB area name

cc....cc:

Node number of the worker node

S:

Continues processing.

Action:

Before adding the worker node with node number cc....cc to the multi-node configuration, execute the adbinit command on the worker node with node number cc....cc to create or recreate the DB directory.

KFAA50162-E

Processing to add the DB area "aa....aa" for the data to be encrypted was canceled, because the HADB encryption key does not exist. (M)

Because the HADB encryption key does not exist, the process of adding a data DB area to be encrypted was aborted.

aa....aa:

Data DB area name

S:

Terminates processing.

Action:

Take one of the following corrective actions, and then re-execute the adbmodarea command.

If encrypting the data DB area displayed in aa....aa

Specify the HADB encryption key file to the server definition's adb_crypto_dmkey_path operand, then restart the HADB server.

If not encrypting the data DB area displayed in aa....aa

Remove the -e option specified in the adbaddarea operand of the DB area addition and modification option of the adbmodarea command.

KFAA50163-E

There is a problem with the HADB encryption key used for this node. (reason = "aa....aa") (M)

There is a problem with the HADB encryption key in use.

aa....aa: Cause of the error

not exist: The HADB encryption key does not exist.

invalid: The HADB encryption key is invalid.

S:

Terminates processing.

Action:

If this message is output on the secondary node

Specify the same HADB encryption key file as the primary node for the server definition's adb_crypto_dmkey_path operand. Then, restart the HADB server.

If this message is output on a worker node

Specify the same HADB encryption key file as the primary node for the server definition's adb_crypto_dmkey_path operand. Then, add a worker node to the multi-node configuration.

KFAA50164-E

Some or all data writes of DB area "aa....aa" to the bucket failed. (cached size = bb....bb KB, object names = "ADBDIRP/cccc/[ddddddd-eeeeeee]/*") (M)

Writing data to the DB area aa....aa in the S3 bucket or container failed in part or in whole.

aa....aa:

DB area name

bb....bb:

Size of cached data (unit: kilobytes)

cccc:

DB area ID of DB area aa....aa

ddddddd:

Area control number in DB area aa....aa

eeeeeee:

Area control number in DB area aa....aa

S:

Terminates processing.

Action:

Check the messages that were output before this message, and eliminate the cause of the error. Once this is done, re-execute the command.

Note that, in the AWS environment or in the Amazon S3-compatible object storage environment, some of the cached data output to bb....bb may have been written to the S3 bucket as a group of S3 objects output in object names. Delete the S3 object manually as needed.

In the Azure environment, some of the cached data output to bb....bb may have been written to the container as a group of BLOBs output to object names. Delete the BLOB manually as necessary.

For details about object names, see the KFAA96248-I message.

KFAA50165-E

When the cloud storage facility is used, block special files cannot be specified. (M)

When using the cloud storage facility, block special files cannot be assigned to DB area files (except for work table DB area files).

S:

Terminates processing.

Action:

Delete all of the following operands and options, and then re-execute the command.

adb_init_mst_blk_path operand

adb_init_dic_blk_path operand

adb_init_stbl_blk_path operand

adbinitdbarea operand, adbaddarea operand, and adbexpandarea operand -v option

KFAA50166-E

When the cloud storage facility is used, you must specify bb....bb for the aa....aa option. (DB area name = "cc....cc") (M)

If you want to use the cloud storage facility, bb....bb must be specified to the aa....aa option.

aa....aa:

Option name

bb....bb:

Value to be specified to the aa....aa option

cc....cc:

DB area name to which the aa....aa option is applied

S:

Terminates processing.

Action:

Specify bb....bb to the aa....aa option of DB area cc....cc, then re-execute the command.

KFAA50167-I

An I/O processing error occurred with the aa....aa. (information1 = "bb....bb", information2 = "cc....cc") (M)

An error occurred during input processing for aa....aa.

aa....aa: Input destination

cache file: Cache file

cloud storage: Cloud storage

bb....bb:

Maintenance information 1

cc....cc:

Maintenance information 2

S:

Continues processing.

KFAA50168-I

Cloud objects that compose the DB area "aa....aa" will be removed. (object names = "ADBDIRP/bbbb/[ccccccc-ddddddd]/*") (M)

Deletes the S3 object or BLOB that stores the data in DB area aa....aa.

aa....aa:

DB area name

bbbb:

DB area ID of DB area aa....aa

ccccccc:

Area control number in DB area aa....aa

ddddddd:

Area control number in DB area aa....aa

S:

Continues processing.

Action:

After this message is output, the deletion process may be terminated due to abnormal termination of the HADB server before the KFAA50169-I message is output. In this case, perform the following corrective actions:

For AWS environment or Amazon S3-compatible object storage environment

Verify that the group of S3 objects output to object names exists in the S3 bucket. If a group of S3 objects exists, delete them manually.

For Azure environment

Check to see if the BLOB groups output to object names are present in the container. If a group of BLOBs exists, delete the BLOBs manually.

For details about object names, see the KFAA96248-I message.

KFAA50169-I

Cloud objects that compose the DB area "aa....aa" were removed. (object names = "ADBDIRP/bbbb/[ccccccc-ddddddd]/*", number of objects = ee....ee) (M)

The S3 object or BLOB that stores the data in DB area aa....aa has been deleted.

aa....aa:

DB area name

bbbb:

DB area ID of DB area aa....aa

ccccccc:

Area control number in DB area aa....aa

ddddddd:

Area control number in DB area aa....aa

ee....ee: Number of S3 objects or BLOBs deleted

The number of S3 objects or BLOBs actually deleted may differ because deletion processing for nonexistent S3 objects or BLOBs is also included in the count.

S:

Continues processing.

Action:

For details about object names, see the KFAA96248-I message.

KFAA50171-I

Memory is insufficient, so remove cloud objects one by one. (M)

Delete S3 objects or BLOBs one by one due to insufficient memory.

S:

Ignores the memory insufficiency and continues processing.

Action:

The deletion process takes longer than when there is no memory shortage.

If you abort the deletion process with the adbcancel command, manually delete any S3 objects or BLOBs that remain undeleted.

KFAA50172-W

The processing to remove cloud objects after a transaction commit or rollback was canceled midway. (M)

The delete processing of an S3 object or BLOB after a transaction commit or rollback has been canceled.

S:

Delete processing of S3 objects or BLOBs is aborted.

Action:

Of the S3 objects or BLOBs to be deleted, manually delete S3 objects or BLOBs that were not deleted.

The S3 objects or BLOBs to be deleted can be checked in the KFAA50168-I message.

KFAA50201-E

The aa....aa command cannot be executed because the bb....bb command was stopped. (M)

The aa....aa command cannot be executed because the bb....bb command has not terminated normally.

aa....aa:

Name of the command that cannot be executed

bb....bb:

Name of the command that has not terminated normally

S:

Terminates processing.

Action:

Re-execute the bb....bb command.

To re-execute the adbimport command, use the re-execute facility that starts from the processing to create B-tree indexes and text indexes of the adbimport command.

To re-execute the adbidxrebuild command, use the re-execute facility of the adbidxrebuild command.

KFAA50202-E

Table "aa....aa"."bb....bb" is not found in the system. (M)

The specified schema name or table identifier does not exist.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Terminates processing.

Action:

Correct the schema name or table identifier, and then re-execute the command. If there is no table to be specified by the command, define the schema and table, and then re-execute the command.

KFAA50203-E

The table "aa....aa"."bb....bb" cannot be specified for the table name. (M)

The command cannot be executed for one of the following reasons:

The table specified when executing the command is not a base table.

The table specified when executing the adbreorgsystemdata command is neither a dictionary table nor a system table.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Terminates processing.

Action:

Correct the schema name or table identifier that is specified, and then re-execute the command.

KFAA50204-E

The aa....aa is invalid because bb....bb. (M)

aa....aa is invalid. The cause is bb....bb.

aa....aa:

Command that was executed

bb....bb: Cause of the error

the -c option is specified in the viewed table: The -c option is specified for a viewed table.

the -c option is specified in the non-multi-chunk table: The -c option is specified for a single-chunk table.

export data output file exists: The file specified as the output data path file already exists.

S:

Terminates processing.

Action:

Eliminate the cause of the error displayed in place of bb....bb, and then re-execute the adbexport command.

KFAA50205-E

The option argument is invalid. (command name = aa....aa, option = bb....bb, reason = cc....cc) (E+M)

The option argument of the command is invalid.

aa....aa:

Executed command

bb....bb:

Invalid option argument

cc....cc:

Cause of the error

S:

Terminates processing.

Action:

If the command executed (aa....aa) is adbdbstatus

Change the value specified for chunk-ID-list-to-be-analyzed in the -c option of the adbdbstatus command, and then re-execute the command. The following describes the causes of the error and the corrective action to take.

If the cause of the error (cc....cc) is An invalid character was specified.

Characters that cannot be used or that are grammatically incorrect are specified for chunk-ID-list-to-be-analyzed.

Example of incorrect specification: -c 1-2-3

Example of correct specification: -c 1-3

If the cause of the error (cc....cc) is The specified value is outside the valid range.

A numeric value outside the range of chunk IDs is specified for chunk-ID-list-to-be-analyzed. Specify a value from 1 to 9,223,372,036,854,775,807 for the chunk ID.

If the cause of the error (cc....cc) is The value on the right side is equal to or less than the value on the left side.

When a range of chunk IDs is specified for chunk-ID-list-to-be-analyzed, the value-to-the-left-of-the-hyphen is equal to or greater than the value-to-the-right-of-the-hyphen. Correct the specification so that the value-to-the-left-of-the-hyphen is less than the value-to-the-right-of-the-hyphen.

Example of incorrect specification: -c 5-2

Example of correct specification: -c 2-5

If the cause of the error (cc....cc) is The specified value exceeds the maximum value that can be specified.

The number of chunk IDs specified for chunk-ID-list-to-be-analyzed exceeds 30,000. Reduce the number of chunk IDs to 30,000 or fewer.

For details about the specification rules for chunk-ID-list-to-be-analyzed in the -c option of the adbdbstatus command, see the following: Explanation of options in Explanation of the specification format and options (outputting information about the need for reorganization of column store tables) in Specification format for the adbdbstatus command in the manual HADB Command Reference.

If the command executed (aa....aa) is adbimport

Re-execute the command with the correct option arguments specified for the -f option of the adbimport command. The following describes the causes of the error and the corrective action to take.

If the error cause (cc....cc) is A fixed-length format is specified for a table that includes an array-type column.

When importing into a table that defines an array-type column, the file format of the input data file is a fixed-length format. Specify CSV format.

KFAA50206-E

An invalid record was found in the index record file aa....aa. (reason = bb....bb) (M)

There is an invalid record among the records in the index record file aa....aa.

aa....aa:

Name of index record file being created by the HADB server

bb....bb: Cause of the error

Tally-length: The total record length, which is fixed length, is not an integer multiple.

Variable-record: The data part length, which is variable length, is invalid.

S:

Terminates processing.

Action:

The index record file is corrupted. Because of this, you must re-execute the command from the beginning.

KFAA50207-E

The option argument is invalid. (command name = aa....aa, option name = bb....bb, option arg = "cc....cc", rows = dd....dd, operand name = ee....ee, operand option name = ff....ff, operand option arg = "gg....gg", reason = hh....hh) (E+M)

The specification of the option file specified in the aa....aa is invalid.

aa....aa: Executed command name

adbchgchunkstatus command

bb....bb: Option argument specifying the option file

-m option

cc....cc:

Value specified for the option argument#1

dd....dd:

Row number#3, #4

ee....ee:

Operand name#4

ff....ff:

Option argument of the operand#2, #3, #4

gg....gg:

Value specified for the option argument of the operand#2, #3, #4, #5, #6

hh....hh:

Cause of the error

#1:

Up to 512 bytes are displayed.

#2:

If the output of hh....hh is No. 15 in the table of corrective actions, * is displayed.

#3:

If the output of hh....hh is No. 16 in the table of corrective actions, * is displayed.

#4:

If the output of hh....hh is No. 17 in the table of corrective actions, * is displayed.

#5:

If a comma-separated list is specified, only the arguments where the error occurred will be displayed.

For example, the -w option displays the chunk ID of the chunk to be changed to the wait status where the error occurred, and the -n option displays the chunk ID of the chunk to be changed to the normal status where the error occurred.

#6:

If the output of hh....hh is No. 7 to 14 in the table of corrective actions, the table name is displayed in the format of "schema-name.table-identifier".

Enclosing characters are not displayed. In addition, lowercase alphabetic characters not surrounded by enclosing characters are displayed in uppercase alphabetic characters.

S:

Terminates processing.

Action:

Review the specification of the option file specified in the -m option of the adbchgchunkstatus command according to the following table. Then, re-execute the adbchgchunkstatus command.

No.

Information output to ee....ee

Information output to ff....ff

Information output to hh....hh

Error causes and corrective actions

1

adbchunkstatus

-w

or

-n

An invalid character was specified.

Characters that cannot be used or that are grammatically incorrect are specified.

Example of incorrect specification: -w 1-2-3

Example of correct specification: -w 1-3

2

The specified value is outside the valid range.

A value that is outside the specification chunk ID range was specified. Specify a value from 1 to 9,223,372,036,854,775,807 for the chunk ID.

3

The value on the right side is equal to or less than the value on the left side.

When a range of chunk IDs is specified, the value-to-the-left-of-the-hyphen is equal to or greater than the value-to-the-right-of-the-hyphen. Correct the specification so that the value-to-the-left-of-the-hyphen is less than the value-to-the-right-of-the-hyphen.

Example of incorrect specification: -w 5-2

Example of correct specification: -w 2-5

4

The specified value exceeds the maximum value that can be specified.

The maximum number of specified chunk IDs exceeds 29,999. Reduce the number of chunk IDs to 29,999 or fewer.

5

-t

The option is not specified.

No option is specified. Specify the table to be processed.

6

The invalid table name is specified.

The specification format of the specified table name is invalid. Specify the table name in the format "schema-name"."table-identifier". If the user owns the table, the schema name can be omitted.

7

The specified table does not exist.

The specified table does not exist. Specify an existing table.

8

The HADB user who executed the command does not have the CHANGE CHUNK STATUS privilege for the specified table.

The HADB user who executed the command does not have CHANGE CHUNK STATUS privilege for the specified table. Grant CHANGE CHUNK STATUS privilege to the HADB user executing the command. For details about how to grant CHANGE CHUNK STATUS privilege, see Granting access privileges to an HADB user in the HADB Setup and Operation Guide.

However, if the schema of the specified table is different from the authorization identifier of the HADB user who executed the command, the specified table itself may not exist.

9

The specified table is not a base table.

The specified table is not a base table. Specify a base table.

10

The specified table is not a multi-chunk table.

The adbchgchunkstatus command could not be executed because the specified table is a single-chunk table.

11

The specified table is an archivable multi-chunk table.

The adbchgchunkstatus command could not be executed because the specified table is an archivable multi-chunk table.

12

The adbimport command was stopped for the specified table.

The table for which the execution of the adbimport command was interrupted is specified. Re-execute the adbimport command and then specify the table. For details, see Handling abnormal termination of the adbimport command in the HADB Command Reference.

13

The adbidxrebuild command was stopped for the specified table.

The table for which the execution of the adbidxrebuild command was interrupted is specified. Re-execute the adbidxrebuild command and then specify the table. For details, see Handling abnormal termination of the adbidxrebuild command in the HADB Command Reference.

14

The same table is already specified.

The same table is already specified. The same table cannot be specified more than once. Therefore, specifications for the same table should be specified with a single adbchunkstatus operand.

15

*

Neither the -w option nor the -n option is specified.

Neither the -w option nor the -n option is specified. Make sure to specify one or both.

16

The specified number of adbchunkstatus items exceeds 32.

The specified number of adbchunkstatus operands exceeds 32. Limit the number of specified adbchunkstatus operands to 32 or less.

17

*

*

Analysis of the file ended with an error.

Failed to analyze the option file. Check the error messages that were output before this message, and eliminate the cause of the error.

KFAA50209-E

The index must be recreated to access the table. (index = "aa....aa"."bb....bb", DB area = "cc....cc") (M)

An attempt was made to access an index that was in unfinished status.

aa....aa:

Schema name

bb....bb:

Index identifier

cc....cc:

DB area name

S:

Terminates processing.

Action:

For the action to be taken if an index is placed in unfinished status, see either of the following sections (whichever is applicable) in the HADB Setup and Operation Guide: Steps to take when unfinished status is applied to a B-tree index.

For the action to be taken if a text index is placed in unfinished status, see Steps to take when unfinished status is applied to a text index in the HADB Setup and Operation Guide.

For the action to be taken if a range index is placed in unfinished status, see Steps to take when unfinished status is applied to a range index in the HADB Setup and Operation Guide.

KFAA50210-E

An error occurred in the table during aa....aa processing. The table is "bb....bb"."cc....cc". (M)

An error occurred in a table while aa....aa was being processed.

aa....aa: The processing that caused the error

scan: Line scan processing

delete: Line deletion processing

insert: Line insertion processing

index generate: Index creation processing

directory update: Directory update processing

directory reference: Directory reference processing

chunk update: Chunk update processing

privilege check: Access privilege check processing

bb....bb:

Schema name

cc....cc:

Table identifier

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the messages that were output prior to this message. Then, re-execute the command.

Restore the database if necessary, and then re-execute the command. For details about how to restore the database, see the corrective action to take when a command terminates abnormally in the manual HADB Command Reference.

KFAA50211-E

The defined information aa....aa could not be acquired. (table = "bb....bb"."cc....cc") (M)

Definition information aa....aa could not be acquired.

aa....aa: Type of definition information that could not be acquired

table: Table definition information

column: Column definition information

index: Index definition information

bb....bb:

Schema name

cc....cc:

Table identifier

S:

Terminates processing.

Action:

An error might have occurred during dictionary table (base table) I/O. Check whether a disk failure has occurred. If you cannot ascertain the cause of the error, contact the customer support center.

Restore the database if necessary, and then re-execute the command. For details about how to restore the database, see the corrective action to take when a command terminates abnormally in the manual HADB Command Reference.

KFAA50212-E

The defined information aa....aa could not be acquired. (schema = "bb....bb") (M)

The aa....aa type of definition information could not be acquired.

aa....aa: Type of definition information that could not be acquired

table: Table definition information

bb....bb:

Schema name

S:

Terminates processing.

Action:

An input/output error might have occurred on the dictionary table (base table).

Eliminate the cause of the error based on the messages that were output prior to this message.

You might need to recover the dictionary DB area. For details about how to recover the database from the backup, see Recovering the database from the backup in the HADB Setup and Operation Guide.

KFAA50213-E

The defined information could not be acquired. (M)

The definition information for the dictionary table (base table) could not be acquired.

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the messages that were output prior to this message.

KFAA50214-E

The DB status information could not be acquired. (M)

The DB status analysis results could not be acquired.

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the messages that were output prior to this message.

The adbdbstatus command has output the DB status analysis results to the standard output during information acquisition processing. Therefore, this message might be output if a communication error occurred during information acquisition processing (if the KFAA50301-E message is output).

KFAA50215-E

An error occurred during storage of data. (input file = aa....aa, row number = bb....bb) (M)

An error occurred when data was being stored in the bb....bbth line.

aa....aa:

The serial number or file name of the input file

bb....bb:

Row number

S:

Terminates processing.

Action:

Check the error messages that were output immediately before and after this message, and eliminate the cause of the error. Then, re-execute the command.

KFAA50216-E

The table "aa....aa"."bb....bb" cannot be specified for the -n option, because the table is not a column store table. (E+M)

Table "aa....aa"."bb....bb" is a row store table. Only column store tables can be specified for the -n option.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Terminates processing.

Action:

If you specify the -d reorginfo option of the adbdbstatus command, specify a column store table for the -n option. The -d reorginfo option can be specified to check the necessity of reorganizing a column store table.

For details about how to check the necessity of reorganizing a row store table, see the following in the HADB Setup and Operation Guide: Checking whether a single-chunk table needs to be reorganized or Checking whether a multi-chunk table needs to be reorganized.

KFAA50217-E

The input data length is invalid. (input file = aa....aa, row = bb....bb, column = cc....cc, element = dd....dd) (M)

The input data length is invalid.

Information about where the error occurred is output for aa....aa to dd....dd.

aa....aa:

The serial number or file name of the input file

bb....bb:

Row number

cc....cc: Field number

If the input data is in the CSV format: Field data number

If the input data is in a fixed-length format: Order of the column definition in the table definition

The columns indicated by the order of column definition in the table definition correspond to the columns specified in the -n option of the adbcolumninfo operand in the column structure information file. The value in the -p option, specified along with the -n option, corresponds to the relevant part of the input data.

dd....dd: Element number of array element

If an error occurs with array type field data:

The element number of the array element in which the error occurred is displayed.

If an error occurs with non-array type field data:

0 is displayed.

S:

Terminates processing.

Action:

A logical error has occurred in input data. For details about the corrective action to take, see How to handle logical errors in input data in the manual HADB Command Reference.

Also, for details about the process up to executing the adbimport command, see Handling abnormal termination of the adbimport command in the manual HADB Command Reference.

KFAA50218-E

The number of elements in the input data exceeds the maximum number of stored elements. (input file = aa....aa, row = bb....bb, column = cc....cc) (M)

The number of array elements in the array type field data exceeds the maximum number of elements.

Information about where the error occurred is output for aa....aa to cc....cc.

aa....aa:

The serial number or file name of the input file

bb....bb:

Row number

cc....cc:

Field data number

S:

Terminates processing.

Action:

The array type field data of the input data is invalid. Refer to the information output to aa....aa to cc....cc and fix the array type field data where the error occurred. For details about the corrective action to take, see How to handle logical errors in input data in the manual HADB Command Reference.

Also, for details about the process up to executing the adbimport command, see Handling abnormal termination of the adbimport command in the manual HADB Command Reference.

KFAA50219-E

The target input data does not exist. (input file = aa....aa, row = bb....bb, column = cc....cc) (M)

Input data of field data number cc....cc of the row bb....bb does not exist.

aa....aa:

The serial number or file name of the input file

bb....bb:

Row number

cc....cc:

Field data number

S:

Terminates processing.

Action:

Correct the data of the relevant row number in the input data file. Alternatively, correct the value specified for the -r option of the adbcolumninfo operand in the column structure information file. For details about the corrective action to take, see How to handle logical errors in input data in the manual HADB Command Reference.

Also, for details about the process up to executing the adbimport command, see Handling abnormal termination of the adbimport command in the manual HADB Command Reference.

KFAA50220-E

An error occurred during conversion of input data. (input file = aa....aa, row = bb....bb, column = cc....cc, element = dd....dd) (M)

An error occurred during input data conversion.

Information about where the error occurred is output for aa....aa to dd....dd.

aa....aa:

The serial number or file name of the input file

bb....bb:

Row number

cc....cc: Field number

If the input data is in the CSV format: Field data number

If the input data is in a fixed-length format: Order of the column definition in the table definition

The columns indicated by the order of column definition in the table definition correspond to the columns specified in the -n option of the adbcolumninfo operand in the column structure information file. The value in the -p option, specified along with the -n option, corresponds to the relevant part of the input data.

dd....dd: Element number of array element

If an error occurs with array type field data:

The element number of the array element in which the error occurred is displayed.

However,0 is displayed if the error occurs in a non-array element, such as "a" instead of {"a"}, which is not enclosed in curly brackets.

If an error occurs with non-array type field data:

0 is displayed.

S:

Terminates processing.

Action:

A logical error has occurred in input data. For details about the corrective action to take, see How to handle logical errors in input data in the manual HADB Command Reference.

Also, for details about the process up to executing the adbimport command, see Handling abnormal termination of the adbimport command in the manual HADB Command Reference.

<When the table to be imported has an array-type column defined>

Check whether the array type field data is surrounded by enclosing characters.

If the array type field data is not surrounded by enclosing characters

It is possible that an array element in the array type field data tried to be imported into a non-array type column, resulting in a logical error in the input data. In this case, use the following procedure:

Surround array type field data with enclosing characters

Re-execute the adbimport command.

If a logical error occurs in the input data, follow the instructions in the output error message and fix the error.

When array type field data is surrounded by enclosing characters

It is possible that an attempt to import array type field data into a non-array type column resulted in a logical error in the input data. In this case, use the following procedure:

Check the input data in bb....bb-th line and correct the input data file

Correct the input data file so that array type field data is imported into array-type columns. If all lines have similar errors, specify the adbimport command with the -r option so that the array type field data is imported into the array-type column.

Re-execute the adbimport command.

KFAA50221-E

The number of columns in the input data does not match the number of stored columns. (input file = aa....aa, row = bb....bb) (M)

The number of columns of input data in the bb....bbth line does not match the column count at the storage destination.

aa....aa:

The serial number or file name of the input file

bb....bb:

Row number

S:

Terminates processing.

Action:

A logical error has occurred in input data. Other possible explanations are as follows, in addition to the possibility that the input data column count does not match the storage destination column count.

Data in the input file includes 0x00.

The final line does not end in a linefeed.

An EOF control character is stated at the end of the file.

For details about the corrective action to take for logical errors in input data, see How to handle logical errors in input data in the manual HADB Command Reference.

Also, for details about the process up to executing the adbimport command, see Handling abnormal termination of the adbimport command in the manual HADB Command Reference.

<When the table to be imported has an array-type column defined>

Check whether the array type field data is surrounded by enclosing characters. If the array type field data is not surrounded by enclosing characters, it is possible that an array element in the array type field data tried to be imported into a non-array type column, resulting in a logical error in the input data.

In this case, use the following procedure:

Surround array type field data with enclosing characters

Re-execute the adbimport command.

If a logical error occurs in the input data, follow the instructions in the output error message and fix the error.

KFAA50222-E

The input data contains an invalid empty string. (input file = aa....aa, row = bb....bb, column = cc....cc) (M)

An empty string is specified in field number cc....cc in the bb....bbth row, which cannot store a null value.

aa....aa:

The serial number or file name of the input file

bb....bb:

Row number

cc....cc: Field number

If the input data is in the CSV format: Field data number

If the input data is in a fixed-length format: Order of the column definition in the table definition

The columns indicated by the order of column definition in the table definition correspond to the columns specified in the -n option of the adbcolumninfo operand in the column structure information file. The value in the -p option, specified along with the -n option, corresponds to the relevant part of the input data.

S:

Terminates processing.

Action:

A logical error has occurred in input data. For details about the corrective action to take, see How to handle logical errors in input data in the manual HADB Command Reference.

Also, for details about the process up to executing the adbimport command, see Handling abnormal termination of the adbimport command in the manual HADB Command Reference.

<When the table to be imported has an array-type column defined>

Check whether the array type field data is surrounded by enclosing characters. If the array type field data is not surrounded by enclosing characters, it is possible that an array element in the array type field data tried to be imported into a non-array type column, resulting in a logical error in the input data.

In this case, use the following procedure:

Surround array type field data with enclosing characters

Re-execute the adbimport command.

If a logical error occurs in the input data, follow the instructions in the output error message and fix the error.

KFAA50223-E

An invalid enclosing character was detected in the data. (input file = aa....aa, row = bb....bb, column = cc....cc) (M)

An invalid enclosing character was detected in the input data.

Information about where the error occurred is output for aa....aa to cc....cc.

aa....aa:

The serial number or file name of the input file

bb....bb:

Row number

cc....cc: Field data number

If an error occurs with array type field data:

The field data number where the error occurred is displayed.

If an error occurs with non-array type field data:

0 is displayed.

S:

Terminates processing.

Action:

A logical error has occurred in input data. For details about the corrective action to take, see How to handle logical errors in input data in the manual HADB Command Reference.

To treat an enclosing character as itself in input data, specify that character twice consecutively.

Also, for details about the process up to executing the adbimport command, see Handling abnormal termination of the adbimport command in the manual HADB Command Reference.

<When the table to be imported has an array-type column defined>

Check whether the array type field data is surrounded by enclosing characters. If the array type field data is not surrounded by enclosing characters, it is possible that an array element in the array type field data tried to be imported into a non-array type column, resulting in a logical error in the input data.

In this case, use the following procedure:

Surround array type field data with enclosing characters

Re-execute the adbimport command.

If a logical error occurs in the input data, follow the instructions in the output error message and fix the error.

KFAA50224-E

The specified data is longer than the column length. (input file = aa....aa, row = bb....bb, column = cc....cc) (M)

The data of field number cc....cc in the bb....bbth row cannot be stored because the data is longer than the column definition.

aa....aa:

The serial number or file name of the input file

bb....bb:

Row number

cc....cc: Field number

If the input data is in the CSV format: Field data number

If the input data is in a fixed-length format: Order of the column definition in the table definition

The columns indicated by the order of column definition in the table definition correspond to the columns specified in the -n option of the adbcolumninfo operand in the column structure information file. The value in the -p option, specified along with the -n option, corresponds to the relevant part of the input data.

S:

Terminates processing.

Action:

A logical error has occurred in input data. For details about the corrective action to take, see How to handle logical errors in input data in the manual HADB Command Reference.

Also, for details about the process up to executing the adbimport command, see Handling abnormal termination of the adbimport command in the manual HADB Command Reference.

KFAA50225-E

The aa....aa specification contains an error or indispensable operand is not specified, or a necessary operand has not been specified. (reason = bb....bb) (M)

There is a bb....bb error in the specification of aa....aa.

aa....aa: Option specified by command

The following table provides details.

Value of aa....aa

Description

table

Table name

schema-name

Schema name

table-identifier

Table identifier

file-name

File name

filetype

Data type

fld-char

Field-delimiting character

fld-char-pre

Field-delimiting character (preceding)

fld-char-suf

Field-delimiting character (following)

trm-char

Line-delimiting character

idx-mode

Index creation method

index

Index identifier

col-inf-n

Column unit information count

col-inf

Column unit information

data-len

Input data length of column

err-inf

Error information

deliminator

Delimiting character

enclosing-character

Enclosing character

table-name-file

Table name description file

table option

Table option

input-path-file-name

Input data path file name

input-file-name

Input data file name

export-path-file-name

Output data path file name

export-data-output-file-name

Output data file name

timing-to-output-progress-message

Output interval for progress message on data import processing

temporary-directory

Path name of the storage directory for temporary work files:

References the command's -w option.

If the -w option is omitted for a command, the path name of the storage directory for temporary work files is $DBDIR/ADBWORK.

import-option-file-name

Import option file name

idxrebuild-option-file-name

Index rebuild option file name

cost-information-collection-option-file-name

Cost information collection option file name

export-option-file-name

Export option file name

merge-chunk-option-file-name

Merge chunk option file name

error-data-file-name

Logical error data file name

sort-buffer-size

Sort buffer size

--force

-- force option (forced execution)

--create-temp-file

--create-temp-file option

user-name

Authorization identifier

index-ID file

Index identifier file

index-ID file name

Index identifier file name

SQL-statement-file-name

SQL statement file name

column-structure-information-file-name

Column structure information file name

-b option

-b option

index-name

Index name ("[schema-name.]index-identifier")

DBarea-name

DB area name

-n option

-n option

-c option

-c option

-m option

-m option

-s option

-s option

-k option

-k option

-r option

-r option

chunk ID

Chunk ID

--compress

File compression option

archive-directory

Archive directory

archive-file-name

Archive file name

file-that-specifies-the-unload-file-directory

Name of the directory path file that specifies the storage directory for unload files

unload-file-directory

Path name of the storage directory for unload files

bb....bb: Detailed information about error

The following table provides details.

Value of bb....bb

Description

invalid char

The specified character is invalid.

This error also occurs if the specified file name includes reserved characters, or if an EOF control character is included in the input control file.

invalid value

The specified value is invalid. Carefully review whether the specification is correct.

invalid combination

The specified combination is invalid. Carefully review whether the specification is correct.

invalid format

The specified format is invalid. Carefully review whether the specification is correct.

invalid length

The specified value length is invalid. Carefully review the specified value length.

length over

The specified value exceeds the limit. Another possibility is that a 0-byte character has been specified. Carefully review the specified value.

length short

The specified value is less than the minimum that can be specified. Carefully review the range of values that can be specified.

limit over

The maximum count that can be specified has been exceeded. Carefully review the specified count.

not directory name

The specified path name is invalid. Carefully review whether the specification is correct.

not file name

The specified path is not a file. Alternatively, the file does not exist. Carefully review whether the specification is correct.

insufficient memory(u)

Memory area cannot be acquired. Read the message output before this message and take the corrective action indicated.

insufficient memory(s)

error convert path

An error occurred in absolute path conversion. Carefully review whether the path specification is correct for input data files and the like.

duplicate

A specification has been used more than once. Alternatively, the specified file name is the same as one of the following file names:

Logical error data file name

Unload file name

Carefully review to make sure that a duplicated value was not specified.

invalid permission

Access permissions are lacking. Carefully review whether access permissions have been granted.

not index-identifier

The specified index identifier does not exist.

table for which "CHUNK" was not specified

The CREATE TABLE statement does not include the chunk specification.

not index name

The specified index does not exist.

not DBarea name

The specified DB area does not exist.

unsupported DBarea name

The specified DB area type is not supported.

S:

Terminates processing.

Action:

Eliminate the cause of the error based on aa....aa and bb....bb. Then, retry the operation.

This message might also be output due to one of the following reasons:

A required operand was not specified.

The sequence of specifying operands is invalid.

A file with the same name as a logical error data file was specified.

If bb....bb is insufficient memory(u) or insufficient memory(s), take the action outlined in the following procedure:

Check for any unnecessary processes. If there are any unnecessary processes, shut them down or delete them.

If there is not enough memory after performing step 1, restart the OS, and then start the HADB server with the adbstart command.

If there is not enough memory after performing step 2, change the kernel parameter setting to increase the amount of memory that processes can use. After restarting the OS, start the HADB server with the adbstart command.

KFAA50226-E

An error was detected in the system. (SQLCODE = aa....aa) (M)

An error was detected in SQLCODE aa....aa.

aa....aa:

SQLCODE

S:

Terminates processing.

Action:

Determine the cause of the error based on SQLCODE, and then eliminate it.

Restore the database if necessary, and then re-execute the command. For details about how to restore the database, see the corrective action to take when a command terminates abnormally in the manual HADB Command Reference.

KFAA50227-E

The SQL statement in the SQL statement file of the adbexport command contains an error. (reason = aa....aa) (M)

There is an error in an SQL statement contained in the SQL statement file that was specified in the adbexport command.

aa....aa: Nature of the error

not SELECT-statement: An SQL statement other than the SELECT statement is specified.

parameters specified: A dynamic parameter is specified.

"ROW" specified in selection expression: ROW is specified in a selection expression.

length over: The length of an SQL statement (including space and linefeed) exceeds 16,000,000 bytes.

length zero: The length of an SQL statement is 0 byte.

S:

Terminates processing.

Action:

Correct the SQL statement in the SQL statement file, and then re-execute the adbexport command.

KFAA50228-E

An SQL error was detected in the aa....aa command. (SQLCODE = bb....bb) (M)

An error indicated by SQLCODE bb....bb occurred during execution of the aa....aa command.

aa....aa:

Name of the executed command

bb....bb:

SQLCODE

S:

Terminates processing.

Action:

Check the message of the indicated SQLCODE or the message output to the message log file, and then eliminate the cause of the error. Once this is done, re-execute the command.

For details about how to interpret the SQLCODE, see 1.4 Interpreting SQLCODEs.

KFAA50229-E

The search buffer specified in aa....aa option bb....bb is invalid. The required size is "cc....cc" MB. (M)

The buffer size specified during execution of the command is insufficient. The buffer size required for executing the command is cc....cc megabytes.

aa....aa: Command option type

export: Export option

archive chunk: Archive chunk option

bb....bb: Option name

adb_export_scan_buff_size

adb_arcv_scan_buff_size

cc....cc:

Required buffer size (megabytes)

S:

Terminates processing.

Action:

▪ If aa....aa is export:

Take one of the following corrective actions:

Change the value of the export option adb_export_scan_buff_size so that it is greater than cc....cc.

Correct the retrieval SQL statement in the SQL statement file. Reduce the number of selection expressions in the outermost query specification or the length of the data resulting from the selection expression.

▪ If aa....aa is archive chunk:

Change the value of the archive chunk option adb_arcv_scan_buff_size so that it is greater than cc....cc.

KFAA50230-I

The adbexport command has executed an SQL statement. (SQL statement = "aa....aa") (M)

The adbexport command has executed the SQL statement aa....aa.

aa....aa: The SQL statement that was executed

Only the first 2,048 bytes of the SQL statement is output. If byte 2,048 is a part of a multi-byte character, the characters up to the one immediately preceding that multi-byte character are output.

S:

Continues processing.

KFAA50235-E

No chunk IDs can change the chunk status. (M)

There are no chunks able to change chunk status.

S:

Terminates processing.

Action:

Check the chunk status. Then, specify the chunk ID of a chunk that can change chunk status, using the -w or -n option, and re-execute the command.

KFAA50236-E

An error occurred during the check of the unload file. (reason = "aa....aa", file = "bb....bb") (M)

An error occurred during the check of the unload file.

aa....aa: Cause of the error

not unloadfile: The checked file is not an unload file.

invalid data: The data is cut off.

bb....bb:

Path name of the checked file

S:

Terminates processing.

Action:

Check whether any other process has updated the unload file during execution of the adbreorgsystemdata command.

If another process has updated the unload file, take one of the following actions, and then re-execute the adbreorgsystemdata command.

Stop the relevant process.

Change the storage directory for unload files to a directory not used by other processes. The storage directory for unload files is specified in directory-path-file-that-specifies-the-storage-directory-for-unload-files for the -f option.

KFAA50239-E

A chunk to be deleted in the table ("aa....aa"."bb....bb") could not be deleted, because an SQL statement or a command has been referencing the table from before the completion of reorganization phase 1 of the previous execution of the adbreorgsystemdata command. (M+S)

Before phase 1 of the reorganization process of the previously executed adbreorgsystemdata command is completed, other SQL statements or commands have been referencing the table aa....aa.bb....bb. Therefore, the adbreorgsystemdata command cannot delete the data before reorganization.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Terminates processing.

Action:

Take one of the following actions. Then, re-execute the adbreorgsystemdata command.

Wait for termination of the SQL statement or command that is referencing table aa....aa.bb....bb .

Manually terminate the SQL statement or command that is referencing table aa....aa.bb....bb without waiting for its termination.

For details about how to terminate SQL statements and commands manually, see Reorganization of dictionary tables and system tables, and lock control in the HADB Setup and Operation Guide.

KFAA50243-E

aa....aa could not access the command status file. (file = bb....bb, reason = cc....cc, kind = dd....dd, last command = ee....ee, errno = ff....ff) (M)

The aa....aa command cannot access the command status file bb....bb.

aa....aa: Command that cannot access the command status file

Import: adbimport command

Index-rebuild: adbidxrebuild command

Unarchive-chunk: adbunarchivechunk command

bb....bb:

Command status file name

cc....cc: Reason code

No-file: The file does not exist.

Invalid-permission: Access privilege (read or write permission) for the file has not been granted.

Version-mismatch: The status file was created by using a different version.

Other-access-error: An access system call error other than the above occurred.

dd....dd: Type of the command status file

Import status file: Command status file of the adbimport command

Index-rebuild status file: Command status file of the adbidxrebuild command

ee....ee: Command that was last suspended

Import: adbimport command

Index-rebuild: adbidxrebuild command

Unarchive-chunk: adbunarchivechunk command

ff....ff:

Error number for the access system call

S:

Terminates processing.

Action:

If cc....cc is No-file or Version-mismatch and aa....aa is Import or Index-rebuild

Execute the adbidxrebuild command with the --force option specified.

If the suspended command is the adbimport command with background import applied (the -b option), executing the adbidxrebuild command with the --force option deletes stored information for table data that was being processed by the adbimport command. In this case, wait for the adbidxrebuild command to complete, and then re-execute the suspended adbimport command with the -b option specified.

If cc....cc is No-file or Version-mismatch and aa....aa is Unarchive-chunk

Re-execute the adbunarchivechunk command with the --force option specified.

If cc....cc is Invalid-permission

Grant access privileges (read or write permission) for the file by using the OS's chmod command or similar. Then, re-execute the command that was last suspended.

chmod command execution example

chmod 644 /home/osuser01/db/ADBSYS/ADBUTL/IMP_20191

If cc....cc is Other-access-error

Check the error number for the access system call in the OS documentation, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA50244-E

The command status file to be used by the command re-execution functionality does not exist. (last command = aa....aa) (M)

The command status file to be used by the following commands does not exist.

adbimport command (re-execute facility that starts from the processing to create B-tree indexes and text indexes)

adbidxrebuild command (re-execute facility)

adbunarchivechunk command

aa....aa: Command that was suspended the previous time

Import: adbimport command

Index-rebuild: adbidxrebuild command

Unarchive-chunk: adbunarchivechunk command

S:

Terminates processing.

Action:

If aa....aa is Import or Index-rebuild

Execute the adbidxrebuild command with the --force option specified.

If the suspended command is the adbimport command with background import applied (the -b option), executing the adbidxrebuild command with the --force option deletes stored information for table data that was being processed by the adbimport command. In this case, wait for the adbidxrebuild command to complete, and then re-execute the suspended adbimport command with the -b option specified.

If aa....aa is Unarchive-chunk

Re-execute the adbunarchivechunk command with the --force option specified.

KFAA50245-E

aa....aa could not access the temporary work file. (file = bb....bb, reason = cc....cc, kind = dd....dd, last command = ee....ee, errno = ff....ff) (M)

The aa....aa command cannot access the temporary work file bb....bb.

aa....aa: Command that cannot access the temporary work file

Import: adbimport command

Index-rebuild: adbidxrebuild command

Unarchive-chunk: adbunarchivechunk command

bb....bb:

Temporary work file name

cc....cc: Reason code

No-file: The file does not exist.

Invalid-permission: Access privilege (read or write permission) for the file has not been granted.

Other-access-error: An access system call error other than the above occurred.

dd....dd: Type of the temporary work file

index record file: Index record file

sort result file: Sort result file

ee....ee: Command that was suspended the previous time

Import: adbimport command

Index-rebuild: adbidxrebuild command

Unarchive-chunk: adbunarchivechunk command

ff....ff:

Error number for the access system call

S:

Terminates processing.

Action:

▪ If cc....cc is No-file:

If aa....aa is Import or Index-rebuild

Execute the adbidxrebuild command with the --create-temp-file option specified.

If aa....aa is Unarchive-chunk

Execute the adbunarchivechunk command with the --force option specified.

▪ If cc....cc is Invalid-permission:

If aa....aa is Import or Index-rebuild

Grant access privileges (read or write permission) for the file by using the OS's chmod command or similar. Then, re-execute the command that was suspended the previous time.

chmod command execution example

chmod 644 /mnt/disk1/xxxxx/_T20191_I30321_P0

If aa....aa is Unarchive-chunk

Grant access privileges (read and write permissions) for the file by using the OS's chmod command or similar.

Alternatively, delete the file, and then re-execute the adbunarchivechunk command with the --force option specified.

▪ If cc....cc is Other-access-error:

Check the error number for the access system call in the OS documentation, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA50246-E

The index record file is illegal. (file = aa....aa, reason = bb....bb) (errno = cc....cc) (M)

Index record file aa....aa is invalid. The cause is indicated by bb....bb.

aa....aa:

Name of index record file being created by the HADB server

bb....bb: Reason code

The following table provides details.

Value of bb....bb

Description

Duplicated-entry

During specification of multiple files, the same file was specified more than once.

Invalid-device

The file format is invalid.

Invalid-header

The header ID does not exist.

Invalid-permission

The permissions (for access) for the file are invalid.

Invalid-record-length

During specification of multiple files, the files had different record lengths.

No-file

The file does not exist.

No-header

The header does not exist.

Other-access-error

An access system call error other than Invalid-permission and No-file occurred.

cc....cc: Error number for the access system call

This is displayed if the reason code is other than Invalid-permission, No-file, or Other-access-error. For other cases, (errno = cc....cc) is not displayed.

S:

Terminates processing.

Action:

Because the index record file is corrupted, it is necessary to re-execute the command. For details about how to restore the database, see the corrective action to take when a command terminates abnormally in the manual HADB Command Reference.

If Other-access-error is displayed for the reason code, check the error number for the access system call in the OS documentation, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If using the multi-node function:

For details about the corrective action to take if the adbimport, adbidxrebuild, or adbunarchivechunk command terminates abnormally and the table to be processed becomes non-updatable, see the following: Releasing a base table from non-updatable status (when the multi-node function is being used) in Base table operations (when the multi-node function is being used) in the HADB Setup and Operation Guide.

KFAA50247-E

The temporary work file to be used by the command re-execution functionality does not exist. (last command = aa....aa) (M)

The temporary work file to be used for the re-execute facility of either the adbimport command (re-execution starting from the processing to create B-tree indexes and text indexes) or the adbidxrebuild command does not exist.

aa....aa: Command that was suspended the previous time

Import: adbimport command

Index-rebuild: adbidxrebuild command

S:

Terminates processing.

Action:

Execute the adbidxrebuild command with the --create-temp-file option specified.

KFAA50248-E

The option --create-temp-file cannot be specified, because the base table does not have a non-updatable status. (M)

The --create-temp-file option cannot be specified because the target table is not in a non-updatable status.

S:

Terminates processing.

Action:

Execute the adbidxrebuild command without specifying the --create-temp-file option.

KFAA50250-E

aa....aa processing was canceled. (M)

aa....aa has been canceled.

aa....aa: Type of processing

Archive-chunk: Chunk archive processing

Clean-synonym-dictionary: Deletion processing of unnecessary files under the storage directory for synonym dictionary files

Convert-audit-trail-file: Conversion processing for the audit trail file

Cost-information-collection: Cost information collection processing

DB-status-analysis: DB status analysis processing

Delete-synonym-dictionary: Synonym dictionary deletion processing

Export: Data export processing

Import: Data import processing

Index-rebuild: Index rebuild processing

Modify-synonym-dictionary: Synonym dictionary registration or update processing

Output-synonym-dictionary: Synonym dictionary output processing

Reorganize-systemdata: Dictionary table or system table reorganization processing

Synchronize-synonym-dictionary: Synchronization processing of synonym dictionary files

S:

Terminates processing.

Action:

Check the other messages that were output to the message log file or standard error output, and then eliminate the cause of the failure. Once this is done, re-execute the command.

KFAA50251-I

The specified value of the option aa....aa is bb....bb. (M)

The value of the aa....aa option at the execution time is bb....bb.

aa....aa:

Command option name

bb....bb:

Value used for execution

S:

Continues processing.

KFAA50252-I

File processing is in progress. (file name = aa....aa, thread number = bb....bb) (M)

The aa....aa file is being processed.

aa....aa:

File name

bb....bb:

Thread number

S:

Continues processing.

KFAA50253-I

The following values were specified for the aa....aa. (M)

A value is specified for aa....aa.

A message indicating the specified value is output after this message.

aa....aa:

index-identifier-file: Index identifier file

temporary-directory-path-file: Directory path file that specifies the storage directory for temporary work files

S:

Continues processing.

KFAA50254-I

aa....aa = bb....bb (M)

bb....bb is specified for aa....aa.

aa....aa:

Index-identifier: Index identifier

Temporary-directory-path: Directory path that specifies the storage directory for temporary work files

bb....bb:

Specified value

S:

Continues processing.

KFAA50255-I

The number of aa....aa specifications is bb....bb. (M)

The number of aa....aa specifications is bb....bb.

aa....aa:

Input data file: Input data file

Export data file: Output data file

Synonym dictionary: Synonym dictionary

bb....bb:

Number of specified aa....aa

S:

Continues processing.

KFAA50256-I

File processing will now end. (file name = aa....aa, thread number = bb....bb) (M)

The aa....aa file processing has finished.

aa....aa:

File name

bb....bb:

Thread number

S:

Continues processing.

KFAA50260-W

The index to be rebuilt does not exist. (M)

There is no index to be rebuilt because there is no index in unfinished status.

S:

Continues processing.

KFAA50265-E

A setting for the column structure information file is invalid. (column name = aa....aa, option = bb, reason = cc....cc) (M)

The specification for the column structure information file contains an error.

aa....aa: Column name specified in -n option of the column structure information file's adbcolumninfo operand

If no column name can be output, three asterisks (***) are displayed.

bb:

Name of option that contains the error

cc....cc: Cause of the error

not column name

The column name specified in the -n option of the adbcolumninfo operand does not exist in the processing-target table.

duplicate

The column name specified in the -n option of the adbcolumninfo operand is a duplicate.

not specified

No option is specified.

invalid value

The specified value is invalid.

The total value of the start position and the length exceeds the record length.

The sum of the start position and length specified in the -p option of the adbcolumninfo operand exceeds the input record length specified in the adb_import_input_record_size operand.

The length value exceeds the number of characters that can be specified.

The value specified for length in the -p option of the adbcolumninfo operand exceeds the number of characters that can be specified for the column specified in the -n option of the adbcolumninfo operand.

The length value is less than the number of characters that can be specified.

The value specified for length in the -p option of the adbcolumninfo operand is less than the number of characters that can be specified for the column specified in the -n option of the adbcolumninfo operand.

The lengths of the values specified for the -c option and for the -p option do not match.

The length of the specified value of the -c option of the adbcolumninfo operand does not match the value specified for length in the -p option of the adbcolumninfo operand.

The length value specified is odd.

The value specified for length in the -p option of the adbcolumninfo operand is an odd number.

The definition data type of the column is not a binary type.

The data type defined for the column is not a binary type.

For a column that cannot store null values, the value empty_string can not be specified.

For a column that cannot store null values, empty_string cannot be specified for the -r option of the adbcolumninfo operand.

The values specified for the -b option between the column name dd....dd do not match.

The value specified for the -b option of the adbcolumninfo operand do not match that of column name dd....dd.

If the value empty_string is specified in the -r option, the -b option cannot be specified.

If empty_string is specified for the -r option of the adbcolumninfo operand, the -b option cannot be specified.

S:

Terminates processing.

Action:

Correct the specification of the column structure information file.

KFAA50266-E

A setting for the column structure information file is invalid. (operand name = aa....aa, reason = bb....bb) (M)

The specification of the column structure information file contains an error.

aa....aa:

Name of operand that contains the error

bb....bb: Cause of the error

limit over: The number of times the operand was specified exceeds the maximum.

S:

Terminates processing.

Action:

Correct the specification of the column structure information file.

KFAA50267-E

For a column that cannot store null values, you must specify the column name in the -n option of the adbcolumninfo operand in the column structure information file. (column name = aa....aa) (M)

If the column cannot store null values, a column name must be specified in the -n option of the column structure information file's adbcolumninfo operand.

aa....aa:

Name of the column that caused error

S:

Terminates processing.

Action:

Specify column aa....aa in the -n option of the column structure information file's adbcolumninfo operand.

KFAA50280-E

The specified table "aa....aa"."bb....bb" has no archive specifications. (M)

The table specified for executing the command is not an archivable multi-chunk table.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Terminates processing.

Action:

Specify an archivable multi-chunk table, and then re-execute the command.

KFAA50281-E

The aa....aa access privilege is required to execute the command. (M)

The access privilege aa....aa is required to execute a command.

aa....aa: Access privilege that is required

IMPORT TABLE: IMPORT TABLE privilege

REBUILD INDEX: REBUILD INDEX privilege

GET COSTINFO: GET COSTINFO privilege

EXPORT TABLE: EXPORT TABLE privilege

MERGE CHUNK: MERGE CHUNK privilege

CHANGE CHUNK COMMENT: CHANGE CHUNK COMMENT privilege

CHANGE CHUNK STATUS: CHANGE CHUNK STATUS privilege

ARCHIVE CHUNK: ARCHIVE CHUNK privilege

UNARCHIVE CHUNK: UNARCHIVE CHUNK privilege

S:

Terminates processing.

Action:

After the required access privilege has been granted using the GRANT statement, re-execute the command.

KFAA50282-E

An error occurred in transaction processing (aa....aa) with reason code bb....bb. (M)

A failure occurred at the start or completion of a transaction.

aa....aa: Type of transaction

begin: Transaction start processing

commit: Commit processing

rollback: Rollback processing

bb....bb:

SQLCODE

S:

Terminates processing.

Action:

Determine the cause of the error based on SQLCODE, and then eliminate it.

If the transaction type is commit or rollback, recover the database to its status prior to command execution using a backup. Then, re-execute the command. For details about how to restore the database, see the corrective action to take when a command terminates abnormally in the manual HADB Command Reference.

KFAA50284-E

No chunk meets the conditions for aa....aa. (M)

There is no chunk that can be archived. Alternatively, there is no chunk that can be released from the archived state.

aa....aa: Performed processing

archive: Chunk archive processing

unarchive: Chunk unarchive processing

S:

Terminates processing.

Action:

Make sure that the target chunk specified by the -c option or -r option of the command is correct.

Alternatively, make sure that the chunk to be processed by the command meets the conditions allowing for archiving or releasing from the archived state. For details about conditions, see the following parts in the manual HADB Command Reference:

Explanation of the -c and -r options in Explanation of the specification format and options in adbarchivechunk (Archive Chunk)

Explanation of the -c and -r options in Explanation of the specification format and options in adbunarchivechunk (Unarchive Chunk)

KFAA50285-E

The environment variable ADBDIR is invalid. (M)

Environment variable ADBDIR has not been set. Another possibility is that the value set in ADBDIR is too long.

S:

Terminates processing.

Action:

Carefully review the value set in the ADBDIR environment variable. Then, re-execute the command.

KFAA50286-E

The aa....aa path is invalid. (reason = "bb....bb", file = cc....cc) (M)

An error occurred when the aa....aa path was checked.

aa....aa: Path type

file: Definition analysis information file

bb....bb: Cause of the error

too long: The maximum length was exceeded.

cc....cc:

Definition analysis information file name

S:

Terminates processing.

Action:

The path length of the definition analysis information file displayed in place of cc....cc exceeds the system's upper limit. Carefully review the server directory ($ABDDIR) path. Then, re-execute the command.

KFAA50287-E

An error occurred in the HADB function. (func = "aa....aa") (M)

An error occurred in HADB server function aa....aa.

aa....aa: Function name

option file analysis: Analysis of option file

columns structure information file: Analysis of column structure information file

S:

Terminates processing.

Action:

Check the other messages that were output to the message log file or standard error output, and eliminate the cause of the error. Then, re-execute the processing.

KFAA50288-E

aa....aa cannot resume by continuing from the last command execution. (reason = bb....bb, last command = cc....cc) (M)

It is not possible to restart aa....aa by resuming the previous command execution.

aa....aa: Type of processing

Import: Data import processing

Index-rebuild: Index rebuild processing

Unarchive-chunk: Chunk unarchive processing

bb....bb: Cause of the error

running authorization identifier dd....dd: The user who executed the command (authorization identifier dd....dd) is not the same as the user who executed it the previous time.

no import status file: The command status file for the adbimport command does not exist.

no index-rebuild status file: The command status file for the adbidxrebuild command does not exist.

incorrect import status file: The command status file for the adbimport command is not correct.

incorrect index-rebuild status file: The command status file for the adbidxrebuild command is not correct.

no unarchive-chunk status file: The command status file for the adbunarchivechunk command does not exist.

incorrect unarchive-chunk status file: The command status file for the adbunarchivechunk command is not correct.

cc....cc: Command that was suspended the previous time

Import: adbimport command

Index-rebuild: adbidxrebuild command

Unarchive-chunk: adbunarchivechunk command

S:

Terminates processing.

Action:

▪ If aa....aa is Import or Index-rebuild:

If bb....bb is running authorization identifier

Take one of the following corrective actions:

- If re-executing after a previous execution, ask the user who executed the command the previous time to re-execute the command. If the user who executed the command the previous time (HADB user) has already been deleted, create an HADB user with the same authorization identifier and password, and re-grant access privileges for the table.

- As another user who has REBUILD INDEX privilege for the target table, execute the adbidxrebuild command with the --force option specified. If the suspended command is the adbimport command with background import applied (-b option specified), executing the adbidxrebuild command with the --force option deletes stored information for table data that was being processed by the adbimport command. In this case, wait for the adbidxrebuild command to complete, and then re-execute the suspended adbimport command with the -b option specified.

If bb....bb is other than the above

Eliminate the cause of the error based on the message that was output immediately prior to this message. Then, execute the adbidxrebuild command with the --force option specified. If the suspended command is the adbimport command with background import applied (-b option specified) , executing the adbidxrebuild command with the --force option deletes stored information for table data that was being processed by the adbimport command. In this case, wait for the adbidxrebuild command to complete, and then re-execute the suspended adbimport command with the -b option specified.

■ If aa....aa is Unarchive-chunk:

If bb....bb is running authorization identifier

Take one of the following corrective actions:

- To resume the previous command execution, ask the user who executed the command the previous time to re-execute the command. If the user who executed the command the previous time (HADB user) has already been deleted, create an HADB user with the same authorization identifier and password, and re-grant access privileges for the table.

- As another user who has UNARCHIVE CHUNK privilege for the target table, execute the adbunarchivechunk command with the --force option specified.

If bb....bb is other than the above

Eliminate the cause of the error based on the message that was output immediately prior to this message. Then, execute the adbunarchivechunk command with the --force option specified.

KFAA50289-E

An error occurred with the output of the error data file. (reason = aa....aa) (M)

An error was detected in input data, but data cannot be output to the error data file for reason aa....aa.

aa....aa: Reason code

ROW_LENGTH: The length of the error data exceeds 32 KB or the record definition length.

S:

Terminates processing.

Action:

Find the relevant data in the input data file based on the messages output prior to this message regarding logical errors in input data output, and then correct the error.

KFAA50290-E

The command cannot be executed because of a conflict with a locked resource. (M)

The command cannot be executed because of contention over a locked resource to be used.

S:

Terminates processing.

Action:

Determine the name of the locked resource in the KFAA40005-E message output to the message log file, wait for all processing that uses the locked resource to terminate, and then re-execute the command.

For details about locked resources acquired by SQL statements and commands, see Locking in the HADB Setup and Operation Guide.

KFAA50291-W

Cost-information-collection processing was skipped for the "aa....aa"."bb....bb" table.(reason = "cc....cc") (M)

Cost information collection processing was skipped for table aa....aa.bb....bb. Possible causes are as follows:

The adbimport command terminated abnormally.

The adbidxrebuild command terminated abnormally.

The adbunarchivechunk command terminated abnormally.

An index is in unfinished status because it was defined after data had been stored in the table.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc: Reason for skipping the processing:

The adbimport command has not been re-executed.

The adbidxrebuild command has not been re-executed.

The adbunarchivechunk command has not been re-executed.

No indexes have been created.

S:

Continues processing.

Action:

If cc....cc is other than No indexes have been created.

Re-execute the command that terminated abnormally, and then use the adbgetcst command to collect cost information.

When cc....cc is No indexes have been created.

Release the indexes from unfinished status, and then use the adbgetcst command to collect the cost information.

For details about how to release the B-tree index from unfinished status, see Steps to take when unfinished status is applied to a B-tree index in the HADB Setup and Operation Guide.

For details about how to release the text index from unfinished status, see Steps to take when unfinished status is applied to a text index in the HADB Setup and Operation Guide.

For details about how to release the range index from unfinished status, see Steps to take when unfinished status is applied to a range index in the HADB Setup and Operation Guide.

When you execute the adbgetcst command, use the -t option to specify the name of the table for which cost information collection processing was skipped.

KFAA50292-E

No table is defined for the "aa....aa" schema, or no schema exists. (M)

No base table is defined in schema aa....aa or the schema is undefined.

aa....aa:

Schema name

S:

Terminates processing.

Action:

Check if base tables are defined in the schema or if the schema is defined.

KFAA50293-E

An error occurred while accessing the system table. (M)

An error occurred while accessing a system table.

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the messages that were output prior to this message. Then, re-execute the command.

KFAA50294-E

No chunk ID was specified in the aa option. (M)

The chunk ID specified in the aa option does not exist in the target table.

aa:

Option name

S:

Terminates processing.

Action:

Specify a chunk ID that exists in the target table in the aa option, and then re-execute the command.

KFAA50295-E

A chunk to be deleted exists. (M)

There is a chunk that is being deleted.

S:

Terminates processing.

Action:

Use the PURGE CHUNK statement to delete all delete-pending chunks, and then re-execute the command.

KFAA50296-E

Fewer than two chunk IDs are specified for the -c option. (M)

Fewer than two chunk IDs are specified in the -c option.

S:

Terminates processing.

Action:

Specify two or more chunk IDs in the -c option, and then re-execute the command. If this message was output even though two or more chunk IDs were specified in the -c option, specify two or more chunk IDs that exist in the target table, and then re-execute the command.

KFAA50297-E

Only one valid chunk ID is defined. (M)

Only one chunk ID exists in the target table. Therefore, there is no need to execute the adbmergechunk command to merge chunks.

S:

Terminates processing.

KFAA50298-E

The specified table "aa....aa"."bb....bb" is not a multi-chunk table. (M)

The specified table "aa....aa"."bb....bb" is not a multi-chunk table.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Terminates processing.

Action:

Specify a multi-chunk table, and then re-execute the command.

KFAA50299-E

The chunk status or archive status of the specified chunk ID is mixed. (M)

The adbmergechunk command cannot be executed due to either of the following causes:

Chunks in different statuses are to be processed by the adbmergechunk command.

Of the chunks to be processed by the adbmergechunk command, some chunks are archived but other chunks are not archived.

This message is output, for example, in the following cases:

Chunks in the normal status and chunks in the wait status are to be processed by the adbmergechunk command.

Archived chunks and chunks released from archived state are to be processed by the adbmergechunk command.

S:

Terminates processing.

Action:

Check the status of the chunks and whether they are archived. Match the status of the chunks and their archive state, and then re-execute the adbmergechunk command.

KFAA50300-E

A system call error occurred. (func = "aa....aa", errno = bb....bb) (M)

An error has occurred in system call aa....aa.

aa....aa:

Name of system call in which the error occurred

bb....bb:

Error number

S:

Terminates processing. However, in the case of temporary errors, the system might retry the operation.

Action:

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

The following table describes the major system call errors and corrective actions to take.

No.

Error details

Possible causes

Corrective actions to take

System call name

Error number

In Linux

In Windows

1

accept

23

24

--

Too many files are opened or too many connections have been established to the HADB server.

The maximum number of descriptors is too small.

Terminate unnecessary processes.

Reduce the number of connections to the HADB server.

Use the kernel parameters nofile and file-max to increase the maximum number of descriptors.# ¹

Reduce the number of DB areas.

2

bind

98

--

The port number used for accepting a connection is being used by another process.

Change the specified port number.

Terminate the other process that is using the same port number.

3

connect

99

10055

The local ports are busy.

Wait for a local port to be available.

Terminate another process that is performing communication.

Use the kernel parameter ip_local_port_range or the Windows command netsh to expand the range of temporary ports assigned by the OS.# ¹

4

101

110

113

10049

10051

10060

10065

An invalid connection destination is specified.

The destination host does not exist.

The specified host name has been resolved to an incorrect IP address.

A communication path failure occurred.# ²

Make sure that the connection destination is specified correctly.

Connect the destination host to the network.

Check the DNS or hosts file settings. Alternatively, specify the IP address for the host name.

Check whether a communication path failure occurred.

5

readv

recv

101

110

113

10060

A communication path failure occurred.# ²

The network configuration or network settings are changed.

Check whether a communication path failure occurred.

Check the physical configuration and settings of the network.

6

104

10054

The remote party process terminated forcibly.

The remote party detected a problem such as a communication timeout or error, and explicitly and forcibly disconnected communications.

The application program has not explicitly disconnected the connection with the HADB server before termination of the process.

Communications were blocked as a result of a communication path failure or similar failure.# ²

After that, attempts to transfer the same transmission packet were made several times. However, no response was received from the other side of communication, so the OS has reset this communication.

At this time, the connection might remain at the communication destination. However, this connection will be terminated after some time has passed.

If an HADB server terminated forcibly, restart it.

If an HADB server in a multi-node configuration terminated forcibly, restart that HADB server.

If the remote party is an HADB server in a multi-node configuration in which another HADB server is running, wait a while, and then reconnect to the HADB server in the multi-node configuration.

If the remote party is an HADB client, re-establish a connection from the HADB client to the HADB server.

If the communication partner is a HADB command, review the specified values of options related to timeout time, such as the --timeout option specified when the command was executed.

Revise the values of timer monitoring operands specified on the remote party. For example, revise the values of the adb_rpc_wait_time operand in the server definition and adb_clt_rpc_sql_wait_time operand in the client definition.

Check the message log file on the remote party. Take corrective action for the output error message.

Revise the contents of application program processing. If the processing to disconnect the HADB server is not specified, add that processing.

To immediately disconnect the remaining connection on the HADB server, use the command adbls to investigate the connection status. After that, disconnect the unnecessary connection by using the command adbcancel.

If communications are frequently reset as a result of the communication path being blocked, identify the location of the blockage in the communication path, and eliminate the cause of the failure.

7

socket

23

24

10024

Too many files are open or too many connections have been established with the HADB server.

The maximum number of descriptors is too small.

Terminate unnecessary processes.

Reduce the number of connections to the HADB server.

Use the kernel parameters nofile and file-max to increase the maximum number of descriptors.# ¹

8

writev

send

32

104

10054

The remote party process terminated forcibly.

The remote party detected a problem such as a communication timeout or error, and explicitly and forcibly disconnected communications.

Communications were blocked as a result of a communication path failure or similar failure.# ²

After that, attempts to transfer the same transmission packet were made several times. However, no response was received from the other side of communication, so the OS has reset this communication.

At this time, the connection might remain at the communication destination. However, this connection will be terminated after some time has passed.

If an HADB server terminated forcibly, restart it.

If an HADB server in a multi-node configuration terminated forcibly, restart that HADB server.

If the remote party is an HADB server in a multi-node configuration in which another HADB server is running, wait a while, and then reconnect to the HADB server in the multi-node configuration.

If the remote party is an HADB client, re-establish a connection from the HADB client to the HADB server.

If the communication partner is a HADB command, review the specified values of options related to timeout time, such as the --timeout option specified when the command was executed.

Revise the values of timer monitoring operands specified on the remote party. For example, revise the values of the adb_rpc_wait_time operand in the server definition and adb_clt_rpc_sql_wait_time operand in the client definition.

Check the message log file on the remote party. Take corrective action for the output error message.

To immediately disconnect the remaining connection on the HADB server, use the command adbls to investigate the connection status. After that, disconnect the unnecessary connection by using the command adbcancel.

If communications are frequently reset as a result of the communication path being blocked, identify the location of the blockage in the communication path, and eliminate the cause of the failure.

9

101

110

113

10060

10065

A communication path failure occurred.# ²

The network configuration or network settings are changed.

Check whether a communication path failure occurred.

Check the physical configuration and settings of the network.

#1

For details, see the OS documentation.

#2

The following shows examples of communication path failures.

- A cable is removed or disconnected.

- A stop or error of the network interface (NIC) is detected.

- A firewall blocks communications (including a case in which packets are discarded without notice).

- Power supply to the communication equipment is turned off.

- The communication equipment failed.

- Packets delayed or disappeared due to concentration of traffic or for other reasons.

- The destination host cannot respond because it is busy.

KFAA50301-E

A communication error occurred. (reason = "aa....aa", operation = "bbbb", IP address = "cc....cc") (M)

A communication error has occurred.

aa....aa: Cause of the error

message: A message error

netdown: Network failure

resource: Insufficient system resources

timeout: Timing out

bbbb: Operation at time error occurred

cnct: Connection acceptance

recv: Reception

send: Transmission

cc....cc: IP address of the connection source

If bbbb is other than recv, an asterisk (*) is displayed.

S:

Terminates processing.

Action:

Take the corrective action for the cause of the error displayed for aa....aa.

▪ If the cause of the error is message:

Establish a connection to the HADB server from the HADB client. If you are using a product other than the HADB client or performing communication directly to the HADB server from the user program, use the HADB client.

If you are not aware of the connection to the HADB server, communications by a malicious third party are suspected. Consider countermeasures, such as identification of the remote party, and security measures.

▪ If the cause of the error is netdown:

If the remote party is an HADB server on another node, check the settings, such as the communication line, server process status, and message log.

If the remote party is an HADB client, a HADB command, or a program (a product other than HADB or a user program) that performs communications without using the HADB communication function, no action is required for the HADB server. In this case, the possible causes of error are as follows.

The HADB client or HADB command forcibly disconnected communications due to detection of a timeout or error.

A process on the client forcibly terminated for some reason. This occurs if, for example, the adbsql command is forcibly terminated by pressing the Ctrl + C keys.

Processing of the application program is specified to terminate the application without explicitly disconnecting the connection with the HADB server.

A server monitoring tool or a malicious third party might have scanned the HADB server port.

Take action such as notifying the persons who execute the application program or security measures according to the cause of the error.

▪ If the cause of the error is resource:

Take one of the corrective actions:

Reduce the number of concurrent connections for the application program or command.

Increase the maximum number of concurrent connections specified for the adb_sys_max_users operand in the server definition.

▪ If the cause of the error is timeout:

Carefully review the value specified in the adb_rpc_wait_time operand in the server definition. For details about the adb_rpc_wait_time operand, see the topic Operands related to status monitoring (set format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide.

If you want to permanently maintain communications to use connection pooling, specify 0 for the adb_rpc_wait_time operand in the server definition. However, if 0 is specified, the HADB server does not perform forced disconnection based on the elapsed time for any other communications. This might allow a malicious third party to continue unauthorized connections. Therefore, if you specify 0 for the adb_rpc_wait_time operand in the server definition, periodically monitor for suspicious connections.

KFAA50303-E

The host IP address cannot be obtained. (reason = "aa....aa", host name = "bb....bb") (M)

The IP address cannot be acquired.

aa....aa: Descriptive text that indicates the cause of the error acquired by the gai_strerror function

The language of the descriptive text that is output depends on the locale.

bb....bb:

Target host name for name resolution

S:

Terminates processing.

Action:

Carefully review the network settings based on aa....aa.

If the host name contains an error, correct the host name.

KFAA50304-E

The data cannot be sent because its total size exceeds 2 gigabytes. (M)

The total length of the transmission data exceeds 2 GB, so the data cannot be transmitted.

S:

Terminates processing.

Action:

Carefully review the number of batch transfer lines, and then reduce the amount of data to be transferred at once.

KFAA50305-E

The aa....aa bb....bb operation failed. (name = "cc....cc") (M)

The bb....bb operation on aa....aa has failed.

aa....aa: Operation target

file: A file

port: A port

bb....bb: Operation type

bind: Binding to socket

delete: Deletion

cc....cc:

The name of the operation target (if a port, the port number)

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the messages that were output prior to this message. Then, retry the operation.

KFAA50306-E

The destination host closed the connection. (M)

The destination host closed the connection.

S:

Terminates processing.

Action:

In the case of an HADB client or a command, re-establish a connection.

If this message is output while the node is returning to the multi-node configuration or while adding a worker node to the multi-node configuration, take action by referring to the message that is output after this message.

For other cases, no action is required.

KFAA50307-E

A connection request will be rejected because it is form a remote party without permission to connect to this HADB server. (IP = "aa....aa", port = bb....bb) (M)

The connection request will be rejected because the request is issued from a remote party that is not permitted to connect to this HADB server.

aa....aa:

IP address of the remote party whose connection request is rejected

bb....bb: Port number of the remote party whose connection request is rejected

If 0 is displayed, no ports are used because the communication is UNIX domain communication with the HADB client on the same server machine as this HADB server.

S:

Disconnects communications.

Action:

If the remote party is an HADB client

An HADB client whose version differs from that of the HADB server cannot connect to the HADB server. Ask the HADB client's administrator to use an HADB client whose version matches that of the HADB server.

If the remote party is an HADB server on another node

Match the HADB server versions on the nodes.

KFAA50308-E

The connection will be disconnected. (IP = "aa....aa", port = bb....bb, reason = "cc....cc") (M)

The connection will be disconnected.

aa....aa:

IP address of communication target

bb....bb: Port number of the communication target

0 indicates that no ports are used because UNIX domain communication within the same host is specified.

cc....cc: Reason connection was disrupted

not alive: A communication API control timeout returned from a function such as KeepAlive was detected.

no DB-CONNECT request: A timeout occurred while waiting for a DB connection request.

S:

Disconnects the connection.

Action:

If cc....cc is not alive

If this message is output by the application, reconnect.

If this message is output by the HADB server, no action is necessary.

If cc....cc is no DB-CONNECT request

A communications delay, network disruption, or an unauthorized connection from a non-HADB product might have occurred.

First, check the network load and whether a failure has occurred. If either of these is the cause, wait for the situation to recover.

If this error occurs when there is no problem with the network and there is a connection from an IP address that is not authorized to connect, consider security countermeasures such as blocking such connections with a firewall. If the connection is directly to an HADB server via the Internet, it might be an attack from a malicious third party, so such security measures are necessary. In these cases, we normally recommend that you operate so that connections to the HADB server originate only from an application server installed behind a firewall, or a similar secure setup.

KFAA50309-E

An API error occurred during communications processing. (func = aa....aa, error = bb....bb, cause = cc....cc, details = "dd....dd") (M)

An API error occurred during communications processing.

aa....aa: Name of the API method where the error occurred

This is output in the form class-name#method-name.

bb....bb:

Name of the exception class thrown by the API method

cc....cc: Name of the exception class that indicates the cause of the error

Outputs null if there is no cause or if the cause is unknown.

dd....dd:

Detail message regarding the cause of the error

S:

Terminates processing.

Action:

Determine the cause of the error based on the name of the exception class and the detail message, and then take corrective action.

KFAA50310-E

The host name "aa....aa" was converted to an IP address of an unsupported protocol. (M)

The host name aa....aa was converted to the IP address of an unsupported protocol.

aa....aa:

Host name

S:

Terminates processing.

Action:

Specify an IPv4 host name.

KFAA50311-E

A valid IP address on the local host cannot be found. (M)

No valid IP address can be found on the local host.

S:

Terminates processing.

Action:

Set an IPv4 address that is not a loopback address for the network interface, and then enable that network interface.

KFAA50313-I

The aa....aa cannot communicate with the remote host "bb....bb":cc....cc. (operation = "dd....dd") (M)

aa....aa cannot communicate with the remote host "bb....bb":cc....cc.

aa....aa: Program that output this message

HADB server: HADB server

HADB client: HADB client or command

HADB JDBC Driver: HADB JDBC driver

bb....bb:

IP address of the communication target

cc....cc: Port number of the communication target

0 indicates that no ports are used because UNIX domain communication within the same host is specified.

dd....dd: Operation where a communication error occurred

connect: Communication establishment

S:

Continues processing.

Action:

Identify the cause of the problem and where it occurred based on the communication-target information indicated in this message (and error messages output before and after it). Then, take corrective action.

KFAA51000-I

The HADB server has received an SQL statement. (SQL statement = "aa....aa", connection information = bb....bb, SQL serial number = cc....cc) (M)

The HADB server received SQL statement aa....aa.

aa....aa: Specified SQL statement

Only the first 2,048 bytes of the SQL statement is output.

bb....bb:

Connection information

cc....cc:

Sequence number of the SQL statement after the connection is established

S:

Continues processing.

KFAA51001-E

The transaction was rolled back because an SQL error occurred. (M)

The transaction was rolled back because an SQL error occurred.

S:

Terminates processing.

KFAA51002-E

The transaction was rolled back because an SQL error was detected during transaction commit processing. (M)

The transaction was rolled back because an SQL error was detected during transaction commit processing.

S:

Terminates processing.

KFAA51003-I

The transaction isolation level was set. (isolation level = "aa....aa") (M)

The transaction isolation level has been set to aa....aa.

aa....aa: The transaction isolation level that was set

READ COMMITTED

REPEATABLE READ

S:

Continues processing.

KFAA51005-I

An error occurred during processing of the SQL statement "aa....aa". (connection information = bb....bb, SQL serial number = cc....cc) (M)

An error occurred during SQL statement processing.

aa....aa: Specified SQL statement

Only the first 2,048 bytes of the SQL statement is output.

bb....bb:

Connection information

cc....cc:

Sequence number of the SQL statement after the connection is established

S:

Continues processing.

Action:

Take corrective action based on the message that was output immediately after this message.

KFAA51006-I

The transaction access mode was set. (access mode = "aa....aa") (M)

A transaction access mode was set.

aa....aa: Transaction access mode that was set

READ WRITE: Read/write mode

READ ONLY: Read-only mode

S:

Continues processing.

KFAA51007-E

An error occurred on a different node. (node number = aa....aa, error message = "bb....bb") (M)

An error occurred in another node.

aa....aa:

Node number of the transmission target

bb....bb:

Error message for the error that occurred

S:

Continues processing.

Action:

Take the corrective action based on the message indicated by bb....bb for the HADB server for the node on which the error occurred.

KFAA51008-E

There is no secondary node or worker node to which the connected HADB client can reconnect. (reason = aa....aa) (M)

There is no secondary node or worker node to which the connected HADB client can reconnect.

aa....aa:

Cause of the error

S:

Terminates processing.

Action:

Take corrective action depending on the cause of the displayed error.

No.

Display of aa....aa

Cause of the error

Corrective action to take

1

no global IP address

There are no secondary or worker nodes with assigned global IP addresses.

Assign global IP addresses to all nodes. Alternatively, check the operating method and, if necessary, revise it so that there are no direct connections from external networks.

KFAA51009-E

A connection from the remote party "aa....aa" to the port for communications between HADB servers was detected, but this remote party is not an HADB server. (M)

A connection from a remote party that is not an HADB server to the HADB server-dedicated communication port was detected.

aa....aa:

IP address of remote party

S:

Disconnects communications.

Action:

If the remote party is an HADB client, configure it to connect to the port specified in the server definition's adb_rpc_port operand.

There is no specific action to take in response to an unauthorized remote party.

KFAA51010-W

An error occurred during processing of the SQL trace. (reason = aa....aa, file = bb....bb) (M)

An error occurred during processing of the SQL tracing file bb....bb because of aa....aa.

aa....aa:

Cause of the error

bb....bb:

SQL trace file name, or name of the file that manages file numbers of SQL trace files

S:

Terminates output of SQL trace information. Execution of the SQL statement continues.

Action:

Take corrective action depending on the cause of the displayed error.

No.

Display of aa....aa

Description

Corrective action to take

1

the SQL trace file disk is full

An attempt to write to the SQL trace file or the file that manages SQL trace file numbers failed because the disk was full.

Allocate sufficient free space on the disk that stores the SQL trace file or the file that manages SQL trace file numbers. Then, execute the adbchgsqltrc command with the -s option specified.

2

the SQL trace file could not be opened because there was no write permission

An attempt to open the SQL trace file or the file that manages SQL trace file numbers failed because there was no write privilege for these files.

Grant write privileges for the SQL trace file or the file that manages SQL trace file numbers. Then, execute the adbchgsqltrc command with the -s option specified.

3

the SQL trace file could not be opened because there was no read permission

An attempt to open the file that manages SQL trace file numbers failed because there was no read permission for this file.

Grant read permission for the file that manages SQL trace file numbers. Then, execute the adbchgsqltrc command with the -s option specified.

4

the SQL trace file could not be opened because the file descriptor was insufficient

An attempt to open the SQL trace file or the file that manages SQL trace file numbers failed because the file descriptor was insufficient.

Close any files that can be closed. Then, execute the adbchgsqltrc command with the -s option specified.

5

errno cc....cc

The error number is cc....cc.

Check the displayed error number in the OS documentation, and then eliminate the cause of the error. Then, execute the adbchgsqltrc command with the -s option specified.

If you cannot determine the corrective action to take based on the displayed error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA51011-W

An error occurred during processing of the SQL trace because memory is insufficient. (required memory = aa....aa) (M)

Memory was insufficient during processing of SQL trace information.

aa....aa:

Amount of requested memory when the error occurred (bytes)

S:

Terminates output of SQL trace information. Execution of the SQL statement continues.

Action:

See the KFAA40007-E message that was output immediately prior to this message, and then take corrective action. Then, execute the adbchgsqltrc command with the -s option specified.

KFAA51012-E

The number of client groups in the server definition is invalid. (M)

The number of client groups specified in the server definition is invalid.

S:

Terminates processing.

Action:

The number of adbcltgrp operands in the server definition exceeds value-specified-for-the-adb_sys_max_users-operand-in-server-definition + 1.

Reduce the number of adbcltgrp operands in the server definition, and then retry the operation.

KFAA51013-E

A value specified for the aa option in the client group (bb....bb) is invalid. (M)

The value specified for the aa option in the client group bb....bb is invalid.

aa:

Option name of the adbcltgrp operand in the server definition

bb....bb:

Client group name or command group name

S:

Terminates processing.

Action:

Check the value specified for the following options. Then, retry the operation.

∙ If aa is -u

If bb....bb indicates a group name

The value specified for the -u option is greater than the value of the -m option of the adbcltgrp operand in the server definition. Change the value specified for the -u option to be equal to or less than the value specified for the -m option.

If bb....bb does not indicate a group name

In the server definition, the sum of the values specified for -u options of the adbcltgrp operands exceeds the value specified for the adb_sys_max_users operand. Change the value specified for the -u option of each adbcltgrp operand so that the sum of the values specified for the -u options does not exceed the value of the adb_sys_max_users operand in the server definition.

∙ If aa is -e

If bb....bb indicates a group name

The value specified for the -e option is greater than the value of the -r option of the adbcltgrp operand in the server definition. Change the value specified for the -e option to be equal to or less than the value specified for the -r option.

If bb....bb does not indicate a group name

In the server definition, the sum of the values specified for -e options of the adbcltgrp operands exceeds the value specified for the adb_sys_rthd_num operand. Change the value specified for the -e option of each adbcltgrp operand so that the sum of the values of the -u options does not exceed the value of the adb_sys_rthd_num operand in the server definition.

For details about the value specification for each option, see the description of the adbcltgrp operand in Operands and options related to the client-group facility (command format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide.

KFAA51014-E

The authorization identifier "aa....aa" has already been specified for the -i option of the same adbclientmang operand or a different adbclientmang operand. (M)

The same authorization identifier is specified more than once for the -i option of the adbclientmang operand in the client-managing definition.

Alternatively, the same authorization identifier is specified for -i options of adbclientmang operands in multiple client-managing definitions.

aa....aa:

Authorization identifier that is specified more than once

S:

Terminates processing.

Action:

Correct the authorization identifier specified more than once for the -i option of the adbclientmang operand in the client-managing definition.

If this message is output when the HADB server starts, restart the HADB server.

If this message is output during execution of the adbclientdefmang command, re-execute the adbclientdefmang command.

KFAA51015-E

More than 30,000 authorization identifiers have been specified for the adbclientmang operand. (M)

The sum of the number of authorization identifiers specified for the adbclientmang operand in the client-managing definition exceeds 30,000.

S:

Terminates processing.

Action:

Reduce the number of authorization identifiers specified for the -i option of the adbclientmang operand in the client-managing definition to 30,000 or less.

If this message is output when the HADB server starts, restart the HADB server.

If this message is output during execution of the adbclientdefmang command, re-execute the adbclientdefmang command.

KFAA51016-E

The authorization identifier "aa....aa" specified for the -i option of the adbclientmang operand is invalid. (reason = bb....bb) (M)

The authorization identifier specified for the -i option of the adbclientmang operand in the client-managing definition is invalid.

aa....aa:

Invalid authorization identifier

bb....bb:

Message text that indicates the cause of the error

Message text beginning with KFAA3 is output. This message is output if an invalid authorization identifier is specified during connection to the HADB server.

S:

Terminates processing.

Action:

Correct the specification of the authorization identifier indicated by aa....aa according to the corrective action for the message indicated by bb....bb.

If this message is output when the HADB server starts, restart the HADB server.

If this message is output during execution of the adbclientdefmang command, re-execute the adbclientdefmang command.

KFAA51017-E

Processing to update the client-managing information failed, because aa....aa. (M)

Processing to update the client-managing definition information failed.

aa....aa:

Cause of update processing failure

S:

Terminates processing.

Action:

Take corrective action according to the cause of update processing failure displayed for aa....aa.

No.

Information displayed for aa....aa

Description

Corrective action to take

1

the DBA privilege is required to execute the adbclientdefmang command

An authorization identifier that has no DBA privileges is specified for the -u option of the adbclientdefmang command.

Specify an authorization identifier that has the DBA privilege for the -u option, and then execute the adbclientdefmang command.

2

an authorization identifier specified for the -i option is invalid

The authorization identifier specified for the -i option of the adbclientdefmang command is invalid.

You can determine the cause of the specification error in the -i option by checking the message that was output immediately prior to this message. Specify the correct authorization identifier for the -i option, and then execute the adbclientdefmang command.

3

the client-managing information does not match the information on other node (node number = bb....bb)

The client-managing information on the primary node does not match that on the secondary node.

bb....bb indicates the node number of the secondary node with inconsistent client-managing information.

Correct the client-managing information on the secondary node indicated by bb....bb.

Then, execute the adbclientdefmang command.

KFAA51018-E

The client-managing definition file is invalid. (reason = aa....aa) (M)

The information specified in the client management definition file is invalid.

aa....aa: Cause of the error

an error occurred during the analysis of the client management definitions

An error occurred during analysis of client-managing definitions.

S:

Terminates processing.

Action:

Correct the information specified in the client management definition file according to the corrective action for the message that was output immediately prior to this message.

If this message is output when the HADB server starts, restart the HADB server.

If this message is output during execution of the adbclientdefmang command, re-execute the adbclientdefmang command.

KFAA51019-E

The client definition file "aa....aa" specified for the -f option of the adbclientmang operand is invalid. (reason = bb....bb) (M)

The client definition file specified for the -f option of the adbclientmang operand in the client-managing definition is invalid.

aa....aa:

Invalid client definition file name on the server

bb....bb:

Cause of the error

S:

Terminates processing.

Action:

Take the corrective action based on the cause of the error displayed for bb....bb.

No.

Information displayed for bb....bb

Description

Corrective action to take

1

the specified client definition file does not exist

The client definition file specified for the -f option does not exist.

Specify an existing client definition file for the -f option.

2

the specified client definition file name is invalid

The client definition file name specified for the -f option is invalid.

A directory path is specified for the client definition file name indicated by aa....aa.

Move the client definition file to a location under the $ADBDIR/conf directory, and specify only the file name of the client definition file for the -f option.

3

an error occurred during the analysis of the client definitions

An error occurred during analysis of the client definitions.

Correct the information specified in the client definition file indicated by aa....aa according to the corrective action for the message that was output immediately prior to this message.

If this message is output when the HADB server starts, restart the HADB server.

If this message is output during execution of the adbclientdefmang command, re-execute the adbclientdefmang command.

KFAA51111-W

The word specified for adb_sql_prep_delrsvd_words is not a reserved word that can be deleted. (word = aa....aa, definition type = bb....bb) (M)

The word specified in the operand adb_sql_prep_delrsvd_words is not a reserved word that can be unregistered.

aa....aa:

The word specified in the operand adb_sql_prep_delrsvd_words that is not a reserved word that can be unregistered

bb....bb: Location that specified the reserved word to be unregistered

server: Server definition

S:

Continues processing.

Action:

Correct the word specified in the adb_sql_prep_delrsvd_words operand.

KFAA51121-W

It might take a long time to execute the SQL statement because all chunks in the archive status are accessed. (archive table name = "aa....aa"."bb....bb") (M)

Processing of the SQL statement might require a long time because the executed SQL statement accesses data in all archived chunks. The archivable multi-chunk table to be accessed is "aa....aa"."bb....bb". <SQLSTATE: 01601>

aa....aa:

Authorization identifier of the archivable multi-chunk table

bb....bb:

Table identifier of the archivable multi-chunk table

S:

Continues processing.

Action:

Consider correcting the SQL statement so that archived chunks to be accessed can be narrowed down. For details, see Considerations when searching an archivable multi-chunk table in the HADB Application Development Guide.

If this message is output during execution of the adbexport command, consider the following corrective actions.

When executing the adbexport command, specify the -c option (specify the chunks to be exported).

When executing the adbexport command, specify the -q option (specify an SQL statement file).

If you specify an SQL statement file, specify the SQL statement so that archived chunks to be accessed can be narrowed down.

KFAA51130-W

A work table was created because a hash table area was insufficient. (Hashtbl_path# = aa....aa, information1 = bb....bb, information2 = cc....cc) (M)

A work table was created because a hash table area was insufficient.

aa....aa: Tree row number of the corresponding access path

If access path statistical information has not been output, 0 is displayed for the tree row number.

bb....bb:

Maintenance information 1

cc....cc:

Maintenance information 2

S:

Continues processing.

Action:

Execution of the SQL statement might require a long time. To reduce the execution time of the SQL statement, increase the value specified for the adb_sql_exe_hashtbl_area_size operand in the server definition or client definition.

If this message is output during execution of the adbexport command, increase the value specified for the adb_export_hashtbl_area_size export option or the adb_sql_exe_hashtbl_area_size operand in the server definition.

If you want to know about the work table that is created if the hash table area is insufficient, check the access path information shown in the location indicated by aa....aa. Also see the following parts in the HADB Application Development Guide:

If hash join is used as the table joining method

Action to take when the hash table area has insufficient space in About hash join

If hash execution is used as the subquery processing method

Hash execution in Methods for processing subqueries that do not contain an external reference column, or Hash execution in Methods for processing subqueries that contain an external reference column

If global hash grouping is used as the grouping method

Global hash grouping in Hash grouping

If hash execution is used as the method for processing SELECT DISTINCT

Hash execution in Method for processing SELECT DISTINCT

If hash execution is used as the method for processing the set operation

Hash execution in Methods for processing set operations

KFAA51200-W

The DB area is undefined. (buffer = aa....aa, DB area = bb....bb) (M)

The DB area bb....bb specified in global buffer aa....aa does not exist. The specification of DB area bb....bb is ignored.

aa....aa:

Global buffer name

bb....bb:

DB area name

S:

Ignores the specification of this DB area and starts the HADB server.

Action:

Check the server definition's adbbuff operand, and then carefully review the DB area name specified with the -n option of global buffer aa....aa.

KFAA51202-W

The global buffer is invalid. (buffer = aa....aa) (M)

This global buffer will now be disabled because none of the DB areas specified in global buffer aa....aa exist.

aa....aa:

Global buffer name

S:

Ignores the specification of this global buffer and starts the HADB server.

Action:

If the -n option is specified in the adbbuff server definition operand

Check the server definition's adbbuff operand, and then carefully review the DB area name specified with the -n option of global buffer aa....aa.

If the -o option is specified in the adbbuff server definition operand

The global buffer for all DB areas is specified explicitly. If you do not need to specify the -o option, delete it.

KFAA51204-W

The table scan buffer specified for the global buffer will be made invalid. (buffer = aa....aa) (M)

The table scan buffer specified for the global buffer aa....aa is to be invalidated.

This message is output when a value of 12 or less is specified for the -k option of the adbbuff operand in the server definition, which defines the global buffer aa....aa.

aa....aa:

Global buffer name

S:

Ignores the specification of the global buffer and starts the HADB server.

Action:

The table scan buffer is invalidated when 12 or a value less than 12 is specified for the -k option of the adbbuff operand. For version 04-01 and later versions of the HADB server, we do not recommend using the -k option. To validate the table scan buffer, specify the -v option instead of the -k option. Then, restart the HADB server.

KFAA51210-E

The DB area is duplicated. (DB area = aa....aa) (M)

The DB area specified in the global buffer is duplicated.

aa....aa:

DB area name

S:

Stops the HADB server's start processing.

Action:

Check the specification of the server definition's adbbuff operand. The DB area name aa....aa specified in the -n option has been duplicated. After correcting the adbbuff operand specification, re-execute the adbstart command.

KFAA51212-E

The global buffer type is not specified. (buffer = aa....aa) (M)

The global buffer type has not been specified.

aa....aa:

Global buffer name

S:

Stops the HADB server's start processing.

Action:

Check the specification of the server definition's adbbuff operand. Specify either the -n or -o option for global buffer aa....aa. After correcting the adbbuff operand specification, re-execute the adbstart command.

KFAA51213-E

More than one type of global buffer cannot be specified. (buffer = aa....aa) (M)

Multiple global buffer types have been specified.

aa....aa:

Global buffer name

S:

Stops the HADB server's start processing.

Action:

Check the specification of the server definition's adbbuff operand. Both the -n and -o options have been specified for global buffer aa....aa. Specify one or the other. After correcting the adbbuff operand specification, re-execute the adbstart command.

KFAA51214-E

The specified name is invalid. (buffer = aa....aa, option = b, reason = cc....cc) (M)

The specified name is invalid.

aa....aa:

Global buffer name

b: Option with invalid specification

g: Global buffer name

n: DB area name

cc....cc: Cause of the error

TOO LONG: The name is too long.

INVALID CHARACTER: The syntax rule of the global buffer name or identifier is violated.

S:

Stops the HADB server's start processing.

Action:

Check the specification of the server definition's adbbuff operand. There is an error in the specification of either the global buffer name specified in the -g option, or the DB area name specified in the -n option. The cause of the error is displayed in place of cc....cc. Take one of the following actions to correct the adbbuff operand specification, and then re-execute the adbstart command:

If cc....cc is TOO LONG

Carefully review the maximum length of each name to sure that names fit within their length ranges.

If cc....cc is INVALID CHARACTER and b is g

Respecify the global buffer name by referencing Operands and options related to global buffers (command format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide.

If cc....cc is INVALID CHARACTER and b is n

See Specifying names in the manual HADB SQL Reference and revise the specified DB area name.

KFAA51216-E

One global buffer cannot be specified for a DB area that has different page sizes. (buffer = aa....aa, DB area = bb....bb) (M)

A single global buffer cannot be assigned to DB areas with different page sizes.

aa....aa:

Global buffer name

bb....bb:

DB area name

S:

Stops the HADB server's start processing.

Action:

Check the specification of the server definition's adbbuff operand. The page sizes of the DB areas specified in the -n option of global buffer aa....aa are different. Make sure that the DB areas have the same page sizes. After correcting the adbbuff operand specification, re-execute the adbstart command.

KFAA51217-E

No global buffer can be specified. (buffer = aa....aa, DB area = bb....bb) (M)

A global buffer cannot be specified for DB area bb....bb.

aa....aa:

Global buffer name

bb....bb:

DB area name

S:

Stops the HADB server's start processing.

Action:

Check the specification of the server definition's adbbuff operand. Delete the specification of DB area bb....bb from the adbbuff operand specification. After correcting the adbbuff operand specification, re-execute the adbstart command.

KFAA51218-E

Specify a separate global buffer for the DB area. (buffer = aa....aa, DB area = bb....bb) (M)

Specify an independent global buffer for DB area bb....bb.

aa....aa:

Global buffer name

bb....bb:

DB area name

S:

Stops the HADB server's start processing.

Action:

Check the specification of the server definition's adbbuff operand. Only specify bb....bb as the DB area specified in global buffer aa....aa. After correcting the adbbuff operand specification, re-execute the adbstart command.

KFAA51221-E

An option specification is duplicated. (buffer = aa....aa, option = b) (M)

Option b has been duplicated.

aa....aa:

Global buffer name

b: Duplicated option

o: -o option of the adbbuff operand

S:

Stops the HADB server's start processing.

Action:

Check the specification of the server definition's adbbuff operand. After you have corrected the adbbuff operand specification, re-execute the adbstart command.

KFAA51223-E

The -k option and the -v option in the server-defined adbbuff operand cannot both be specified at the same time. (buffer = aa....aa) (M)

Either the -k option or the -v option, but not both, can be specified for the operand adbbuff in the server definition.

aa....aa:

Global buffer name

S:

Stops the HADB server's start processing.

Action:

Check the specification of the operand adbbuff in the server definition in which the global buffer name displayed in aa....aa is specified. We recommend specifying the -v option. In order to do so, delete the specification of the -k option. After you have corrected the specification of the operand adbbuff, re-execute the command adbstart.

KFAA51224-E

A specified value is duplicated in an option argument of an operand specified in the file. (file name = "aa....aa", operand name = bb....bb, name of option arg of operand = cc....cc, specified option arg of operand = "dd....dd", num of lines where specified value is duplicated = ee....ee, line num where specified value is duplicated = "ff....ff") (M)

The specified value of the option argument for the operand specified in the "aa....aa" file is duplicated.

aa....aa:

Definition file name or option file name

bb....bb:

Operand name

cc....cc:

Operand option argument

dd....dd:

Specified value of the operand option argument

ee....ee:

Number of rows with duplicate specified values

ff....ff: Row number of the row where the specified value is duplicated

A maximum of 5 row numbers are output. If there are more than 5 row numbers in a row with duplicate values, "..." is output at the end.

S:

Terminates processing.

Action:

The specified value of the option argument of the operand (the value of dd....dd) cannot have the same value. Change the specified value so that there is no duplication. Then, re-execute the operation that caused an error.

KFAA51230-W

An invalid range index name is specified in the adb_sql_rngidx_preread operand (number = aa....aa). (M)

The range index name specified in the adb_sql_rngidx_preread operand (the aa....aath specification) is invalid.

aa....aa:

Position where invalid range index name is specified (where the highest-level specification is first)

S:

Ignores the specified value.

Action:

The syntax of the aa....aath range index name specification is incorrect. Check the following:

That the range index name obeys the rules given in Index name specification format in Qualifying a name in the manual HADB SQL Reference.

Whether the range index name has been specified without a schema name. (The schema name cannot be omitted from range index names specified in the adb_rngidx_preread operand.)

That the range index name is correct. For details about how to check the range index names that have been defined, see Searching a dictionary table in the HADB Setup and Operation Guide.

KFAA51231-W

Pre-reading of the range index "aa....aa"."bb....bb" failed. (reason = cc....cc) (M)

Pre-reading of the range index "aa....aa"."bb....bb" has failed.

aa....aa:

Schema name

bb....bb:

Index identifier

cc....cc:

Cause of the error

S:

Suspends pre-reading of range index "aa....aa"."bb....bb" and continues with the next processing.

Action:

Take one of the following corrective actions based on the cause of the error that is output:

Cause of the error

Corrective action

The specified range index does not exist.

The range index specified in the server definition's adb_sql_rngidx_preread operand has not been defined. Check the defined range index name and correct the adb_sql_rngidx_preread operand specification. For details about how to check the range index names that have been defined, see Searching a dictionary table in the HADB Setup and Operation Guide.

The specified range index is already specified elsewhere.

A single range index name has been specified multiple times in server definition adb_sql_rngidx_preread operands. Delete the duplicate range index names.

The buffer size is insufficient.

There is not enough global buffer to pre-read the range index. Either the -a option (page count for global buffer dedicated to range indexes) has not been specified for the global buffer of the DB area where the range index is stored, or the -a option value is too small. Check the specification of the -a option of the adbbuff operand in the server definition. For details about the -a option of the adbbuff operand, see the topic Operands and options related to global buffers (command format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide.

Use the following procedure to check the relevant global buffer:

Check the name of the DB area where the range index output in this message is stored. For details about how to check DB areas that store range indexes, see Searching a dictionary table in the HADB Setup and Operation Guide.

Open the server definition file and search for the DB area name found in step 1. This determines which global buffer is involved.

The specified range index is in unfinished status.

The range index specified in the server definition's adb_sql_rngidx_preread operand is in unfinished status. Take one of the following corrective actions:

Check and, if necessary, revise the value of the adb_sql_rngidx_preread operand

Use the adbidxrebuild command to rebuild the index.

KFAA51232-I

Pre-reading of the range index "aa....aa"."bb....bb" succeeded. (M)

Pre-reading of the range index "aa....aa"."bb....bb" was successful.

aa....aa:

Schema name

bb....bb:

Index identifier

S:

Continues processing.

KFAA51240-I

aa....aa chunks can be allocated for the "bb....bb" DB area. (M)

The remaining number of chunks that can be managed in the DB area bb....bb is aa....aa.

aa....aa:

Remaining number of chunks that can be managed in the DB area

bb....bb:

DB area name

S:

Continues processing.

KFAA51241-I

aa....aa chunks can be created for the "bb....bb"."cc....cc" table. (M)

The remaining number of chunks that can be created for the table "bb....bb"."cc....cc" is aa....aa.

aa....aa:

Remaining number of chunks that can be created for the table

bb....bb:

Schema name

cc....cc:

Table identifier

S:

Continues processing.

KFAA51242-I

A chunk was created. (chunk id = aa....aa) (M)

A chunk having chunk ID aa....aa was created.

aa....aa:

Chunk ID

S:

Continues processing.

KFAA51243-I

A chunk was deleted. (chunk id = aa....aa) (M)

The chunk having chunk ID aa....aa was deleted.

aa....aa:

Chunk ID

S:

Continues processing.

KFAA51244-I

A chunk in the wait status was created. (chunk id = aa....aa) (M)

A chunk that is in wait status was created.

aa....aa:

Chunk ID of the chunk that is in wait status

S:

Continues processing.

KFAA51245-E

Chunks cannot be allocated because the "aa....aa" DB area requires more chunks. (required number of chunks = bb....bb) (M)

The maximum number of chunks that can be managed in the data DB area aa....aa was exceeded by bb....bb. Therefore, a table or index cannot be defined in this data DB area. Another possibility is that the maximum number of chunks cannot be changed for the table.

aa....aa:

DB area name

bb....bb:

The number of chunks exceeding the maximum that can be managed in the DB area

S:

Invalidates this transaction.

Action:

Following this message, a message is output regarding the processing in which allocation of the maximum number of chunks has failed. Take the appropriate action according to that message.

KFAA51246-E

Chunks cannot be created because the "aa....aa"."bb....bb" table exceeds max number of chunks. (max = cc....cc) (M)

No more chunk can be created because the maximum number of chunks specified when the table "aa....aa"."bb....bb" was defined has been reached.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc:

Maximum number of chunks specified for the chunk specification in the CREATE TABLE statement

S:

Invalidates this transaction.

Action:

Take the appropriate action by referencing Problems related to the background-import facility in Troubleshooting in the HADB Setup and Operation Guide.

KFAA51247-I

Processing to delete chunks in the table ("aa....aa"."bb....bb") was skipped, because a SQL statement or a command was referencing the table and NOWAIT was specified for the --purge-chunk option of the adbmergechunk command. (M)

An SQL statement or a command is referencing the table "aa....aa"."bb....bb". Processing to delete the merge-source chunks was skipped because the adbmergechunk command was executed with NOWAIT specified for the --purge-chunk option.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

Action:

See the corrective action for the KFAA96785-E message.

KFAA51253-E

The system logfile was created by a later version. (E+M)

There is a user log file that was created by a later version.

S:

Stops the HADB server's start processing.

Action:

Upgrade the HADB server to the later version used the last time the HADB server started normally. After that, start the HADB server.

If the HADB server still does not start, even after it has been upgraded, restore the database from its backup.

KFAA51260-E

The adbmodbuff command is being executed. (M)

Another instance of the adbmodbuff command cannot be executed because an adbmodbuff command is already executing.

S:

Terminates processing.

Action:

Multiple adbmodbuff commands cannot be executed concurrently. Wait for the adbmodbuff command that is executing to terminate, and then execute the next adbmodbuff command.

KFAA51270-E

The path of the input data file of the system-defined function aa....aa is invalid. (reason = bb....bb, file = cc....cc) (M)

An error occurred during check of the path name of the file that will be the input data of the system-defined function aa....aa.

aa....aa: System-defined function name

ADB_AUDITREAD

ADB_CSVREAD

bb....bb: Cause of the error

INVALID PATH FORMAT: The specification format of the path name is invalid.

LENGTH ERROR: The specified path name is too long.

INVALID PATH: The file of the specified path cannot be used as the input data of the system-defined function.

cc....cc: Path name of the file in which the error occurred

If the path name of the file cannot be acquired, an asterisk (*) is displayed.

S:

Invalidates this transaction.

Action:

■ If aa....aa is ADB_AUDITREAD

If bb....bb is INVALID PATH FORMAT

Specify the path name of the audit trail file by using an absolute path.

Also, make sure that the special character is correctly specified in the audit trail file path.

If bb....bb is LENGTH ERROR

Reduce the length of the audit trail file path name (excluding leading and trailing spaces) to 1,024 bytes or less.

If the audit trail file path name contains a special character, reduce the length of the target audit trail file path name to 1,024 bytes or less.

If bb....bb is INVALID PATH

The path to the current audit trail file cannot be specified in the ADB_AUDITREAD function. Specify an audit trail file other than the current file.

■ If aa....aa is ADB_CSVREAD

If bb....bb is INVALID PATH FORMAT

Specify the path name of the CSV file by using an absolute path.

If bb....bb is LENGTH ERROR

Reduce the length of the CSV file path name (excluding leading and trailing spaces) to 510 bytes or less.

KFAA51271-E

The file format of the input data file of the system-defined function aa....aa is invalid. (file = bb....bb) (M)

The data format of the file containing the data to be input into the system-defined function aa....aa is invalid.

aa....aa: System-defined function name

ADB_AUDITREAD

ADB_CSVREAD

bb....bb:

Path name of the file with an invalid data format

S:

Invalidates this transaction.

Action:

■ If aa....aa is ADB_AUDITREAD

Make sure that the file indicated by bb....bb is either of the following files:

Audit trail file

Audit trail file that has been compressed by the OS's gzip command

■ If aa....aa is ADB_CSVREAD

Check the following sequentially:

Make sure that the file indicated by bb....bb is a regular file.

If GZIP is specified for the compression format option COMPRESSION_FORMAT, make sure that the file indicated by bb....bb satisfies either of the following conditions:

The file has been compressed by the OS's gzip command.

The file is a compressed file exported by using the adbexport command.

If this message is output when you access an archivable multi-chunk table, the file indicated by bb....bb (archive file) has been corrupted. In this case, see Recovering the database from the backup in the HADB Setup and Operation Guide, and then recover the database.

KFAA51272-E

An error occurred in the input data file of the system-defined function ADB_CSVREAD. (reason = aa....aa, file = bb....bb, row = cc....cc, field = dd....dd) (M)

An error occurred in the file that will be the input data of the ADB_CSVREAD function. The location of the error can be identified based on bb....bb, cc....cc, and dd....dd.

aa....aa: Cause of the error

DATA CONVERSION ERROR: An error occurred during file conversion processing.

NO FIELD: Field data does not exist.

INVALID ENCLOSING CHARACTER: Invalid enclosing characters exist in the data.

bb....bb:

Path name of the file in which the error occurred

cc....cc:

Row number of data in the file

dd....dd:

Field data number in the file

S:

Invalidates this transaction.

Action:

Make sure that the compression format of the file indicated by bb....bb matches the specification of the compression format option COMPRESSION_FORMAT of the ADB_CSVREAD function.

If they match, identify the field data that caused the error based on the information indicated by cc....cc and dd....dd. Then, take the corrective action for the cause of the error indicated by aa....aa.

If aa....aa is DATA CONVERSION ERROR

The data type specified for the table function column list is not compatible with the data type of the field data. Correct the data type specified for the table function column list.

If the error occurred at the end of the row, check that the row ends with a linefeed in the file indicated by bb....bb.

If aa....aa is NO FIELD

Add field data.

Alternatively, make sure that the field data number is specified correctly for the specification column option.

If aa....aa is INVALID ENCLOSING CHARACTER

Correct the invalid enclosing characters.

Alternatively, make sure that the enclosing character specification option is specified correctly.

If this message is output when you access an archivable multi-chunk table, the file indicated by bb....bb (archive file) has been corrupted. In this case, see Recovering the database from the backup in the HADB Setup and Operation Guide, and then recover the database.

KFAA51275-I

The maintenance processing of the updated-row columnizing facility has finished for the table "aa....aa"."bb....bb". (M)

The maintenance processing of the updated-row columnizing facility for the table aa....aa.bb....bb has finished.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA51276-E

The adbcolumnize command cannot be executed. (reason = aa....aa) (M)

The adbcolumnize command cannot be executed.

aa....aa:

Cause of the error

S:

Terminates processing.

Action:

Take the corrective action for the cause of the error displayed for aa....aa.

If the cause of the error indicated by aa....aa is the HADB server operation mode is "QUIESCENCE"

The adbcolumnize command cannot be executed because the HADB server operation mode is quiescence mode. Execute the adbchgsrvmode command to change the HADB server's operation mode to a mode other than quiescence mode. Then, execute the adbcolumnize command.

If aa....aa is the HADB server is returning to, or a worker node is being added to, a multi-node configuration

The adbcolumnize command cannot be executed because a node is being returned or a worker node is being added to the multi-node configuration. Wait for completion of processing to return the node or processing to add the worker node to the multi-node configuration, and then execute the adbcolumnize command.

KFAA51277-I

The maintenance processing of the updated-row columnizing facility has not been performed during the past 24 hours. (M)

Maintenance processing of the updated-row columnizing facility has not been performed during the past 24 hours.

S:

Continues processing.

Action:

For details about corrective actions, see Action to be taken if the maintenance processing is not performed in the HADB Setup and Operation Guide.

KFAA51280-W

An error occurred in the maintenance processing of the updated-row columnizing facility. (table = "aa....aa"."bb....bb") (M)

An error occurred during maintenance processing of the updated-row columnizing facility. The error occurred in table aa....aa.bb....bb.

aa....aa:

Schema name

If the maintenance processing is not for a specific table, an asterisk (*) is displayed.

bb....bb:

Table identifier

If the maintenance processing is not for a specific table, an asterisk (*) is displayed.

S:

Terminates processing.

Action:

Perform the following procedure to take action.

Execute the adbcolumnize --stop command to disable the updated-row columnizing facility.

Check the error message that was output prior to this message. Eliminate the cause of the error according to that error message. However, even if the corrective action in the error message indicates re-execution of the SQL statement or command, there is no need to re-execute them.

Execute the adbcolumnize --start command to enable the updated-row columnizing facility.

KFAA51281-W

Memory is insufficient. (memory type = aa....aa, request size = bb....bb) (M)

A memory shortage occurred.

aa....aa: Type of memory that is insufficient

THREAD: Real thread private memory used for the HADB server

bb....bb:

Size of memory you attempted to acquire (unit: bytes)

S:

Continues processing.

Action:

In the server definition, set the adb_sys_rthd_area_max operand to a value of rthd_max that is equal to or larger than the value determined from the following formula.

Formula (unit: megabytes)

rthd_max = max_size + get_size + 1

max_size

Value of the adb_sys_rthd_area_max operand in the server definition when there is insufficient memory.

Round up to the nearest 100 megabytes using the following method.

↑max_size÷100↑×100

get_size

Value output to bb....bb

Round up to the nearest 100 megabytes using the following method.

↑get_size÷(100×1,024×1,024)↑×100

KFAA51282-W

The file is invalid. (file category = "aa....aa", file name = "bb....bb", reason = "cc....cc") (M)

The "aa....aa" file is invalid.

aa....aa: Type of file

reuse information file (in the cache file storage directory)

Reuse information file stored in the cache file storage directory

reuse information file (in cloud storage)

Reuse information file stored in cloud storage

cache file

Cache file

bb....bb:

File name

cc....cc: Cause of the error

does not exist: The target file does not exist.

not a regular file: The target file is not a regular file.

invalid permission: The privilege for the target file is invalid.

corrupted: The target file is corrupted.

S:

Continues processing.

Action:

There is a possibility that the target file was improperly manipulated. The HADB server deletes the target file and continues processing. Therefore, no action is needed.

KFAA51283-E

The file is invalid. (file category = "aa....aa", file name = "bb....bb", reason = "cc....cc") (M)

The "aa....aa" file is invalid.

aa....aa: Type of file

reuse information file (in the cache file storage directory)

Reuse information file stored in the cache file storage directory

reuse information file (in cloud storage)

Reuse information file stored in cloud storage

cache file

Cache file

bb....bb:

File name

cc....cc: Cause of the error

does not exist: The target file does not exist.

not a regular file: The target file is not a regular file.

invalid permission: The privilege for the target file is invalid.

corrupted: The target file is corrupted.

S:

Terminates processing.

Action:

There is a possibility that the target file was improperly manipulated while the HADB server was running. Use the adbstart command to restart the HADB server.

KFAA51284-W

The operation of file failed. (file category = "aa....aa", file name = "bb....bb", operation = "cc....cc", errno = dd....dd) (M)

An operation on the file "aa....aa" failed.

aa....aa: Type of file

reuse information file (in the cache file storage directory)

Reuse information file stored in the cache file storage directory

cache file

Cache file

bb....bb:

File name

cc....cc:

Name of system call in which the error occurred

dd....dd:

Error number

S:

Continues processing.

Action:

In the OS documentation, check the system call indicated by cc....cc and the error number indicated by dd....dd, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are output, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA51285-W

Storage capacity became insufficient during operations on cache files used by the cloud storage facility. Decrease the total cache file size used by the cloud storage facility, and continue processing. (cache group = "aa....aa", before = bb....bb GB, after = cc....cc GB) (M)

There was insufficient storage capacity while operating the cache file. Continue processing by reducing the upper limit of the total size of the cache file.

aa....aa:

Name of cache group to be changed

bb....bb:

Upper limit of the total cache file size before the change (in gigabytes)

cc....cc:

Upper limit of the total cache file size after the change (in gigabytes)

S:

To avoid running out of storage capacity, reduce the upper limit of the total cache file size and continue processing.

Action:

If the total amount of cache files that can be created is reduced due to insufficient storage capacity, performance may be affected. After dealing with the storage capacity shortage, restart the HADB server.

If you cannot deal with the lack of storage capacity, do one of the following.

If the server definition's adbcachegrp operand is specified

Refer to the value output to cc....cc and reduce the specified value of the -s option for this operand.

If the server definition's adb_core_path operand is omitted

Refer to the value output to cc....cc and reduce the specified value of the server definition adb_sys_cld_cache_total_size operand.

If this message is output when the adbinit command terminates normally, there is no need to take any action to deal with insufficient capacity or to re-execute the command.

This message may also be output by an insufficient number of i nodes in the file system, even if there is ample storage capacity. In that case, instead of allocating storage capacity, allocate a i node.

KFAA51286-W

Memory became insufficient during operations on cache files used by the cloud storage facility. Adjust the number of cache files used by the cloud storage facility and continue processing. (request size = aa....aa) (M)

A memory shortage occurred during operation of the cache file. Adjust the number of cache files and continue processing.

aa....aa:

Size of memory area you attempted to acquire (bytes)

S:

To avoid running out of memory, adjust the number of cache files and continue processing.

Action:

If the number of cache files that can be created is reduced due to insufficient memory, performance may be affected. Take one of the following corrective actions, and then restart the HADB server.

When the adb_sys_memory_limit operand is specified in the server definition

Specify a value that is greater than or equal to the value obtained by adding the value output to aa....aa to the adb_sys_memory_limit operand of the server definition.

When the adb_sys_memory_limit operand is not specified in the server definition

In the server definition, set the adb_sys_proc_area_max operand to a value of proc_max that is equal to or larger than the value determined from the following formula.

Formula (unit: megabytes)

proc_max = max_size + get_size + 1

max_size: The MAX value of the line with THREAD-NO 0 in the output of the adbls -d mem command#

get_size: Value output to aa....aa#

#

Round up to the nearest 100 megabytes using the following method.

↑A÷(100×1,024×1,024)↑×100

A: max_size or get_size value

If this message is output when the adbinit command terminates normally, there is no need to take any action to deal with insufficient capacity or to re-execute the command.

KFAA51287-E

The operation on the aa....aa failed. (object key = "bb....bb", error type = cc....cc, msg = "dd....dd", exception name = ee....ee, response code = ff....ff, request id = gg....gg, ipaddress = hh....hh) (M)

Failed to operate S3 bucket.

aa....aa: Operation target

S3 bucket: S3 bucket

bb....bb: Object key

If it cannot be output, * is displayed.

cc....cc:

Error type

dd....dd: Message

If it cannot be output, * is displayed.

ee....ee: Exception name

If it cannot be output, * is displayed.

ff....ff:

Response code

gg....gg: Request ID

If it cannot be output, * is displayed.

hh....hh: IP address of remote host

If it cannot be output, * is displayed.

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the information output in this message. This message will output the information returned from AWS.

Note that if ee....ee is InternalError, it indicates an error due to a temporary AWS problem. In this case, there is nothing for the user to do.

In addition, an S3 object with the following name, created in the S3 bucket to check the privilege, might remain in the S3 bucket without being deleted (the name of the S3 object is output to bb....bb).

ADBCHECK-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

X is a random alphanumeric character.

If the S3 object with the above name is not deleted but remains in the S3 bucket, delete that S3 object manually.

The following lists the main causes of errors output in this message and their corrective actions.

Cause of the error

Corrective action

One of the bucket name, region name, or endpoint is incorrect

If this message is output when starting the HADB server

Review the following server definition operand specifications:

adb_sys_cld_aws_region operand

adb_sys_cld_aws_bucket operand

adb_sys_cld_endpoint operand

If this message is output when executing the adbinit command

Review the following initialization option operand specifications:

adb_init_cld_aws_region operand

adb_init_cld_aws_bucket operand

adb_sys_cld_endpoint operand

Procedure for setting up the HADB server required to use the cloud storage facility is incomplete

Review and adjust the settings to meet the following conditions:

The authentication information is configured correctly.

The actions required to retrieve, add, and delete S3 objects are allowed.

For details on setting authentication information and allowing actions, see Setting the authentication information required to access Amazon S3 in Building a HADB server in an AWS environment in the manual HADB Setup and Operation Guide.

Environment variable is set incorrectly

Check that the following environment variables are not set:

AWS_ACCESS_KEY_ID

AWS_SECRET_ACCESS_KEY

AWS_SESSION_TOKEN

AWS_SHARED_CREDENTIALS_FILE

AWS_PROFILE

KFAA51288-E

The operation on the aa....aa failed. (object key = "bb....bb", status code = cc....cc, error code = dd....dd, msg = "ee....ee", request id = ff....ff) (M)

The container operation failed.

aa....aa: Operation target

Container: Container

bb....bb: Object key

If it cannot be output, * is displayed.

cc....cc: Status code

If it cannot be output, * is displayed.

dd....dd: Error code

If it cannot be output, * is displayed.

ee....ee:

Message

ff....ff: Request ID

If it cannot be output, * is displayed.

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the information output in this message. This message will output the information returned from Azure. In addition, Azure-specific messages may be output to standard output or the message log file along with this message.

The following describes the causes of the error and the corrective action to take.

Incorrect storage account name or container name

Check the specification of the adb_sys_cld_az_storage_account operand or adb_sys_cld_az_container operand in the server definition. If the operand specification is invalid, restart the HADB server after correcting the operand specification.

If this message is output when the adbinit command is executed, check the specification of the adb_sys_cld_az_storage_account operand or the adb_sys_cld_az_container az_container operand in the initialization option. If the operand specification is invalid, re-execute the adbinit command after correcting the operand specification.

The necessary steps to build a HADB server in an Azure environment have not been implemented.

Possible causes are as follows:

Custom roles have not been created

A service principal is not created

Managed IDs are not assigned

No custom roles assigned to service principals or managed IDs

Azure CLI commands are not signed in to Azure

The authentication using the environment variable is not set correctly

See Creating a HADB Server in an Azure Environment in the manual HADB Setup and Operation Guide and the Azure documentation to review the steps for creating a HADB server.

A BLOB with the following name will be created in the container to check for permissions.

ADBCHECK-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

X is a random alphanumeric character.

The BLOB with the above name may remain in the container without being deleted. In that case, delete the BLOB manually. The name of the BLOB that is created is displayed in bb....bb.

KFAA51289-E

There is an error in the specified adbcachegrp operand. (reason = aa....aa, option = b) (M)

The specification for the adbcachegrp operand in the server definition is invalid.

aa....aa:

Cause of the error

b: Option of the adbcachegrp operand in the server definition

o: -o option

g: -g option

n: -n option

d: -d option

*: aa....aa is output if not an option is duplicated.

S:

Stops the HADB server's start processing.

Action:

Perform corrective action by following the following table, then re-execute the adbstart command.

Information output to aa....aa

Cause of the error

Corrective action to take

an option is duplicated

The option specified in b is duplicated.

If b is o or d

Specify only one adbcachegrp operand with either the -o option or the -d option.

If b is g or n

The name specified in the -g or -n option cannot be specified in another adbcachegrp operand. The name specified for the -g or -n option should be duplicate among all adbcachegrp operands.

the -g and -o options are specified together

The -g and -o options are specified together.

Revise the specified adbcachegrp operand.

the -n and -o options are specified together

The -n and -o options are specified together.

the -g and -d options are specified together

The -g option and -d options are specified together.

the -n and -d options are specified together

The -n option and -d options are specified together.

the -o and -d options are specified together

The -o option and -d options are specified together.

neither the -g, -o, nor -d option is specified

None of the -g option, -o option, or -d option is specified.

the -n option is not specified together with the -g option

The -n and - g options are not specified together.

the -s option is not specified

The -s option is not specified.

too many operands

The number of specified adbcachegrp operands exceeds the upper limit.

Limit the number of adbcachegrp operands with the -g option to 1,014 or less.

too many DB area names

The number of specified data DB area names exceed the upper limit.

Specify the data DB area names that exist so that there are no duplicates, and so that the total number of DB area names for data specified in the -n option does not exceed 1,014 across all adbcachegrp operands.

the operand is specified with the adb_sys_cld_cache_total_size

The operand is specified together with the adb_sys_cld_cache_total_size operand in the server definition.

The adbcachegrp operand cannot be specified with the adb_sys_cld_cache_total_size operand. Delete either all adbcachegrp operands or adb_sys_cld_cache_total_size operands.

no operand is specified with the -o option

There is no adbcachegrp operand with the -o option specified.

Add a adbcachegrp operand with the -o and -s options.

For details about the adbcachegrp operand, see the topic Operands and options related to cache group (command format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide.

KFAA51290-E

The name specified for an adbcachegrp operand option is invalid. (name = aa....aa, option = b, reason = cc....cc) (M)

The name specified in the option of the server definition adbcachegrp operand is invalid.

aa....aa:

Name with invalid specification

b: Option where the specified name is invalid

g: -g option (cache group name)

n: -n option (data DB area name)

cc....cc:

Cause of the error

S:

Stops the HADB server's start processing.

Action:

Perform corrective action by following the following table, then re-execute the adbstart command.

Information output in cc....cc

Cause of the error

Corrective action to take

too long

The name is too long.

The name of the cache group or data DB area should be within the maximum number of characters that can be specified.

invalid character

The syntax rules for the cache group name or identifier have been violated.

If b is g

The cache group name contains characters that cannot be specified. For details about the characters that can be specified in the cache group name, see the topic Operands and options related to cache group (command format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide.

If b is n

The name of the data DB area contains characters that cannot be used. For details about the rules for characters that can be specified in data DB area names, see Specifying names in the manual HADB SQL Reference.

the DB area does not exist

The specified data DB area name does not exist.

Specify an existing data DB area name.

unspecifiable DB area

The data DB area name cannot be specified.

KFAA51291-I

The library was loaded. (library name = "aa....aa") (M)

Library was loaded.

aa....aa: Library name

libadbarrow.so: Library for controlling Apache Arrow

libadbiceberg.so: Library for controlling Apache Iceberg

S:

Continues processing.

KFAA51292-E

An Apache Arrow API error occurred during the execution of the COPY statement. (SQL serial no = aa....aa, column name = "bb....bb", cause = "cc....cc", detail = "dd....dd") (M)

An Apache Arrow API error occurred while executing the COPY statement.

aa....aa:

SQL statement sequence number since the connection was established

bb....bb: Column name or field name that caused the error

The column or field names displayed are those derived from the outermost query specification in the query expression body of the COPY statement.

If no column name or the field name of that column can be output, three asterisks (***) are displayed.

cc....cc:

Apache Arrow status code

dd....dd:

Detailed information set by the Apache Arrow API

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Refer to the information output in cc....cc and dd....dd to remove the cause of the error. For information on Apache Arrow status codes output for cc....cc, see Programming Support in the Apache Arrow documentation.

The detailed information of the Apache Arrow API output for dd....dd may contain position information that indicates the location that caused the error. However, the meaning of the position information may differ from the HADB errors. For example, if the position information is a column number, the column number output in case of the Apache Arrow API detailed information starts from 0, but the column number output in case of HADB starts from 1. Therefore, if there is no problem at the location indicated in the position information, review the surrounding locations as well.

If you cannot determine the corrective action to take based on the information that was output, execute the adbinfoget command, collect troubleshooting information, and then contact the customer support center.

KFAA51293-I

The system directory support option for the cloud storage facility was enabled. (M)

The system directory support option for cloud storage facility has been enabled.

S:

Continues processing.

KFAA51295-I

The processing to remove cloud objects has started. (number of objects = aa....aa) (M)

Deletion process of S3 object or BLOB started.

aa....aa:

Number of S3 objects or BLOBs to be deleted

S:

Continues processing.

Action:

If the HADB server terminates abnormally after the output of this message but before the KFAA51296-I message is output, the S3 objects or BLOBs to be deleted may remain without being deleted. However, since the remaining S3 objects or BLOBs are reused by the HADB server, no action is required.

KFAA51296-I

The processing to remove cloud objects has ended. (number of objects = aa....aa) (M)

Delete processing of S3 object or BLOB is finished.

aa....aa:

Number of S3 objects or BLOBs to be deleted

S:

Continues processing.

KFAA51300-I

A dictionary / system table was created. (table name = "aa....aa"."bb....bb") (M)

A dictionary table or a system table was created.

aa....aa:

Schema name of the created dictionary or system table

bb....bb:

Table identifier of the created dictionary or system table

S:

Continues processing.

KFAA51301-I

A dictionary index (or an index for a system table) was created. (index name = "aa....aa"."bb....bb") (M)

An index for a dictionary table or a system table was created.

aa....aa:

Schema name of the index created for a dictionary or system table

bb....bb:

Index identifier of the index created for a dictionary or system table

S:

Continues processing.

KFAA51302-E

A dictionary / system table cannot be created. (M)

A dictionary table or a system table cannot be created.

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA51303-E

A dictionary index (or an index for a system table) cannot be created. (M)

An index cannot be created for a dictionary table or a system table.

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA51304-I

A column was added to a dictionary / system table. (table name = "aa....aa"."bb....bb", column_name = "cc....cc") (M)

A column was added to a dictionary table (or a system table).

aa....aa:

Schema name of the dictionary table (or the system table) to which a column was added

bb....bb:

Table identifier of the dictionary table (or the system table) to which a column was added

cc....cc:

Name of the column that was added

S:

Continues processing.

KFAA51305-E

A column cannot be added to a dictionary / system table. (M)

Columns could not be added to a dictionary table (or a system table).

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the message that was output immediately prior to this message. Then, execute the adbstart command.

KFAA51306-E

A column attribute cannot be changed a column of dictionary / system table. (M)

Values of columns in dictionary (or system) tables cannot be changed.

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA51307-I

A view table was invalidated. (view table name = "aa....aa"."bb....bb", reason = "cc....cc") (M)

A viewed table was invalidated.

This message is output when a viewed table is invalidated by version upgrading of the database or by execution of one of the following SQL statements:

ALTER TABLE statement

ALTER VIEW statement

DROP FOREIGN TABLE statement

DROP SCHEMA statement

DROP SERVER statement

DROP TABLE statement

DROP USER statement

DROP VIEW statement

REVOKE statement

aa....aa:

Schema name of the viewed table that has been invalidated

bb....bb:

Table identifier of the viewed table that has been invalidated

cc....cc:

Reason why the viewed table was invalidated

The view table depends on a table for which SELECT privileges were revoked by using a REVOKE statement

The viewed table depends on a table for which the SELECT privilege was revoked by using a REVOKE statement.

The view table depends on a table that was changed from a multi-chunk table to an archivable multi-chunk table by using an ALTER TABLE statement

The viewed table depends on a table that was changed from a regular multi-chunk table to an archivable multi-chunk table by using an ALTER TABLE statement.

The view table depends on a table that was changed from an archivable multi-chunk table to a multi-chunk table by using an ALTER TABLE statement

The viewed table depends on a table that was changed from an archivable multi-chunk table to a regular multi-chunk table by using an ALTER TABLE statement.

The view table depends on a table for which a column name was changed by using an ALTER TABLE statement

The viewed table depends on a table for which a column name was changed by using an ALTER TABLE statement.

The view table depends on a table whose name was changed by using an ALTER TABLE statement

The viewed table depends on a table for which a table name was changed by using an ALTER TABLE statement.

The view table depends on a table for which a column attribute was changed by using an ALTER TABLE statement

The viewed table depends on a table for which a column attribute was changed (the maximum number of elements in the array-type column has been increased) by using an ALTER TABLE statement.

The view table depends on a table that was deleted by using a DROP TABLE, DROP FOREIGN TABLE, DROP USER, DROP SCHEMA, DROP VIEW, DROP SERVER, or REVOKE statement

The viewed table depends on a table that was deleted by using a DROP TABLE, DROP FOREIGN TABLE, DROP USER, DROP SCHEMA, DROP VIEW, DROP SERVER, or REVOKE statement.

The view table depends on a table that was recreated by using an ALTER VIEW statement

The viewed table depends on a table that was re-created by using an ALTER VIEW statement.

The view table depends on a dictionary / system table that was recreated by upgrading database

The viewed table depends on a dictionary table or system table that was re-created during version upgrading of the database.

S:

Terminates processing.

Action:

Check whether the invalidated viewed table is necessary.

If the viewed table is necessary, release the viewed table from invalidation. For details, see Releasing a viewed table from invalidation in the HADB Setup and Operation Guide.

If the viewed table is not necessary, delete it by using the DROP VIEW statement. When you execute the DROP VIEW statement, specify CASCADE for drop behavior.

KFAA51308-E

The DB area "aa....aa" specified for the server definition adb_sql_default_dbarea_shared is invalid. (M)

The DB area name specified for the adb_sql_default_dbarea_shared operand in the server definition is invalid.

aa....aa:

DB area name specified for the operand

S:

Terminates processing.

Action:

Correct the DB area name specified for the adb_sql_default_dbarea_shared operand. For details about the rules for specifying DB area names, see Specifying names in the manual HADB SQL Reference.

KFAA51309-W

The DB area "aa....aa" specified for the server definition adb_sql_default_dbarea_shared is not a DB area for data. (M)

A DB area that is not a data DB area is specified for the adb_sql_default_dbarea_shared operand in the server definition.

aa....aa:

DB area name specified for the operand

S:

Continues processing.

Action:

Specify a data DB area name for the adb_sql_default_dbarea_shared operand.

KFAA51310-W

The DB area "aa....aa" specified for the server definition adb_sql_default_dbarea_shared does not exist. (M)

The DB area specified for the adb_sql_default_dbarea_shared operand in the server definition does not exist.

aa....aa:

DB area name specified for the operand

S:

Continues processing.

Action:

Take one of the following actions:

Specify the name of an existing DB area for the adb_sql_default_dbarea_shared operand.

Execute the adbmodarea command to add the DB area specified for the adb_sql_default_dbarea_shared operand.

KFAA51311-I

A view table was recreated. (table name = "aa....aa"."bb....bb") (M)

A viewed table was re-created.

aa....aa:

Schema name of the viewed table that was re-created

bb....bb:

Table identifier of the viewed table that was re-created

S:

Continues processing.

KFAA51312-W

A view table could not be recreated. (table name = "aa....aa"."bb....bb") (M)

The viewed table could not be recreated.

aa....aa:

Schema name of the viewed table that could not be re-created

bb....bb:

Table identifier of the viewed table that could not be re-created

S:

Continues processing.

Action:

Wait until the adbstart command terminates, and then re-create the viewed table by referring to Releasing a viewed table from invalidation in the HADB Setup and Operation Guide.

KFAA51313-I

The column definitions for the foreign table will be generated from the foreign data. (file = aa....aa) (M)

The column definitions for the foreign table will be generated from the foreign data with the file path name aa....aa.

aa....aa:

File path for foreign data search

S:

Continues processing.

KFAA51400-E

Databases with no schemas cannot be upgraded. (M)

A database with no schema cannot be upgraded.

S:

Terminates processing.

Action:

Take the appropriate action by referencing Steps to take when the KFAA51400-E message is output in Steps to take when version upgrading fails in the HADB Setup and Operation Guide.

KFAA51401-E

An error occurred while calling aa....aa. (func = "bb....bb", cc....cc = dd....dd, errmsg = ee....ee) (M)

An error occurred while calling aa....aa.

aa....aa: Type of function called

a Windows API: A Windows API function

a PAM library function: A PAM library function

an OpenSSL library function: An OpenSSL library function

a libcurl library function: A libcurl library function

a jansson library function: A jansson library function

a cjose library function: A cjose library function

a system call: A system call

bb....bb:

Name of the function in which the error occurred

cc....cc: Name of numerical value that indicates the nature of the error

errcode: Error code (Windows, OpenSSL, libcurl, jansson, or cjose)

errno: Error number (Linux)

dd....dd:

In the case of Linux, an error number is displayed. If the error code or error number cannot be obtained, three asterisks (***) are displayed.

ee....ee: Error message for the error code

If no error message can be acquired, three asterisks (***) are displayed.

S:

Terminates processing.

Action:

Check the OS documentation for the information that was displayed in the message, and then eliminate the cause of the error.

If you cannot determine the corrective action to take based on the information that was output, execute the adbinfoget command, collect troubleshooting information, and then contact the customer support center.

KFAA51402-E

The audit trail directory is invalid. (details = "aa....aa") (M)

The audit trail directory specified for the adb_audit_log_path operand in the server definition is invalid.

aa....aa:

Cause of the error

S:

Terminates processing.

Action:

Take the corrective action for the cause of the error displayed for aa....aa.

If this message is output during execution of the adbstart command, take the corrective action for the cause of the error, and then re-execute the adbstart command.

If this message is output during execution of the adbaudittrail command, execute the adbstop command to terminate the HADB server normally. After taking the corrective action for the cause of the error, execute the adbstart command to start the HADB server, and then execute the adbaudittrail command.

If aa....aa is No audit trail directory was specified

An audit trail directory is not specified for the adb_audit_log_path operand. Specify the audit trail directory.

If aa....aa is The audit trail directory path is invalid

The specification format of the audit trail directory path specified for the adb_audit_log_path operand is invalid. Alternatively, the path contains invalid characters or the length of the path is 1 byte or less.

If aa....aa is The audit trail directory does not exist

A directory that does not exist is specified for the adb_audit_log_path operand. Create the directory specified for the adb_audit_log_path operand. Alternatively, specify an existing directory for the adb_audit_log_path operand.

If aa....aa is The HADB administrator does not have permissions for the audit trail directory

The necessary privileges for the audit trail directory specified for the adb_audit_log_path operand have not been granted. Grant the HADB administrator the read, write, and execution permissions for the audit trail directory.

KFAA51403-E

Processing to aa....aa failed, because bb....bb. (M)

Operation of the audit trail facility has failed.

aa....aa: Failed operation

start the audit trail facility: Enabling the audit trail facility

terminate the audit trail facility: Disabling the audit trail facility

swap the audit trail file: Swapping the audit trail file

display the audit trail information: Displaying information relating to the audit trail facility

bb....bb:

Cause of the error

S:

Terminates processing.

Action:

Take the corrective action for the cause of the error displayed for bb....bb.

If bb....bb is the AUDIT ADMIN privilege is required to execute the adbaudittrail command

The HADB user who executed the adbaudittrail command does not have the audit admin privilege. Ensure that an HADB user with the audit admin privilege executes the adbaudittrail command.

If bb....bb is the AUDIT ADMIN privilege or the AUDIT VIEWER privilege is required to execute the adbaudittrail command

The HADB user who executed the adbaudittrail command does not have the audit admin privilege or audit viewer privilege. Ensure that an HADB user with the audit admin privilege or audit viewer privilege executes the adbaudittrail command.

If bb....bb is file descriptors were insufficient and the audit trail file could not be opened

An attempt to open the audit trail file failed because the file descriptors were insufficient. If there are files that can be closed, close them.

If bb....bb is memory was insufficient

A memory shortage occurred. Take the corrective action for the KFAA40007-E message that was output immediately prior to this message.

If bb....bb is the audit trail facility is INACTIVE

If the audit trail facility is disabled, the adbaudittrail --swap command cannot be executed. Enable the audit trail facility, and then execute the adbaudittrail --swap command.

KFAA51404-E

An error occurred during the processing of the audit trail file. (reason = "aa....aa", file = "bb....bb") (M)

An error occurred during processing of the audit trail file.

aa....aa:

Cause of the error

bb....bb:

Path name of the audit trail file in which the error occurred

S:

Terminates processing.

Action:

Take the corrective action for the cause of the error displayed for aa....aa.

If aa....aa is The audit trail file disk is full

An attempt to write to the audit trail file failed because the disk was full. Reserve sufficient free space on the disk where the audit trail directory is created. For details about how to take corrective actions, see Steps to take when the disk containing the audit trail directory is full in the HADB Setup and Operation Guide.

If aa....aa is The audit trail file could not be opened, because file descriptors were insufficient

An attempt to open the audit trail file failed because the file descriptors were insufficient. If there are files that can be closed, close them. For details about how to take corrective actions, see Steps to take when there are insufficient file descriptors in the HADB Setup and Operation Guide.

If aa....aa is errno cc....cc

cc....cc indicates an error number. In the OS documentation, check the error number indicated by cc....cc, and then eliminate the cause of the error. For details about how to take corrective actions, see Steps to take when a failure occurs in the disk containing the audit trail directory in the HADB Setup and Operation Guide.

If the HADB server has terminated abnormally, restart it by executing the adbstart command.

If you cannot determine the corrective action to take based on the displayed error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA51405-E

An error occurred during the processing of the audit trail because the files exceeding the number of files specified in the server definition adb_audit_log_max_num are stored in the directory specified in the server definition adb_audit_log_path. (adb_audit_log_path = aa....aa, adb_audit_log_max_num = bb....bb) (M)

An error occurred during processing of the audit trail facility because the number of audit trail files stored under the audit trail directory exceeded the upper limit.

aa....aa:

Audit trail directory (the directory specified in the adb_audit_log_path operand in the server definition)

bb....bb:

Upper limit of the number of audit trail files (the value specified for the adb_audit_log_max_num operand in the server definition)

S:

Terminates processing.

Action:

If this message is issued during execution of the adbstart command

Take one of the following corrective actions, and then re-execute the adbstart command.

Reduce the number of audit trail files under the audit trail directory by moving or deleting them.

Increase the value specified for the adb_audit_log_max_num operand.

If this message is issued during execution of the adbaudittrail command

Take one of the following corrective actions, and then re-execute the adbaudittrail command.

Reduce the number of audit trail files under the audit trail directory by moving or deleting them.

Terminate the HADB server by using the adbstop command, and then increase the value specified for the adb_audit_log_max_num operand. Then, execute the adbstart command to start the HADB server.

Important

You need to ensure that the number of audit trail files under the audit trail directory does not exceed the value specified for the adb_audit_log_max_num operand.

KFAA51406-E

The HADB server terminated abnormally, because an error occurred during the write processing of the audit trail facility. (M)

The HADB server terminates abnormally because an error occurred during write processing to an audit trail file.

S:

Terminates the HADB server abnormally.

Action:

Take the corrective action for the message that was output immediately prior to this message. After taking the corrective action for the cause of the error, execute the adbstart command to restart the HADB server.

KFAA51407-E

An error occurred on another node during the processing of the adbaudittrail command. (node number = aa....aa, host name = bb....bb, IP address = cc....cc) (M)

An error occurred in another node during execution of the adbaudittrail command.

aa....aa:

Node number of the node where the error occurred

bb....bb:

Host name of the node where the error occurred

cc....cc:

IP address of the node where the error occurred

S:

Terminates processing.

Action:

Take corrective action for the error message output to the message log file for the node on which the error occurred. Then, re-execute the adbaudittrail command.

KFAA51408-W

Audit trails from and including aa....aa were discarded, because an error occurred during the write processing of the audit trail file. (M)

Audit trails output from aa....aa are discarded because an error occurred during write processing to an audit trail file.

aa....aa: Date and time when discarding of audit trails started

This is displayed in the format YYYY/MM/DD hh:mm:ss.nnnnnn.

YYYY: Year

MM: Month

DD: Date

hh: Hour

mm: Minute

ss: Second

nnnnnn: Fractional seconds

S:

Continues processing.

Action:

Take the corrective action for the message that was output immediately prior to this message.

KFAA51409-I

Audit trails from and including aa....aa were output, because the cause of the error was eliminated. (M)

Output of audit trails to the audit trail file is restarted because the cause of the write error for the audit trail file has been corrected.

aa....aa: Date and time when output of audit trails restarted

This is displayed in the format YYYY/MM/DD hh:mm:ss.nnnnnn.

YYYY: Year

MM: Month

DD: Date

hh: Hour

mm: Minute

ss: Second

nnnnnn: Fractional seconds

S:

Continues processing.

KFAA51410-W

Output of the audit trail file is currently suppressed. (M)

Output of audit trails to the audit trail file is currently suppressed.

S:

Continues processing.

Action:

Take the corrective action for the KFAA51408-W message that was output prior to this message.

KFAA51411-W

The audit trail file to be switched over was not found. The audit trail file might be missing. (file = "aa....aa") (M)

The audit trail file to be swapped was not found. The audit trail file aa....aa might have been lost.

aa....aa:

Path to the audit trail file

S:

Continues processing.

Action:

No action is required.

KFAA51412-W

The audit trail file was deleted, because the status of the file is incorrect. (file = "aa....aa") (M)

The audit trail file aa....aa was deleted because it was in an inappropriate state.

aa....aa:

Path to the deleted audit trail file

S:

Continues processing.

Action:

No action is required.

KFAA51413-W

The value of adb_audit_log_max_num is invalid. A value from 1 to 3 cannot be specified. The value of adb_audit_log_max_num will be set to 4. (adb_audit_log_max_num = a) (M)

A value from 1 to 3 is specified as the maximum number of audit trail file generations for the adb_audit_log_max_num operand of the server definition. The specified value is invalidated and the maximum number of audit trail file generations is assumed to be 4.

a:

Value specified for the adb_audit_log_max_num operand

S:

Continues processing.

Action:

Correct the value specified for the adb_audit_log_max_num operand. For details about the approximate values to be specified, see the description of the adb_audit_log_max_num operand in Operands related to audit trail facility (set format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide.

KFAA51414-W

The HADB server confirmed that an external program or user performed an operation on the file. (file = "aa....aa") (M)

The HADB server confirmed that the audit trail file aa....aa was operated from the outside.

aa....aa:

Path to the audit trail file

S:

Continues processing.

Action:

No action is required.

KFAA51415-E

The adbaudittrail command cannot be executed, because the HADB server is not running on the specified node. (node number = aa....aa, host name = bb....bb, IP address = cc....cc) (M)

The adbaudittrail command could not be executed for one of the following reasons.

The node numbers of the nodes that are disconnected from the multi-node configuration are specified in the -n option.

The node number of the worker node that is deleted from the multi-node configuration is specified in the -n option.

The node numbers of the nodes that does not exist in the multi-node configuration are specified in the -n option.

aa....aa:

Node number specified for the -n option

bb....bb:

Host name of the node with the node number specified for the -n option#

cc....cc:

IP address of the node with the node number specified for the -n option#

#

In the following instances, nothing is displayed.

If the -n option specifies the node number of a worker node that is being deleted from a multi-node configuration

If the -n option specifies the node number of a node that does not exist in a multi-node configuration

S:

Terminates processing.

Action:

Confirm that the node number specified in the -n option is correct.

If the node number of a node that has been disconnected from the multi-node configuration is specified with the -n option, re-execute the adbaudittrail command after returning the node.

If the node number of a worker node that has been deleted from the multi-node configuration is specified with the -n option, re-execute the adbaudittrail command after adding the worker node.

KFAA51416-E

The specified node (node number aa....aa) does not exist, because the current HADB configuration is a multi-node configuration with bb....bb nodes specified. (M)

The node with the node number specified for the -n option of the adbaudittrail command does not exist.

This message is output if, for example, 4 is specified for the -n option when the number of nodes in a multi-node configuration is 3.

aa....aa:

Node number specified for the -n option

bb....bb:

Number of nodes in the multi-node configuration

S:

Terminates processing.

Action:

Re-execute the adbaudittrail command with the correct node number specified for the -n option.

KFAA51417-E

Processing to convert the audit trail file failed because aa....aa. (M)

Conversion processing for the audit trail file failed.

aa....aa:

Cause of the error

S:

Terminates processing.

Action:

Take corrective action as described in the following table:

Information output to aa....aa

Description

Action to take

memory was insufficient

A memory shortage occurred.

See the KFAA40007-E message that was output immediately prior to this message, and then take corrective action.

the audit trail facility is INACTIVE

The command adbconvertaudittrailfile was executed while the audit trail facility was disabled.

Enable the audit trail facility, and then execute the command adbconvertaudittrailfile.

the AUDIT VIEWER privilege is required to execute the adbconvertaudittrailfile command

The command adbconvertaudittrailfile was executed when the value specified for the -u option was the authorization identifier of an HADB user who does not have the audit viewer privilege.

For the -u option, specify the authorization identifier of an HADB user who has the audit viewer privilege, and then re-execute the command adbconvertaudittrailfile.

KFAA51418-I

The audit trail file was converted to the common format. (file = aa....aa, output directory = bb....bb) (M)

The audit trail file was converted to a common format audit trail file.

aa....aa:

Path name of the audit trail file that was converted

bb....bb:

Path name of the output-directory for common format audit trail

S:

Continues processing.

KFAA51419-I

The output destination of the common-format audit trail file was changed from aa....aa to bb....bb. (M)

The output-directory for common format audit trail was swapped from the file aa....aa to the file bb....bb.

aa....aa:

Name of the common format audit trail file before swapping

bb....bb:

Name of the common format audit trail file after swapping

S:

Continues processing.

KFAA51420-E

The output directory of the common-format audit trail is invalid. (details = aa....aa) (M)

The specified output-directory for common format audit trail is invalid.

aa....aa:

Cause of the error

S:

Terminates processing.

Action:

Respecify the output-directory for common format audit trail as shown in the following table:

Information output to aa....aa

Description

Action to take

The output-directory path is invalid

The specification of the output-directory for common format audit trail contains one or more of the following errors:

The specification format of the directory path is invalid.

The specified directory path contains at least one invalid character.

The length of the directory path is 1 byte or less.

Check the specification of the output-directory for common format audit trail, and revise the specified value as necessary.

The output-directory does not exist

The specified output-directory for common format audit trail does not exist.

Specify an existing directory as the output-directory for common format audit trail.

The HADB administrator does not have permissions for the output-directory directory

The HADB administrator does not have the necessary access privilege for the output-directory for common format audit trail.

Set the read, write, and execution permissions so that the HADB administrator can access the output-directory for common format audit trail.

KFAA51421-E

The path of the input data file (bb....bb) of the command adbconvertaudittrailfile is invalid. (reason = aa....aa) (M)

The path name of the audit trail file bb....bb that is specified for the command adbconvertaudittrailfile is invalid.

aa....aa: Cause of the error

INVALID PATH FORMAT: The specification format of the audit trail file path name is invalid.

INVALID PATH: The file indicated by the specified path cannot be specified for the command adbconvertaudittrailfile.

bb....bb: Path name of the file for which the error occurred

If the specified path name exceeds 1,024 bytes, the beginning of the path name is truncated when the path name is displayed.

If the path name of the file cannot be acquired, an asterisk (*) is displayed.

S:

Terminates processing.

Action:

Respecify the path name of the audit trail file as shown in the following table:

Information output to aa....aa

Action to take

INVALID PATH FORMAT

For the command adbconvertaudittrailfile, specify an absolute path for the path name of the audit trail file.

INVALID PATH

The path name of the current audit trail file cannot be specified for the command adbconvertaudittrailfile. Specify an audit trail file other than the current audit trail file.

KFAA51422-E

The file format of the input data file (aa....aa) of the command adbconvertaudittrailfile is invalid. (M)

The data format of the file aa....aa that is specified for the command adbconvertaudittrailfile is invalid.

aa....aa:

Path name of the file with an invalid data format

S:

Terminates processing.

Action:

Make sure that the file displayed for aa....aa is one of the following:

An audit trail file

An audit trail file that has been compressed by using the OS's gzip command

KFAA51423-W

An HADB encryption key file is specified in the server definition adb_crypto_dmkey_path, but the encrypted DB area does not exist. (M)

The adb_crypto_dmkey_path operand in the server definition specifies a HADB encryption key file, but the DB area to be encrypted does not exist.

S:

Continues processing.

Action:

If necessary, execute the adbmodarea command to add the data DB area to be encrypted.

Note that the adb_crypto_dmkey_path operand in the server definition is not required if the DB area encryption facility is not used. Start the HADB server after deleting the adb_crypto_dmkey_path operand.

KFAA51424-E

The specified HADB encryption key file is invalid. (reason = "aa....aa", file name = "bb....bb") (M)

The specified HADB encryption key file is invalid.

aa....aa:

Cause of the error

bb....bb: HADB encryption key file name

The path name of the HADB encryption key file is displayed as an absolute path. However, if the path name of the HADB encryption key file does not exist, asterisks (***) are displayed.

S:

Terminates processing.

Action:

Take corrective action as described in the following table:

Information output to aa....aa

Cause of the error

Corrective action to take

The encrypted DB area exists, but the server definition adb_crypto_dmkey_path is not specified.

The encrypted DB area exists, but the adb_crypto_dmkey_path operand is not specified in the server definition.

Specify the adb_crypto_dmkey_path operand of the server definition.

You cannot specify an HADB encryption key file other than the HADB encryption key file that is currently in use.

A HADB encryption key file different from the HADB encryption key file in use is specified.

Specify the HADB encryption key file in use to the adb_crypto_dmkey_path operand of the server definition.

The permission for the specified the HADB encryption key file is invalid.

The permissions of the HADB encryption key file are invalid.

Set the permissions for the HADB encryption key file to 400.

The permission for the specified the directory containing the HADB encryption key file is invalid.

The permissions of the directory where the HADB encryption key file is saved are invalid.

Set the permissions of the directory where the HADB encryption key file is stored to 700.

A file already exists in the output destination of the specified HADB encryption key file.

A file exists at the output destination of the specified HADB encryption key file.

You cannot overwrite an existing HADB encryption key file. Specify a different HADB encryption key file name than the specified HADB encryption key file.

The specified HADB encryption key file does not exist.

The specified HADB encryption key file does not exist.

Specify the name of an existing HADB encryption key file.

KFAA51425-E

Processing to aa....aa failed, because the CRYPTO ADMIN privilege is required to execute the bb....bb command. (M)

Processing for the HADB encryption key failed. CRYPTO ADMIN privileges are required to execute the commands.

aa....aa: Processing that failed

create an HADB encryption key: Process to create a HADB encryption key

update the HADB encryption key: Process to update the HADB encryption key

bb....bb: Executed node

If aa....aa is create an HADB encryption key

adbmkdmk (command to create a HADB encryption key)

If aa....aa is update the HADB encryption key

adbupddmk (command to update the HADB encryption key)

S:

Terminates processing.

Action:

For the -u option, specify the authorization identifier of an HADB user who has the CRYPTO ADMIN privilege, and then re-execute the command.

KFAA51426-E

An error occurred in the processing of the HADB encryption key file. (reason = "aa....aa", file name = "bb....bb") (M)

An error occurred during processing of the HADB encryption key file.

aa....aa:

Cause of the error

bb....bb: HADB encryption key file name

The path name of the HADB encryption key file is displayed as an absolute path.

S:

Terminates processing.

Action:

Take corrective action as described in the following table:

Information output to aa....aa

Cause of the error

Corrective action to take

The specified HADB encryption key file is not a regular file.

The specified HADB encryption key file is not a regular file.

Re-execute the operation you performed, specifying the HADB encryption key file created with the adbinit or adbmkdmk command.

The specified HADB encryption key file is corrupted.

The specified HADB encryption key file is corrupt.

Re-execute the operation you performed, specifying the HADB encryption key file created with the adbinit or adbmkdmk command.

If you get this message when starting the HADB server, check that the adb_crypto_dmkey_path operand in the server definition specifies the HADB encryption key file created with the adbinit or adbmkdmk command.

The HADB encryption key usage password is incorrect.

The HADB encryption key usage password for the HADB encryption key file is incorrect.

Re-execute the executed operation and enter the HADB encryption key usage password.

KFAA51427-E

The aa....aa file is invalid. (details = bb....bb) (M)

The private key file or public key file is invalid.

aa....aa: Invalid file

private key: Private key file

public key: Public key file

bb....bb:

Cause of the error

S:

Terminates processing.

Action:

Take corrective action as described in the following table: Then, execute the adbstart command to start the HADB server.

Information output to bb....bb

Cause of the error

Corrective action to take

the private key file or the public key file does not exist

The private key file or public key file specified in the server definition does not exist.

If private key is displayed for aa....aa.

Specify the path name of the existing private key file in the server definition's adb_auth_passwd_privkey_path operand using an absolute path.

If public key is displayed for aa....aa.

Specify the path name of the existing public key file in the server definition's adb_cmd_passwd_pubkey_path operand using an absolute path.

the private key file or the public key file is not a regular file

The private key file or public key file specified in the server definition is not a regular file.

If private key is displayed for aa....aa.

Specify the path name of the regular file private key file in the server definition's adb_auth_passwd_privkey_path operand using an absolute path.

If public key is displayed for aa....aa.

Specify the path name of the regular file public key file in the server definition's adb_cmd_passwd_pubkey_path operand using an absolute path.

the permission for the private key file or the public key file is invalid

The permissions for the private key file or public key file specified in the server definition is invalid.

If private key is displayed for aa....aa.

Grant the HADB administrator read permission for the private key file specified in the server definition's adb_auth_passwd_privkey_path operand.

If public key is displayed for aa....aa.

Grant the HADB administrator read permission for the public key file specified in the server definition's adb_cmd_passwd_pubkey_path operand.

the format of the private key file or the public key file is invalid

The format of the private key file or public key file specified in the server definition is invalid.

If private key is displayed for aa....aa.

Specify the path name of the correct format private key file in the server definition's adb_auth_passwd_privkey_path operand using an absolute path.

If public key is displayed for aa....aa.

Specify the path name of the correct format public key file in the server definition's adb_cmd_passwd_pubkey_path operand using an absolute path.

the specified combination of a private key file and a public key file is invalid

The combination of the private key file and the public key file with or without the server definition is invalid.

The combination of the adb_auth_passwd_privkey_path operand and adb_cmd_passwd_pubkey_path operand in the server definition is invalid.

Take one of the following corrective actions:

Specify both the adb_auth_passwd_privkey_path operand and the adb_cmd_passwd_pubkey_path operand in the server definition.

Do not specify either the adb_auth_passwd_privkey_path operand or the adb_cmd_passwd_pubkey_path operand in the server definition. In this case, however, the password is not encrypted when using PAM authentication.

KFAA51428-E

There is an error in the specification of the server definition required for Keycloak authentication. (reason = aa....aa, detail = "bb....bb") (M)

There is an error in the specification of the server definition operand related to Keycloak authentication.

aa....aa:

Cause of the error

bb....bb: Error message

If the error message cannot be obtained, * is displayed.

S:

Terminates processing.

Action:

Take the corrective action for the cause of the error indicated by aa....aa.

If aa....aa shows some of the server definitions required for Keycloak authentication are not specified

A required operand is not specified. When using authentication, the following operands must be specified in the server definition. Check whether all of the following operands are specified.

adb_auth_keyc_endpoint

adb_auth_keyc_realm

adb_auth_keyc_clt_id

Note that if Keycloak authentication is not used, do not specify the above operands or the adb_auth_clt_keyc_endpoint operand.

If aa....aa shows the endpoint could not be reached

Cannot connect from the HADB server to the endpoint output to bb....bb. The following causes are possible.

There is an error in the specification of the adb_auth_keyc_endpoint operand or the adb_auth_keyc_realm operand in the server definition.

The Keycloak server is not running.

KFAA51429-E

The operation on the aa....aa failed. (error type = bb....bb, msg = "cc....cc") (M)

An attempt to perform aa....aa failed.

aa....aa: Processing that failed to execute

connection to Keycloak server: Connection to the Keycloak server

bb....bb: Error type

If the error type cannot be obtained, * is displayed.

cc....cc: Error message

If the error message cannot be obtained, * is displayed.

S:

Terminates processing.

Action:

Take appropriate action based on the error type output in bb....bb and the error message output in cc....cc. The main causes of the error and their corrective actions are shown below.

Display of bb....bb

Display of cc....cc

Corrective action to take

invalid_grant

Invalid user credentials

The specified authorization identifier or password is incorrect. Specify the correct authorization identifier and password.

No external user corresponding to the specified authorization identifier exists. Create an external user with the same name as the authorization identifier.

An attempt was made to connect to the Keycloak server with a user who has multi-factor authentication such as OTP enabled. Disable the multi-factor authentication settings.

Account is not fully set up

The user account created on the Keycloak server is not fully configured. Check whether the password and other settings have been completed.

Realm does not exist

*

The realm name specified in the adb_auth_keyc_realm operand of the server definition does not exist. Specify an existing realm name in the adb_auth_keyc_realm operand.

invalid_client

Invalid client or Invalid client credentials

There is an error in the client ID specified in the adb_auth_keyc_clt_id operand of the server definition. Specify the correct client ID in the adb_auth_keyc_clt_id operand.

unauthorized_client

Client not allowed for direct access grants

The Authentication flow of the client configured on the Keycloak server is not set to Direct access grants. Set it to Direct access grants.

KFAA51500-E

The adbsyndict command cannot be executed at the same time. (E+M)

Multiple adbsyndict commands cannot be executed at the same time.

S:

Terminates processing.

Action:

Wait for the running adbsyndict command to terminate, and then execute the adbsyndict command.

KFAA51501-E

The aa....aa is invalid. (line = bb....bb, option = cc....cc, reason = dd....dd, value = ee....ee) (E+M)

Information specified in the dictionary creation file or dictionary deletion file is invalid.

aa....aa: File that contains invalid information

dictionary-creation-file: Dictionary creation file

dictionary-deletion-file: Dictionary deletion file

bb....bb:

Line that generated the error

cc....cc: Invalid item

synonym-list-definition-file: Synonym list definition file name

synonym-dictionary-name: Synonym dictionary name

comment: Comment

correction-rule: Notation-correction option

record: Whole line

If one of the following conditions exists, record is output:

- The number of specified options is invalid.

- The file does not end with a linefeed.

dd....dd: Cause of the error

invalid length: The length of the specified value is invalid.

invalid value: The specified value is invalid.

The specified notation-correction option is invalid. Alternatively, although character encoding used by the HADB server is Shift-JIS, CORRECTIONRULE or CR is specified for correction search.

invalid character: Invalid characters are specified.

Characters that cannot be used are specified in the synonym dictionary name, synonym list definition file name, or comment.

invalid format: One of the following errors exists.

- The number of specified items is invalid.

- The file does not end with a linefeed.

- The specified enclosing characters are invalid.

invalid path format: The specified path is not an absolute path.

duplicate: A synonym dictionary name is specified more than once in the dictionary creation file. Alternatively, a synonym dictionary name is specified more than once in the dictionary deletion file.

ee....ee: Specified value

If one of the following conditions exists, an asterisk (*) is output:

dd....dd is invalid format.

dd....dd is invalid length and either of the following is not specified:

- Synonym list definition file name

- Synonym dictionary name

dd....dd is invalid length and the maximum length of one of the following is exceeded.

- Synonym dictionary name

- Synonym list definition file name

- Notation-correction option

- Comment

S:

Terminates processing.

Action:

Correct the information specified in the dictionary creation file or dictionary deletion file. Then, re-execute the adbsyndict command.

KFAA51502-E

The number of synonym dictionaries you are trying to register exceeds the upper limit (50). (E+M)

The number of synonym dictionaries exceeds the maximum of 50.

S:

Terminates processing.

Action:

If this message is output during registration of a synonym dictionary

A maximum of 50 synonym dictionaries can be registered.

Check the sum of the number of registered synonym dictionaries and the number of synonym dictionaries specified in the dictionary creation file. To check the sum of the number of registered synonym dictionaries, display a list of synonym dictionaries and then count the number of synonym dictionaries. For details about how to display the list of synonym dictionaries, see Checking the information about all synonym dictionaries in Checking the information about synonym dictionaries in the HADB Setup and Operation Guide.

If this message is output during deletion of a synonym dictionary

A maximum of 50 synonym dictionaries can be deleted.

Check the sum of the number of synonym dictionaries specified in the dictionary deletion file.

KFAA51503-E

The aa....aa is invalid. (path = bb....bb, reason = cc....cc, errno = dd....dd) (E+M)

One of the following specifications is invalid:

Synonym list definition file name

Name of the storage directory for synonym dictionary files

Name of the multi-node synonym dictionary storage directory

aa....aa: Invalid item

synonym-list-definition-file: Synonym list definition file name

synonym-dictionary-storage-directory: Name of the storage directory for synonym dictionary files

multi-node-synonym-dictionary-storage-directory: Name of the multi-node synonym dictionary storage directory

bb....bb: Specified path name

If cc....cc is No-definition, an asterisk (*) is displayed.

cc....cc:

Cause of the error

dd....dd:

Error number

S:

Terminates processing.

Action:

Take the corrective action for the cause of the error indicated by cc....cc.

Display of cc....cc

Cause of the error

Corrective action to take

No-file

The synonym list definition file specified in the dictionary creation file does not exist. Alternatively, anything other than a file is specified.

Correct the synonym list definition file name specified in the dictionary creation file.

Invalid-permission

Access privilege (read or write permission) for the file or directory has not been granted.

Grant access privilege (read or write permission) for the file or directory by using the OS's chmod command or the like.

No-definition

The adb_syndict_storage_path operand or adb_syndict_node_storage_path operand is not specified in the server definition.

Add the adb_syndict_storage_path operand or adb_syndict_node_storage_path operand to the server definition.

Not-directory

The specified path does not exist. Alternatively, the specified path is not a directory.

Correct the specified path name.

Illegal-symbolic-link

The link destination for the specified symbolic link cannot be acquired.

Other-access-error

An access system call error other than the above occurred.

Check the error number for the access system call in the OS documentation, and then eliminate the cause of the error.

If you cannot determine the corrective action to take based on the error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA51504-W

Failed to delete the aa....aa. (path = bb....bb, reason = cc....cc, errno = dd....dd) (E+M)

An attempt to delete the synonym dictionary file or temporary work file failed.

aa....aa: File that could not be deleted

synonym-dictionary-file: Synonym dictionary file

temporary-work-file: Temporary work file

unnecessary-file: Unnecessary file

bb....bb:

Path name of the file

cc....cc:

Cause of the error

dd....dd:

Error number

S:

Continues processing.

Action:

Take the corrective action for the cause of the error indicated by cc....cc.

Display of cc....cc

Cause of the error

Corrective action to take

No-file

The synonym dictionary file or temporary work file does not exist.

No action is needed because the file has already been deleted.

Invalid-permission

An attempt to delete the synonym dictionary file or temporary work file failed because the access privilege for the file has not been granted.

Check whether the necessary privilege for the storage directory for synonym dictionary files has been granted. For details about necessary privileges, see Assigning permissions to the directory for storing synonym dictionary files in Preparing for synonym search operations in the HADB Setup and Operation Guide.

Other-access-error

An access system call error other than the above occurred.

Check the error number for the access system call in the OS documentation, and then eliminate the cause of the error.

If an error message was output prior to this message

Take the corrective action for the error message output prior to this message and the corrective action for this message.

Even if you do not take the corrective action for this message, the adbsyndict command will not cause an error. However, unnecessary files still remain under the storage directory for synonym dictionary files. Therefore, take the corrective action for the cause of the error indicated by cc....cc. Then, execute the adbsyndict --clean command to delete the unnecessary files under the storage directory for synonym dictionary files.

If the multi-node function is used, you must also execute the adbsyndict -s command to synchronize the synonym dictionary files. Unnecessary files are automatically deleted by synchronization processing of synonym dictionary files.

If the KFAA51509-I is output in addition to this message

You can perform a synonym search because the processing to register, update, or delete the synonym dictionary has been completed. However, unnecessary files still remain under the storage directory for synonym dictionary files. Therefore, take the corrective action for the cause of the error indicated by cc....cc. Then, execute the adbsyndict --clean command to delete the unnecessary files under the storage directory for synonym dictionary files.

If the multi-node function is used, you must also execute the adbsyndict -s command to synchronize the synonym dictionary files. Unnecessary files are automatically deleted by synchronization processing of synonym dictionary files.

Note

Even if unnecessary files remain, you can perform a synonym search and execute the adbsyndict command.

KFAA51505-E

The synonym list definition file is invalid. (path = aa....aa, reason = bb....bb, line = cc....cc, column = dd....dd) (E+M)

The information specified in the synonym list definition file is invalid.

aa....aa:

Path name of the synonym list definition file

bb....bb: Cause of the error

invalid format: The format of a synonym or file is invalid.

limit over: The maximum number of synonyms that can be specified for a synonym group is exceeded. Alternatively, the number of synonym groups exceeds the maximum.

length over: The maximum number of characters that can be specified for synonyms is exceeded.

cc....cc:

Number of the row in which the synonym that caused the error is described

dd....dd:

Column in which the synonym that caused the error is described (the number of columns from the start of the line)

S:

Terminates processing.

Action:

Correct the information specified in the synonym list definition file.

If bb....bb is invalid format, check for the following errors:

A synonym group contains only one synonym.

A synonym contains a horizontal tab X'09' (HT), linefeed character X'0A' (LF), or X'00'.

Enclosing characters are not specified in pair.

Enclosing characters contained in a synonym, if any, are not specified in succession.

A delimiter and an enclosing character are not specified in succession.

A synonym contains no character.

A synonym group does not end with a linefeed.

Invalid characters are specified as the bit pattern for the character encoding specified in the ADBLANG environment variable.

KFAA51506-I

The synonym dictionary will be registered or updated with the specified values. (synonym dictionary name = aa....aa, path of the synonym list definition file = bb....bb, correction rule = cc....cc, comment = dd....dd) (M+S)

The synonym dictionary will be registered or updated.

aa....aa:

Synonym dictionary name

bb....bb:

Synonym list definition file name

cc....cc: Notation-correction option

If the notation-correction option is omitted, an asterisk (*) is displayed.

dd....dd: Comment

If the comment is omitted, an asterisk (*) is displayed.

S:

Continues processing.

KFAA51507-I

The synonym dictionary will be deleted. (synonym dictionary name = aa....aa) (M+S)

The synonym dictionary will be deleted.

aa....aa:

Synonym dictionary name

S:

Continues processing.

KFAA51508-I

A synonym dictionary file is being created for the synonym dictionary (aa....aa). (M+S)

A synonym dictionary file for the synonym dictionary aa....aa is being created.

aa....aa:

Synonym dictionary name

S:

Continues processing.

KFAA51509-I

The synonym dictionary (aa....aa) has been bb....bb. (M+S)

bb....bb processing for the synonym dictionary is completed.

aa....aa:

Synonym dictionary name

bb....bb: Operation for the synonym dictionary

registered: Registration

updated: Update

deleted: Deletion

S:

Continues processing.

KFAA51510-W

Failed to read the synonym dictionary file. (path = aa....aa, func = "bb....bb", errno = cc....cc) (E+M)

An attempt to read the synonym dictionary file failed when performing a synonym search. The synonym search can be performed, but it might require a long time.

aa....aa:

Path of the synonym dictionary file

bb....bb: Processing in which the error occurred

Opening the file

Closing the file

Moving a pointer on the file

Reading the file

cc....cc:

Error number

S:

Continues processing.

Action:

Take one of the following actions:

If the path of the synonym dictionary file is indicated by aa....aa

In the OS documentation, check the system call indicated by bb....bb and the error number indicated by cc....cc, and then eliminate the cause of the error. Then, restart the HADB server.

If you cannot determine the corrective action to take based on the system call and error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If the error is caused by the absence of a synonym dictionary file, re-create the synonym dictionary file by using the adbsyndict command. For details about how to re-create a synonym dictionary file, see Steps to take if synonym dictionary files or their storage directory is accidentally deleted in the HADB Setup and Operation Guide.

If the path of the synonym dictionary file is not indicated by aa....aa

An attempt to allocate memory for acquiring synonym dictionary information failed. Check for any unnecessary processes. If there are any unnecessary processes, stop them or delete them, and then restart the HADB server.

KFAA51511-E

The aa....aa is invalid. (reason = bb....bb, path = cc....cc, errno = dd....dd) (E+M)

The dictionary creation file or dictionary deletion file specified in the option argument of the adbsyndict command is invalid.

aa....aa: Invalid file

dictionary-creation-file: Dictionary creation file

dictionary-deletion-file: Dictionary deletion file

bb....bb:

Cause of the error

cc....cc:

Path name of the file

dd....dd:

Error number

S:

Terminates processing.

Action:

Take the corrective action for the cause of the error indicated by bb....bb.

Display of bb....bb

Cause of the error

Corrective action to take

No-file

The file specified for the option argument of the adbsyndict command does not exist. Alternatively, anything other than a file is specified.

Specify the correct path name and execute the adbsyndict command.

Invalid-permission

Access privilege (read or write permission) for the file or directory has not been granted.

Grant access privilege (read or write permission) for the file or directory by using the OS's chmod command or the like.

Invalid-path-format

The path specified for the option argument of the adbsyndict command is not an absolute path.

Specify the correct path name and execute the adbsyndict command.

Invalid-letter

Invalid characters are used in the path name. Control characters (0x01 to 0x1f, 0x7f) are specified in the path name.

Correct the path name of the dictionary creation file or dictionary deletion file.

Other-access-error

An access system call error other than the above occurred.

Check the error number for the access system call in the OS documentation, and then eliminate the cause of the error.

If you cannot determine the corrective action to take based on the error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA51512-E

Failed to delete the synonym dictionary (aa....aa). (E+M)

An attempt to delete the synonym dictionary failed because the synonym dictionary name specified in the dictionary deletion file was invalid.

aa....aa:

Invalid synonym dictionary name specified

S:

Terminates processing.

Action:

Check the synonym dictionary name specified in the dictionary deletion file. The specified synonym dictionary name is invalid (the specified synonym dictionary does not exist).

If multiple synonym dictionary names are specified in the dictionary deletion file, none of the specified synonym dictionaries are deleted if at least one of the synonym dictionary names is invalid.

KFAA51513-E

The value specified for the server definition "aa....aa" is invalid. (reason = bb....bb, errno = cc....cc) (M)

Either of the following operands specified in the server definition is invalid:

adb_syndict_storage_path

adb_syndict_node_storage_path

aa....aa:

Invalid operand specified in the server definition

bb....bb:

Cause of the error

cc....cc:

Error number

S:

Terminates processing.

Action:

Take the corrective action for the cause of the error indicated by bb....bb. Then, execute the adbstart command to start the HADB server.

Display of bb....bb

Cause of the error

Corrective action to take

Invalid-permission

Access privilege for the directory specified for the aa....aa operand has not been granted.

Grant access privilege (read or write permission) for the file or directory by using the OS's chmod command or the like.

Not-directory

The path specified for the aa....aa operand does not exist. Alternatively, the specified path is not a directory.

Correct the specified path name.

Illegal-symbolic-link

The link destination for the symbolic link specified for the aa....aa operand cannot be acquired.

Illegal-directory

A directory that cannot be specified is specified for the aa....aa.

If adb_syndict_storage_path is displayed for aa....aa

Specify a different storage directory for synonym dictionary files. For details about directories that cannot be specified as the storage directory for synonym dictionary files, see Creating the directory for storing synonym dictionary files in Preparing for synonym search operations in the HADB Setup and Operation Guide.

If adb_syndict_node_storage_path is displayed for aa....aa

Specify a different multi-node synonym dictionary storage directory. For details about directories that cannot be specified as the multi-node synonym dictionary storage directory, see Creating the multi-node synonym dictionary storage directory in Preparing for synonym search operations in Performing synonym search operations (when using the multi-node function) in the HADB Setup and Operation Guide.

Invalid-path-format

The path specified for the aa....aa operand is not an absolute path.

Change the specified path to an absolute path.

Invalid-letter

Invalid characters are used in the path name specified for the aa....aa operand. Control characters (0x01 to 0x1f, 0x7f) are specified.

Correct the specified path name.

Length-error

The path length of the directory specified for the aa....aa operand is invalid.

Other-access-error

An access system call error other than the above occurred.

Check the error number for the access system call in the OS documentation, and then eliminate the cause of the error.

If you cannot determine the corrective action to take based on the error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA51514-E

The aa....aa bb....bb operation failed. (path = cc....cc, errno = dd....dd) (E+M)

The bb....bb operation on aa....aa failed.

aa....aa: Operation target

synonym-list-definition-file: Synonym list definition file

dictionary-creation-file: Dictionary creation file

dictionary-deletion-file: Dictionary deletion file

synonym-dictionary-file: Synonym dictionary file

temporary-work-file: Temporary work file

synonym-dictionary-storage-directory: Storage directory for synonym dictionary files

synonym-list-output-file: Synonym list output file

bb....bb: Operation details

open: Opening the file

close: Closing the file

write: Writing to the file

read: Reading the file

lseek: Moving a pointer on the file

stat: File existence check

flock: Locking the file

fchmod: Changing the file mode

mkstemp: Creating a file

rename: Renaming a file

opendir: Opening the directory

readdir: Reading the directory

closedir: Closing the directory

cc....cc: Path name

If aa....aa is synonym-dictionary-storage-directory, the path name of the storage directory for synonym dictionary files is displayed.

If aa....aa is other than synonym-dictionary-storage-directory, the path name of the file on which operation failed is displayed.

dd....dd:

Error number

S:

Terminates processing.

Action:

In the OS documentation, check the system call name indicated by bb....bb and the error number indicated by dd...dd, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the displayed system call name and error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If the error number is 0, an attempt to allocate memory failed during processing to read the file. Check for any unnecessary processes. If there are any unnecessary processes, shut them down or delete them. Then, re-execute the adbsyndict command.

KFAA51515-I

Synchronization of all nodes will now start. (synonym dictionary name = aa....aa) (M+S)

Synchronization processing of synonym dictionary files for the synonym dictionary aa....aa for all nodes will now start.

aa....aa:

Synonym dictionary name

S:

Continues processing.

KFAA51516-I

Synchronization of all nodes is complete. (synonym dictionary name = aa....aa) (M+S)

Synchronization processing of synonym dictionary files for the synonym dictionary aa....aa for all nodes has ended.

aa....aa:

Synonym dictionary name

S:

Continues processing.

KFAA51517-W

The aa....aa bb....bb operation failed. (path = cc....cc, errno = dd....dd) (E+M)

Synchronization processing of file cc....cc was canceled because the bb....bb operation on aa....aa failed.

aa....aa: Operation target

synonym-dictionary-file: Synonym dictionary file

bb....bb: Operation details (system call name)

open: Opening the file

close: Closing the file

write: Writing to the file

read: Reading the file

lseek: Moving a pointer on the file

stat: File existence check

fchmod: Changing the file mode

rename: Renaming a file

cc....cc:

Path name of the file

dd....dd:

Error number

S:

Continues processing.

Action:

In the OS documentation, check the system call name indicated by bb....bb and the error number indicated by dd...dd, and then eliminate the cause of the error. Then, execute the adbsyndict -s command to re-synchronize the synonym dictionary files.

If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

If the error number is 0, an attempt to allocate memory failed during processing to read the file. Check for any unnecessary processes. If there are any unnecessary processes, shut them down or delete them. Then, execute the adbsyndict -s command to re-synchronize the synonym dictionary files.

KFAA51518-W

Node number aa....aa is not operational. (IP address = bb....bb) (E+M)

A stopped node is found.

aa....aa:

Node number of the stopped node

bb....bb:

IP address of the stopped node

S:

Continues processing.

Action:

If the stopped node has been returned to the multi-node configuration, execute the adbsyndict -s command to synchronize the synonym dictionary files.

KFAA51519-E

Failed to create a synonym dictionary file on the node. (synonym dictionary = aa....aa, node number = bb....bb, IP address = cc....cc) (E+M)

An attempt to create a synonym dictionary file failed on the node with node number bb....bb for one of the following reasons.

The primary node or secondary node with node number bb....bb was separated from a multi-node configuration during execution of the adbsyndict command

The worker node with node number bb....bb was deleted from a multi-node configuration during execution of the adbsyndict command

An error occurred on the node with node number bb....bb.

aa....aa:

Synonym dictionary file name

bb....bb:

Node number of the node on which an attempt to create a synonym dictionary file failed

cc....cc:

IP address of the node on which an attempt to create a synonym dictionary file failed

S:

Terminates processing.

Action:

If the primary node or secondary node with node number bb....bb was separated from a multi-node configuration during execution of the adbsyndict command

Return the node to the multi-node configuration, and then re-execute the adbsyndict command. If it is difficult to immediately return the node, re-execute the adbsyndict command before returning the node. After the node is returned, execute the adbsyndict -s command to synchronize the synonym dictionary files.

If the worker node with node number bb....bb was deleted from a multi-node configuration during execution the adbsyndict command

Add the node to the multi-node configuration, and then re-execute the adbsyndict command. If it is difficult to immediately add the node, re-execute the adbsyndict command before adding the node. After the node is added, execute the adbsyndict -s command to synchronize the synonym dictionary files.

If the node with node number bb....bb is running

Check the message log file for the node on which the error occurred, and then take corrective action for the output error message. Then, re-execute the adbsyndict command.

KFAA51520-W

Failed to delete a synonym dictionary file on the node. (node number = aa....aa, IP address = bb....bb) (E+M)

An attempt to delete a synonym dictionary file failed on the node with node number aa....aa.

aa....aa:

Node number of the node on which an attempt to delete a synonym dictionary file failed

bb....bb:

IP address of the node on which an attempt to delete a synonym dictionary file failed

S:

Continues processing.

Action:

Check the message log file for the node on which the error occurred, and then take corrective action for the output error message. Then, execute the adbsyndict -s command to synchronize the synonym dictionary files.

KFAA51521-W

Because the existence of the synonym dictionary file could not be confirmed on node number aa....aa, synchronous processing of the synonym dictionary file was skipped. (IP address = bb....bb) (E+M)

Because the HADB server could not confirm the existence of the synonym dictionary file on the node with node number aa....aa, synchronization processing of the synonym dictionary file on that node was skipped.

aa....aa:

Node number of the node where the error occurred

bb....bb:

IP address of the node where the error occurred

S:

Continues processing.

Action:

Re-synchronize the synonym dictionary files in the following procedure:

Check the error message that was output immediately before the KFAA51536-E message output to the message log file for the node with node number aa....aa.

Eliminate the cause of the error according to the corrective action for the error message.

Execute the adbsyndict -s command.

KFAA51522-E

Because the multi-node facility is not in use, the adbsyndict command cannot be executed with the -s option specified. (E+M)

Because the multi-node function is not used, the adbsyndict command with the -s option specified cannot be executed.

S:

Terminates processing.

Action:

If the multi-node function is not used, do not specify the -s option in the adbsyndict command.

KFAA51523-W

Because there is an invalid character in the synonym dictionary file, invalid characters were directly output to the file. (line = aa....aa, column = bb....bb) (E+M)

The synonym dictionary file contains invalid characters (characters that do not exist in the character encoding specified for the ADBLANG environment variable). Invalid characters are output as they are to the file to which the list of synonyms are output.

aa....aa: Number of the line in which invalid characters exist in the output destination file

If the list of synonyms cannot be output due to a format error of the synonym dictionary file, an asterisk (*) is displayed.

bb....bb: Column in which invalid characters exist in the output destination file (the position from the beginning of the line)

An asterisk (*) is displayed in the following cases:

If the list of synonyms cannot be output due to a format error of the synonym dictionary file

If the format of line aa....aa in the synonym dictionary file is invalid and data of that line is output

S:

Continues processing.

Action:

The synonym dictionary file is in invalid status because file is corrupted or because the file was updated by a method other than executing the adbsyndict command. A synonym search performed in this status might cause invalid search results. Take the following actions:

If the synonym dictionary file has been backed up after the synonym dictionary was registered or updated

Make sure that the backup file name is the same as the synonym dictionary file name, and then restore the synonym dictionary file from the backup.

If the synonym dictionary file has not been backed up after the synonym dictionary was registered or updated

Re-create the synonym dictionary file for the synonym dictionary for which a list of synonyms has been output. For details about how to re-create a synonym dictionary file, see Steps to take if synonym dictionary files or their storage directory is accidentally deleted in the HADB Setup and Operation Guide.

If you cannot re-create the synonym dictionary file, restore the database from the latest full backup.

KFAA51524-W

Deletion of the synonym dictionary was canceled. (E+M)

The adbsyndict command is executed successfully, but deletion of the synonym dictionary file that is no longer required is canceled.

S:

Terminates processing.

Action:

Execute the adbsyndict --clean command to delete the unnecessary files under the storage directory for synonym dictionary files.

If the multi-node function is used, you must also execute the adbsyndict -s command to synchronize the synonym dictionary files. Unnecessary files are automatically deleted by synchronization processing of synonym dictionary files.

Note

Even if unnecessary files remain, you can perform a synonym search and execute the adbsyndict command.

KFAA51525-W

The server definition "adb_syndict_node_storage_path" is not specified. To use synonym search with the multi-node facility, specify a value for "adb_syndict_node_storage_path". (E+M)

The adb_syndict_node_storage_path operand is not specified in the server definition. To perform a synonym search when the multi-node function is used, you must specify the adb_syndict_node_storage_path operand.

S:

Continues processing.

Action:

Specify the adb_syndict_node_storage_path operand in the server definition.

Note

To perform a synonym search when the multi-node function is used, you must specify both the adb_syndict_storage_path operand and the adb_syndict_node_storage_path operand in the server definition.

KFAA51526-I

The synonym dictionary file (aa....aa) for use with the multi-node facility will now be bb....bb. (M+S)

Processing to create or delete the synonym dictionary file used in the multi-node function has started.

aa....aa:

Synonym dictionary file name

bb....bb: Processing details

created: Creating the synonym dictionary file

deleted: Deleting the synonym dictionary file

S:

Continues processing.

KFAA51527-I

aa....aa of the synonym dictionary file (bb....bb) for use with the multi-node facility is complete. (M+S)

Processing to create or delete the synonym dictionary file used in the multi-node function has finished.

aa....aa: Processing details

Creation: Creating the synonym dictionary file

Deletion: Deleting the synonym dictionary file

bb....bb:

Synonym dictionary file name

S:

Continues processing.

KFAA51528-I

Output of the synonym dictionary (aa....aa) will now start. (M+S)

Processing to output the synonym list in the synonym dictionary has started.

aa....aa:

Synonym dictionary name

S:

Continues processing.

KFAA51529-I

Output of the synonym dictionary (aa....aa) is complete. (M+S)

Processing to output the synonym list in the synonym dictionary has finished.

aa....aa:

Synonym dictionary name

S:

Continues processing.

KFAA51530-E

The value aa....aa, specified to output the list of synonyms, is invalid. (reason = bb....bb) (E+M)

The specification of the -n option or -o option in the adbsyndict command executed to output the list of synonyms is invalid.

aa....aa: Argument of the invalid option

synonym-dictionary-name: Synonym dictionary name

synonym-list-output-file-path: Synonym list output file name

bb....bb: Cause of the error

invalid length: The length of the specified name is invalid.

illegal symbolic link: The link destination for the specified symbolic link cannot be acquired.

invalid character: Invalid characters that cannot be used in synonym dictionary names are specified.

illegal directory: A directory that cannot be specified is specified.

invalid path format: The specified path is not an absolute path.

duplicate: A file having the same name as the synonym list output file exists.

invalid permission: Access privilege for the directory has not been granted.

no synonym dictionary: The specified synonym dictionary name does not exist.

S:

Terminates processing.

Action:

Correct the specified -n option or -ooption, and then re-execute the adbsyndict command.

KFAA51531-I

Unnecessary files will now be deleted. (path = aa....aa) (M+S)

Processing to delete unnecessary files under the storage directory for synonym dictionary files (the directory specified for the adb_syndict_storage_path operand in the server definition) will now start.

aa....aa:

Path to the files to be deleted

S:

Continues processing.

KFAA51532-I

Deletion of unnecessary files is complete. (path = aa....aa) (M+S)

Processing to delete unnecessary files under the storage directory for synonym dictionary files (the directory specified for the adb_syndict_storage_path operand in the server definition) has finished.

aa....aa:

Path to the deleted files

S:

Continues processing.

KFAA51533-I

Failed to delete the aa....aa. (path = bb....bb, reason = cc....cc, errno = dd....dd) (M+S)

An attempt to delete aa....aa failed. The unnecessary file still remains under the storage directory for synonym dictionary files.

aa....aa: File that could not be deleted

unnecessary-file: Unnecessary file

bb....bb:

Path to the file

cc...cc: Cause of the error

Invalid-permission: Access privilege for the file or directory has not been granted.

Other-access-error: A system call error other than the above occurred.

dd....dd:

Error number

S:

Continues processing.

Action:

Take the corrective action for the cause of the error indicated by cc....cc, and then execute the adbsyndict --clean command to delete the unnecessary files under the storage directory for synonym dictionary files.

If cc....cc is Invalid-permission

An attempt to delete the file failed because the access privilege for the synonym dictionary file or temporary work file has not been granted. Grant the necessary access privilege.

If cc....cc is Other-access-error

An attempt to delete the file failed because a system call error occurred. Check the error number for the access system call in the OS documentation, and then eliminate the cause of the error.

Note

Even if unnecessary files remain, you can perform a synonym search and execute the adbsyndict command.

KFAA51534-I

The aa....aa bb....bb operation failed. (path = cc....cc, errno = dd....dd) (M+S)

The bb....bb operation on aa....aa failed. The unnecessary file still remains under the storage directory for synonym dictionary files.

If you registered, updated, or deleted the synonym dictionary by executing the adbsyndict command, the HADB server has deleted unnecessary files under the storage directory for synonym dictionary files. Because the operation on the storage directory for synonym dictionary files failed during deletion of unnecessary files, unnecessary files remain undeleted.

aa....aa: Operation target

synonym-dictionary-storage-directory: Storage directory for synonym dictionary files

bb....bb: Processing details (system call name)

opendir: Opening the directory

readdir: Reading the directory

closedir: Closing the directory

cc....cc:

Path name of the storage directory for synonym dictionary files

dd....dd:

Error number

S:

Terminates processing.

Action:

In the OS documentation, check the system call name indicated by bb....bb and the error number indicated by dd...dd, and then eliminate the cause of the error. Then, execute the adbsyndict --clean command to delete the unnecessary files.

If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Note

Even if unnecessary files remain, you can perform a synonym search and execute the adbsyndict command.

KFAA51535-W

The aa....aa bb....bb operation failed. (path = cc....cc, errno = dd....dd) (M+S)

The bb....bb operation on aa....aa failed.

If you synchronized the synonym dictionary file by executing the adbsyndict -s command, the HADB server has deleted unnecessary files under the cc....cc directory. Because the operation on the cc....cc directory failed during deletion of unnecessary files, unnecessary files remain undeleted.

aa....aa: Operation target

multi-node-synonym-dictionary-storage-directory: Multi-node synonym dictionary storage directory

bb....bb: Processing details (system call name)

opendir: Opening the directory

readdir: Reading the directory

closedir: Closing the directory

cc....cc:

Path name of the multi-node synonym dictionary storage directory

dd....dd:

Error number

S:

Terminates processing.

Action:

In the OS documentation, check the system call name indicated by bb....bb and the error number indicated by dd...dd, and then eliminate the cause of the error. Then, execute the adbsyndict -s command to synchronize the synonym dictionary files. When you synchronize the synonym dictionary files, unnecessary files are automatically deleted.

If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Note

Even if unnecessary files remain, you can perform a synonym search and execute the adbsyndict command.

KFAA51536-E

Because the existence of the synonym dictionary file could not be confirmed, synchronous processing of the synonym dictionary file was skipped. (E+M)

Because the HADB server could not confirm the existence of the synonym dictionary file, synchronization processing of that synonym dictionary file was skipped.

S:

Stops processing.

Action:

Re-synchronize the synonym dictionary files in the following procedure:

See the message log file and check the error message that was output immediately before this message.

Eliminate the cause of the error according to the corrective action for the error message.

Execute the adbsyndict -s command.

KFAA51537-W

The storage directory for the synonym file that is used with the multi-node facility does not contain the most recent version of the synonym dictionary file (aa....aa). (E+M)

The latest version of the synonym dictionary file is not stored in the multi-node synonym dictionary storage directory.

aa....aa:

Name of the synonym dictionary for which the version of the synonym dictionary file is old

S:

Continues processing.

Action:

Check whether the adb_syndict_node_storage_path operand is specified in the server definition.

If the adb_syndict_node_storage_path operand is specified

Execute the adbsyndict -s command to synchronize the synonym dictionary files.

If the adb_syndict_node_storage_path operand is not specified

After specifying the adb_syndict_node_storage_path operand, execute the adbsyndict -s command to synchronize the synonym dictionary files.

Even if the latest synonym dictionary file is not stored in the secondary node or worker node, you can perform a synonym search. However, if execution of an SQL statement is allocated to that secondary node or worker node, that execution is not performed on the secondary node or worker node. In this case, execution of the SQL statements will take place on the primary node. If this status continues, load on the primary node might increase. In addition, processing that changes the node for executing the SQL statement occurs, which might degrade search performance. For this reason, take care to synchronize the synonym dictionary files so that the latest synonym dictionary files are always stored on the secondary node or worker node.

KFAA51538-W

Failed to create a synonym dictionary file on the node. (synonym dictionary = aa....aa, node number = bb....bb, IP address = cc....cc) (E+M)

An attempt to create a synonym dictionary file failed on the node with node number bb....bb for one of the following reasons.

The primary node or secondary node with node number bb....bb was separated from a multi-node configuration during execution of the adbsyndict command

The worker node with node number bb....bb was deleted from a multi-node configuration during execution of the adbsyndict command

An error occurred on the node with node number bb....bb.

aa....aa:

Synonym dictionary file name

bb....bb:

Node number of the node on which an attempt to create a synonym dictionary file failed

cc....cc:

IP address of the node on which an attempt to create a synonym dictionary file failed

S:

Continues processing.

Action:

If the primary node or secondary node with node number bb....bb was separated from a multi-node configuration during execution of the adbsyndict command

Return the node to the multi-node configuration, and then re-execute the adbsyndict command. If it is difficult to immediately return the node, re-execute the adbsyndict command before returning the node. After the node is returned, execute the adbsyndict -s command to synchronize the synonym dictionary files.

If the worker node with node number bb....bb was deleted from a multi-node configuration during execution of the adbsyndict command

Add the node to the multi-node configuration, and then re-execute the adbsyndict command. If it is difficult to immediately add the node, re-execute the adbsyndict command before adding the node. After the node is added, execute the adbsyndict -s command to synchronize the synonym dictionary files.

If the node with node number bb....bb is running

Check the message log file for the node on which the error occurred, and then take corrective action for the output error message. Then, execute the adbsyndict -s command to synchronize the synonym dictionary files.

KFAA51539-E

The adbsyndict command cannot be executed because the cloud storage facility is being used. (E+M)

Because the cloud storage function is used, the adbsyndict cannot be executed.

S:

Terminates processing.

Action:

When using the cloud storage facility,the adbsyndict command cannot be executed. Therefore, synonym searches also cannot be performed.

KFAA52000-I

Threads for command execution were reserved. (command = "aa....aa", number of reserved threads = bb....bb) (M+S)

The command aa....aa is to be executed with bb....bb threads.

aa....aa:

Command name

bb....bb:

Number of threads to be used for command execution

S:

Continues processing.

KFAA52001-I

The number of threads that the command uses during the processing of "aa....aa" is bb....bb. (M)

The number of threads to be used in the command processing (aa....aa) is bb....bb.

aa....aa: Command processing

LOAD_RTHD: Data storage processing

SCAN_RTHD: Target table data search processing

IDXRECORD_RTHD: Index record file creation processing

SORT_RTHD: Index record file sort processing

INDEX_RTHD: Index creation and maintenance processing

OUTPUT_RTHD: Search result output processing

WATCH_RTHD: Progress monitoring processing

REMOVE_CHUNK_RTHD_NUM: Chunk deletion processing

PURGE_CHUNK_RTHD_NUM: Processing to delete data in chunks

bb....bb:

Number of threads used for aa....aa

S:

Continues processing.

KFAA52002-I

The number of threads used in the processing of "aa....aa" was set to bb....bb. (object = "cc....cc"."dd....dd") (M)

The number of processing real threads used for processing commands (aa....aa) for the target index "cc....cc"."dd....dd" has been set to bb....bb.

aa....aa: Command processing

INDEX_RTHD: Index creation and maintenance processing

bb....bb:

Number of processing real threads used for aa....aa

cc....cc:

Schema name

dd....dd:

Index identifier

S:

Continues processing.

KFAA52005-I

Now waiting for a process that is referencing table "aa....aa"."bb....bb" to finish. (command = "cc....cc") (M+S)

The system is waiting for termination of the processing that is referencing table "aa....aa"."bb....bb".

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc:

Command name

S:

Continues processing.

Action:

Wait for termination of the processing that is referencing table "aa....aa"."bb....bb". Alternatively, cancel the processing that is referencing table "aa....aa"."bb....bb".

KFAA52100-E

The file format is invalid. (command = "aa....aa", file name = "bb....bb", row = cc....cc) (E+M)

The format of the file bb....bb is invalid.

aa....aa:

Name of the executed command

bb....bb:

Input data file name

cc....cc:

Row number

S:

Terminates processing.

Action:

Data item no. cc....cc in the input data file output to bb....bb is invalid. Check the following:

When the input data file is in CSV format, make sure that there is a linefeed at the end of data item no. cc....cc. If there is no linefeed, enter a linefeed character.

When the input data file (including the linefeed code) is in a fixed-length format, make sure that the number of bytes in the linefeed code of data item no. cc....cc are included in the input record length.

Make sure that the end of data item no. cc....cc is not cut off. If the data is cut off, check the contents of the input data file, and enter the correct data.

<When the table to be imported has an array-type column defined>

Check whether the array type field data is surrounded by enclosing characters. If the array type field data is not surrounded by enclosing characters, it is possible that an array element in the array type field data tried to be imported into a non-array type column, resulting in a logical error in the input data.

In this case, use the following procedure:

Surround array type field data with enclosing characters

Re-execute the adbimport command.

If a logical error occurs in the input data, follow the instructions in the output error message and fix the error.

KFAA52101-E

Unable to acquire the cost of the column store table. (E+M)

Cost information from the column store table cannot be collected.

S:

Terminates processing.

Action:

You cannot use the command adbgetcst to collect table cost information from the column store table.

This message is output when the column store table is specified for the -t option of the command adbgetcst.

KFAA52110-E

The HADB encryption key file is specified incorrectly, or the HADB encryption key usage password is incorrect. (file name = "aa....aa") (E+M)

Either the HADB encryption key file is incorrectly specified or the HADB encryption key usage password is invalid.

aa....aa: HADB encryption key file name

The path name of the HADB encryption key file is displayed as an absolute path.

S:

Terminates processing.

Action:

Check the following: Once this is done, re-execute the command.

Is a file other than the HADB encryption key file specified?

Is the HADB encryption key usage password specified correctly?

KFAA52111-E

The command cannot be executed, because the DB area encryption facility is not in use. (command = "aa....aa") (E+M)

The command cannot be executed because the DB area encryption facility is not used.

aa....aa:

Name of the executed command

S:

Terminates processing.

Action:

Execute the command while using the DB area encryption facility.

For details about how to check whether you are using the DB area encryption facility, see Checking whether the DB area encryption facility is used in the HADB Setup and Operation Guide.

KFAA52112-E

The same HADB encryption key cannot be specified as both the current HADB encryption key and the new HADB encryption key. (E+M)

The same HADB encryption key cannot be specified for the HADB encryption key in use and the new HADB encryption key.

S:

Terminates processing.

Action:

Make sure that the following HADB encryption key file name specified in an adbexport command's options is correct. Once this is done, re-execute the command.

HADB encryption key file in use (file name specified in the server definition's adb_crypto_dmkey_path operand).

New HADB encryption key file name

For the new HADB encryption key file name, specify the HADB encryption key file previously created with the adbmkdmk command. If the previously created HADB encryption key file is unknown, see Updating the HADB Encryption Key in the manual HADB Setup and Operation Guide and update the HADB encryption key again.

KFAA52113-E

You cannot specify an HADB encryption key file other than the HADB encryption key file that is currently in use. (E+M)

A HADB encryption key different to the HADB encryption key in use cannot be specified.

S:

Terminates processing.

Action:

Make sure that the name of the HADB encryption key file in use specified in the options of the adbupddmk command is the same as the name of the HADB encryption key file in use on the HADB server (the file name specified in the adb_crypto_dmkey_path operand of the server definition). Once this is done, re-execute the command.

KFAA52200-E

The operand "aa....aa" cannot be used. Use the operand "bb....bb". (M)

You can no longer specify the operand aa....aa in the server definition. Specify the operand bb....bb in the server definition instead.

aa....aa: Name of the operand that can no longer be specified

adb_cmd_rthd_num

bb....bb: Name of the operand to specify

adb_sql_exe_max_rthd_num

S:

Stops the HADB server's start processing.

Action:

You cannot specify the operand adb_cmd_rthd_num in HADB server version 04-01 or later versions. Therefore, delete this operand. The operand adb_sql_exe_max_rthd_num takes the place of the operand adb_cmd_rthd_num. Therefore, revise the value specification for the operand adb_sql_exe_max_rthd_num, and then start the HADB server.

For details about the actions to take when the operand adb_cmd_rthd_num is specified, see Re-examining the values specified in the server definition and command options (version 04-01 or later) in Steps to take after version upgrading in the HADB Setup and Operation Guide.

KFAA52201-W

The operand "aa....aa" is specified. (M)

The aa....aa operand is specified in the server definition.

aa....aa: Operand name

adb_sta_log_size_unit

S:

Continues processing.

Action:

The adb_sta_log_size_unit operand, specified during verification of system operation, can be used to change the unit of the maximum size of statistics log files. If this message is output at any time other than during verification of system operation, comment out the adb_sta_log_size_unit operand. In addition, confirm that there is no problem with the value specified for the adb_sta_log_max_size operand in the server definition.

KFAA52202-E

The adbimport command cannot be executed in addition mode because the cloud storage facility is being used. (E+M)

When using the cloud storage facility, data import cannot be performed in addition mode.

S:

Terminates processing.

Action:

If you are using the cloud storage facility, re-execute the adbimport command with the background-import facility applied (-b option specified).

KFAA52203-E

The option --concurrency-prior cannot be specified because an archivable multi-chunk table is specified. (E+M)

The --concurrency-prior option cannot be specified because an archivable multi-chunk table is specified in the table to be processed.

S:

Terminates processing.

Action:

Re-execute the adbmergechunk command without specifying the --concurrency-prior option.

KFAA52204-I

A conflict with other processing for a locked resource was detected. Execution of the other processing will be prioritized. (name = aa....aa, object = bb....bb) (M+S)

A conflict with another process has occurred for a locked resource. The execution of other processes is given priority.

aa....aa: Locked resource where the conflict arose

TABLE: Table

bb....bb: Locked resource to be acquired

bb....bb is output in the format of "schema-name"."table-identifier"

S:

Continues processing.

2.4 Messages from KFAA60000 to KFAA69999

KFAA60001-E

An error occurred during processing to initialize the HADB system. For more information, see the message log. (L+M)

An error occurred during HADB server start processing. For details, check the message log file.

S:

Terminates processing.

Action:

Check the message log file and eliminate the cause of the error. Then, execute the adbstart command again to start the HADB server.

KFAA60002-E

An error occurred during processing to terminate the HADB system. For more information, see the message log. (L+M)

An error occurred during HADB server termination processing. For details, check the message log file.

S:

Terminates processing.

Action:

Check the message log file and eliminate the cause of the error. Then, execute the adbstop command again to terminate the HADB server.

KFAA60003-E

The HADB system aborted because an error occurred. (information 1= aa....aa, information 2 = bb....bb, information 3 = cc....cc, information 4 = dd....dd, information 5 = ee....ee, information 6 = ff....ff) (L+M)

The HADB server, a command, or an application program terminated abnormally because an error occurred.

aa....aa to ff....ff: Troubleshooting information

If no information to display exists, three asterisks (***) are displayed.

In addition, the abort code may be output as troubleshooting information in bb....bb. For details about the abort code, see 3.1 Abort codes

S:

Terminates the HADB server abnormally.

Action:

Take the appropriate action based on the message indicating the cause of error that was output immediately before this message.

KFAA60004-E

An error occurred in the HADB system. (information = aa....aa) Save troubleshooting information by the "adbinfoget" command, and then contact customer service. (M)

A failure has occurred on the HADB server.

aa....aa:

Troubleshooting information

S:

Terminates the HADB server abnormally.

Action:

Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA60005-E

An internal contradiction was detected in the HADB system. (information 1 = aa....aa, information 2 = bb....bb, information 3 = cc....cc, information 4 = dd....dd, information 5 = ee....ee, information 6 = ff....ff) Save troubleshooting information by the "adbinfoget" command, and then contact customer service. (L+M)

This message is output when an internal conflict is detected.

aa....aa to ff....ff: Troubleshooting information

If no information to display exists, three asterisks (***) are displayed.

In addition, the abort code may be output as troubleshooting information in bb....bb. For details about the abort code, see 3.1 Abort codes

S:

Terminates the HADB server abnormally.

Action:

Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA60007-E

An internal contradiction was detected in the HADB system. (information 1 = aa....aa, information 2 = bb....bb, information 3 = cc....cc, information 4 = dd....dd, information 5 = ee....ee, information 6 = ff....ff) Save troubleshooting information by the "adbinfoget" command, and then contact customer service. (L+M)

This message is output when an internal conflict is detected.

aa....aa to ff....ff: Troubleshooting information

If no information to display exists, three asterisks (***) are displayed.

In addition, the abort code may be output as troubleshooting information in bb....bb. For details about the abort code, see 3.1 Abort codes

S:

Terminates processing.

Action:

Execute the adbinfoget command, collect troubleshooting information, and then contact the customer support center. After that, re-execute the SQL statement or command.

KFAA60008-W

Only one server is running in a multi-node configuration. (host name = aa....aa, IP address = bb....bb) (L+M)

Only one node (excluding worker nodes) is operating in a multi-node configuration.

aa....aa: Host name

Name of the host of the operating node

bb....bb: IP address

IP address of the operating node

S:

Continues processing.

Action:

If necessary, return another node to the multi-node configuration.

Important

This message is a warning message that is output when the secondary node (the node for primary node switchover) runs out.

Worker nodes will not be the nodes for primary node switchover. Therefore, if the current primary node terminates abnormally, the HADB server in the multi-node configuration will terminate abnormally even if multiple worker nodes are in operation.

KFAA60009-E

The HADB server in the multi-node configuration will now stop, because aa....aa. (L+M)

The HADB server in the multi-node configuration will terminate for the following reason.

No node can switch over to a primary node.

aa....aa: Reason of termination of HADB server in multi-node configuration

there is no node that can switch over to the primary node

No node can switch over to a primary node.

S:

Terminates processing.

Action:

See the message output in the message log file, and then eliminate the cause of the error. Then, start the HADB server in a multi-node configuration.

KFAA60010-W

The HADB server of the connection-destination node terminated abnormally. (node number = aa....aa, host name = bb....bb, IP address = cc....cc) (L+M)

An abnormal termination was detected on the HADB server at the connection target.

aa....aa:

Number of the node where abnormal HADB server termination was detected

bb....bb:

Host name of the node where abnormal HADB server termination was detected (communication between servers)

cc....cc:

IP address of the node where abnormal HADB server termination was detected (communication between servers)

S:

Continues processing.

Action:

If this message is output on the primary or secondary node

Remove the cause of the error that triggered the abnormal termination of the HADB server. Then, return the node disconnected from the multi-node configuration to the multi-node configuration. For details about how to return the node to the multi-node configuration, see Returning a node to the multi-node configuration in the HADB Setup and Operation Guide.

If this message is output on a worker node

Remove the cause of the error that triggered the abnormal termination of the HADB server. Then, add the worker node deleted from the multi-node configuration to the multi-node configuration. For details about how to add the worker node to the multi-node configuration, see Re-adding a worker node deleted from the multi-node configuration in the HADB Setup and Operation Guide.

KFAA60012-E

A inconsistency occurred between the node status of HADB server and the server status of HA monitor. Terminate either the HADB server on the other node (node number = aa....aa) or the HADB server on local node forcibly. (L+M)

An inconsistency occurred between the node status of the HADB server and the server status of HA Monitor.

Forcibly terminate the HADB server on the node with node number aa....aa or the HADB server on the node where this message was output.

aa....aa:

Node number of the node with inconsistent status

S:

Continues processing.

Action:

If this message is output on the primary node

On the secondary node with aa....aa, execute the adbstop --force command to forcibly terminate the HADB server.

If necessary, return the node disconnected from the multi-node configuration to the multi-node configuration.

If this message is output on the secondary node

If aa....aa indicates the primary node, execute the adbstop --force command to forcibly terminate the HADB server on the node where this message was output.

If aa....aa indicates a secondary node, forcibly terminate the HADB server on either of the following nodes by using the adbstop --force command:

The node where this message was output

The node of aa....aa

Of the above nodes, forcibly terminate the HADB server on the node for which a larger value is specified for the standbypri operand in HA Monitor's servers file.

If necessary, return the node disconnected from the multi-node configuration to the multi-node configuration.

KFAA60013-E

The processing to switch over to the primary node failed because the HADB server of switching destination node was performing termination processing. (L+M)

An attempt to switch over a primary node failed because the HADB server on the switching destination node was performing termination processing.

S:

Terminates processing.

Action:

If primary node switchover failed, another secondary node is selected as the switching destination (the secondary node with the next higher priority is selected by HA Monitor).

If the switching-destination secondary node does not exist, the HADB server in the multi-node configuration terminates. If necessary, start the HADB server in the multi-node configuration.

KFAA60014-W

The aa....aa processing is delayed. (file = bb....bb) (L+M)

The aa....aa processing for the file bb....bb is delayed.

aa....aa: Processing that is delayed

read: Read processing

write: Write processing

bb....bb:

File name

S:

Continues processing.

Action:

A failure might have occurred on the disk where the file bb....bb is stored. Terminate the HADB server, and then check whether a disk failure occurred. If a disk failure occurred, eliminate the cause of the failure. Then, start the HADB server.

If no disk failure occurred, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA60100-E

An internal parameter is invalid. (information1 = aa....aa, information2 = bb....bb, information3 = "cc....cc") Save troubleshooting information by the "adbinfoget" command, and then contact customer service. (M)

An internal parameter is invalid.

aa....aa:

Troubleshooting information 1

bb....bb:

Troubleshooting information 2

cc....cc:

Troubleshooting information 3

S:

Terminates processing.

Action:

Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA60200-W

Reorganization is recommended for the chunk with the chunk ID "aa....aa" in the table "bb....bb"."cc....cc". (E+M)

We recommend that you reorganize chunk data (chunk ID "aa....aa") in the table "bb....bb"."cc....cc".

aa....aa:

Chunk ID

bb....bb:

Schema name

cc....cc:

Table identifier

S:

Continues processing.

Action:

Performance of data retrieval from the chunk data (chunk ID "aa....aa") in the table "bb....bb"."cc....cc" might have decreased due to addition, update, or deletion repeated by SQL statements. We recommend that you reorganize chunk data (chunk ID "aa....aa") in the table "bb....bb"."cc....cc".

For details about how to reorganize data in multi-chunk tables and the causes of decreased retrieval performance, see Checking whether a multi-chunk table needs to be reorganized in the HADB Setup and Operation Guide.

For details about how to reorganize data in single-chunk tables and the causes of decreased retrieval performance, see Checking whether a single-chunk table needs to be reorganized in the HADB Setup and Operation Guide.

KFAA60209-E

A logical inconsistency occurred in the program. (func = aa....aa, invalid data = bb....bb) (L+M)

A logical inconsistency has occurred in the program.

aa....aa:

Function name

bb....bb:

Invalid data

S:

Terminates processing.

Action:

Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA60284-E

The data type aa....aa is not supported. (L+M)

Data type aa....aa is not supported.

aa....aa:

Data type

S:

Terminates processing.

Action:

Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA60300-E

Initialization of the communication service failed. (reason = "aa....aa") (L+M)

Initialization of the communication service has failed.

aa....aa: Cause of the error

environment: The server environment is invalid.

resource: Insufficient system resources

system call: A system call error

S:

Terminates processing.

Action:

Open the message log file and check the messages that were output prior to this message. Eliminate the cause of the error based on those messages, and then retry the operation.

KFAA60302-E

An unexpected error occurred. (info. = "aa....aa") Save troubleshooting information by the "adbinfoget" command, and then contact customer service. (L+M)

An unexpected error has occurred.

aa....aa:

Maintenance information

S:

Terminates processing.

Action:

Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA61200-W

Page allocation is delayed. (DB area = aa....aa, page type = b) (L+M)

Page allocation has been delayed.

aa....aa:

Affected DB area name

b: Page whose allocation is delayed

d: Directory page

w: Work table page

t: Data page

h: Upper page

f: Leaf page

r: Row ID directory page

s: Row ID list page

a: Range index page

i: String control page

p: Position control page

S:

Continues processing.

Action:

The number of global buffer sectors allocated to the DB area might be insufficient.

Once processing has terminated, execute the adbstop command to terminate the HADB server. Then, take one of the following corrective actions:

If the affected DB area name aa....aa is specified in the server definition's adbbuff operand

Take corrective action as described in the following table:

Target page displayed for b

Corrective action

-a option specified

-a option omitted

The target page is a.

Increase the value specified in the -a option of the adbbuff operand.

Increase the value specified in the -p option of the adbbuff operand.

The target page is not a.

Increase the value specified in the -p option of the adbbuff operand.

If the affected DB area name aa....aa is not specified in the server definition's adbbuff operand

Allocate a new global buffer to the affected DB area name aa....aa.

Once you have taken the appropriate corrective action, start the HADB server with the adbstart command, and then re-execute the processing.

KFAA61205-W

During execution of aa....aa, key values on a unique index were duplicated. Processing for aa....aa will continue. (index ID = bb....bb) (L+M)

Duplicate key values were inserted in an index while the aa....aa command was being executed. Command processing continues.

aa....aa:

Name of the command that was executing

bb....bb:

Index ID

S:

Continues processing.

Action:

The affected index violates uniqueness constraints. Find the duplicate key values in the table for which that index is defined, and then delete the lines that have the duplicate key values.

For details about how to find duplicate key values, see Steps to take when the uniqueness constraint is violated (when the KFAA61205-W message is output) in the HADB Setup and Operation Guide.

Note that you can use an index ID as a key to identify the names of the table and column in which key value duplication exists. For details about how to do this, see Searching a dictionary table in the HADB Setup and Operation Guide.

KFAA61210-E

DB area pages are insufficient. DB area = "aa....aa" (L+M)

A DB area file cannot be expanded because there is not enough free disk space.

aa....aa:

DB area name

S:

Invalidates this transaction.

Action:

Change the storage location of the DB area file. Alternatively, expand the disk space that holds DB area files. For details about this problem, see Problems related to free space on the disk in the HADB Setup and Operation Guide.

KFAA61211-E

The amount of free space in the system log file "aa....aa" is insufficient. (L+M)

There is not enough storage area for the system log file.

aa....aa:

System log file name

S:

Invalidates this transaction.

Action:

Allocate a sufficient amount of space on the disk that stores the system log file aa....aa, and then re-execute the operation.

KFAA61212-W

An attempt to delete an archive directory failed. (L+M)

An attempt to delete an archive directory failed.

S:

Ignores the error indicated in the KFAA41205-E message and then continues processing.

Action:

Check the existence of the file or directory indicated by aa....aa in the KFAA41205-E message that was output immediately prior to this message.

▪ If the file or directory does not exist:

Check whether the file or directory under the archive directory has been deleted. Files and directories under the archive directory can be deleted only when an instruction is given from the HADB server.

▪ If the file or directory exists:

Perform the following procedure to take action.

In the OS documentation, check the system call name indicated by bb....bb and the error number indicated by cc....cc in the KFAA41205-E message that was output immediately prior to this message, and then eliminate the cause of the error.

If an error occurred in a symbolic link file, check the link target files in addition to that file.

If you cannot determine the corrective action to take based on the displayed system call name and error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Execute the adbdbstatus command for all the archivable multi-chunk tables to acquire usage information for the archived chunks.

Confirm the archive file name output to the Archive_file_name column of usage information.

If the directory name indicated by aa....aa in the KFAA41205-E message is not included in the archive file path name you confirmed in step 3, delete this directory.

(Example)

Assume that /aaa/bbb/ccc is indicated by aa....aa in the KFAA41205-E message.

If /aaa/bbb/ccc is indicated in the Archive_file_name column

Do not delete the directory indicated by aa....aa.

If /aaa/bbb/ddd is indicated in the Archive_file_name column

Delete the directory indicated by aa....aa.

If /aaa/bbb/ccc/ddd is indicated in the Archive_file_name column

Do not delete the directory indicated by aa....aa.

Note that if the archive directory has been created on another server, the possible causes of the error are as follows:

A communication is not established between servers.

The file system containing the archive directory is not mounted correctly.

If the HADB server terminates abnormally during processing to restore the database due to rollback, restart of the HADB server, or primary node switchover, deletion processing is performed again for the deleted directory. At this time, even if this message and the KFAA41205-E message are output, you can ignore them.

KFAA61213-W

The number of unused segments will soon not be enough to reorganize the table "aa....aa"."bb....bb". Only cc....cc% of the segments remain unused. Execute the adbreorgsystemdata command for the table. (L+M)

The number of unused segments will soon not be enough to reorganize the table aa....aa.bb....bb. cc....cc% of the segments remain unused. Execute the adbreorgsystemdata command for the table aa....aa.bb....bb.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc:

Percentage (50, 30, 20, or 10)

S:

Continues processing.

Action:

Execute the adbreorgsystemdata command for the table aa....aa.bb....bb. For details about the adbreorgsystemdata command, see adbreorgsystemdata (Reorganize Dictionary Table and System Table) in the manual HADB Command Reference.

If the number of segments used by the table aa....aa.bb....bb and by the index defined for this table aa....aa.bb....bb exceeds the number of unused segments, the adbreorgsystemdata command might be disabled. If the adbreorgsystemdata command cannot be executed, invalid row data continuously increases and finally, no free space will be left on the disk to store DB area files. As a result, operation that updates the dictionary table (base table) or system table (base table) can no longer be performed.

For details about how to reorganize the dictionary table (base table) or system table (base table), see Reorganizing dictionary tables and system tables in the HADB Setup and Operation Guide.

KFAA61214-W

The number of unused segments is not enough to reorganize the table "aa....aa"."bb....bb". Execute the adbreorgsystemdata command for the table as soon as possible. (L+M)

The number of unused segments is not enough to reorganize the table aa....aa.bb....bb. Immediately execute the adbreorgsystemdata command for the table aa....aa.bb....bb.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

Action:

Immediately execute the adbreorgsystemdata command for the table aa....aa.bb....bb. For details about the adbreorgsystemdata command, see adbreorgsystemdata (Reorganize Dictionary Table and System Table) in the manual HADB Command Reference.

If executing the adbreorgsystemdata command results in the KFAA30756-E message output, follow the instruction of the corrective action for the KFAA30756-E message.

KFAA61220-E

An internal contradiction was detected in the interface with the Apache Arrow library. (cause = "aa....aa", information = "bb....bb") (L+M)

An internal inconsistency was detected in the interface part in the library for accessing foreign data.

aa....aa: Cause of the internal inconsistency

Invalid memory size for URI information: The memory size for URI information is invalid.

Invalid argument: The argument is invalid.

C++ Exception: An exception occurred in C++ processing.

bb....bb:

Maintenance information

S:

Terminates processing.

Action:

Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA61400-W

Failed to delete aa....aa. (S+L+M)

An attempt to delete aa....aa failed.

aa....aa:

an unload file: Unload file

S:

Ignores the error indicated in the KFAA41205-E message and continues processing.

Action:

Check the existence of the file or directory indicated by aa....aa in the KFAA41205-E message that was output immediately prior to this message.

If the file or directory does not exist

The unload file has already been deleted. No action is needed.

If the file or directory exists

In the OS documentation, check the system call name indicated by bb....bb and the error number indicated by cc....cc in the KFAA41205-E message that was output immediately prior to this message, and then eliminate the cause of the error.

If you cannot determine the corrective action to take based on the displayed system call name and error number, execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Eliminate the cause of the error, and then delete the target file.

KFAA61600-E

An internal contradiction was detected in the interface with the Apache Iceberg library. (cause = "aa....aa", information = "bb....bb") (L+M)

An internal inconsistency was detected in the interface part with the Apache Iceberg library.

aa....aa: Cause of the internal inconsistency

Invalid memory size for URI information: The memory size for URI information is invalid.

Invalid argument: The argument is invalid.

Rust Exception: An exception occurred in Rust processing.

bb....bb:

Maintenance information

S:

Terminates processing.

Action:

Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

2.5 Messages from KFAA70000 to KFAA79999

KFAA70000-I

A connection was established. (connection identifier = aaaa, application identifier = "bb....bb", client group = "cc....cc", connection serial number = dd....dd, connection information = ee....ee) (M)

A connection to the HADB server has been established. The connection ID is aaaa.

aaaa:

Connection ID

bb....bb:

Application identifier

cc....cc:

Name of the client group to which the client belongs, or name of the command group to which the command belongs

dd....dd:

Connection sequence number (starting with 1) that is allocated after the HADB server starts

ee....ee:

Connection information

S:

Continues processing.

KFAA70001-I

The connection was ended. (connection identifier = aaaa, connection information = bb....bb) (M)

The connection of connection ID aaaa has been terminated.

aaaa:

Connection ID

bb....bb:

Connection information

S:

Continues processing.

KFAA70002-I

The client directory specified for the environment variable ADBCLTDIR is "aa....aa". (M)

The client directory specified in environment variable ADBCLTDIR is aa....aa.

aa....aa:

Path of the client directory specified in environment variable ADBCLTDIR

S:

Continues processing.

KFAA70003-I

The HADB client version is "aa....aa(bb....bb)". (M)

The version of the HADB client is aa....aa(bb....bb).

aa....aa:

The HADB client version

This is output in the format vv-rr-zz. zz might not be output.

vv: Version number

rr: Revision number

zz: Code

bb....bb:

Additional version information for the HADB client

S:

Continues processing.

KFAA70004-I

The character encoding specified for the environment variable ADBCLTLANG is "aa....aa". (M)

The character encoding specified for the environment variable ADBCLTLANG is aa....aa.

aa....aa:

The character encoding specified for the environment variable ADBCLTLANG

S:

Continues processing.

KFAA70005-I

The HADB client has sent an SQL statement to the HADB server. (SQL statement = "aa....aa", node number=b) (M)

The HADB client has sent SQL statement aa....aa to the HADB server.

aa....aa: Specified SQL statement

Only the first 2,048 bytes of the SQL statement is output.

b: Node number

If you are not using the multi-node function, the node number is always 1.

S: Continues processing.

If an error occurred during preprocessing of the SQL statement output by this message, (for a_rdb_SQLExecDirect(), this also includes when the SQL statement is executed), an error message is output immediately after this message.

KFAA70006-I

A transaction isolation level was set. (isolation level = "aa....aa") (M)

The transaction isolation level has been set to aa....aa.

aa....aa: The transaction isolation level set

READ COMMITTED

REPEATABLE READ

S:

Continues processing.

KFAA70008-E

ISO cannot be specified for the sorting order, because the character encoding to be used on the HADB client is not Unicode (UTF-8). (ADBCLTLANG = aa....aa, adb_clt_sql_order_mode = bb....bb) (M)

ISO cannot be specified as the sort order because the character encoding used by the HADB client is not Unicode (UTF-8).

aa....aa: Value of the ADBCLTLANG environment variable

SJIS: Shift-JIS is specified as the character encoding used by the HADB client.

bb....bb: Value of the adb_clt_sql_order_mode client definition operand

ISO: ISO is specified as the sort order.

S:

Continues processing.

Action:

Specify BYTE in the adb_clt_sql_order_mode client definition operand, and then re-execute the application program.

KFAA70009-I

The transaction access mode was set. (access mode = "aa....aa") (M)

A transaction access mode was set.

aa....aa: Transaction access mode that was set

READ WRITE: Read/write mode

READ ONLY: Read-only mode

S:

Continues processing.

KFAA71002-E

This object is not active because a transaction terminated. (J)

This object was invalidated because its transaction has terminated (which includes implicit rollbacks). <SQLSTATE: R2411>

S:

Terminates processing.

Action:

Re-create the relevant Statement, PreparedStatement, and ResultSet objects.

KFAA71017-E

The table type is invalid. (index = aa....aa, table type = bb....bb) (J)

The type of the table specified by the getTables method argument for the String-type array is invalid. <SQLSTATE: R2412>

aa....aa: Subscript of String-type array

If a String-type array with a length of 0 is specified, 0 is displayed.

bb....bb: Value of specified table type

If a String-type array with a length of 0 is specified, *** is displayed.

S:

Terminates processing.

Action:

Specify the table type correctly.

KFAA71202-E

Processing cannot continue because the statement is already closed. (J)

Processing cannot be accepted because the Statement instance is already closed. <SQLSTATE: R2413>

S:

Terminates processing.

Action:

Re-generate the Statement instance, and then retry the operation.

KFAA71203-E

Conversion of the character encoding failed. (J)

Conversion of the character encoding failed. <SQLSTATE: R2414>

S:

Terminates processing.

Action:

Check and, if necessary, revise the following values:

The value of the property ENCODELANG specified when a connection to the database is established

The value of encodelang in the URL specified when a connection to the database is established

The value specified for the setEncodeLang method, which is a connection information setup method

Also make sure that invalid characters are not contained in the character string that was being handled when an error occurred.

KFAA71204-E

Reading of java.io.Reader or java.io.InputStream failed. (J)

An attempt to read from the java.io.Reader or java.io.InputStream specified by one of the following methods of the PreparedStatement interface has failed. <SQLSTATE: R2415>

setAsciiStream

setCharacterStream

S:

Terminates processing.

Action:

Carefully review the specified java.io.Reader or java.io.InputStream.

KFAA71206-E

Processing cannot continue because the connection is already closed. (J)

Processing cannot be accepted because the Connection instance is already closed. <SQLSTATE: R2416>

S:

Terminates processing.

Action:

Re-generate the Connection instance, and then retry the operation.

KFAA71209-E

The method is not supported. (method = aa....aa) (J)

Method aa....aa cannot be used because is not supported. <SQLSTATE: R2417>

aa....aa:

Method name

S:

Terminates processing.

Action:

Make sure that method aa....aa is not called.

KFAA71210-E

Batch SQL processing failed because the result set of the following SQL was returned. (SQL = "aa....aa") (J)

Batch processing cannot be performed because the SQL statement aa....aa returns a result set. <SQLSTATE: R2418>

aa....aa:

SQL statement

S:

Terminates processing.

Action:

Carefully review the specified SQL statement.

KFAA71211-E

The fetch direction is not supported. (direction = aa....aa) (J)

The operation cannot be executed because aa....aa, which was specified with the setFetchDirection method, is not supported. <SQLSTATE: R2419>

aa....aa: The literal name defined by the ResultSet of the value specified with the setFetchDirection method

However, when the specified value is not defined with ResultSet, aa....aa is the value specified with the setFetchDirection method.

S:

Terminates processing.

Action:

Specify ResultSet.FETCH_FORWARD.

KFAA71212-E

The fetch size is invalid. (size = aa....aa) (J)

The value aa....aa of an argument specified with the setFetchSize method has one of the following errors. <SQLSTATE:R2420>

The argument has a value outside the range 0 to 65535.

The value specified with the setMaxRows method is 1 or more, and the value specified with the setFetchSize method is greater than the value specified with the setMaxRows method.

The value specified with the setLargeMaxRows method is 1 or more, and the value specified with the setFetchSize method is greater than the value specified with the setLargeMaxRows method.

aa....aa:

The value of the argument specified with the setFetchSize method

S:

Terminates processing.

Action:

Carefully review the contents of the specified argument.

KFAA71218-E

Processing cannot continue because aa....aa is already closed. (J)

Processing cannot be accepted because the aa....aa instance is already closed. <SQLSTATE: R2421>

aa....aa:

Instance name

S:

Terminates processing.

Action:

Re-generate the aa....aa instance, and then retry the operation.

KFAA71222-E

Unable to acquire the object of the specified class = aa....aa in the unwrap method. (J)

Objects of the class specified by the unwrap method of the Wrapper interface cannot be acquired. <SQLSTATE: R2423>

aa....aa:

The fully qualified name of the class specified as an argument of the unwrap method

S:

Terminates processing.

Action:

Specify an appropriate class.

KFAA71223-E

The length of an SQL statement exceeds 16,000,000 characters. (J)

The length of an SQL statement exceeds 16,000,000 characters. <SQLSTATE: R2473>

S:

Ignores this SQL statement.

Action:

Correct the SQL statement length.

KFAA71301-E

Registration of the JDBC driver failed. (J)

An attempt to register the JDBC driver with the driver manager has failed. <SQLSTATE: R2424>

S:

Terminates processing.

Action:

There might be a problem with the Java execution environment. Check for Java execution environment-related problems, such as problems with the JRE version.

KFAA71446-W

The result set type was changed to aa....aa because the TYPE_SCROLL_SENSITIVE result set type is not supported. (J)

The result set type was changed to aa....aa because the result set type that allows scrolling with updated content is not supported. <SQLSTATE: 01J11>

aa....aa:

Result set type after the change

S:

Continues processing.

KFAA71447-W

The result set type was changed to the concurrent processing type aa....aa because CONCUR_UPDATABLE result sets are not supported. (J)

The result set type was changed to aa....aa, the concurrent processing type, because updatable result sets are not supported. <SQLSTATE: 01J12>

aa....aa:

Concurrent processing type in the result set, after the change

S:

Continues processing.

KFAA71448-E

The result set type is invalid. (type = aa....aa) (J)

The scroll type value aa....aa of the specified result set is an invalid scroll type that is not defined by ResultSet. <SQLSTATE: R2425>

aa....aa:

Scroll type value for the specified result set

S:

Terminates processing.

Action:

Carefully review the scroll type of the result set.

KFAA71449-E

The result set concurrency type is invalid. (concurrency = aa....aa) (J)

The concurrent processing type value aa....aa of the specified result set is an invalid concurrent processing type that is not defined by ResultSet. <SQLSTATE: R2426>

aa....aa:

Value of concurrent processing type for the specified result set

S:

Terminates processing.

Action:

Carefully review the concurrent processing type of the result set.

KFAA71450-E

The escape syntax is invalid. (code = aaaa) (J)

The escape clause of the specified SQL statement is invalid. <SQLSTATE: R2427>

aaaa: Reason code

0001: The escape clause contains { and keywords (d, t, ts, escape, fn) but does not contain }.

0009: No argument is specified following LOG10 in the escape clause.

S:

Terminates processing.

Action:

Specify a valid escape clause.

KFAA71452-E

The connection information specified in aa....aa is invalid. (value = "bb....bb") (J)

The connection information specified by aa....aa is invalid. <SQLSTATE: R2428>

aa....aa:

■If the connection was established using the getConnection method of the DriverManager class

One of the following is displayed:

Settings specified for the URL or user properties

Note that the following information is displayed, just as for user properties, even if the URL's host name or port number is invalid.

• Host name: adb_clt_rpc_srv_host

• Port number: adb_clt_rpc_srv_port

setLoginTimeout

If the value specified with the setLoginTimeout method is invalid, setLoginTimeout is displayed.

■If the setXXX method for setting connection information of the DataSource or ConnectionPoolDataSource class is executed

The method name of the setXXX method is displayed.

■In other cases

The item specified for a system property is displayed.

bb....bb: Value specified by aa....aa

If no value was specified, null is displayed.

S:

Terminates processing.

Action:

Carefully review the connection information specified by aa....aa.

KFAA71453-E

The result set holdability value (aa....aa) is invalid. (J)

The value aa....aa of the holdability of the specified result set is an invalid value that is not defined in the ResultSet class. <SQLSTATE: R2429>

aa....aa:

Holdability value in the specified result set

S:

Terminates processing.

Action:

Carefully review the holdability value of the result set.

KFAA71454-W

The result set holdability value was changed to aa....aa because the CLOSE_CURSORS_AT_COMMIT result set holdability is not supported. (J)

Because CLOSE_CURSORS_AT_COMMIT cannot be specified for the result set holdability, the result set holdability has been changed to aa....aa. <SQLSTATE: 01J13>

aa....aa:

Holdability of the result set after the change

S:

Continues processing.

KFAA71562-E

The max rows value is invalid. (value = aa....aa) (J)

Negative values cannot be specified for the maximum selection row count that is specified with the setMaxRows method or setLargeMaxRows method. <SQLSTATE: R2430>

aa....aa:

The value for the maximum selection row count specified with the setMaxRows method or setLargeMaxRows method

S:

Terminates processing.

Action:

Carefully review the maximum selection row count specified with the setMaxRows method or setLargeMaxRows method.

KFAA71563-E

The SQL statement is invalid. It might be NULL or empty. (J)

The specified SQL statement might be a null value or a character string with a length of 0. <SQLSTATE: R2431>

S:

Terminates processing.

Action:

Correct the SQL statement.

KFAA71564-E

The query timeout value is invalid. It might be negative. (value = aa....aa) (J)

Negative values cannot be specified for the timeout value that is specified with the setQueryTimeout method. <SQLSTATE: R2432>

aa....aa:

Timeout value specified with the setQueryTimeout method

S:

Terminates processing.

Action:

Carefully review the timeout value specified with the setQueryTimeout method.

KFAA71565-E

The max field size is invalid. It might be negative. (size = aa....aa) (J)

Negative values cannot be specified for the maximum field length that is specified with the setMaxFieldSize method. <SQLSTATE: R2433>

aa....aa:

The value for the maximum field length specified with the setMaxFieldSize method

S:

Terminates processing.

Action:

Carefully review the maximum field length specified with the setMaxFieldSize method.

KFAA71566-E

This SQL cannot be executed by executeQuery. (J)

This SQL statement cannot be executed by executeQuery. <SQLSTATE: R2434>

S:

Terminates processing.

Action:

Specify an SQL statement that returns a result set in executeQuery.

KFAA71567-E

This SQL cannot be executed by executeUpdate. (J)

This SQL statement cannot be executed by executeUpdate method or executeLargeUpdate method. <SQLSTATE: R2435>

S:

Terminates processing.

Action:

Specify an SQL statement that does not return a result set in executeUpdate method or executeLargeUpdate method.

KFAA71569-E

The number of registration entries exceeded the max. (J)

The number of batch registrations exceeded the upper limit of 2,147,483,647. <SQLSTATE: R2436>

S:

Terminates processing.

Action:

Change the number of batch registrations to 2,147,483,647 or fewer.

KFAA71570-E

Execution of an SQL statement timed out during the retry processing that waits for threads to become available. (J)

A timeout occurred during execution of an SQL statement because processing to allocate a processing real thread was repeated. <SQLSTATE: R2476>

The timeout period is specified by the following method or property.

setQueryTimeout method

adb_clt_rpc_sql_wait_time, which is a system property, user property, or URL connection property

S:

Terminates processing.

Action:

For details about how to take action, see Note about executing multiple retrieval SQL statements concurrently in the same connection in How to retrieve data in the HADB Application Development Guide.

KFAA71571-E

The SQL batch processing was canceled before it was complete. (last SQL statement no. = aa....aa) (J)

Processing was canceled during batch execution of SQL statements. <SQLSTATE: R2477>

aa....aa:

Registration number of the last executed SQL statement

S:

Terminates processing.

Action:

Re-create the Statement instance and re-execute it.

KFAA71680-E

This SQL type is not supported. (type = aa....aa) (J)

Parameters of the SQL data type aa....aa cannot be set. <SQLSTATE: R2437>

aa....aa: The specified SQL type

The literal name defined by java.sql.Types is displayed.

S:

Terminates processing.

Action:

Do not specify aa....aa as an SQL type.

KFAA71681-E

A parameter is not set. (index = aa....aa) (J)

The aa....aath parameter has not been set. <SQLSTATE: R2438>

aa....aa:

Parameter number

S:

Terminates processing.

Action:

Set the aa....aath parameter.

KFAA71682-E

A parameter is invalid. (code = aa(bb....bb)) (J)

The content of a parameter is invalid. <SQLSTATE: R2439>

aa: Reason code

01: Reason code that indicates invalid length

bb....bb: Additional information

invalid length: Negative values cannot be specified in byte counts of streams specified in arguments.

S:

Terminates processing.

Action:

Guided by the details of the additional information for the reason code, carefully review the parameter contents.

KFAA71683-E

The parameter index is invalid. (index = aa....aa) (J)

The value of the parameter index is invalid. <SQLSTATE: R2440>

aa....aa:

Parameter index value

S:

Terminates processing.

Action:

Correct the parameter index value.

KFAA71687-E

The object cannot be converted to the SQL type. (object = "aa....aa", SQL type = "bb....bb") (J)

The object aa....aa that was specified with the setObject method cannot be converted to the SQL data type bb....bb. <SQLSTATE: R2441>

aa....aa:

Object name of the specified object

bb....bb: The specified SQL type

The literal name specified by java.sql.Types is displayed.

S:

Terminates processing.

Action:

Specify an SQL type that can be converted. Alternatively, specify an object compatible with the SQL type.

KFAA71690-E

The data cannot be converted to the table definition type. The number of integer digits might conflict. (J)

The data cannot be converted to the data type of the table definition because the number of digits of the integer portion of the specified data exceeds the number of digits of the integer part of the table definition. <SQLSTATE: R2442>

S:

Terminates processing.

Action:

Carefully review the specified data.

KFAA71691-E

A value might be outside the valid table definition range, or might be of an unconvertable type. (data type = aa....aa, parameter index = bb....bb) (J)

The data is a value that is outside the range of the data type at the conversion destination, or else it is in a format that cannot be converted. <SQLSTATE:R2443>

aa....aa: Conversion target data type

In the case of processing to convert to the data type of the corresponding dynamic parameter, one of the following SQL data types:

{BINARY|BOOLEAN|CHAR|DATE|DECIMAL|DOUBLE PRECISION|INTEGER|REAL|ROW|SMALLINT|STRING|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE|UUID|VARBINARY|VARCHAR}

bb....bb:

Specified parameter index value

S:

Terminates processing.

Action:

Review the data.

KFAA71692-E

This parameter type is not supported. (type = aa....aa, index = bb....bb) (J)

The data type of the dynamic parameter that corresponds to the specified parameter index cannot be used with this setXXX method. <SQLSTATE:R2444>

aa....aa: Data type of the parameter (SQL data type)

{ARRA|BINARY|BOOLEAN|CHAR|DATE|DECIMAL|DOUBLE PRECISION|INTEGER|REAL|ROW|SMALLINT|STRING|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE|UUID|VARBINARY|VARCHAR}

bb....bb:

Parameter index content

S:

Terminates processing.

Action:

Use the setXXX method that corresponds to the data type of the parameter.

KFAA71701-E

The column name is invalid. (column name = "aa....aa") (J)

The column name specified with the getXXX method of the ResultSet class is invalid. <SQLSTATE: R2445>

aa....aa:

The specified column name

S:

Terminates processing.

Action:

Carefully review the specified column name.

KFAA71704-E

The getString method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getString method of the ResultSet class. <SQLSTATE: R2446>

aa....aa:

Column number

bb....bb:

Data type of column (SQL data type)

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class that corresponds to the data type of the column.

KFAA71705-E

The getBoolean method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getBoolean method of the ResultSet class. <SQLSTATE: R2447>

aa....aa:

Column number

bb....bb: Data type of column (SQL data type)

{BINARY|DATE|ROW|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE|UUID|VARBINARY}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class that corresponds to the data type of the column.

KFAA71706-E

The getByte method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getByte method of the ResultSet class. <SQLSTATE:R2448>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BINARY|VARBINARY|CHAR|DATE|DECIMAL|DOUBLE PRECISION|INTEGER|REAL|ROW|SMALLINT|STRING|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE|UUID|VARBINARY|VARCHAR}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71707-E

The getShort method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getShort method of the ResultSet class. <SQLSTATE:R2449>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BINARY|VARBINARY|CHAR|DATE|DECIMAL|DOUBLE PRECISION|INTEGER|REAL|ROW|SMALLINT|STRING|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE|UUID|VARBINARY|VARCHAR}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71708-E

The getInt method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getInt method of the ResultSet class. <SQLSTATE:R2450>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BINARY|VARBINARY|CHAR|DATE|DECIMAL|DOUBLE PRECISION|INTEGER|REAL|ROW|STRING|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE|UUID|VARBINARY|VARCHAR}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71709-E

The getLong method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getLong method of the ResultSet class. <SQLSTATE:R2451>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BINARY|VARBINARY|CHAR|DATE|DECIMAL|DOUBLE PRECISION|REAL|ROW|STRING|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE|UUID|VARBINARY|VARCHAR}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71710-E

The getFloat method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getFloat method of the ResultSet class. <SQLSTATE:R2452>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BINARY|CHAR|DATE|ROW|STRING|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE|UUID|VARBINARY|VARCHAR}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71711-E

The getDouble method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getDouble method of the ResultSet class. <SQLSTATE:R2453>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BINARY|CHAR|DATE|ROW|STRING|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE|UUID|VARBINARY|VARCHAR}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71712-E

The getBigDecimal method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getBigDecimal method of the ResultSet class. <SQLSTATE:R2454>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BINARY|CHAR|DATE|ROW|STRING|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE|UUID|VARCHAR|VARBINARY}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71713-E

The getBytes method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getBytes method of the ResultSet class. <SQLSTATE:R2455>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BOOLEAN|CHAR|DATE|DECIMAL|DOUBLE PRECISION|INTEGER|REAL|SMALLIN|STRINGT|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE|UUID|VARCHAR}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71714-E

The getDate method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getDate method of the ResultSet class. <SQLSTATE:R2456>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BINARY|BOOLEAN|DECIMAL|DOUBLE PRECISION|INTEGER|REAL|ROW|SMALLINT|UUID|VARBINARY}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71715-E

The getTime method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getTime method of the ResultSet class. <SQLSTATE:R2457>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BINARY|BOOLEAN|DATE|DECIMAL|DOUBLE PRECISION|INTEGER|REAL|ROW|SMALLINT|UUID|VARBINARY}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71716-E

The getTimestamp method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getTimestamp method of the ResultSet class. <SQLSTATE:R2458>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BINARY|BOOLEAN|DECIMAL|DOUBLE PRECISION|INTEGER|REAL|ROW|SMALLINT|UUID|VARBINARY}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71717-E

The getAsciiStream method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getAsciiStream method of the ResultSet class. <SQLSTATE:R2459>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BOOLEAN|DATE|DECIMAL|DOUBLE PRECISION|INTEGER|REAL|ROW|SMALLINT|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71719-E

The getBinaryStream method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getBinaryStream method of the ResultSet class. <SQLSTATE:R2474>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BOOLEAN|DATE|DECIMAL|DOUBLE PRECISION|INTEGER|REAL|ROW|SMALLINT|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71721-E

Processing cannot continue because the result set is already closed. (J)

Processing cannot be accepted because the ResultSet instance is already closed. Note that the JDBC driver might have closed the ResultSet instance by closing the Statement instance. <SQLSTATE: R2460>

S:

Terminates processing.

Action:

Re-generate the ResultSet instance, and then retry the operation.

KFAA71722-E

The getCharacterStream method cannot get the data. (column index = aa....aa, data type = bb....bb) (J)

The specified column data cannot be acquired with the getCharacterStream method of the ResultSet class. <SQLSTATE:R2461>

aa....aa:

Column number

bb....bb: Data type of the column (SQL data type)

{BOOLEAN|DATE|DECIMAL|DOUBLE PRECISION|INTEGER|REAL|ROW|SMALLINT|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE}

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71727-E

The column index is invalid. (index = aa....aa) (J)

The column index specified with the getXXX method of the ResultSet class is invalid. <SQLSTATE: R2462>

aa....aa:

Specified column index value

S:

Terminates processing.

Action:

Revise the specified column index.

KFAA71730-E

The data format for java.sql.Date is invalid. (J)

Data cannot be acquired with the getXXX method of the ResultSet class used because the data acquired from the database does not match the date data format. <SQLSTATE: R2464>

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class for the data type to be acquired.

KFAA71731-E

The data format for java.sql.Time is invalid. (J)

Data cannot be acquired with the getXXX method of the ResultSet class used because the data acquired from the database does not match the time data format. <SQLSTATE: R2465>

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class for the data type to be acquired.

KFAA71732-E

The data format for java.sql.Timestamp is invalid. (J)

Data cannot be acquired with the getXXX method of the ResultSet class used because the data acquired from the database does not match the time stamp data format. <SQLSTATE: R2466>

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class for the data type to be acquired.

KFAA71733-E

Scrolling is not possible because the current result set type is TYPE_FORWARD_ONLY. (J)

Scrolling is not possible because the result set type of this ResultSet object is TYPE_FORWARD_ONLY. <SQLSTATE: R2467>

S:

Terminates processing.

Action:

Use with a ResultSet whose result set type is compatible with scrolling.

KFAA71735-E

Zero is specified in an absolute method. (J)

Zero was specified with the absolute method. <SQLSTATE: R2468>

S:

Terminates processing.

Action:

Specify a value other than 0.

KFAA71736-E

The cursor is in an invalid position. (J)

The cursor is not on a valid row. <SQLSTATE: R2469>

S:

Terminates processing.

Action:

Change the cursor position to a valid row.

KFAA71737-E

The getObject method cannot be converted to the class "aa....aa". (column index = bb....bb, data type = cc....cc) (J)

The data of the specified column cannot be converted to the class aa....aa of the Java data type specified in the getObject method of the ResultSet class. <SQLSTATE: R2475>

aa....aa:

Java data type class specified as the argument

bb....bb:

Column number

cc....cc:

Data type of the column (SQL data type)

{BINARY|BOOLEAN|CHAR|DATE|DECIMAL|DOUBLE PRECISION|INTEGER|REAL|ROW|SMALLINT|STRING|TIME|TIMESTAMP|TIMESTAMP WITH TIME ZONE|UUID|VARBINARY|VARCHAR}

S:

Terminates processing.

Action:

Specify a Java data type class that corresponds to the data type of the column.

KFAA71740-E

You cannot use the getArray method of the ResultSet class, because the specified column is not an array-type column. (J)

The specified column is not an array-type column, so the getArray method of the ResultSet class cannot be used to retrieve the result. <SQLSTATE: R2484>

S:

Terminates processing.

Action:

Specify the getXXX method of the ResultSet class corresponding to the column data type.

KFAA71741-E

You cannot use this method to get the result of an array-type column. (J)

This method cannot retrieve results for array-type columns. <SQLSTATE: R2485>

S:

Terminates processing.

Action:

To get the result of an array-type column, use the getArray or getObject method of the ResultSet class.

KFAA71801-E

The argument is invalid. (number = aa....aa, value = bb....bb, method = cc....cc) (J)

An argument value is invalid. <SQLSTATE: R2470>

aa....aa:

Order number of argument

bb....bb:

Argument value

cc....cc:

Method name

S:

Terminates processing.

Action:

Carefully review the argument value.

KFAA71903-E

The login timeout value is invalid. (value = aa....aa) (J)

An invalid value is specified for an argument of the setLoginTimeout method. <SQLSTATE: R2471>

aa....aa:

Value specified for an argument of the setLoginTimeout method

S:

Terminates processing.

Action:

Correct the value specified for an argument of the setLoginTimeout method.

KFAA71908-E

The character set value is invalid. (J)

An invalid character string was specified in the argument of the setEncodeLang method. <SQLSTATE: R2472>

S:

Terminates processing.

Action:

Carefully review the value specified in the argument of the setEncodeLang method.

KFAA72000-E

A character encoding conversion error occurred. (data = aa....aa) (O)

A character encoding conversion error occurred. <SQLSTATE: 5C002>

aa....aa: Hexadecimal dump of the data before the character encoding conversion

If the dump contains data that cannot be displayed, an ellipsis (...) is displayed at the end.

S:

Terminates processing.

Action:

Data aa....aa contains data whose character encoding could not be converted. Correct the data, and then retry the operation.

KFAA72001-W

Characters that could not be converted during character encoding conversion were replaced with "#". (O)

Characters that could not be converted during character encoding conversion were replaced with hash marks (#). <SQLSTATE: 01S51>

S:

Terminates processing.

Action:

Check the data that were replaced with hash marks (#).

KFAA72002-E

An error occurred in the client library, and the message could not be obtained. (information = aa....aa) (O)

An error occurred in the client library, and the message could not be obtained. <SQLSTATE: 5D001>

aa....aa: Error cause code

For details about error cause codes, see List of error cause codes in Return values of the CLI functions in the HADB Application Development Guide.

S:

Terminates processing.

Action:

Take the appropriate action by referencing the descriptions of the error cause code in List of error cause codes in Return values of the CLI functions in the HADB Application Development Guide.

KFAA72003-E

An error occurred in the ODBC driver. (SQLSTATE = aa....aa) (O)

An error occurred in the ODBC driver.

aa....aa:

Value of SQLSTATE

S:

Terminates processing.

Action:

Check the value of SQLSTATE that is displayed in this message, and then take the appropriate action. For details about SQLSTATE values, see 4.2 List of SQLSTATE values and ODBC Programmer's Reference in MSDN library.

KFAA72004-E

A data conversion error occurred in the ODBC driver. (ColumnNumber = aaaa, SQLSTATE = bb....bb, SQL DataType = cc....cc, SQL_C_DataType = dd....dd, reason = ee....ee) (O)

An error occurred in data type conversion processing performed by the ODBC driver. <SQLSTATE: 07006, 22003, 22007, 22018, 5C002, 5C037, 5C038, HY001, HY003, HY004, HY009, HY013, HY090, HY104, HYC00>

aaaa:

Number of the column in which the error occurred

bb....bb:

Value of SQLSTATE

cc....cc:

ODBC SQL data type whose conversion failed

dd....dd:

C data type whose conversion failed

ee....ee:

Cause of the error

S:

Terminates processing.

Action:

Check the following and take corrective action, as necessary:

SQLSTATE value displayed in place of bb....bb

Data type conversion combination

Cause of the error displayed in place of ee....ee

The following table lists the possible causes of the error that are displayed in place of ee....ee and the corrective action to take.

Item No.

Content displayed for ee....ee

Cause of the error and corrective action to take

1

conversions are not supported

The combination of data types that was specified cannot be converted. Change the combination of data types specified to a combination of data types that can be converted. For details about the combinations of data types that can be converted, see Combinations of data types that can be retrieved (conversion from ODBC's SQL data types to C data types), under Correspondence between ODBC's SQL data types and C data types, in the HADB Application Development Guide.

2

value outside the scope of the conversion destination data type

The value is outside the range for the data type into which the value will be converted. Change the data type into which the value will be converted to something larger.

3

data type cannot be converted

The data format cannot be converted. Specify a different data type, or re-enter the data in the correct data format.

4

multiple reasons

One of the following errors has occurred:

The value is outside the range for the data type into which the value will be converted.

The data format cannot be converted.

Take the corrective action for item 2 or item 3, or check the value of SQLSTATE.

KFAA72005-W

Data was truncated when a data type was converted in the ODBC driver. (ColumnNumber = aaaa, SQLSTATE = bb....bb, SQL DataType = cc....cc, SQL_C_DataType = dd....dd, reason = ee....ee) (O)

Data was truncated in data type conversion processing performed by the ODBC driver. <SQLSTATE: 01004, 01S07>

aaaa:

Number of the column where data was truncated

bb....bb:

Value of SQLSTATE

cc....cc:

ODBC SQL data type where data was truncated

dd....dd:

C data type where data was truncated

ee....ee:

Reason why data was truncated

S:

Terminates processing.

Action:

The following table lists the possible reasons for truncation that are displayed in place of ee....ee and the corrective action to take.

Item No.

Content displayed for ee....ee

Reason for the truncation and corrective action to take

1

The column for values other than character data was truncated

A character string was truncated because the conversion-target area was too small.

Specify a sufficiently large conversion-target area, and then retry the operation.

2

The column for values other than data decimal numbers was truncated or fractions were omitted

Data not allowed by the fractional seconds specification or data following the decimal point, for example, was truncated because the conversion-target area was too small or because the setting status of the attribute value does not allow the data.

If floating-point type data was converted to integer values, for example, data following the decimal point was truncated.

For other conversions, specify a sufficiently large conversion-target area, and then retry the operation.

If the data type of the value to be saved as the conversion-target data is SQL_C_NUMERIC, use SQLSetDescField to specify SQL_DESC_PRECISION and SQL_DESC_SCALE, set a sufficient number of places following the decimal point, and then retry the operation by using SQLBindCol and SQLFetch. Scale values that indicate the number of places following the decimal point cannot be changed by using SQLGetData.

3

multiple reasons

Warning for other reason. Check the value of SQLSTATE.

KFAA72006-E

A data conversion error occurred in the ODBC driver. (ParameterNumber = aaaa, SQLSTATE = bb....bb, SQL_C_DataType = cc....cc, SQL DataType = dd....dd, reason = ee....ee) (O)

An error occurred in data type conversion processing performed by the ODBC driver. <SQLSTATE: 07006, 22001, 22003, 22007, 22008, 22018, 5C002, 5C036, HY001, HY003, HY004, HY009, HY013, HY090, HY104, HYC00>

aaaa:

Sequence number of the dynamic parameter in which the error occurred

bb....bb:

Value of SQLSTATE

cc....cc:

C data type whose conversion failed

dd....dd:

ODBC SQL data type whose conversion failed

ee....ee:

Cause of the error

S:

Terminates processing.

Action:

Check the following and take corrective action, as necessary:

SQLSTATE value displayed for bb....bb

Data type conversion combination

Cause of the error displayed for ee....ee

The following table lists the possible causes of the error that are displayed in place of ee....ee and the corrective action to take.

Item No.

Content displayed for ee....ee

Cause of the error and corrective action to take

1

conversions are not supported

The combination of data types that was specified cannot be converted. Change the combination of data types specified to a combination of data types that can be converted. For details about the combinations of data types that can be converted, see Combinations of data types that can be compared and stored or assigned (conversion from C data types to ODBC's SQL data types), under Correspondence between ODBC's SQL data types and C data types, in the HADB Application Development Guide.

2

value outside the scope of the conversion destination data type

The input value is outside the range for the data type into which the value will be converted. Change the input value to something in the range for the data type into which the value will be converted.

3

insufficient memory

Memory is insufficient. Retry the operation after shutting down another application.

4

data type cannot be converted

The data format cannot be converted. Specify a different data type, or re-enter the data in the correct data format.

5

multiple reasons

One of the following errors has occurred:

The input value is outside the range for the data type into which the value will be converted.

The data format cannot be converted.

Take the corrective action for item 2 or item 4, or check the value of SQLSTATE.

6

data for the parameter was not bound

The data for a dynamic parameter was not bound. Either bind the input parameter area for the dynamic parameter with SQLBindParameter, or specify it with SQLPutData.

7

String data, right-truncated

The character string or binary data was truncated on its right end. Change the input value to be in the range for the data it will be converted into.

KFAA72007-E

The length of an SQL statement exceeds 16,000,000 characters. (O)

The length of an SQL statement exceeded 16,000,000 characters. <SQLSTATE: 5C051>

S:

Ignores this SQL statement.

Action:

Correct the SQL statement length.

KFAA72008-W

A warning occurred in the ODBC driver. (SQLSTATE = aa....aa) (O)

A warning occurred in the ODBC driver.

aa....aa:

Value of SQLSTATE

S:

Terminates processing.

Action:

Check the SQLSTATE value displayed in place of aa....aa.

This message indicates that a warning level event occurred. There is no SQLSTATE in the message itself.

KFAA72009-E

The versions of the ODBC driver and the HADB client are different. (ODBC driver version = aa....aa, HADB client version = bb....bb) (O)

The versions of the ODBC driver and the HADB client are different. <SQLSTATE: 5C052>

aa....aa:

Version of the ODBC driver

This is output in the format vv-rr.

vv: Version number

rr: Revision number

bb....bb:

Version of the HADB client

This is displayed in the format vv-rr.

vv: Version number

rr: Revision number

If the version of the HADB client is 03-05 or earlier, 03-05 or earlier is displayed.

S:

Terminates processing.

Action:

Match the versions of the ODBC driver and the HADB client, and then retry the operation.

KFAA72099-E

An internal conflict was detected in the ODBC driver. (file = aa....aa, location = bb....bb) (O)

An internal conflict occurred in the ODBC driver. <SQLSTATE: 5C035>

aa....aa:

Name of the source file in which the error was detected

bb....bb:

Location of the error

S:

Terminates processing.

Action:

When this message is output, re-execute the application program. If the same event recurs, make a backup of the client message log file, and then contact the customer support center.

2.6 Messages from KFAA80000 to KFAA89999

KFAA80000-I

Processing to initialize the HADB system will now start. (L+M)

Processing to start the HADB server is starting.

S:

Continues processing.

KFAA80001-I

Processing to initialize the HADB system has finished. (return code = aa....aa) (L+M)

HADB server start processing has terminated.

aa....aa: Return code

0: Normal termination

4: Termination with warning

8: An error occurred

S: If the return code is 0, processing continues.

If the return code is 4, a warning is issued but processing continues.

If the return code is 8, processing terminates.

Action:

If the return code is 4, a warning has been issued. Access the message log file to check the warning message.

If the return code is 8, eliminate the cause of the error based on the message that was output immediately prior to this message.

Then, re-execute the adbstart command.

KFAA80002-I

The HADB system started. (L+M)

The HADB server has started.

S:

Terminates processing.

KFAA80003-I

Analysis of the server definitions will now start. (L+M)

Analysis of the server definitions is starting.

S:

Continues processing.

KFAA80004-I

Analysis of the server definitions has finished. (return code = aa....aa) (L+M)

Analysis of the server definitions has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: An error occurred

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80005-I

Processing to initialize the common memory of the HADB system will now start. (L+M)

Initialization of the process common memory is starting.

S:

Continues processing.

KFAA80006-I

Processing to initialize the common memory of the HADB system has finished. (return code = aa....aa) (L+M)

Initialization of the process common memory has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80007-I

Processing to initialize the HADB system manager will now start. (L+M)

Processing to start the system manager is starting.

S:

Continues processing.

KFAA80008-I

Processing to initialize the HADB system manager has finished. (return code = aa....aa) (L+M)

Processing to start the system manager has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80009-I

Processing to initialize real threads will now start. (L+M)

Processing to start a real thread is starting.

S:

Continues processing.

KFAA80010-I

Processing to initialize real threads has finished. (return code = aa....aa) (L+M)

Processing to start a real thread has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80011-I

Phase 1 of the processing to initialize the database manager will now start. (L+M)

Phase 1 of the database manager start processing is starting.

S:

Continues processing.

KFAA80012-I

Phase 1 of the processing to initialize the database manager has finished. (return code = aa....aa) (L+M)

Phase 1 of the database manager start processing has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80013-I

Phase 1 of the processing to initialize the dictionary manager will now start. (L+M)

Phase 1 of the processing to start the dictionary manager will now start.

S:

Continues processing.

KFAA80014-I

Phase 1 of the processing to initialize the dictionary manager has finished. (return code = aa....aa) (L+M)

Phase 1 of the processing to start the dictionary manager has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80015-I

Processing to initialize the SQL analyzer will now start. (L+M)

Processing to start the SQL analyzer is starting.

S:

Continues processing.

KFAA80016-I

Processing to initialize the SQL analyzer has finished. (return code = aa....aa) (L+M)

Processing to start the SQL analyzer has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80017-I

Phase 1 of the processing to initialize the communication manager will now start. (L+M)

Phase 1 of the communication manager start processing is starting.

S:

Continues processing.

KFAA80018-I

Phase 1 of the processing to initialize the communication manager has finished. (return code = aa....aa) (L+M)

Phase 1 of the communication manager start processing has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80019-I

The server directory specified for the environment variable ADBDIR is "aa....aa". (L+M)

The server directory specified in environment variable ADBDIR is aa....aa.

aa....aa:

The path name of the server directory specified in environment variable ADBDIR

S:

Continues processing.

KFAA80020-I

The HADB system version is "aa....aa(bb....bb)". (L+M)

The HADB server version is aa....aa(bb....bb).

aa....aa:

HADB server version

This is output in the format vv-rr-zz, where zz might not be output.

vv: Version number

rr: Revision number

zz: Code

bb....bb:

Additional version information for the HADB server

S:

Continues processing.

KFAA80021-I

The character encoding specified for the environment variable ADBLANG is "aa....aa". (L+M)

The character encoding specified for the environment variable ADBLANG is aa....aa.

aa....aa:

The character encoding specified for the environment variable ADBLANG

S:

Continues processing.

KFAA80023-I

The DB directory is "aa....aa". (L+M)

The DB directory specified in the server definition's adb_db_path operand is aa....aa.

aa....aa:

The path name of the DB directory

S:

Continues processing.

KFAA80024-I

The HADB start mode is "aa....aa". (L+M)

The HADB server's startup mode is aa....aa.

aa....aa: Startup mode

NORMAL: Normal start

RECOVER: Restart

VUP RECOVER: Restart after upgrade error

S:

Continues processing.

KFAA80026-I

Processing to terminate the HADB system will now start. (L+M)

Processing to terminate the HADB server is starting.

S:

Continues processing.

KFAA80027-I

Processing to terminate the HADB system has finished. (return code = aa....aa) (L+M)

HADB server termination processing has terminated.

aa....aa: Return code

0: Normal termination

4: Termination with warning

S:

Terminates termination processing.

Action:

If the return code is 4, a warning or error has been issued. Access the message log file to check the warning or error message. If an error message was output, eliminate the cause of the error.

KFAA80028-I

Phase 1 of the processing to terminate the communication manager will now start. (L+M)

Phase 1 of the communication manager termination processing is starting.

S:

Continues processing.

KFAA80029-I

Phase 1 of the processing to terminate the communication manager has finished. (return code = aa....aa) (L+M)

Phase 1 of the communication manager termination processing has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80030-I

Processing to terminate the SQL analyzer will now start. (L+M)

Processing to terminate the SQL analyzer is starting.

S:

Continues processing.

KFAA80031-I

Processing to terminate the SQL analyzer has finished. (return code = aa....aa) (L+M)

Processing to terminate the SQL analyzer has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80032-I

Processing to terminate the dictionary manager will now start. (L+M)

Processing to terminate the dictionary manager is starting.

S:

Continues processing.

KFAA80033-I

Processing to terminate the dictionary manager has finished. (return code = aa....aa) (L+M)

Processing to terminate the dictionary manager has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80034-I

Processing to terminate the database manager will now start. (L+M)

Processing to terminate the database manager is starting.

S:

Continues processing.

KFAA80035-I

Processing to terminate the database manager has finished. (return code = aa....aa) (L+M)

Processing to terminate the database manager has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80036-I

Processing to terminate real threads will now start. (L+M)

Processing to terminate a real thread is starting.

S:

Continues processing.

KFAA80037-I

Processing to terminate real threads has finished. (return code = aa....aa) (L+M)

Processing to terminate a real thread has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80038-I

Processing to terminate the HADB system manager will now start. (L+M)

Processing to terminate the system manager is starting.

S:

Continues processing.

KFAA80039-I

Processing to terminate the HADB system manager has finished. (return code = aa....aa) (L+M)

Processing to terminate the system manager has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80040-I

Processing to terminate the common memory of the HADB system will now start. (L+M)

Processing to release process common memory is starting.

S:

Continues processing.

KFAA80041-I

Processing to terminate the common memory of the HADB system has finished. (return code = aa....aa) (L+M)

Processing to release process common memory has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80042-I

Phase 2 of the processing to initialize the database manager will now start. (L+M)

Phase 2 of the processing to start the database manager will now start.

S:

Continues processing.

KFAA80043-I

Phase 2 of the processing to initialize the database manager has finished. (return code = aa....aa) (L+M)

Phase 2 of the processing to start the database manager has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80044-I

Processing to initialize the HADB controller will now start. (L+M)

Processing to start the HADB controller will now start.

S:

Continues processing.

KFAA80045-I

Processing to initialize the HADB controller has finished. (return code = aa....aa) (L+M)

Processing to start the HADB controller has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80046-I

Phase 2 of the processing to initialize the communication manager will now start. (L+M)

Phase 2 of the processing to start the communication manager will now start.

S:

Resumes processing.

KFAA80047-I

Phase 2 of the processing to initialize the communication manager has finished. (return code = aa....aa) (L+M)

Phase 2 of the processing to start the communication manager has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code was 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80048-I

Phase 2 of the processing to terminate the communication manager will now start. (L+M)

Phase 2 of the processing to terminate the communication manager will start.

S:

Resumes processing.

KFAA80049-I

Phase 2 of the processing to terminate the communication manager has finished. (return code = aa....aa) (L+M)

Phase 2 of the processing to terminate the communication manager finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code was 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80050-I

Processing to initialize the statistics manager will now start. (L+M)

The statistics manager startup processing is beginning.

S:

Continues processing.

KFAA80051-I

Processing to initialize the statistics manager has finished. (return code = aa....aa) (L+M)

The statistics manager startup processing has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code was 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80052-I

Processing to terminate the statistics manager will now start. (L+M)

The statistics manager termination processing is beginning.

S:

Continues processing.

KFAA80053-I

Processing to terminate the statistics manager has finished. (return code = aa....aa) (L+M)

The statistics manager termination processing has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code was 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80054-I

Processing to initialize the database modification manager will now start. (L+M)

The database modification manager start processing is starting.

S:

Continues processing.

KFAA80055-I

Processing to initialize the database modification manager has finished. (return code = aa....aa) (L+M)

The database modification manager start processing has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Abnormal termination

S: If the return code was 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80056-I

Processing to terminate the database modification manager will now start. (L+M)

The database modification manager termination processing is starting.

S:

Continues processing.

KFAA80057-I

Processing to terminate the database modification manager has finished. (return code = aa....aa) (L+M)

The database modification manager termination processing has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Abnormal termination

S: If the return code was 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80058-I

Phase 3 of the processing to initialize the database manager will now start. (L+M)

Phase 3 of the database manager start processing is starting.

S:

Continues processing.

KFAA80059-I

Phase 3 of the processing to initialize the database manager has finished. (return code = aa....aa) (L+M)

Phase 3 of the database manager start processing has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Abnormal termination

S: If the return code was 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80060-I

Phase 1 of the processing to upgrade the database will now start. (L+M)

Phase 1 of the database upgrade processing is starting.

S:

Continues processing.

KFAA80061-I

Phase 1 of the processing to upgrade the database has finished. (return code = aa....aa) (L+M)

Phase 1 of the database upgrade processing has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Abnormal termination

S: If the return code was 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80062-I

Phase 2 of the processing to upgrade the database will now start. (L+M)

Phase 2 of the database upgrade processing is starting.

S:

Continues processing.

KFAA80063-I

Phase 2 of the processing to upgrade the database has finished. (return code = aa....aa) (L+M)

Phase 2 of the database upgrade processing has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Abnormal termination

S: If the return code was 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80064-I

Phase 3 of the processing to upgrade the database will now start. (L+M)

Phase 3 of the database upgrade processing is starting.

S:

Continues processing.

KFAA80065-I

Phase 3 of the processing to upgrade the database has finished. (return code = aa....aa) (L+M)

Phase 3 of the database upgrade processing has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Abnormal termination

S: If the return code was 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80066-I

Processing of the system view table definition will now start. (L+M)

The system viewed table definition processing is starting.

S:

Continues processing.

KFAA80067-I

Processing of the system view table definition has finished. (return code = aa....aa) (L+M)

The system viewed table definition processing has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Abnormal termination

S: If the return code was 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80068-I

The HADB server operation mode changed from "aa....aa" to "bb....bb". (L+M)

The HADB server operation mode was changed from aa....aa to bb....bb.

aa....aa: HADB server operation mode before change

NORMAL: Normal mode

QUIESCENCE: Quiescence mode

OFFLINE: Offline mode

MAINTENANCE: Maintenance mode

bb....bb: HADB server operation mode after change

NORMAL: Normal mode

QUIESCENCE: Quiescence mode

OFFLINE: Offline mode

MAINTENANCE: Maintenance mode

S:

Continues processing.

KFAA80069-I

The HADB server operation mode is "aa....aa". (L+M)

The HADB server operation mode is aa....aa.

aa....aa: HADB server operation mode

NORMAL: Normal mode

QUIESCENCE: Quiescence mode

OFFLINE: Offline mode

MAINTENANCE: Maintenance mode

S:

Continues processing.

KFAA80070-I

Processing to initialize the command manager will now start. (L+M)

Processing to start the command manager is starting.

S:

Continues processing.

KFAA80071-I

Processing to initialize the command manager has finished. (return code = aa....aa) (L+M)

Processing to start the command manager has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Abnormal termination

S: If the return code was 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80072-I

The HADB server node type is "aa....aa". (L+M)

The node type of the HADB server is aa....aa.

aa....aa: Node type

PRIMARY: Primary node

SECONDARY: Secondary node

WORKER: Worker node

S:

Continues processing.

KFAA80073-I

The HADB server node type was changed to "aa....aa". (L+M)

The node type of the HADB server changed to aa....aa.

aa....aa: Node type

PRIMARY: Primary node

SECONDARY: Secondary node

S:

Continues processing.

KFAA80074-I

Processing to initialize the database initializer manager will now start. (L+M)

Processing to start the database initialization manager is starting.

S:

Continues processing.

KFAA80075-I

Processing to initialize the database initializer manager has finished. (return code = aa....aa) (L+M)

Processing to start the database initialization manager has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, continues processing.

If the return code is not 0, terminates processing.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80076-I

The HADB server is waiting to connect to another node. (host name = aa....aa, IP address = bb....bb) (L+M)

The HADB server is waiting to connect to another node.

aa....aa:

Host name of the node that is waiting to connect to another node (communication between servers)

bb....bb:

IP address of the node that is waiting to connect to another node (communication between servers)

S:

Continues processing.

Action:

Start the HADB server on the other node.

KFAA80077-I

A connection with another node was established. (node number = aa....aa, host name = bb....bb, IP address = cc....cc) (L+M)

A connection was established to another node in a multi-node configuration.

aa....aa:

Node number of the node that established connection

bb....bb:

Host name of the node that established connection (communication between servers)

cc....cc:

IP address of the node that established connection (communication between servers)

S:

Continues processing.

KFAA80078-I

The startup of HA Monitor on the server was confirmed. (alias = "aa....aa") (L+M)

The startup of HA Monitor was confirmed for server ID aa....aa.

aa....aa:

Server ID of the HA Monitor

S:

Continues processing.

KFAA80079-I

Processing to terminate the HADB controller will now start. (L+M)

Processing to terminate the HADB controller will now start.

S:

Continues processing.

KFAA80080-I

Processing to terminate the HADB controller has finished. (return code = aa....aa) (L+M)

Processing to terminate the HADB controller has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80081-I

Processing to recover the database in the switchover of the primary node will now start. (L+M)

Processing to restore the database due to primary node switchover has started.

S:

Continues processing.

KFAA80082-I

Processing to recover the database in the switchover of the primary node has finished. (return code = aa....aa) (L+M)

Processing to restore the database due to primary node switchover has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message.

KFAA80084-I

Analysis of the client-managing definitions will now start. (L+M)

Analysis of the client-managing definitions has started.

S:

Continues processing.

KFAA80085-I

Analysis of the client-managing definitions has finished. (return code = aa....aa) (L+M)

Analysis of the client-managing definitions has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80086-I

Phase 2 of the processing to initialize the dictionary manager will now start. (L+M)

Phase 2 of the processing to start the dictionary manager will now start.

S:

Continues processing.

KFAA80087-I

Phase 2 of the processing to initialize the dictionary manager has finished. (return code = aa....aa) (L+M)

Phase 2 of the processing to start the dictionary manager has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Error

S:

If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80088-I

Phase 4 of the processing to upgrade the database will now start. (L+M)

Phase 4 of the database upgrade processing will now start.

S:

Continues processing.

KFAA80089-I

Phase 4 of the processing to upgrade the database has finished. (return code = aa....aa) (L+M)

Phase 4 of the database upgrade processing has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Abnormal termination

S:

If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80090-I

Processing to initialize the audit trail manager will now start. (L+M)

Processing to start the audit trail manager will now start.

S:

Continues processing.

KFAA80091-I

Processing to initialize the audit trail manager has finished. (return code = aa....aa) (L+M)

Processing to start the audit trail manager has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80092-I

Processing to terminate the audit trail manager will now start. (L+M)

Processing to terminate the audit trail manager will now start.

S:

Continues processing.

KFAA80093-I

Processing to terminate the audit trail manager has finished. (return code = aa....aa) (L+M)

Processing to terminate the audit trail manager has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80094-I

Processing to initialize the updated-row columnizing facility will now start. (L+M)

Processing to start the updated-row columnizing facility will now start.

S:

Continues processing.

KFAA80095-I

Processing to initialize the updated-row columnizing facility has finished. (return code = aa....aa) (L+M)

Processing to start the updated-row columnizing facility has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA80096-I

Processing to terminate the updated-row columnizing facility will now start. (L+M)

Processing to terminate the updated-row columnizing facility will now start.

S:

Continues processing.

KFAA80097-I

Processing to terminate the updated-row columnizing facility has finished. (return code = aa....aa) (L+M)

Processing to terminate the updated-row columnizing facility has finished.

aa....aa: Return code

0: Normal termination

Other than 0: Cause of the error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstop command.

KFAA80099-I

The output destination of the message log file was changed from aa....aa to bb....bb. (L+M)

The output destination for the message log file has been changed from aa....aa to bb....bb.

aa....aa:

Message log file name before the change

bb....bb:

Message log file name after the change

S:

Continues processing.

Action:

Message logs output to the message log file prior to the change may be overwritten. Back up the message log file as necessary. For details about working with message log files, see Working with the message log files in the HADB Setup and Operation Guide.

KFAA80201-I

aa....aa processing started. (S+L+M)

Processing aa....aa has started.

aa....aa: Processing that was performed

Export: Data export processing

Modify-buffer: Buffer modification processing

Modify-synonym-dictionary: Synonym dictionary registration or update processing

Delete-synonym-dictionary: Synonym dictionary deletion processing

Synchronize-synonym-dictionary: Synchronization processing of synonym dictionary files

Output-synonym-dictionary: Output processing of a list of synonyms registered in the synonym dictionary

Clean-synonym-dictionary: Deletion processing of unnecessary files under the storage directory for synonym dictionary files

Create-encryption-key: Creating processing of a HADB encryption key

Update-encryption-key: Updating processing of a HADB encryption key

S:

Continues processing.

KFAA80202-I

aa....aa processing started. The table is "bb....bb"."cc....cc". (S+L+M)

aa....aa has started.

aa....aa: Executed processing

Import: Data import processing

Index-rebuild: Index rebuild processing

Merge-chunk: Merge chunk processing

Change-chunk-comment: Set, change, or delete chunk comments processing

Change-chunk-status: Change chunk status processing

Archive-chunk: Chunk archive processing

Unarchive-chunk: Chunk unarchive processing

Reorganize-systemdata: Dictionary table or system table reorganization processing

bb....bb:

Schema name

cc....cc:

Table identifier

S:

Continues processing.

KFAA80203-I

aa....aa rows loaded. (chunk id = bb....bb) (M+S)

aa....aa rows have been loaded.

aa....aa:

The number of rows loaded

bb....bb: Chunk ID of the chunk released from the archived state

Before the chunk is released from the archived state, the (chunk id = bb....bb) part is output.

S:

Continues processing.

KFAA80204-I

aa....aa processing ended. (return code = bb) (S+L+M)

Processing of aa....aa has terminated.

aa....aa: Executed processing

Cost-information-collection: Cost information collection processing

DB-status-analysis: DB status analysis processing

Export: Data export processing

Import: Data import processing

Index-rebuild: Index rebuild processing

Merge-chunk: Merge chunk processing

Change-chunk-comment: Set, change, or delete chunk comments processing

Change-chunk-status: Change chunk status processing

Modify-buffer: Buffer modification processing

Archive-chunk: Chunk archive processing

Unarchive-chunk: Chunk unarchive processing

Reorganize-systemdata: Dictionary table or system table reorganization processing

Modify-synonym-dictionary: Synonym dictionary registration or update processing

Delete-synonym-dictionary: Synonym dictionary deletion processing

Synchronize-synonym-dictionary: Synchronization processing of synonym dictionary files

Output-synonym-dictionary: Output processing of a list of synonyms registered in the synonym dictionary

Clean-synonym-dictionary: Deletion processing of unnecessary files under the storage directory for synonym dictionary files

Create-encryption-key: Creating processing of a HADB encryption key

Update-encryption-key: Updating processing of a HADB encryption key

bb: Return code

0: Processing terminated normally.

4: Processing terminated normally, but a warning message was output.

8: The specified command was invalid or an error occurred during command execution.

12: The specified command was invalid or an error occurred during command execution. For dictionary table reorganization processing, the data before reorganization remains in the dictionary DB area. For system table reorganization processing, the data before reorganization remains in the system-table DB area.

20: Part of command processing was skipped.

S:

Terminates processing.

Action:

If the return code is not 0, take the action described below.

If the specified command was invalid and return code 8 was output, check the command specification format, and then re-execute the command.

If the return code is 4

Processing aa....aa

Corrective action to take

Cost-information-collection

Check the displayed warning message or the warning message output to the message log file, and then take corrective action for that warning message.

If the KFAA50291-W message was output, the cost information collection processing might have been skipped for some tables because the tables were in non-updatable status or their indexes were in unfinished status. If this is the case, release the tables from non-updatable status or the indexes from unfinished status, and then collect the cost information.

For details about how to release tables from non-updatable status, see Steps to take when a base table becomes non-updatable in the HADB Setup and Operation Guide.

For details about how to release the B-tree index from unfinished status, see Steps to take when unfinished status is applied to a B-tree index in the HADB Setup and Operation Guide.

For details about how to release the text index from unfinished status, see Steps to take when unfinished status is applied to a text index in the HADB Setup and Operation Guide.

For details about how to release the range index from unfinished status, see Steps to take when unfinished status is applied to a range index in the HADB Setup and Operation Guide.

DB-status-analysis

Check the displayed warning message or the warning message output to the message log file, and then take corrective action for that warning message.

Export

Import

Check the displayed warning message or the warning message output to the message log file, and then take corrective action for that warning message.

If either of the messages listed below was output, a problem has occurred, including constraint violation and unimported data.

If the KFAA61205-W message was output

If this message (a warning message indicating that a duplicate key value was detected) was output, the uniqueness constraint of the table and B-tree index has been violated. Therefore, find the duplicated key values and delete the affected rows. For details about the corrective action to take, see Steps to take when the uniqueness constraint is violated (when the KFAA61205-W message is output) in the HADB Setup and Operation Guide.

If a message indicating that a logical error was detected in the data was output

For details about the logical error in the data, check the message that was output. Note that if 1 is specified in the adb_import_errmsg_lv import option, a message that provides the details of logical error in the data is not output.

For normal data, the data import processing has been completed. For details about the corrective action to take if there is a logical error in the data, see How to handle logical errors in input data in the manual HADB Command Reference.

Index-rebuild

Check the displayed warning message or the warning message output to the message log file, and then take corrective action for that warning message.

If the KFAA61205-W message (a warning message indicating that a duplicate key value was detected) was output, the uniqueness constraint of the table and B-tree index has been violated. Therefore, find the duplicated key values and delete the affected rows. For details about the corrective action to take, see Steps to take when the uniqueness constraint is violated (when the KFAA61205-W message is output) in the HADB Setup and Operation Guide.

Merge-chunk

Check the displayed warning message or the warning message output to the message log file, and then take corrective action for that warning message.

Change-chunk-comment

Change-chunk-status

Modify-buffer

Archive-chunk

Unarchive-chunk

Reorganize-systemdata

Modify-synonym-dictionary

Delete-synonym-dictionary

Synchronize-synonym-dictionary

Check the displayed warning message or the warning message output to the message log file, and then take corrective action for that warning message.

Also see Return codes in adbsyndict (Manage Synonym Dictionary) in the manual HADB Command Reference.

Output-synonym-dictionary

Check the displayed warning message or the warning message output to the message log file, and then take corrective action for that warning message.

Clean-synonym-dictionary

Create-encryption-key

Update-encryption-key

If the return code is 8

Processing aa....aa

Corrective action to take

Cost-information-collection

For details about the cause of the error and the corrective action to take, check the error message that was displayed or the error message that was output to the message log file.

DB-status-analysis

Export

Import

For details about the cause of the error and the corrective action to take, check the error message that was displayed or the error message that was output to the message log file.

For details about the actions to take when the adbimport command terminates abnormally, see Handling abnormal termination of the adbimport command in the manual HADB Command Reference.

Index-rebuild

For details about the cause of the error and the corrective action to take, check the error message that was displayed or the error message that was output to the message log file.

For details about the actions to take when the adbidxrebuild command terminates abnormally, see Handling abnormal termination of the adbidxrebuild command in the manual HADB Command Reference.

Merge-chunk

For details about the cause of the error and the corrective action to take, check the error message that was displayed or the error message that was output to the message log file.

For details about the actions to take when the adbmergechunk command terminates abnormally, see Handling abnormal termination of the adbmergechunk command in the manual HADB Command Reference.

Change-chunk-comment

For details about the cause of the error and the corrective action to take, check the error message that was displayed or the error message that was output to the message log file.

Change-chunk-status

Modify-buffer

Archive-chunk

Unarchive-chunk

For details about the cause of the error and the corrective action to take, check the error message that was displayed or the error message that was output to the message log file.

For details about the action to take when the adbunarchivechunk command terminates abnormally, see Handling abnormal termination of the adbunarchivechunk command in the manual HADB Command Reference.

Reorganize-systemdata

For details about the cause of the error, check the error message that was displayed or the error message that was output to the message log file.

At this time, the target table is in the status before the adbreorgsystemdata command is executed. Eliminate the cause of abnormal termination, and then re-execute the adbreorgsystemdata command.

Modify-synonym-dictionary

For details about the cause of the error and the corrective action to take, check the error message that was displayed or the error message that was output to the message log file.

Delete-synonym-dictionary

Synchronize-synonym-dictionary

Output-synonym-dictionary

Clean-synonym-dictionary

Create-encryption-key

Update-encryption-key

If the return code is 12

Processing aa....aa

Corrective action to take

Reorganize-systemdata

For details about the cause of the error, check the error message that was displayed or the error message that was output to the message log file.

At this time, the target table contains the data before reorganization and the data after reorganization. Eliminate the cause of abnormal termination, and then re-execute the adbreorgsystemdata command.

If the return code is 20

Processing aa....aa

Corrective action to take

Merge-chunk

The processing terminated normally, but the merge-source chunk could not be deleted. Therefore, the merge-source chunk is in the deletion-pending status. Execute the PURGE CHUNK statement to delete all deletion-pending chunks. Check the deletion-pending chunks based on the displayed message or the KFAA96785-E message.

KFAA80205-I

Row number aa....aa is being processed. (chunk id = bb....bb) (M+S)

Row number aa....aa is being processed.

aa....aa:

Row count

bb....bb: Chunk ID being processed

The (chunk id = bb....bb) part is output in the following cases:

Index rebuild is performed for a multi-chunk table.

A chunk is placed in the archived state.

A chunk is released from the archived state.

S:

Continues processing.

KFAA80206-I

The index information file was assigned. (index = "aa....aa"."bb....bb", DB area = "cc....cc", file = dd....dd) (chunk id = ee....ee) (M+S)

The index information of index aa....aa.bb....bb stored in DB area cc....cc has been assigned to dd....dd.

aa....aa:

Schema name

bb....bb:

Index identifier

cc....cc:

DB area name

dd....dd:

File name where index information was output

ee....ee: Chunk ID being processed

The (chunk id = ee....ee) part is output in the following cases:

Index rebuild is performed for a multi-chunk table.

A chunk is released from the archived state.

S:

Continues processing.

KFAA80207-I

Processing to generate the index started. (index = "aa....aa"."bb....bb", DB area = "cc....cc") (chunk id = dd....dd) (M+S)

Processing to generate index aa....aa.bb....bb has started.

aa....aa:

Schema name

bb....bb:

Index identifier

cc....cc:

DB area name

dd....dd: Chunk ID being processed

The (chunk id = dd....dd) part is output in the following cases:

Index rebuild is performed for a multi-chunk table.

A chunk is released from the archived state.

S:

Continues processing.

KFAA80208-I

Processing to generate the index ended. (index = "aa....aa"."bb....bb", DB area = "cc....cc", return code = dd) (chunk id = ee....ee) (M+S)

Processing to generate index aa....aa.bb....bb has terminated.

aa....aa:

Schema name

bb....bb:

Index identifier

cc....cc:

DB area name

dd: Return code

0: Normal termination

12: Abnormal termination

ee....ee: Chunk ID being processed

The (chunk id = ee....ee) part is output in the following cases:

Index rebuild is performed for a multi-chunk table.

A chunk is released from the archived state.

S:

Continues processing.

Action:

In the case of an abnormal termination, eliminate the cause of the error based on the message that was output immediately prior to this message.

Restore the database, and then retry the operation.

KFAA80209-I

aa....aa processing started. (S+L+M)

Processing aa....aa has started.

aa....aa: Processing that is being performed:

Cost-information-collection: Cost information collection processing

S:

Continues processing.

KFAA80210-I

Row aaaa for table "bb....bb"."cc....cc" stored in DB area "dd....dd" was deleted. (M+S)

The row data of table bb....bb.cc....cc stored in DB area dd....dd has been deleted.

aaaa:

Deleted data

bb....bb:

Schema name

cc....cc:

Table identifier

dd....dd:

DB area name

S:

Continues processing.

KFAA80211-I

Processing for the chunk will start. (chunk id = aa....aa) (bb....bb/cc....cc) (M+S)

Processing for the chunk with chunk ID aa....aa has started.

aa....aa:

Chunk ID being processed

bb....bb:

Sequential number of the processed chunk

For the adbidxrebuild, adbarchivechunk, or adbunarchivechunk command

The sequential number indicates the order in which the chunk was processed in the above command.

However, sequential numbers might not start with 1 in the following cases:

- If the re-execute facility of the adbidxrebuild command is used, processing is resumed from the chunk where it was suspended. Therefore, the displayed sequential number starts with the one when the processing was suspended.

- If the adbidxrebuild command is executed with the --create-temp-file option specified after the adbimport command was suspended, the displayed number is the same as the value displayed for cc....cc (number of chunks to be processed).

For the adbmergechunk command

1 is displayed.

cc....cc:

Number of chunks to be processed

For the adbidxrebuild command

The total number of chunks in the base table before execution of the above command is displayed.

However, this does not apply to the adbidxrebuild command that is executed with the --create-temp-file option specified after the adbimport command with background import applied (-b option specified) was suspended. In this case, the total number of chunks (before execution of the adbidxrebuild command) plus 1 is displayed.

For the adbarchivechunk or adbunarchivechunk command

The number of chunks (specified by the -c or -r option) to be archived or to be released from the archived state is displayed.

For the adbmergechunk command

1 is displayed.

S:

Continues processing.

KFAA80212-I

Processing for the chunk finished. (chunk id = aa....aa) (bb....bb/cc....cc) (M+S)

Processing for the chunk with chunk ID aa....aa has finished.

aa....aa:

Chunk ID being processed

bb....bb:

Sequential number of the processed chunk

For the adbidxrebuild, adbarchivechunk, or adbunarchivechunk command

The sequential number indicates the order in which the chunk was processed in the above command.

However, sequential numbers might not start with 1 in the following cases:

- If the re-execute facility of the adbidxrebuild command is used, processing is resumed from the chunk where it was suspended. Therefore, the displayed sequential number starts with the one when the processing was suspended.

- If the adbidxrebuild command is executed with the --create-temp-file option specified after the adbimport command was suspended, the displayed number is the same as the value displayed for cc....cc (number of chunks to be processed).

adbmergechunk command

1 is displayed.

cc....cc:

Number of chunks to be processed

For the adbidxrebuild command

The total number of chunks in the base table before execution of the above command is displayed.

However, this does not apply to the adbidxrebuild command that is executed with the --create-temp-file option specified after the adbimport command with background import applied (-b option specified) was suspended. In this case, the total number of chunks (before execution of the adbidxrebuild command) plus 1 is displayed.

For the adbarchivechunk or adbunarchivechunk command

The number of chunks (specified by the -c or -r option) to be archived or to be released from the archived state is displayed.

For the adbmergechunk command

1 is displayed.

S:

Continues processing.

KFAA80213-I

The adbimport command recognized the input data file as a compressed file. (compression format = aa....aa, file = bb....bb) (M)

The adbimport command recognized the input data file as a compressed file. The file compression format is aa....aa.

aa....aa: Compression format

GZIP

bb....bb:

Path name of the input data file

S:

Continues processing.

KFAA80215-I

Index-rebuild will ignore last status, because --force option is specified. (M+S)

The previous status will be ignored because the --force option was specified.

S:

Continues processing.

KFAA80216-I

aa....aa will resume by continuing from the last command. (process = bb....bb) (M+S)

Processing will resume by continuing from the last command.

aa....aa: Processing command

Import: adbimport command

Index-rebuild: adbidxrebuild command

Unarchive-chunk: adbunarchivechunk command

bb....bb: Processing that will resume

Scan: Data scanning

Sort: Sort processing

Index: Processing to create a B-tree index

Terminate: Termination processing

S: Continues processing.

If bb....bb is Terminate, the following processing has finished by the last command:

Creation of table data and index

Release of chunks from the archived state

Therefore, only termination processing will be performed by the current command.

Action:

If this message is output during execution of the adbunarchivechunk command, only termination processing of the last adbunarchivechunk command was performed. Therefore, if you intend to re-execute the adbunarchivechunk command but this command has never been executed, you need to execute the adbunarchivechunk command again.

KFAA80217-I

Data will be imported in the created mode because the --force option is specified. (M+S)

Data import processing will be performed in creation mode because the --force option has been specified for the adbimport command.

S:

Continues processing.

KFAA80218-I

Sort processing was started. (input-file = aa....aa) (chunk id = bb....bb) (M+S)

Sort processing has started.

aa....aa:

Path name of sort input file

bb....bb: Chunk ID being processed

The (chunk id = bb....bb) part is output in the following cases:

Index rebuild is performed for a multi-chunk table.

A chunk is released from the archived state.

S:

Continues processing.

KFAA80219-I

Sort processing was ended. (output-file = aa....aa) (chunk id = bb....bb) (M+S)

Sort processing has terminated.

aa....aa:

Path name of sort output file

If a text index is processed, the file name of one file is displayed.

bb....bb: Chunk ID being processed

The (chunk id = bb....bb) part is output in the following cases:

Index rebuild is performed for a multi-chunk table.

A chunk is released from the archived state.

S:

Continues processing.

KFAA80220-I

All sort processing is complete. (chunk id = aa....aa) (M+S)

All sort processing is complete.

aa....aa: Chunk ID being processed

The (chunk id = aa....aa) part is output in the following cases:

Index rebuild is performed for a multi-chunk table.

A chunk is released from the archived state.

S:

Continues processing.

KFAA80222-I

Data search processing will resume because the option --create-temp-file is specified. (last command = aa....aa) (M+S)

Processing will restart from the table data search processing because the --create-temp-file option is specified.

aa....aa: Command that was suspended the previous time

Import: adbimport command

Index-rebuild: adbidxrebuild command

S:

Continues processing.

KFAA80223-I

aa....aa rows were exported. (M+S)

aa....aa rows were output.

aa....aa:

Number of rows that were output

S:

Continues processing.

KFAA80227-I

Export processing started. (exported data output file = aa....aa) (M+S)

Processing of output data file aa....aa has started.

aa....aa:

Output data file name

S:

Continues processing.

KFAA80228-I

Export processing ended. (aa....aa rows, exported data output file = bb....bb) (M+S)

Processing of output data file bb....bb has finished.

aa....aa:

Number of rows output to the output data file

bb....bb:

Output data file name

S:

Continues processing.

KFAA80229-I

Archive-chunk processing started. (archive file = aa....aa) (M+S)

Processing for the archive file aa....aa has started.

aa....aa:

Archive file name

S:

Continues processing.

KFAA80230-I

Archive-chunk processing ended. (aa....aa rows, archive file = bb....bb) (M+S)

Processing for the archive file aa....aa has terminated. The number of output rows is aa....aa.

aa....aa:

Number of output rows

bb....bb:

Archive file name

S:

Continues processing.

KFAA80231-I

Processing to change chunk statuses of the "aa....aa"."bb....bb" table started. (M+S)

The process of changing the chunk status of base table "aa....aa"."bb....bb" has started.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80232-I

Processing to change chunk statuses of the "aa....aa"."bb....bb" table ended. (M+S)

The process of changing the chunk status of base table "aa....aa"."bb....bb" has finished.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80233-I

aa....aa rows searched. (chunk id = bb....bb) (M+S)

aa....aa rows were searched.

aa....aa:

Number of rows searched

bb....bb: Chunk ID being processed

This is output if index rebuild is performed for a multi-chunk table. For a single-chunk table, (chunk id = bb....bb) is not output.

S:

Continues processing.

KFAA80234-I

Rows were searched to collect cost information. (number of rows = aa....aa) (M+S)

aa....aa rows were searched to collect cost information.

aa....aa:

Number of rows searched

S:

Continues processing.

KFAA80235-I

Collection of cost information will now start. (table = "aa....aa"."bb....bb") (M+S)

Collection of cost information will start.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80236-I

Collection of cost information is complete. (table = "aa....aa"."bb....bb", analyzed = cc....cc/dd....dd) (M+S)

Collection of cost information is complete.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc:

Number of analyzed rows

dd....dd: Total number of rows

An asterisk (*) is output when both of the following conditions are satisfied:

The target table for cost information collection is a row store table in which a B-tree index is not defined.

The time required for collecting cost information exceeds the time specified for the cost-information collection option adb_getcst_collect_time (the KFAA80237-I message is output).

If the target table contains an archived chunk, the number of rows in that chunk is not included in the number of rows output for cc....cc and dd....dd.

S:

Continues processing.

KFAA80237-I

The cost information collection time has exceeded the specified time. (table = "aa....aa"."bb....bb") (M+S)

The time required for collecting cost information exceeds the specified time.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Registers the cost information that was collected until this message was output, and then continues processing.

Action:

This message is output if the time required for collecting cost information exceeds the time specified for the cost-information collection option adb_getcst_collect_time.

As a basic rule, even if this message is output, there is no need to collect cost information again. However, if the access path selected during execution of an SQL statement is different from the one you expected, increase the value specified for the cost-information collection option adb_getcst_collect_time, and then re-execute the adbgetcst command.

For details about the cost-information collection option adb_getcst_collect_time, see Explanation of specification format in Format of the cost-information collection option in the manual HADB Command Reference.

KFAA80240-I

Following chunk ids are source of Data-migration. (chunk id = aa....aa) (M+S)

The data in the chunks with chunk IDs aa....aa will be migrated.

aa....aa: Chunk IDs

If data in multiple chunks are to be migrated, the multiple chunk IDs are displayed in the following format:

chunk-ID,chunk-ID,chunk-ID,chunk-ID,chunk-ID

A maximum of five chunk IDs are displayed in one message. If data in more than five chunks are to be migrated, multiple messages are output to list all of the chunk IDs.

S:

Continues processing.

KFAA80241-I

The chunk ID of the migration destination is "aa....aa". (M+S)

The target chunk ID that is the destination of the migration is aa....aa.

aa....aa:

Chunk ID

S:

Continues processing.

KFAA80242-I

aa....aa processing started. (M+S)

Processing aa....aa has started.

aa....aa: Processing that has started

Merge-data: Table data merge processing

Purge-chunk: Chunk deletion processing

Index-rebuild: Index rebuild processing

S:

Continues processing.

KFAA80243-I

aa....aa processing ended. (return code = bb) (M+S)

Processing aa....aa has finished.

aa....aa: Processing that was performed

Merge-data: Table data merge processing

Purge-chunk: Chunk deletion processing

Index-rebuild: Index rebuild processing

bb: Return code

0: Normal termination

4: Termination with warning

8: An error occurred.

20: Part of command processing was skipped.

S:

Terminates processing.

Action:

If the return code is not 0, take the action described below.

If the specified command was invalid and the return code 8 was output, check the command specification format, and then re-execute the command.

Return code

Corrective action to take

4

Check the warning message that was displayed or that was output to the message log file, and then take the corrective action indicated in that message.

8

For details about the cause of the error and the corrective action to take, check the error message that was displayed or that was output to the message log file.

For details about the actions to take when the adbmergechunk command terminates abnormally, see Handling abnormal termination of the adbmergechunk command in the manual HADB Command Reference.

20

The processing terminated normally, but the merge-source chunk could not be deleted. Therefore, the merge-source chunk is in the deletion-pending status. Execute the PURGE CHUNK statement to delete all deletion-pending chunks. Check the deletion-pending chunks based on the displayed message or the KFAA96785-E message.

KFAA80244-I

The processing of the unarchive chunk was rolled back. (chunk id = aa....aa) (M+S)

The processing to release the chunk from the archived state was rolled back.

aa....aa:

Chunk ID of the target chunk

S:

Continues processing.

KFAA80245-I

The ID of the chunk to be processed by aa....aa is bb....bb. The range of the chunk is cc....cc. (M+S)

The chunk ID of the chunk subject to aa....aa processing is bb....bb. The range of the values stored in this chunk is cc....cc.

This message is output for the following chunks:

All chunks to be archived when the adbarchivechunk command is executed

All chunks that are released from the archived state when the adbunarchivechunk command is executed

aa....aa:

Archive-chunk: Chunk archive processing

Unarchive-chunk: Chunk unarchive processing

bb....bb:

Chunk ID of the chunk to be processed

cc....cc: Range of data values stored in the chunk

This value is displayed in the following format. However, if no data is stored in the chunk, a space is displayed.

minimum-data-value-maximum-data-value

The following shows display examples.

If the data type of the archive range column is DATE

2016/06/01-2016/06/30

If the data type of the archive range column is TIMESTAMP

2016/06/05 14:00:00.000000-2016/06/05 14:59:59.999999

The fractional seconds precision is set to the precision of the columns of the TIMESTAMP type specified for the archive range column.

If the data type of the archive range column is TIME

2016/06/05 3:00:00 PM.000000-15/06/05 10:22 AM.123456

The fractional seconds precision is set to the precision of the columns of the TIME type specified for the archive range column.

If the data type of the archive range column is CHARACTER

"2016-06-10"-"2016-06-20"

If characters cannot be displayed, a single-byte space is displayed.

If the data type of the archive range column is INTEGER, BIGINT, SMALLINT, DECIMAL, or NUMERIC

100-999

10.000-19.999

If the data type of the archive range column is DOUBLE PRECISION, FLOAT, or REAL

1.0E1-1.0E3

S:

Continues processing.

KFAA80246-I

aa....aa rows were archived. (chunk id = bb....bb) (M+S)

aa....aa rows in the chunk are archived.

aa....aa:

Number of archived rows

bb....bb:

Chunk ID of the chunk to be processed

S:

Continues processing.

KFAA80247-W

No chunk meets the conditions for aa....aa. (M+S)

There is no chunk that can be archived. Alternatively, there is no chunk that can be released from the archived state.

aa....aa: Performed processing

archive: Chunk archive processing

unarchive: Chunk unarchive processing

S:

Terminates processing.

Action:

Make sure that the target chunk specified by the -c option or -r option of the command is correct.

Alternatively, make sure that the chunk to be processed by the command meets the conditions for archive (or conditions to release from the archived state). For details about conditions, see the following parts in the manual HADB Command Reference:

Explanation of the -c and -r options in Explanation of the specification format and options in adbarchivechunk (Archive Chunk)

Explanation of the -c and -r options in Explanation of the specification format and options in adbunarchivechunk (Unarchive Chunk)

KFAA80248-I

The statuses of aa....aa chunks were changed. (M+S)

aa....aa chunk status was changed.

aa....aa:

Number of chunks whose chunk status has been changed

S:

Continues processing.

KFAA80249-I

The archive file was deleted because it contained 0 data items. (archive file = aa....aa) (M+S)

The archive file is deleted because it contains no data.

aa....aa:

Archive file name

S:

Continues processing.

KFAA80250-I

A chunk comment was changed. (chunk ID = aa....aa) (M+S)

A chunk comment changed.

aa....aa:

Chunk ID of the chunk whose comment was changed

S:

Terminates processing.

KFAA80251-I

The status of one or more chunks changed to "aa....aa". (chunk id = bb....bb) (M+S)

A chunk status changed.

aa....aa: Chunk status after change

normal: Normal status

wait: Wait status

bb....bb: Chunk ID of the chunk whose chunk status changed

If the chunk status was changed for multiple chunks, multiple chunk IDs are output, separated by commas. Up to five chunk IDs are output per message. If there are six or more chunk IDs, message KFAA80251-I is output multiple times.

S:

Continues processing.

KFAA80252-I

The status of one or more chunks changed to "aa....aa". (table name = "bb....bb"."cc....cc", chunk id = dd....dd) (M+S)

The chunk status of the "bb....bb"."cc....cc" base table has been changed.

aa....aa: Status of the chunk after the change

normal: Normal status

wait: Wait status

bb....bb:

Schema name

cc....cc:

Table identifier

dd....dd: Chunk ID that changed the chunk status

If there are multiple chunks that have changed chunk status, multiple chunk IDs are output separated by commas. A maximum of 5 chunk ID are output in a message. If there are 6 or more chunk IDs, multiple KFAA80252-I messages are displayed.

S:

Continues processing.

KFAA80253-I

The delete-pending data will now be deleted from the table "aa....aa"."bb....bb". (M+S)

Processing to delete the data in the deletion-pending status in the table aa....aa.bb....bb will now start.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80254-I

The delete-pending data has been deleted from the table "aa....aa"."bb....bb". (return code = cc....cc) (M+S)

Processing to delete the data in the deletion-pending status in the table aa....aa.bb....bb has terminated.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc: Return code

0: Normal termination

Other than 0: Error

S:

If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbreorgsystemdata command.

KFAA80255-I

Phase 1 of the processing to reorganize the table "aa....aa"."bb....bb" will now start. (M+S)

Phase 1 of the processing to reorganize the table aa....aa.bb....bb will now start.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80256-I

Phase 1 of the processing to reorganize the table "aa....aa"."bb....bb" has finished. (return code = cc....cc) (M+S)

Phase 1 of the processing to reorganize the table aa....aa.bb....bb has finished.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc: Return code

0: Normal termination

Other than 0: Error

S:

If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbreorgsystemdata command.

KFAA80257-I

Phase 2 of the processing to reorganize the table "aa....aa"."bb....bb" will now start. (M+S)

Phase 2 of the processing to reorganize the table aa....aa.bb....bb will now start.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80258-I

Phase 2 of the processing to reorganize the table "aa....aa"."bb....bb" has finished. (return code = cc....cc) (M+S)

Phase 2 of the processing to reorganize the table aa....aa.bb....bb has finished.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc: Return code

0: Normal termination

Other than 0: Error

S:

If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbreorgsystemdata command.

KFAA80259-I

The total number of segments used by the table "aa....aa"."bb....bb" and by the index defined for that table changed from cc....cc to dd....dd. (reason = "ee....ee") (M+S)

The total number of segments used by the table aa....aa.bb....bb and the indexes defined for the table aa....aa.bb....bb changed from cc....cc to dd....dd.

aa....aa:

Schema name of the target table

bb....bb:

Table identifier of the target table

cc....cc:

Total number of segments used by the target table and the indexes defined for that table before the reorganization processing of the dictionary table or system table

dd....dd:

Total number of segments currently used by the target table and the indexes defined for that table after the reorganization processing of the dictionary table or system table

ee....ee: Reason

The new data after reorganization was stored.: The data after reorganization is stored.

The original data before reorganization was deleted.: The data before reorganization is deleted.

S:

Continues processing.

KFAA80280-I

The number of lines of logical error data output to the error data file reached the maximum. (max. lines output to file = aa....aa) (M+S)

The number of lines of logical error data output to the logical error data file has reached the maximum number of lines that can be output.

aa....aa:

The maximum number of lines that can be output to the logical error data file

S:

Continues processing.

Action:

Take one of the following corrective actions:

Increase the value specified in import option adb_import_errdata_num in order to increase the maximum number of lines that can be output to the logical error data file.

Eliminate the causes of the logical errors in input data so that the number of logical errors in the input data file does not reach the maximum number of lines that can be output to the logical error data file.

Then, re-execute the adbimport command specifying the -d option and not specifying the -e option. Data import processing is then executed in creation mode, and processing continues even if a logical error is detected.

If the -e option is specified, processing terminates when a logical error is detected.

KFAA80281-I

The input data contains a logical error. (error count = aa....aa) (M+S)

A logical error has occurred in input data.

aa....aa: Number of logical errors

If the -e option was specified, this is the number of logical errors that were detected before this message was output.

S:

Terminates processing.

Action:

Check messages pertaining to logical error data, and eliminate the causes of the logical errors in data in the input data file. Then, re-execute the adbimport command.

However, if the adbimport command was executed specifying 1 for import option adb_import_errmsg_lv, no messages pertaining to logical errors are displayed. In this case, determine the cause of the logical errors from the input data that was not loaded into the database, and then eliminate the cause of the logical errors.

For details about the corrective action to take when logical errors occur in input data, see How to handle logical errors in input data in the manual HADB Command Reference.

KFAA80282-I

Cost-information search processing was started for the "aa....aa"."bb....bb" table. (M+S)

Retrieval processing for collecting cost information for base table aa....aa.bb....bb has started.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80283-I

Cost-information search processing was ended for the "aa....aa"."bb....bb" table. (M+S)

Retrieval processing for collecting cost information for base table aa....aa.bb....bb has been completed.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80284-I

Cost-information storage processing in a system table was started for the "aa....aa"."bb....bb" table. (M+S)

The processing to store cost information for base table aa....aa.bb....bb in the system tables has started.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80285-I

Cost-information storage processing in a system table was ended for the "aa....aa"."bb....bb" table. (M+S)

The processing to store cost information for base table aa....aa.bb....bb in the system tables has been completed.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80286-I

Cost-information deletion processing in a system table was started for the "aa....aa"."bb....bb" table. (M+S)

The processing to delete cost information for base table aa....aa.bb....bb from the system tables has started.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80287-I

Cost-information deletion processing in a system table was ended for the "aa....aa"."bb....bb" table. (M+S)

The processing to delete cost information for base table aa....aa.bb....bb from the system tables has been completed.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80288-I

Cost-information deletion processing in a system table was skipped for the "aa....aa"."bb....bb" table. (M+S)

The processing to delete cost information for base table aa....aa.bb....bb from the system tables was skipped because there is no cost information for that base table in the system tables.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80291-I

Processing to collect cost information about the "aa....aa"."bb....bb" table started. (M+S)

The consolidation of cost information for base table aa....aa.bb....bb has started.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80292-I

Processing to collect cost information about the "aa....aa"."bb....bb" table ended. (M+S)

The consolidation of cost information for base table aa....aa.bb....bb has finished.

aa....aa:

Schema name

bb....bb:

Table identifier

S:

Continues processing.

KFAA80295-I

Processing to output the statistics log started. (file = aa....aa) (M)

The processing to output a statistics log started.

aa....aa:

Name of the statistics log file

S:

Continues processing.

KFAA80296-I

The output destination for the statistics log was changed from aa....aa to bb....bb. (M)

The target file for statistics log output changed from aa....aa to bb....bb.

aa....aa:

Name of the statistics log file before change

bb....bb:

Name of the statistics log file after change

S:

Continues processing.

Action:

Statistical information output to the statistics log file before the change might be overwritten. If you need to save the statistical information, output the statistical information for SQL statements using the adbstat command.

KFAA80297-I

The size of the statistics log file was reduced.(file name = aa....aa , size = b GB) (M)

The size of the statistics log file changed.

aa....aa:

Name of the statistics log file

b:

Size of the statistics log file after change

S:

Continues processing.

KFAA80300-I

The communication service started. (port = aaaaa) (L+M)

The communication service has been started.

aaaaa:

Service port number

S:

Continues processing.

KFAA80301-I

The communication service terminated. (port = aa....aa) (L+M)

The communication service has stopped.

aa....aa:

Service port number

S:

Terminates processing.

KFAA80500-I

Processing to initialize the DB area encryption facility will now start. (L+M)

Starts the start processing for the DB area encryption facility.

S:

Continues processing.

KFAA80501-I

Processing to initialize the DB area encryption facility has finished. (return code = aa....aa) (L+M)

DB area encryption facility start processing has terminated.

aa....aa: Return code

0: Normal termination

Other than 0: Error

S: If the return code is 0, processing continues.

If the return code is not 0, processing terminates.

Action:

If the return code is not 0, eliminate the cause of the error based on the message that was output immediately prior to this message. Then, re-execute the adbstart command.

KFAA81000-I

A connection was established. (connection identifier = aaaa, application identifier = "bb....bb", client group = "cc....cc", IP address = "dd....dd", process ID = ee....ee, connection serial number = ff....ff, connection information = gg....gg) (M)

A connection has been established with an application program or command using connection ID aaaa.

aaaa:

Connection ID

bb....bb:

Application identifier

cc....cc:

Name of the client group to which the client belongs, or name of the command group to which the command belongs

dd....dd:

IP address

ee....ee:

Process ID

ff....ff:

Connection sequence number (starting with 1) that is allocated after the HADB server starts

gg....gg:

Connection information

S:

Continues processing.

KFAA81001-I

The connection was ended. (connection identifier = aaaa, connection information = bb....bb) (M)

The connection with an application program or command whose connection ID is aaaa has been terminated.

aaaa:

Connection ID

bb....bb:

Connection information

S:

Continues processing.

KFAA81002-I

The transaction ended normally. (connection identifier = aaaa) (M)

The transaction of connection ID aaaa has terminated normally.

aaaa:

Connection ID

S:

Continues processing.

KFAA81003-I

The transaction was rolled back. (connection identifier = aaaa) (M)

The transaction of connection ID aaaa has been rolled back.

aaaa:

Connection ID

S:

Continues processing.

KFAA81004-I

The output destination file of the SQL trace was changed from aa....aa to bb....bb. (M)

The output destination of SQL trace information is changed from aa....aa to bb....bb.

aa....aa:

SQL trace file name before change

bb....bb:

SQL trace file name after change

S:

Continues processing.

Action:

SQL trace information that has been output to the SQL trace file before change might be overwritten by the new SQL trace information. If you want to save the SQL trace information, back up the trace file.

KFAA81200-I

The server definition adb_dbbuff_wrktbl_clt_blk_num was changed from aa....aa to bb....bb. (L+M)

The value specified in the server definition's adb_dbbuff_wrktbl_clt_blk_num operand has changed from aa....aa to bb....bb.

aa....aa:

Value specified in the server definition's adb_dbbuff_wrktbl_clt_blk_num operand before it was changed (number of pages of buffer for local work table)

bb....bb:

Value specified in the server definition's adb_dbbuff_wrktbl_clt_blk_num operand after it was changed (number of pages of buffer for local work table)

S:

Continues processing.

KFAA81205-I

Processing to check for transactions that require recovery will begin. Now checking for transactions that were aa....aa. (size of the system log to be checked = bb....bb KB) (M)

Processing to check for transactions that require recovery will now start.

aa....aa: Type of the transaction

updating system info

Transaction that is updating system information

in commit or rollback after updating system info

Transaction that was being completed after updating system information

updating the data DB area

Transaction that is updating the data DB area

in commit or rollback after updating the data DB area

Transaction that was being completed after updating the data DB area

removing archive files

Transaction that is deleting the archive directory

updating database resident info

Transaction that is updating database resident information

bb....bb:

Size of the system log to be checked (KB)

S:

Continues processing.

KFAA81206-I

Processing to check for transactions that require recovery is complete. (M)

Processing to check for transactions that require recovery has terminated.

S:

Continues processing.

KFAA81207-I

Processing to recover the database will now begin. (total number of transactions = aa....aa, total number of user log files = bb....bb, total size of system logs to be recovered = cc....cc KB) (M)

Processing to recover the database will now start.

aa....aa:

Total number of transactions that must be recovered

bb....bb:

Total number of user log files that must be recovered

cc....cc:

Total size of system logs that must be recovered (KB)

S:

Continues processing.

KFAA81208-I

Processing to recover the database is complete. (M)

Processing to recover the database has terminated.

S:

Continues processing.

KFAA81209-I

Processing to recover transactions will now begin. (transaction ID = aa....aa, number of user log files = bb....bb, size of system logs to be recovered = cc....cc KB) (M)

Processing to recover the transaction will now start.

aa....aa:

Transaction ID

bb....bb:

Number of user log files that must be recovered

cc....cc:

Size of system logs that must be recovered (KB)

S:

Continues processing.

KFAA81210-I

Processing to recover transactions is complete. (transaction ID = aa....aa) (M)

Processing to recover the transaction has terminated.

aa....aa:

Transaction ID

S:

Continues processing.

KFAA81211-I

Processing to recover transactions is complete. (transaction ID = aa....aa, recovered rows = {ins: bb....bb, upd: cc....cc, del: dd....dd}, buffer requests = ee....ee, pages read = {count: ff....ff, total size: gg....gg KB}, pages written = {count: hh....hh, total size: ii....ii KB}) (L+M)

Processing to recover the transaction has terminated.

aa....aa:

Transaction ID

bb....bb:

Number of rows inserted by the INSERT statement that was being executed by the transaction to be recovered#

cc....cc:

Number of rows updated by the UPDATE statement that was being executed by the transaction to be recovered#

dd....dd:

Number of rows deleted by the DELETE statement that was being executed by the transaction to be recovered#

ee....ee:

Number of page requests for the global buffer

ff....ff:

Number of times pages were read

gg....gg:

Total size of pages that were read (KB)

hh....hh:

Number of times data was written to pages

ii....ii:

Total size of pages to which data was written (KB)

#

This includes the number of rows processed by the HADB server for the dictionary table (base table), system table (base table), and location table.

S:

Continues processing.

Action:

This message is output if recovery processing of a transaction took more time than the value specified for the adb_log_rec_msg_interval operand in the server definition.

If processing to recover a transaction took a longer time than you expected, check the information output to this message. Then, consider reducing the amount of information updated in one transaction by, for example, increasing the number of times transactions are committed.

KFAA81214-I

Now checking transactions... (time elapsed in minutes = aa....aa, size of system logs that have been checked = bb....bb KB, progress = ccc% complete) (L+M)

Transaction check processing is in progress. aa....aa minutes have elapsed since the start.

aa....aa:

Time elapsed since the check processing started (minutes)

bb....bb:

Size of the checked system log file (KB)

ccc:

Progress of check processing (%)

S:

Continues processing.

KFAA81215-I

Now recovering the database... (time elapsed in minutes = aa....aa, total size of system logs that have been recovered = bb....bb KB, progress = ccc% complete) (L+M)

Processing to recover the database is in progress. aa....aa minutes have elapsed since the recovery processing started.

aa....aa:

Time elapsed since the database recovery processing started (minutes)

bb....bb:

Size of the recovered system log file (KB)

ccc:

Progress of recovery processing (%)

S:

Continues processing.

Action:

This message is output at certain intervals according to the value specified for the adb_log_rec_msg_interval operand in the server definition.

From this message, estimate the time required to complete the database recovery processing and allow subsequent processing to be restarted.

For details, see Steps to take when the processing time for restarting the HADB server takes too long in the HADB Setup and Operation Guide.

KFAA81220-I

The updated-row columnizing facility is aa....aa. (L+M)

The status of the updated-row columnizing facility is aa....aa.

aa....aa: Status of the updated-row columnizing facility

ACTIVE: Enabled

INACTIVE: Disabled

S:

Continues processing.

KFAA81221-I

Input/output control for the files used by the updated-row columnizing facility has started. (M)

Input/output control for the files used by the updated-row columnizing facility has started.

S:

Continues processing.

KFAA81260-I

Cache files were reused. (DB area = "aa....aa", file num = bb....bb, size = cc....cc) (L+M)

Cache files were reused.

aa....aa:

DB area name

bb....bb:

Number of cache files reused

cc....cc:

Total size of the reused cache files (unit: bytes)

S:

Continues processing.

KFAA81261-I

Cache files were not reused. (DB area = "aa....aa", file num = bb....bb, size = cc....cc, reason = "dd....dd") (L+M)

There are cache files in the DB area that cannot be reused.

aa....aa:

Name of DB area where cache files cannot be reused

bb....bb:

Number of cache files that could not be reused

cc....cc:

Total size of cache files that could not be reused (unit: bytes)

dd....dd: Reason it cannot be reused

The maximum capacity of the cache group has decreased.

If the server definition's adbcachegrp operand is specified

Cache files in the DB area allocated to a cache group with a smaller cache group capacity limit (the value specified by the -s option of the adbcachegrp operand in the server definition) cannot be reused.

If the server definition's adb_core_path operand is omitted

If the specified value of the adb_sys_cld_cache_total_size operand (upper limit of the total cache file size) in the server definition is smaller, all cache files cannot be reused.

The allocation of the cache group has changed.

Cache files in the data DB area for which the cache group to which they are assigned has been changed cannot be reused.

S:

Continues processing.

KFAA81262-I

None of the cache files were reused. (reason = "aa....aa") (L+M)

All cache files were not reused.

aa....aa:

Reason

S:

Continues processing.

Action:

Take corrective action as described in the following table:

Information output to aa....aa

Reason for not reusing

Action to take

Now upgrading the HADB version.

The cache file cannot be reused at the first start of the HADB server after the HADB server has been upgraded.

In this case, no action is needed.

The reuse information file (in the cache file storage directory) does not exist.

The reuse information file does not exist in the cache file storage directory.

Possible causes are as follows:

Deleted or moved the reuse information file after the termination of the HADB server.

An error occurred during the HADB server processing.

The HADB server did not terminate normally

Problem with creating reuse information file when terminating HADB server

If you have problems creating the reuse information file when terminating the HADB server, see the warning message that precedes the KFAA81264-I message.

Note that even if there is a problem with the creation of the reuse information file in the cache file storage directory, aa....aa may output The reuse information file (in cloud storage) does not exist..

The reuse information file (in cloud storage) does not exist.

Reuse information file does not exist in cloud storage.

The cache file content does not match the cloud storage.

The contents of the cache file do not match the contents of the cloud storage data.

The contents of the cache file may differ from the contents of the cloud storage data. When the cloud storage database was recovered from backup, the reuse information file may have remained in the cache file storage directory. In this case, no action is needed.

***

Read the warning message output before this message and take the corrective action indicated.

Read the warning message output before this message and take the corrective action indicated.

KFAA81263-I

The reuse information file was created. (L+M)

A reuse information file was created.

S:

Continues processing.

KFAA81264-I

The reuse information file was not created. (L+M)

The reuse information file was not created.

S:

Continues processing.

Action:

Check the warning message that was output prior to this message.

KFAA81265-I

The processing to delete the reuse information file is complete. (L+M)

Deletion of the reuse information file was executed.

S:

Continues processing.

KFAA81400-I

The audit trail facility is aa....aa. (M)

The audit trail facility is aa....aa.

aa....aa: Status of the audit trail facility

ACTIVE: Enabled

INACTIVE: Disabled

S:

Continues processing.

KFAA81401-I

The file to which the audit trail is output was swapped. (file name = aa....aa) (M)

The file to which the audit trail is output was swapped.

aa....aa:

Absolute path of the swap-source audit trail file (absolute path after the rename)

S:

Continues processing.

Action:

If a value other than 0 is specified for the adb_audit_log_max_num operand in the server definition, the old audit trail file might be deleted. Therefore, if this message is output, we recommend that you move audit trail files to the audit trail storage directory.

KFAA81402-I

The audit trail file was renamed. (file name = aa....aa) (M)

The audit trail file was renamed.

aa....aa:

Absolute path of the audit trail file after the rename

S:

Continues processing.

KFAA82000-I

The compression type for column "cc....cc" in table "aa....aa"."bb....bb" is "dd....dd". (thread no. = ee....ee) (M)

The compression type of the "cc....cc" column of the column store table "aa....aa"."bb....bb" is dd...dd. The thread number used to perform compression is ee....ee.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc:

Column name

dd....dd: Column-data compression type

NONE: Not compressed

RUNLENGTH: Compression by run-length encoding

DELTA: Delta compression

DELTA_RUNLENGTH: Compression by delta run-length encoding

DICTIONARY: Compression by dictionary encoding

ee....ee:

Real thread number

S:

Continues processing.

KFAA82002-I

The storage ratio for column "cc....cc" in table "aa....aa"."bb....bb" is dd....dd (ee....ee) bytes to ff....ff bytes (gg....gg%). (data type = hh....hh) (M)

The data storage rate of the "cc....cc" column of the column store table "aa....aa"."bb....bb" is gg....gg%.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc:

Column name

dd....dd:

Size of the column data when data is stored without compression (bytes)

This is the size of the column data when NONE is specified for the column-data compression type.

ee....ee:

Data size of the input data file (bytes)

This is the size of the character string data extracted from the input data file.

ff....ff:

Size of the column data after compression (bytes)

gg....gg:

Storage rate (%)

hh....hh:

Data type of the cc....cc column

S:

Continues processing.

KFAA82003-I

The compression ratio of table "aa....aa"."bb....bb" is cc....cc (dd....dd) bytes to ee....ee bytes (ff....ff%). (M)

The data storage rate of the entire column store table "aa....aa"."bb....bb" is ff....ff%.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc:

Data size of the of the entire table when data is stored without compression (bytes)

This is the data size of the entire table when NONE is specified for the column-data compression type.

dd....dd:

Data size of the input data file (bytes)

This is the size of the character string data (including delimiting characters) extracted from the input data file.

ee....ee:

Data size of the entire table after compression (bytes)

ff....ff:

Storage rate (%)

S:

Continues processing.

KFAA82004-I

The number of segments used in table "aa....aa"."bb....bb" is cc....cc. (max = dd....dd, min = ee....ee, average = ff....ff, unused pages = gg....gg) (M)

The number of segments that are used to import data from the column store table "aa....aa"."bb....bb" is cc....cc.

The maximum number of data items stored in one segment is dd....dd. The minimum number is ee....ee. The average number is ff....ff. The number of unused pages in the segments where data is stored is gg....gg.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc:

Number of segments where data is stored

dd....dd:

The maximum number of data items that are stored in one segment

ee....ee:

The minimum number of data items that are stored in one segment

ff....ff:

The average number of data items that are stored in one segment

gg....gg:

Number of unused pages in the segments where data is stored

S:

Continues processing.

2.7 Messages from KFAA90000 to KFAA99999

KFAA90000-I

aa....aa processing started. (M+S)

Processing of the aa....aa command has started.

aa....aa:

Executed command

S:

Continues processing.

KFAA90001-I

aa....aa processing ended. (return code = bb) (M+S)

Processing of the aa....aa command has terminated.

aa....aa:

Executed command

bb: Return code

0: Normal termination

4: Termination with warning

8: Abnormal termination

12: Re-execution required

16: Disrupted communication with an HADB server

20: Part of processing skipped

S:

Continues processing.

Action:

■ If the return code is 4

Although processing of the executed command terminated, a warning or an error occurred in an extension of processing. Check the warning message or error message output to the message log.

■ If the return code is 8

Eliminate the cause of the error based on the message that was output immediately prior to this message, and then re-execute the command.

■ If the return code is 12

Although processing of the executed command terminated, the command must be re-executed for postprocessing. Eliminate the cause of the error based on the message that was output immediately prior to this message, and then take the following action.

If the executed command is the adbreorgsystemdata command

The data before reorganization remains in the dictionary DB area or the system-table DB area. Re-execute the adbreorgsystemdata command.

■ If the return code is 16

Communication with the HADB server was disconnected during command execution. For the cause of this disconnection, check the error message that was displayed or the error message that was output to the message log file.

In addition, check the warning message or error message output to the message log to confirm that the command terminated normally.

For details about the corrective action to take, see the description for return code 16 in Return codes in the aa....aa command in the manual HADB Command Reference.

■ If the return code is 20

For details about the corrective action to take, see the description for return code 20 in Return codes in adbmergechunk (Merge Chunks) in the manual HADB Command Reference.

KFAA90002-E

The command arguments or command options are invalid. (command name = aa....aa, reason = bb....bb) (E+M)

The command specification format is invalid.

aa....aa:

Executed command

bb....bb: Description of error

no necessary option

A required option was not found.

invalid option

An invalid option was specified.

number of command arguments are invalid

The number of command arguments specified is invalid.

invalid argument

The specified value of an option argument is invalid.

S:

Terminates processing.

Action:

Correct the specification format of the command as indicated by the Usage note output after this message, and then retry the operation.

KFAA90003-E

The option argument is invalid. (command name = aa....aa, option = bb....bb, reason = cc....cc) (E+M)

A specification for a command option argument is invalid.

aa....aa:

Executed command

bb....bb:

Invalid option

cc....cc: Description of error

the length(byte) of option argument is invalid

The length of an option argument is invalid.

character attribute of option argument is invalid

A character attribute specified in the option argument is invalid.

out of range

The value specified as the option argument is outside the allowed range.

S:

Terminates processing.

Action:

Correct the specification of the option argument, and then re-execute the command.

KFAA90004-E

The HADB system is not running. First start the HADB system, and then re-execute the command. (E+M)

The command cannot be executed because the HADB server is not running.

S:

Terminates processing.

Action:

Once the HADB server has started, execute the command.

KFAA90005-E

The HADB system is running. First stop the HADB system, and then re-execute the command. (E+M)

The command cannot be executed because the HADB server has not stopped.

S:

Terminates processing.

Action:

Once the HADB server has terminated, execute the command.

KFAA90006-E

The adbstart command, the adbstop command, the adbchgsrvmode command or the adbinit command is already executing. (E+M)

This command cannot be executed because the adbstart, adbstop, adbchgsrvmode, or adbinit command is executing.

S:

Terminates processing.

Action:

Only one of the commands adbstart, adbstop, adbchgsrvmode, or adbinit can be executed at any one time. Wait for the adbstart, adbstop, adbchgsrvmode, or adbinit command to terminate, and then re-execute the command.

KFAA90008-Q

Specify a password: (M+S)

Specify a password for the authorization identifier that connects to the HADB server.

S:

Continues processing.

Action:

Specify a password.

KFAA90009-E

An error occurred while reading from the standard input. (func = "aa....aa", errno = bb....bb) (E+M)

An error occurred while reading from the standard input.

aa....aa:

Name of the function being executed

bb....bb:

Error number returned in errno

S:

Terminates processing.

Action:

Check in the OS documentation for the error number that was displayed in errno (bb....bb), and then eliminate the cause of the error.

If you cannot determine the corrective action to take based on the error number that was displayed in errno (bb....bb), execute the adbinfoget command, collect troubleshooting information, and then contact the customer support center.

KFAA90010-I

The following values were specified for the aa....aa command. (M)

A value is specified for the aa....aa command.

A message indicating the specified value is output after this message.

aa....aa:

Name of the command executed

S:

Continues processing.

KFAA90011-I

aa....aa : bb....bb (M)

bb....bb is specified for the aa....aa command.

aa....aa:

Command name

bb....bb: Specified value

If the specified value exceeds 1,024 bytes, the 1,024th and subsequent bytes are truncated.

S:

Continues processing.

KFAA90012-E

The length of the entered password is invalid. (E+M)

The length of the entered password is invalid.

S:

Terminates processing.

Action:

Enter the correct password.

KFAA90013-Q

Specify aa....aa: (M+S)

Enter the HADB encryption key usage password.

aa....aa: Entered HADB encryption key usage password

the current HADB encryption key usage password

HADB encryption key usage password for the HADB encryption key in use

a new HADB encryption key usage password

HADB encryption key usage password to be set for the newly created HADB encryption key

S:

Continues processing.

Action:

If aa....aa is the current HADB encryption key usage password

Enter the HADB encryption key usage password for the HADB encryption key in use.

If aa....aa is a new HADB encryption key usage password

Set the HADB encryption key usage password for the newly created HADB encryption key. Enter the HADB encryption key usage password you wish to set.

KFAA90014-E

The specified HADB encryption key usage password is invalid. (E+M)

The specified HADB encryption key usage password is invalid.

Possible causes are as follows:

The specified HADB encryption key usage password contains unusable characters.

S:

Terminates processing.

Action:

Specify the correct HADB encryption key usage password, and then re-execute the command. The same specification rules apply to the HADB encryption key usage password as to the password for the authorization identifier. For details about the rules for specifying passwords (usable characters, etc.), see Password specification rules in the HADB Setup and Operation Guide.

KFAA90500-E

The "aa....aa" option cannot be used. Use the "bb....bb" option. (E+M)

You can no longer specify the command option aa....aa. Specify the option bb....bb instead.

aa....aa:

Name of the option that can no longer be specified.

bb....bb:

Name of the option that takes the place of the option that can no longer be specified

S:

Terminates processing.

Action:

Take one of the following actions:

If this message is output when the command adbimport is executed

You cannot specify the following import options:

adb_import_dataload_rthd_num

adb_import_sort_rthd_num

adb_import_dividx_rthd_num

For the import option adb_import_rthd_num, specify the number of processing real threads to be used during execution of the command adbimport. For details about adb_import_rthd_num, see Options related to performance in Explanation of specification format in Format of import options in the manual HADB Command Reference.

If this message is output when the command adbidxrebuild is executed

You cannot specify the following index rebuild options:

adb_idxrebuild_scan_rthd_num

adb_idxrebuild_sort_rthd_num

adb_idxrebuild_dividx_rthd_num

For the index rebuild option adb_idxrebuild_rthd_num, specify the number of processing real threads to be used during execution of the command adbidxrebuild. For details about adb_idxrebuild_rthd_num, see Explanation of specification format in Format of index rebuild options in the manual HADB Command Reference.

If this message is output when the command adbgetcst is executed

You cannot specify the following cost-information collection option:

adb_getcst_scan_rthd_num

For the cost-information collection option adb_getcst_rthd_num, specify the number of processing real threads to be used during execution of the command adbgetcst. For details about adb_getcst_rthd_num, see Explanation of specification format in Format of the cost-information collection option in the manual HADB Command Reference.

If this message is output when the command adbexport is executed

You cannot specify the following export option:

adb_export_scan_rthd_num

For the export option adb_export_rthd_num, specify the number of processing real threads to be used during execution of the command adbexport. For details about adb_export_rthd_num, see Options related to performance in Explanation of specification format in Format of export options in the manual HADB Command Reference.

If this message is output when the command adbmergechunk is executed

You cannot specify the following merge chunk options:

adb_mergechunk_scan_rthd_num

adb_mergechunk_sort_rthd_num

adb_mergechunk_dividx_rthd_num

For the merge chunk option adb_mergechunk_rthd_num, specify the number of processing real threads to be used during execution of the command adbmergechunk. For details about adb_mergechunk_rthd_num, see Explanation of specification format in Format of merge chunk options in the manual HADB Command Reference.

If this message is output when the command adbarchivechunk is executed

You cannot specify the following archive chunk option:

adb_arcv_scan_rthd_num

For the archive chunk option adb_arcv_rthd_num, specify the number of processing real threads to be used during execution of the command adbarchivechunk. For details about adb_arcv_rthd_num, see Explanation of specification format in Format of archive chunk options in the manual HADB Command Reference.

If this message is output when the command adbunarchivechunk is executed

You cannot specify the following unarchive chunk options:

adb_unarcv_dataload_rthd_num

adb_unarcv_sort_rthd_num

adb_unarcv_dividx_rthd_num

For the unarchive chunk option adb_unarcv_rthd_num, specify the number of processing real threads to be used during execution of the command adbunarchivechunk. For details about adb_unarcv_rthd_num, see Explanation of specification format in Format of unarchive chunk options in the manual HADB Command Reference.

KFAA91000-E

An error occurred while processing a command. (command name = aa....aa, reason = bb....bb) (E+M)

Processing stopped because an error occurred during execution of a command.

aa....aa:

Executed command

bb....bb:

Cause of the error

S:

Terminates processing.

Action:

Take the corrective action that corresponds to the cause of the error that was output, as described in the following table.

Cause of the error

Definition

Action to take

A memory is insufficient

Memory is insufficient.

Delete any unnecessary processes. If there are no unnecessary processes, memory is insufficient.

The execution environment is invalid

The execution environment of the command is invalid.

The structure of the directory specified for the ADBDIR environment variable is invalid. Re-install the HADB server. For details about how to install the HADB server, see Installing the HADB server in the HADB Setup and Operation Guide.

Communication error

A communication error occurred.

The possible causes are as follows:

The HADB server is stopped.

An error occurred on the HADB server, and the connection was closed.

An error occurred in communications initialization processing.

A network failure occurred.

Allocation of communication port numbers failed.

Internal error

There is an internal conflict.

Take the corrective action described in the message that was output.

Lack of file descriptor

There are no longer enough file descriptors.

If there are files that can be closed, close them.

Failed operation of shared memory

An attempt to access shared memory failed.

Eliminate the cause of the error as indicated for the message that was output, and then re-execute the command.

If the HADB server is set up to automatically start from Job Management Partner 1/Automatic Job Management System 3, this error might be output because the kernel parameters specified in /etc/security/limits.conf do not take effect. See Estimating the kernel parameters in the HADB Setup and Operation Guide, and then check that the kernel parameters are configured to take effect.

Failed operation of semaphore

Semaphore operation has failed.

Eliminate the cause of the error based on the message that was output, and then re-execute the command.

Trouble shoot information is exist

Troubleshooting information already exists.

Collect troubleshooting information with the adbinfoget command, re-execute the command, and then delete the troubleshooting information.

I/O error

An I/O error has occurred.

A failure might have occurred on a disk that holds the server directory. After taking corrective action, re-execute the command.

Creation of a process failed

The process creation failed because the resource limit was reached.

An attempt was made to create more processes than the maximum number that can be created. Revise the specified value of kernel parameter nproc. After taking corrective action, re-execute the command.

For details about nproc, see Estimating the kernel parameters in the HADB Setup and Operation Guide.

KFAA91001-W

An error occurred during command execution. (reason = aa....aa) (E+M)

An error occurred during command execution, but processing continues.

aa....aa:

Cause of the error

S:

Terminates processing.

Action:

Take the corrective action that corresponds to the cause of the error that was output, as described in the following table.

Cause of the error

Definition

Action to take

message log file disk full

An attempt to write to a message log file failed because the disk is full.

Terminate the HADB server with the adbstop command, increase the amount of free space on the disk that holds the server directory, and then re-execute the command.

message log file write failed

An attempt to write to a message log file failed.

Confirm that the status of the message log file allows writes, and then re-execute the command.

KFAA91100-I

Usage: adbstart [{--normal | --quiescence | --offline | --maintenance}] (M+S)

Indicates the specification format of the adbstart command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA91101-W

The adbstart command does not need to be executed because the HADB system is already running. (E+M)

There is no need to execute the adbstart command because the HADB server is already running.

S:

Terminates processing.

KFAA91102-E

An error occurred during the HADB system start processing. (information = aa....aa) (E+M)

An error occurred during the HADB system start processing.

aa....aa:

Message ID

S:

Terminates processing.

Action:

The start processing error message (the message corresponding to the message ID output as aa....aa) has been output to a message log file. Take corrective action as indicated for that error message.

If an error occurs before the area for communication between the adbstart process and the server process is prepared, and the message ID cannot be acquired, 00000 is output for aa....aa. In that case, check the message that was output immediately prior to this message, since the cause of the error is sometimes output to the message log.

If no message is output, the file might have failed to open because there are not enough file descriptors. In this case, reduce the number of file descriptors used in the system as a whole, and then retry the operation.

00000 is also output for information even when the server process is terminated due to one of the following errors prior to completion of server process startup.

When the server process is terminated by the OS's kill command

When the server process is forcibly terminated by OOM Killer because sufficient memory could not be allocated by the OS

When the multi-node configuration with HA Monitor is used and the adbstart command is executed without waiting for the HA Monitor server to stop

In these cases, the cause of the error is output to syslog. Check syslog, eliminate the cause of the error, and then retry the operation.

KFAA91104-Q

Are you sure you want to discard trouble shoot information? (y/N) (M+S)

Specify whether you want to delete troubleshooting information.

S:

Continues processing.

Action:

Take one of the following corrective actions:

If troubleshooting information has not been collected by using the adbinfoget command, enter either n (or N), and then terminate the adbstart command. After that, use the adbinfoget command to collect troubleshooting information. For details about how to collect troubleshooting information, see Collecting troubleshooting information (adbinfoget command) in Error Handling in the HADB Setup and Operation Guide.

If troubleshooting information has been collected by using the adbinfoget command, enter y (or Y). The HADB server will start after the troubleshooting information created by the HADB server has been deleted from the shared memory.

KFAA91105-I

The HADB system was started aa....aa. (HADB server operation mode = "bb....bb") (S+L+M)

The HADB server has started normally. The HADB server operation mode is bb....bb.

aa....aa: Startup mode

normally: Normal start

bb....bb: HADB server operation mode

NORMAL: Normal mode

QUIESCENCE: Quiescence mode

OFFLINE: Offline mode

MAINTENANCE: Maintenance mode

S:

Terminates processing.

KFAA91107-Q

Are you sure you want to upgrade database from version "aa....aa" to version "bb....bb"? (y/N) (M+S)

Specify whether you want to upgrade the database.

aa....aa:

Version of the HADB server before upgrade

bb....bb:

Version of the HADB server after upgrade

S:

Continues processing.

Action:

If you want to upgrade the database, enter y (or Y). If you want to cancel upgrading, enter n (or N).

KFAA91108-E

The upgrade of the database was canceled. (E+M)

The database upgrade processing was canceled.

S:

Terminates processing.

KFAA91109-I

Execute the monbegin command of HA Monitor. (M+S)

Execute HA Monitor's monbegin command.

S:

Terminates processing.

Action:

If this message is output, execute HA Monitor's monbegin command. If the monbegin command had already been executed when this message is output, first execute the monend command. Then, re-execute the monbegin command.

KFAA91110-I

The HADB node type is "aa....aa". (S+L+M)

The node type of the HADB server is aa....aa.

aa....aa: Node type

PRIMARY: Primary node

SECONDARY: Secondary node

WORKER: Worker node

S:

Terminates processing.

KFAA91111-I

The upgrade of the database from version "aa....aa" to version "bb....bb" was complete. (S+L+M)

The upgrade of the database has been completed.

aa....aa:

Version of the HADB server before upgrade

bb....bb:

Version of the HADB server after upgrade

S:

Terminates processing.

KFAA91150-I

Usage: adbstop [{--wait {connection | transaction} [-t <time-out-period>] [--node] | --cancel [--node] | --force | --node}] (M+S)

Indicates the specification format of the adbstop command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA91151-W

The adbstop command does not need to be executed because the HADB system is not running. (E+M)

There is no need to execute the adbstop command, because the HADB server has already terminated.

S:

Terminates processing.

KFAA91152-E

An error occurred during the HADB system terminate processing. (information = aa....aa) (E+M)

An error occurred during HADB server termination processing.

aa....aa:

Message ID

S:

Terminates processing.

Action:

The termination processing error message (the message corresponding to the message ID output as aa....aa) is output to a message log file. Take corrective action as indicated for the error message.

KFAA91153-Q

Are you sure you want to perform a forced termination? (y/N) (M+S)

Specify whether you want to force the HADB server to terminate.

S:

Continues processing.

Action:

To forcibly terminate, specify y (or Y). To cancel forcible termination, specify n (or N).

KFAA91154-I

The HADB system was terminated aa....aa. (S+L+M)

The HADB server terminated normally or forcibly.

aa....aa: Termination mode

normally: Normal termination

forcibly: Forced termination

S:

Terminates processing.

KFAA91155-I

The forced termination of the HADB system was canceled. (M+S)

Forcible termination of the HADB server was canceled.

S:

Terminates processing.

KFAA91250-I

Usage: adbcancel {--ALL | -u <connection-identifier>} (M+S)

Indicates the specification format of the adbcancel command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA91251-Q

Are you sure you want to cancel all connections? (y/N) (M+S)

Specify whether to forcibly terminate all connections.

S:

Continues processing.

Action:

To forcibly terminate all connections, specify y (or Y); to not terminate forcibly, specify n (or N).

KFAA91252-E

A connection using the specified connection identifier (-u option of adbcancel command) was not established. (E+M)

The connection of the connection ID specified using the -u option of the adbcancel command has not been established.

S:

Terminates processing.

Action:

Check whether the connection ID specified with the -u option is correct.

KFAA91253-I

The cancel processing was canceled. (M+S)

Cancel processing has been stopped.

S:

Terminates processing.

KFAA91254-E

An error occurred during cancellation processing. (information = aa....aa) (E+M)

An error occurred during cancellation processing.

aa....aa:

Message ID

S:

Terminates processing.

Action:

Check the termination processing error message output to the message log file (the message ID is output to aa....aa), and then eliminate the cause of the error. Then, retry the operation.

KFAA91300-I

Usage: adbls -d {srv | cnct | mem [-a] | shm [-a] | thd | ver | gbuf | lbuf | lock | node | cltgrp | prl | cfm} [-t] [-c] (M+S)

Indicates the specification format of the adbls command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA91301-E

There is no information to be output. (reason = "aa....aa") (E+M)

There is no information to be output.

aa....aa: Reason

SERVER NOT UP: The HADB server has not started.

SHARE MEMORY NOT FOUND: The shared memory does not exist.

S:

Terminates processing.

Action:

After the HADB server has started, re-execute the adbls command.

KFAA91350-I

Usage: adbshmdump {-m | -o <shmdump-file-path>} [-n <shm-no>] (M+S)

Indicates the specification format of the adbshmdump command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA91400-I

Usage: adbinfoget {-g | -m | -o <output-directory>} [-f <core-file>] [-l] [-r] (S)

Indicates the specification format of the adbinfoget command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA91401-I

adbinfoget processing started. (S)

Processing of the adbinfoget command is starting.

S:

Continues processing.

KFAA91402-I

adbinfoget processing ended. (return code = aa....aa) (S)

Processing of the adbinfoget command is terminating.

aa....aa:

Return code

S:

Terminates processing.

Action:

If the return code was not 0, take the corrective action indicated for the message that was output immediately prior to this message, and then eliminate the cause of the error.

KFAA91403-E

The specified path "aa....aa" is invalid. (reason = bb....bb) (E)

There is a problem with the specified path.

aa....aa:

Specified path

bb....bb: Cause of the error

not directory: The specified directory was not found. Another possibility is that it is not a directory.

not file: The specified file was not found. Another possibility is that the path does not point to a file.

too long: The path is too long.

invalid character: An invalid character was specified.

not full path: The path was not specified as an absolute path starting with a slash (/).

root directory: The root directory was specified.

invalid directory: Directories that include server directories or client directories cannot be specified.

not authorized: You do not have permission.

S:

Terminates processing.

Action:

Eliminate the cause of the error, and then re-execute the command.

KFAA91404-I

The troubleshooting information (aa....aa) output by the adbinfoget command is bb....bb bytes. (S)

The size of the troubleshooting-information file that is output when the adbinfoget command is executed is bb....bb bytes.

aa....aa: Type of troubleshooting-information file

detail: Troubleshooting-information file (detailed version)

light, mail: Troubleshooting-information file (light version and mail version)

root: Troubleshooting-information file (root version)

bb....bb:

Output size of troubleshooting information (bytes)

S:

Continues processing.

KFAA91405-E

The work directory is already exist. (E)

The work directory already exists.

S:

Terminates processing.

Action:

The adbinfoget command might have been executed simultaneously. Re-execute the command.

KFAA91406-I

Creation of a light-version troubleshooting information file started. (S)

Creation of a troubleshooting-information file (light version) is beginning.

S:

Continues processing.

KFAA91407-I

Creation of a light-version troubleshooting information file is complete. (S)

Creation of a troubleshooting-information file (light version) has finished.

S:

Continues processing.

KFAA91408-I

Creation of a detail-version troubleshooting information file started. (S)

Creation of a troubleshooting-information file (detailed version) is beginning.

S:

Continues processing.

KFAA91409-I

Creation of a detail-version troubleshooting information file is complete. (S)

Creation of a troubleshooting-information file (detailed version) has finished.

S:

Continues processing.

KFAA91410-I

Creation of a root-version troubleshooting information file started. (S)

Creation of a troubleshooting-information file (root version) will now start.

S:

Continues processing.

KFAA91411-I

Creation of a root-version troubleshooting information file is complete. (S)

Creation of a troubleshooting-information file (root version) has finished.

S:

Continues processing.

KFAA91412-E

The troubleshooting information could not be obtained because root privileges could not be obtained. (E)

The troubleshooting information could not be obtained because root privileges could not be obtained.

S:

Terminates processing.

Action:

Eliminate the cause of the error, and then re-execute the command.

KFAA91413-I

Output of the troubleshooting information specified for the -g option started. (S)

Output of troubleshooting information specified by the -g option will start.

S:

Continues processing.

After this message is output and until the KFAA91414-I message is output, the system pauses HADB server operation to output troubleshooting information.

KFAA91414-I

Output of the troubleshooting information specified for the -g option is complete. (S)

Output of troubleshooting information specified by the -g option has finished.

S:

Continues processing.

After the KFAA91413-I message is output and until this message is output, the system pauses HADB server operation to output troubleshooting information.

KFAA91415-W

The adbinfoget command with the -g option specified does not need to be executed because the HADB system is not running. (E)

Because the HADB server is not running, there is no need to specify the -g option when the adbinfoget command is executed.

S:

Terminates processing.

KFAA91450-I

Usage: adbinfosweep (S)

Indicates the specification format of the adbinfosweep command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA91451-I

adbinfosweep processing started. (S)

Processing of the adbinfosweep command is starting.

S:

Continues processing.

KFAA91452-I

adbinfosweep processing ended. (return code = aa....aa) (S)

Processing of the adbinfosweep command is terminating.

aa....aa:

Return code

S:

Terminates processing.

Action:

If the return code was not 0, eliminate the cause of the error as indicated for the message that was output immediately prior to this message.

KFAA91453-E

The adbinfosweep command cannot be executed because the HADB system is running. (E)

The adbinfosweep command cannot be executed while the HADB server is running.

S:

Terminates processing.

Action:

After the HADB server has terminated, execute the adbinfosweep command.

KFAA91500-I

Usage: adbchgsrvmode {--normal | --quiescence | --offline | --maintenance} (M+S)

Indicates the specification format of the adbchgsrvmode command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA91501-E

An error occurred during the HADB server operation mode change processing. (information = aaaaa) (E+M)

An error occurred while the HADB server operation mode was being changed.

aaaaa:

Message ID

S:

Terminates processing.

Action:

Check the error message about the mode change processing that was output to the message log file (the message corresponding to the message ID displayed as information), eliminate the cause of the error, and then perform the processing again.

If the server process was killed before the HADB server mode change processing was completed, 00000 might be displayed as information.

KFAA91502-I

The HADB server operation mode was changed to "aa....aa". (S+L+M)

The HADB server operation mode was changed to aa....aa.

aa....aa: HADB server operation mode after change

NORMAL: Normal mode

QUIESCENCE: Quiescence mode

OFFLINE: Offline mode

MAINTENANCE: Maintenance mode

S:

Terminates processing.

KFAA91503-E

The HADB server operation mode cannot be changed from "aa....aa" to "bb....bb". (E+M)

The HADB server operation mode cannot be changed from aa....aa to bb....bb.

aa....aa: HADB server operation mode before change

NORMAL: Normal mode

QUIESCENCE: Quiescence mode

OFFLINE: Offline mode

MAINTENANCE: Maintenance mode

bb....bb: HADB server operation mode after change

NORMAL: Normal mode

QUIESCENCE: Quiescence mode

OFFLINE: Offline mode

MAINTENANCE: Maintenance mode

S:

Terminates processing.

Action:

If aa....aa is OFFLINE or MAINTENANCE, and bb....bb is QUIESCENCE

The HADB server operation mode cannot be changed from offline or maintenance to quiescence. First change the HADB server operation mode to normal, and then change it to quiescence.

If aa....aa is QUIESCENCE or MAINTENANCE, and bb....bb is OFFLINE

The HADB server operation mode cannot be changed from quiescence or maintenance to offline. First change the HADB server operation mode to normal, and then change it to offline.

If aa....aa is QUIESCENCE or OFFLINE, and bb....bb is MAINTENANCE

The HADB server operation mode cannot be changed from quiescence or offline to maintenance. First change the HADB server operation mode to normal, and then change it to maintenance.

KFAA91504-W

The adbchgsrvmode command does not need to be executed because the HADB server operation mode is already "aa....aa". (E+M)

The adbchgsrvmode command does not need to be executed because the HADB server operation mode is already aa....aa.

aa....aa: HADB server operation mode to be changed

NORMAL: Normal mode

QUIESCENCE: Quiescence mode

OFFLINE: Offline mode

MAINTENANCE: Maintenance mode

S:

Terminates processing.

KFAA91550-I

Usage: aa....aa {-s <server-directory-path> | -c <client-directory-path>} (S)

Indicates the specification format of the adbinstall command. This message is displayed when command help is requested or when the command format is invalid.

aa....aa:

Command name

S:

Terminates processing.

KFAA91551-I

aa....aa processing started. (S)

Processing aa....aa command has started.

aa....aa:

Command name

S:

Continues processing.

KFAA91552-I

aa....aa processing ended. (return code = b) (S)

Processing of the aa....aa command has terminated.

aa....aa:

Command name

b: Return code

0: Normal termination

4: Warning termination

8: Abnormal termination

S:

Continues processing.

Action:

If the return code is 8, eliminate the cause of the error as indicated for the message that was output immediately prior to this message, and then re-execute the command.

If the return code is 4, command processing terminated, but a warning was issued in an extension of command processing. Check the warning message that was output prior to this message.

KFAA91553-E

An error occurred while the HADB server or a client was being installed. (reason = aa....aa, command = bb....bb, return code = cc....cc) (E)

An error occurred while the HADB server or a client was being installed.

aa....aa:

Cause of the error

bb....bb:

Name of the command resulting in an error

cc....cc:

Return code

S:

Terminates processing.

Action:

Take corrective action depending on the cause of the error that was output. After performing the corrective action above, re-execute the adbinstall command.

Display of aa....aa

Cause of the error

Corrective action

permission to write to the server directory was denied

An attempt to write to the server directory failed.

Perform the following corrective actions:

Check whether there is sufficient free space in the server directory. If there is not enough free space, allocate enough free space in the server directory.

Also make sure that the HADB administrator has write permission for the following directories. If the HADB administrator does not have write permission, grant write permission for the server directory to the HADB administrator.

permission to write to the client directory was denied

An attempt to write to the client directory failed.

Perform the following corrective actions:

Check whether there is sufficient free space in the client directory. If there is not enough free space, allocate enough free space in the client directory.

Check whether the OS user who manages the HADB client has write permission for the client directory. If the OS user does not have write permission, grant write permission for the client directory to the OS user.

permission to write to the install directory was denied

An attempt to write to the directory used for installation failed.

Perform the following corrective actions:

Check that there is enough free space in the directory used for installation. If there is not enough space, make sure there is enough free space in the directory used for installation.

If this message is displayed when installing the HADB server, check whether the HADB administrator has write permission for the directory used for installation. If the HADB administrator does not have write permission, grant write permission for the directory used for installation to the HADB administrator.

For an example of executing an OS command when granting write permission, see Installing the HADB Server in the HADB Setup and Operation Guide.

If this message is output during installation of the HADB client, check whether the OS user who manages the HADB client has write permission for the directory used for installation. If the HADB administrator does not have write permission, grant write permission for the directory used for installation to the HADB administrator.

For an example of executing an OS command when granting write permission, please refer to Installing an HADB Client in HADB Client for Linux in the HADB Application Development Guide.

a file has the same name as the specified directory or subdirectory

Another file has the same name as the specified directory name.

An existing file has the same name as the directory or subdirectory name specified by the -s or -c option of the adbinstall command. Delete that existing file, and then re-execute the command.

file extraction failed

An attempt to expand the file failed.

Check if you have read permission for the tar.gz format file stored in the directory used for installation. If you do not have read permission, grant read permission for the tar.gz file.

the install file does not exist

The file required for installation is not stored in the directory used for installation.

Or, the name of the file stored in the directory used for installation is incorrect.

If this message is output during installation of the HADB server

Save the tar.gz file contained on the HADB server installation CD-ROM to the directory used for installation (the directory where the adbinstall command is stored).

If this message is output during installation of the HADB client

Save the tar.gz file contained on the HADB client installation CD-ROM to the directory used for installation (the directory that contains the adbinstall command).

an error occurred during execution of a command

An error occurred during execution of a command.

There is an error in the tar.gz format file used during the installation of the HADB server. Or, the prerequisite package for the HADB server is not installed.

This message is output when an error occurs in a HADB command executed as an extension of the adbinstall command (such as the adbls command) and the return code is 127. Perform the following corrective actions. In addition, check the OS error message output immediately before this message.

It is possible that the tar.gz format file corresponding to the OS version you are using has not been copied to the directory used for installation. Check the version of the OS you are using. After checking, copy the tar.gz file in the HADB server installation CD-ROM that corresponds to the OS version you are using to the directory used for installation.

After copying the correct files, continue with the ongoing work.

If this message appears even though you have copied the tar.gz format file corresponding to the OS version you are using, the prerequisite packages for the HADB server may not have been installed. Check if all the prerequisite packages for the HADB server are installed and install any prerequisite packages that are not installed. For details about HADB prerequisite packages, see Checking prerequisite packages in Tasks that must be performed before HADB server installation in the HADB Setup and Operation Guide.

This message is output only when the HADB server is being installed. Note that the message is not output even if the tar.gz file used during the installation of the HADB client is incorrect or if the prerequisite packages are not installed.

some other error occurred during execution of a command

An error other than the above occurred during execution of a command.

This message is output when an error occurs in a HADB command executed as an extension of the adbinstall command (such as the adbls command) and the return code is not 127. Check the error messages that were output immediately before this message was output, and eliminate the cause of the error.

In addition, check the return code output in this message and take appropriate action.

If the return code is 8

This return code is output when the value set for the environment variable LANG is incorrect. Check the value set for the environment variable LANG. In addition, verify whether the locales supported by the HADB server (prerequisite packages glibc-langpack-ja or glibc-langpack-en) are installed. If the prerequisite packages are not installed, install them. For details on how to check installed packages, see Checking prerequisite packages in Tasks that must be performed before HADB server installation in the HADB Setup and Operation Guide.

If the return code is 126

This return code is output when the adbls command cannot be executed. Check the OS message output immediately before this message. If a message indicating "Permission denied" is displayed, restart the installation process from the operation of copying the tar.gz file stored on the installation CD-ROM to the directory where the installation data is stored.

If the return code is other than the above

Check the OS message output immediately before this message.

KFAA91554-Q

The directory specified in the aa option already exists. Do you want to overwrite it? (y/N) (S)

The directory specified in the aa option in the command already exists. Specify whether you want to overwrite it.

aa:

Command option name

S:

Continues processing.

Action:

If you want to overwrite the directory, enter y (or Y); otherwise, enter n (or N).

KFAA91555-I

The user stopped the directory from being overwritten. Command execution was terminated. (S)

The directory overwrite processing was canceled, as requested by the user. The command execution is terminated.

S:

Terminates processing.

KFAA91556-I

The directory was overwritten. (S)

The directory overwrite processing was executed.

S:

Continues processing.

KFAA91557-I

HADB was installed successfully. (S)

The HADB server or the HADB client has been installed successfully.

S:

Continues processing.

KFAA91558-W

The aa....aa command is being executed by a root. (E)

The aa....aa command is being executed by a root.

aa....aa:

Command name

S:

Continues processing.

Action:

The message appears if the aa....aa command is executed by a root.

Follow the instructions indicated in the KFAA91559-Q message that is output after this message.

KFAA91559-Q

Do you want to continue execution of this command? (y/N) (S)

Do you want to continue execution of this command?

S:

Continues processing.

Action:

You attempt to execute the command as a root. Enter n (or N) in response. Once this is done, execute the command as HADB administrator.

Enter y (or Y) only if the root is the same as the HADB administrator.

KFAA91560-I

A user stopped command processing. Execution of the command will now terminate. (S)

Processing is stopped at the request of the user. Execution of the command will now terminate.

S:

Terminates processing.

KFAA91561-I

A user requested command execution. Execution of the command will now continue. (S)

Execution of the command continues at the request of the user.

S:

Continues processing.

KFAA91580-I

Usage: adboptinstall aa....aa [-d] (S)

This message indicates the specification format of the adboptinstall command. This message is displayed when command help is requested or when the command format is invalid.

aa....aa: Option type

s3option: HADB option for AWS

azoption: HADB option for Azure

S:

Terminates processing.

KFAA91581-E

An error occurred while the HADB Option was being installed. (reason = aa....aa, command = bb....bb, return code = cc....cc) (E)

An error occurred while the HADB Option was being installed.

aa....aa:

Cause of the error

bb....bb:

Name of the OS command resulting in an error

cc....cc:

Return code

S:

Terminates processing.

Action:

Take corrective action depending on the cause of the error that was output.

Display of aa....aa

Cause of the error

Corrective action

permission to write to the server directory was denied

An attempt to write to the server directory failed. Or no permissions have been granted.

The following describes the causes of the error and the corrective action to take.

The free space in the server directory is insufficient

Check whether there is sufficient free space in the server directory. If there is not enough free space, allocate enough free space in the server directory.

The HADB administrator has not been granted write, read, or execution permissions for the server directory

Check whether the HADB administrator has been granted write, read, and execution permissions for the server directory (including directories and files under the server directory). If the HADB administrator does not have the necessary permissions, grant the HADB administrator write, read, and execution permissions.

After performing the corrective action above, re-execute the adboptinstall command.

the server directory does not exist

The server directory does not exist.

The following describes the causes of the error and the corrective action to take.

The value of the specified environment variable ADBDIR is invalid.

Check and, if necessary, revise the value of the specified environment variable ADBDIR. If the specified value of the environment variable ADBDIR is invalid, specify the correct value for the environment variable ADBDIR.

The server directory does not exist in the path specified in the environment variable ADBDIR

Check whether the server directory exists in the path specified in the environment variable ADBDIR. If the server directory does not exist in the path specified in the environment variable ADBDIR, specify the correct path in the environment variable ADBDIR.

Incorrect configuration in the server directory or the server directory is corrupt

If this message appears even though the server directory exists in the path specified in the environment variable ADBDIR, the server directory may be corrupt. In this case, back up the server directory and then recreate the server directory using the adbinstall command.

After performing the corrective action above, re-execute the adboptinstall command.

permission to write to the install data storage directory was denied

An attempt to write to the directory used for installation failed. Or no permissions have been granted.

The following describes the causes of the error and the corrective action to take.

The free space in the directory used for installation is insufficient

Check that there is enough free space in the directory used for installation. If there is not enough space, make sure there is enough free space in the directory used for installation.

The HADB administrator has not been granted write, read, or execution permissions for the directory used for installation

Check whether the HADB administrator has been granted write, read, and execution permissions for the directory used for installation (including directories and files under the directory used for installation). If the HADB administrator does not have the necessary permissions, grant the HADB administrator write, read, and execution permissions.

After performing the corrective action above, re-execute the adboptinstall command.

extraction of the install file failed

Failed to expand the tar.gz format file required for installation.

The following describes the causes of the error and the corrective action to take.

The HADB administrator has not been granted read permission for the tar.gz file under the directory used for installation.

Check if the HADB administrator has been granted read permission for the tar.gz file under the directory used for installation. read If the HADB administrator not have the read permission, grant the HADB administrator the read permission.

The hash value of the tar.gz format file under the directory user for installation does not match the hash value file

Check the hash value of the tar.gz format file under the directory user for installation. If the hash value is different from the hash value file of the cloud storage facility (adbhashfile_s3option_sha256.txt for AWS environment or Amazon S3-compatible object storage environment, adbhashfile_azoption_sha256.txt for Azure environment), re-copy the installation data in the installation CD-ROM.

After performing the corrective action above, re-execute the adboptinstall command.

the install file does not exist

The directory used for installation does not contain the tar.gz format file that is required for installation. Or, the file name in tar.gz format is incorrect.

The following describes the causes of the error and the corrective action to take.

The tar.gz format file required for installation is not stored in the directory used for installation.

Copy the tar.gz file from the installation CD-ROM to the directory used for installation.

The tar.gz file name in the directory used for installation does not match the tar.gz file name on the installation CD-ROM.

Copy the tar.gz file from the installation CD-ROM to the directory used for installation.

If you have manually renamed the tar.gz file on the installation CD-ROM after copying it to the directory used for installation, copy the tar.gz file from the installation CD-ROM again.

After performing the corrective action above, re-execute the adboptinstall command.

the HADB server version is invalid

The version of the HADB server is invalid.

The following describes the causes of the error and the corrective action to take.

The version of the HADB server installed does not support the HADB option.

Install the version of the HADB server that supports the HADB Option. For details, see HADB Server Version Upgrade in the HADB Setup and Operation Guide.

After performing the corrective action above, re-execute the adboptinstall command.

an error occurred during execution of a command

An error occurred during the execution of the adboptinstall command.

This message is output when an error occurs in a HADB command executed as an extension of the adboptinstall command.

Check the OS or HADB error message output immediately before this message.

The main causes when an OS error message is output are described below.

The prerequisite packages for the HADB server are not installed.

The server directory is incorrect or corrupted.

The main causes when an HADB error message is output are described below.

The value set for the environment variable LANG is incorrect.

Check the return code output in this message and take appropriate action.

If the return code is 8

This return code is output when the value set for the environment variable LANG is incorrect. Check the value set for the environment variable LANG. In addition, verify whether the locales supported by the HADB server (prerequisite packages glibc-langpack-ja or glibc-langpack-en) are installed. If the prerequisite packages are not installed, install them. For details on how to check installed packages, see Checking prerequisite packages in Tasks that must be performed before HADB server installation in the HADB Setup and Operation Guide.

If the return code is 126

This return code is output when the adbls command cannot be executed. Check the OS message output immediately before this message. If a message indicating "Permission denied" is displayed, the server directory may be corrupted. In this case, after backing up the server directory, re-execute the adbinstall command to perform the HADB server installation.

If the return code is 127

Verify whether the prerequisite packages for the HADB server are installed. If the prerequisite packages are not installed, install them. For details on how to check installed packages, see Checking prerequisite packages in Tasks that must be performed before HADB server installation in the HADB Setup and Operation Guide.

In addition, if the server directory is corrupted, back up the server directory and then re-execute the adbinstall command to perform the HADB server installation.

If the return code is other than the above

Check the OS message output immediately before this message.

After performing the above corrective actions, re-execute the adboptinstall command.

KFAA91582-I

The HADB Option was aa....aa successfully. (S)

Installation or uninstallation of the HADB option is complete.

aa....aa: Processing that was completed

installed: Installed

uninstalled: Uninstalled

S:

Continues processing.

KFAA91583-E

An error occurred while the HADB Option was being uninstalled. (reason = aa....aa, command = bb....bb, return code = cc) (E)

An error occurred while the HADB Option was being installed.

aa....aa:

Cause of the error

bb....bb:

Name of the OS command resulting in an error

cc:

Return code

S:

Terminates processing.

Action:

Take corrective action depending on the cause of the error that was output. After taking corrective action, re-execute the adboptinstall command.

Display of aa....aa

Cause of the error

Corrective action

permission to write to the server directory was denied

An attempt to write to the server directory failed. Or no permissions have been granted.

The following describes the causes of the error and the corrective action to take.

The HADB administrator has not been granted write, read, or execution permissions for the server directory

Check whether the HADB administrator has been granted write, read, and execution permissions for the server directory (including directories and files under the server directory). If the HADB administrator does not have the necessary permissions, grant the HADB administrator write, read, and execution permissions.

the server directory does not exist

The server directory does not exist.

The following describes the causes of the error and the corrective action to take.

The value of the specified environment variable ADBDIR is invalid.

Check and, if necessary, revise the value of the specified environment variable ADBDIR. If the specified value of the environment variable ADBDIR is invalid, specify the correct value for the environment variable ADBDIR.

The server directory does not exist in the path specified in the environment variable ADBDIR

Check whether the server directory exists in the path specified in the environment variable ADBDIR. If the server directory does not exist in the path specified in the environment variable ADBDIR, specify the correct path in the environment variable ADBDIR.

Incorrect configuration in the server directory or the server directory is corrupt

If this message appears even though the server directory exists in the path specified in the environment variable ADBDIR, the server directory may be corrupt. In this case, back up the server directory and then recreate the server directory using the adbinstall command. After recreating the server directory, it is not necessary to re-execute the adboptinstall command.

KFAA91584-W

Some or all of the files targeted for deletion do not exist. (E)

Some or all of the files targeted for deletion do not exist.

S:

Only existing files to be deleted are deleted and processing continues.

KFAA91585-Q

Do you want to aa....aa the bb....bb? (y/N) (S)

For AWS environments, specify whether you want to install or overwrite the AWS SDK for C++ library.

For Azure environments, specify whether you want to install or overwrite the Azure SDK for C++ library.

aa....aa: Processing information

install: Install

perform an overwrite installation of: Overwrite installation

bb....bb: Library type

AWS SDK for C++ library: AWS SDK for C++ library

Azure SDK for C++ library: Azure SDK for C++ library

S:

Continues processing.

Action:

Specify y (or Y); otherwise, specify n (or N).

If y (or Y) is specified and an OS message requesting the root password is output, enter the password as instructed by the OS message. If the root password is entered incorrectly, the installation process will not be executed (the adboptinstall command will result in an error).

If you cannot enter the root password, specify n (or N). In this case, you must manually install the library output in bb....bb.

For instructions on how to manually install the AWS SDK for C++ library, see the Installing AWS SDK for C++ library in Installing HADB Option in the manual HADB Setup and Operation Guide.

For instructions on how to manually install the Azure SDK for C++ library, see the Installing Azure SDK for C++ library in Installing HADB Option in the manual HADB Setup and Operation Guide.

KFAA91586-I

In response to a user request, aa....aa. (S)

For the AWS environment, the AWS SDK for C++ library was installed or overwritten as requested by the user.

For the Azure environment, the Azure SDK for C++ library was installed or overwritten as requested by the user.

aa....aa: Processing information

the AWS SDK for C++ library was installed:

Installation of AWS SDK for C++ library

an overwrite installation of the AWS SDK for C++ library was performed:

Overwrite installation of AWS SDK for C++ library

the Azure SDK for C++ library was installed:

Installation of Azure SDK for C++ library

an overwrite installation of the Azure SDK for C++ library was performed:

Overwrite installation of Azure SDK for C++ library

S:

Continues processing.

KFAA91587-I

In response to a user request, the aa....aa of the bb....bb was stopped. (S)

For AWS environment, installation or overwrite installation of the AWS SDK for C++ library was stopped at the request of the user.

For Azure environments, the installation or overwrite installation of the Azure SDK for C++ library was stopped at the request of the user.

aa....aa: Processing information

installation: Installation

overwrite installation: Overwrite installation

bb....bb: Library type

AWS SDK for C++ library: AWS SDK for C++ library

Azure SDK for C++ library: Azure SDK for C++ library

S:

Continues processing.

KFAA91601-E

An error occurred while processing a node type change on the HADB server. (information = aaaaa) (E+M)

An error occurred during processing to change the node type of the HADB server.

aaaaa:

Message ID

S:

Terminates processing.

Action:

Eliminate the cause of the error based on the error message for node-type change processing that was output to the message log file (the message for the message ID output for information), and then retry the operation.

If a server process was killed before processing to change the node type of the HADB server finished, 00000 might be output for information. In that case, begin execution from HADB server startup.

KFAA91602-I

The HADB server node type was changed to "aa....aa". (S+L+M)

The node type of the HADB server changed to aa....aa.

aa....aa: Node type after the change

PRIMARY: Primary node

S:

Terminates processing.

KFAA91603-E

The node type could not be changed from "aa....aa" to "bb....bb". (E+M)

The HADB server node type cannot be changed from aa....aa to bb....bb.

aa....aa: Current node type

PRIMARY: Primary node

SECONDARY: Secondary node

WORKER: Worker node

SINGLE: System that is not using the multi-node function

bb....bb: Changed node type

PRIMARY: Primary node

SECONDARY: Secondary node

S:

Terminates processing.

Action:

To use the multi-node function when the current node type is SINGLE

Terminate the relevant HADB server first. Next, refer to Migrating to a system that uses the multi-node function in the HADB Setup and Operation Guide and switch the relevant HADB server to a system that uses the multi-node function.

If the current node type is PRIMARY and the changed node type is SECONDARY

The primary node cannot be switched to a secondary node.

If the current node type is WORKER

Worker nodes cannot change the node type.

KFAA91605-W

The adbchgnodetype command does not need to be executed because the HADB node type is already "aa....aa". (E+M)

The node type of the HADB server is already aa....aa, so there is no need to execute the adbchgnodetype command.

aa....aa: Type of node that the adbchgnodetype command attempted to change

PRIMARY: Primary node

SECONDARY: Secondary node

S:

Terminates processing.

KFAA91650-I

Usage: adbmonitor [-n] [-r [-c <retry-count>] [-e]] [-i] (M+S)

Indicates the specification format for the adbmonitor command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA91651-E

This command cannot be executed because adbmonitor has already started. (E+M)

The adbmonitor command cannot be executed because it is already running.

S:

Terminates processing.

Action:

Check the following to determine if your operation is set up to execute multiple instances of the adbmonitor command.

Is the adbmonitor command executed multiple times in the shell used for system operations or in the HA Monitor shell?

Does your setup attempt to execute the adbmonitor command in an environment in which it is already running?

KFAA91652-E

The -e option was specified for the adbmonitor command, but the server definition adb_crypto_dmkey_path was not specified. (E+M)

You have specified the adbmonitor command with the -e option, but have not specified the adb_crypto_dmkey_path operand of the server definition.

S:

Terminates processing.

Action:

If the HADB server being monitored by the adbmonitor command does not use the DB area encryption facility, delete the -e option and execute the adbmonitor command.

KFAA91700-I

Usage: adbchgsqltrc { -d | -e | -s [-y <trace-info>] [-n <trace-info>] [-l <trace-level>] | -y <trace-info> [-n <trace-info>] [-l <trace-level>] | -n <trace-info> [-y <trace-info>] [-l <trace-level>] | -l <trace-level> [-y <trace-info>] [-n <trace-info>] } (M+S)

Indicates the specification format of the adbchgsqltrc command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA91701-I

aa....aa was changed to bb....bb. (S+L+M)

aa....aa was changed to bb....bb.

aa....aa: Information that was changed

The SQL trace: SQL trace information

The output of the access path in the SQL trace: Access path information and access path statistical information

The output of the parameters in the SQL trace: Dynamic parameter information

The SQL trace level: Output level of SQL trace information

bb....bb: Output status or output level after change

ACTIVE: Output

INACTIVE: Not output

CALL: Output for each call

SQL: Output for each SQL statement

S:

Terminates processing.

KFAA91702-E

The adbchgsqltrc command is already executing. (E+M)

The adbchgsqltrc is being executed.

S:

Terminates processing.

Action:

Multiple adbchgsqltrc commands cannot be executed at the same time. Wait for the currently running adbchgsqltrc command to terminate, and then re-execute the adbchgsqltrc command.

KFAA91703-E

An error occurred during processing to change the SQL trace status. (information = aa....aa) (E+M)

An error occurred during processing to change the output status of SQL trace information.

aa....aa:

Message ID

S:

Terminates processing.

Action:

See the error message output to the message log file (the message corresponding to the message ID indicated for information), and eliminate the cause of the error. Then, re-execute the command.

Note that if the server process terminated during command processing due to one of the following causes, aa....aa indicates "00000".

▪ Cause of abnormal termination of the server process

The HADB server terminated by the adbstop command.

The HADB server terminated abnormally.

KFAA91704-E

The adbchgsqltrc command option arguments are invalid. (reason = aa....aa, value = bb....bb) (E+M)

Processing is canceled because an option argument of the adbchgsqltrc command is invalid.

aa....aa: Cause of the error

The trace information of the -y option argument is invalid: Invalid trace information is specified for the -y option.

The trace information of the -n option argument is invalid: Invalid trace information is specified for the -n option.

The same trace information is specified in the -y option and the -n option: The same trace information is specified for the -y option and the -n option.

The trace level of the -l option argument is invalid: An invalid trace level is specified for the -l option.

bb....bb:

Invalid specified value

S:

Terminates processing.

Action:

Correct the specified option argument, and then re-execute the command.

KFAA91750-I

Usage: adbsystoru -s <server-directory> -l <adblang> -o <output-directory> (M+S)

This message indicates how to use the adbsystoru command.

This message is output if the contents of the IT Report Utility collection pattern definition file (!8A9_HADB) are invalid.

S:

Terminates processing.

Action:

Make sure that the server directory path and the character encoding for use with the HADB server are specified correctly in the !8A9_HADB file.

KFAA91800-I

Usage: adbclientdefmang -u <user-name> [-p <password>] {--update | [-i <authorization-identifier-to-be-output>]} (M+S)

Indicates the specification format of the adbclientdefmang command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA91801-I

The client-managing information was successfully updated. (S+L+M)

The client-managing definition information was successfully updated.

S:

Terminates processing.

KFAA91802-E

The adbclientdefmang command is already being executed. (E+M)

The adbclientdefmang is being executed.

S:

Terminates processing.

Action:

Multiple adbclientdefmang commands cannot be executed at the same time. Wait for the running adbclientdefmang command to terminate, and then execute the adbclientdefmang command.

KFAA91803-E

An error occurred during the execution of the adbclientdefmang command. (information = aa....aa) (E+M)

An error occurred during the execution of the adbclientdefmang command.

aa....aa:

Message ID

S:

Terminates processing.

Action:

See the error message output to the message log file (the message corresponding to the message ID indicated by aa....aa), and then eliminate the cause of the error. Then, execute the adbclientdefmang command.

KFAA91850-I

Usage: adbaudittrail -u <user-name> [-p <password>] {--start [--write-error {DOWN | FAILSOFT}] | --stop | --swap [-n <node-number>] | -d [-n <node-number>]} (M+S)

Indicates the specification format of the adbaudittrail command. This message is displayed when command help is requested or if the command format is invalid.

S:

Terminates processing.

KFAA91851-I

The audit trail facility was successfully aa....aa. (S+L+M)

The audit trail facility was successfully aa....aa.

aa....aa:

started: Enabled

terminated: Disabled

S:

Terminates processing.

KFAA91852-I

The audit trail file was successfully swapped. (S+L+M)

The audit trail file was successfully swapped.

S:

Terminates processing.

KFAA91853-E

The adbaudittrail command is already being executed. (E+M)

Because the adbaudittrail command is already running, another adbaudittrail command cannot be executed.

S:

Terminates processing.

Action:

Wait for the running adbaudittrail command to terminate, and then execute another adbaudittrail command.

KFAA91854-E

An error occurred during the execution of the adbaudittrail command. (information = aa....aa) (E+M)

An error occurred during execution of the adbaudittrail command.

aa....aa:

Message ID

S:

Terminates processing.

Action:

See the error message output to the message log file (the message corresponding to the message ID indicated for information), and eliminate the cause of the error. Then, re-execute the command.

KFAA91855-W

The adbaudittrail command does not need to be executed, because the audit trail facility is already aa....aa. (E+M)

The adbaudittrail command does not need to be executed because the audit trail facility is already aa....aa.

aa....aa:

ACTIVE: Enabled

INACTIVE: Disabled

S:

Terminates processing.

KFAA91900-I

Usage: adbconvertaudittrailfile -u <user-name> [-p <password>] --common -d <output-directory> <input-data-path> (M+S)

This message shows the specification format of the command adbconvertaudittrailfile. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA91901-E

The command adbconvertaudittrailfile is already running. (E+M)

The command adbconvertaudittrailfile is being executed.

S:

Terminates processing.

Action:

Only one instance of the command adbconvertaudittrailfile can be executed at a time. Wait for the currently running instance of the command adbconvertaudittrailfile to terminate, and then re-execute the command adbconvertaudittrailfile.

KFAA91902-E

An error occurred while the command adbconvertaudittrailfile was running. (information = aa....aa) (E+M)

An error occurred during execution of the adbconvertaudittrailfile command.

aa....aa:

Message ID

S:

Terminates processing.

Action:

See the error message output to the message log file (the message corresponding to the message ID indicated for information), and eliminate the cause of the error. Then, re-execute the command.

KFAA92000-E

Heap memory is insufficient. (size = aa....aa, information = "bb....bb") (E+M)

A shortage of heap memory occurred.

aa....aa:

Size of memory whose allocation was attempted (bytes)

bb....bb:

Maintenance information

S:

Terminates processing.

Action:

Check for unnecessary processes. If any exist, shut them down or delete them, and then re-execute the command.

If there is still not enough memory after taking step 1, restart the OS, and then re-execute the command.

If there is still not enough memory after taking step 2, increase the kernel parameter specification value (maximum memory that can be used by a process), re-start the OS, and then re-execute the command.

KFAA92001-E

The HADB server refused a request from the adbmodbuff command. (E+M)

The HADB server refused a request from an adbmodbuff command because it had already received a cancel request.

S:

Terminates processing.

Action:

Re-execute the command.

KFAA92002-I

Usage: adbmodbuff <modify-buffer-option-file-name> (M+S)

Indicates the specification format of the adbmodbuff command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA92003-E

An error occurred in the check of the aa....aa path. (reason = "bb....bb", path = "cc....cc") (E+M)

An error occurred when checking the aa....aa path.

aa....aa: File type

option file: An option file

bb....bb: Cause of the error

too long: The path name exceeds its maximum length.

not full path: An absolute path that starts with a slash (/) was not specified.

cc....cc: Path name

If the number of characters exceeds the displayable maximum, an ellipsis (...) is displayed at the end.

S:

Terminates processing.

Action:

Eliminate the cause of the error, and then re-execute the command.

KFAA92004-E

An error occurred in an HADB function. (func = "aa....aa") (E+M)

An error occurred in processing aa....aa.

aa....aa: Process in which error occurred

option file analysis: Analysis of an option file

S:

Terminates processing.

Action:

Check the message log, take the corrective action that is indicated for the error message that was output immediately prior to this message, and then re-try the processing.

KFAA92005-E

No operands to be used to modify the buffer are specified in the modify buffer option file. (E+M)

A required operand is not specified in the buffer-modifying option file.

S:

Terminates processing.

Action:

Specify the following operand in the buffer-modifying option file.

adb_dbbuff_wrktbl_clt_blk_num

KFAA93001-I

Usage: adbsyndict {-m <dictionary-creation-file-path> | -d <dictionary-deletion-file-path> | -s | -n <synonym-dictionary-name> -o <synonym-list-output-file-path> | --clean} (M+S)

Indicates the specification format of the adbsyndict command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA93002-E

The HADB server refused a request from the adbsyndict command. (E+M)

The HADB server refused a request from the adbsyndict command.

S:

Terminates processing.

Action:

Check whether the KFAA51509-I message is output to the message log file.

If the KFAA51509-I message is output, processing on the HADB server has finished normally. No action is needed.

If the KFAA51509-I message is not output, re-execute the adbsyndict command.

KFAA93100-I

Usage: adbcolumnize {--start | --stop | -d} (M+S)

Indicates the specification format of the adbcolumnize command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA93101-I

The updated-row columnizing facility was successfully aa....aa. (S+L+M)

The updated-row columnizing facility was aa....aa.

aa....aa: Status of the updated-row columnizing facility

started: Enabled

terminated: Disabled

S:

Terminates processing.

KFAA93102-E

An error occurred during the execution of the adbcolumnize command. (information = aa....aa) (E+M)

An error occurred during execution of the adbcolumnize command.

aa....aa: Message ID

If the server process terminated during adbcolumnize command processing due to one of the following causes, "00000" is output.

The HADB server terminated by executing the adbstop command.

The HADB server terminated abnormally.

S:

Terminates processing.

Action:

See the error message output to the message log file (the message corresponding to the message ID indicated by aa....aa), and then eliminate the cause of the error. Then, execute the adbcolumnize command.

KFAA93103-W

The adbcolumnize command does not need to be executed, because the updated-row columnizing facility is already aa....aa. (E+M)

The adbcolumnize command does not need to be executed because the updated-row columnizing facility is already aa....aa.

aa....aa: Status of the updated-row columnizing facility

ACTIVE: Enabled

INACTIVE: Disabled

S:

Terminates processing.

KFAA96200-I

Usage: adbinit -u <user-name> [-p <password>] <init-control-file-path> <DB-directory-path> (M+S)

Indicates the specification format of the adbinit command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96201-I

Database initialization started. (M+S)

Database initialization has started.

S:

Continues processing.

KFAA96202-I

Database initialization ended. (return code = a) (M+S)

Database initialization has ended with a return code of a.

a: Return code

0: Normal termination

4: Termination with warning

8: An error occurred

S:

Terminates processing.

Action:

If an error occurred, access the message output to standard error output or the message log, eliminate the cause of the error, and then re-execute initialization of the database (the adbinit command).

KFAA96203-E

Database initialization is canceled because an interruption was detected. (signal = aa) (E+M)

DB area initialization was stopped because an interrupt was detected.

aa:

Signal number

S:

Terminates processing.

Action:

Re-execute the adbinit command.

KFAA96204-I

The DB directory "aa....aa" is bb....bb. (S+L+M)

bb....bb is now being performed on DB directory aa....aa.

aa....aa:

Name of the DB directory

bb....bb: Operation on the DB directory

initialized: Initialization

modified: Modification

S:

Continues processing.

KFAA96205-I

The DB area "aa....aa" bb....bb processing was cc....cc. (M+S)

Processing bb....bb on DB area aa....aa resulted in cc....cc.

aa....aa:

DB area name

bb....bb: Processing on the DB area

add: Adding the DB area

remove: Deleting the DB area

expand: Expanding the DB area

cc....cc: Processing results

committed: Committed

rolled back: Rolled back

S:

Terminates processing.

Action:

If cc....cc is rolled back, re-execute the command.

KFAA96206-I

The DB area "aa....aa" was bb....bb. (M+S)

Processing bb....bb on DB area aa....aa has been completed.

aa....aa:

DB area name

bb....bb: Processing on the DB area

added: Adding the DB area

removed: Deleting the DB area

expanded: Expanding the DB area

S:

Terminates processing.

KFAA96207-I

The number of file creation threads generated is aaaa. (M+S)

aaaa file creation threads were generated.

aaaa:

Number of threads generated

S:

Continues processing.

KFAA96211-E

Memory is insufficient. (size = aa....aa, information = "bb....bb") (E+M)

A heap memory shortage occurred.

aa....aa:

Size of memory you attempted to allocate (bytes)

bb....bb:

Maintenance information

S:

Terminates processing.

Action:

Use the procedure given below to resolve the shortage of memory. Then, re-execute the command.

Check for any unnecessary processes. If there are any unnecessary processes, shut them down.

If there is not enough memory after performing step 1, restart the OS.

If there is not enough memory after performing step 2, change the kernel parameter setting to increase the amount of memory that processes can use. Then, restart the OS.

KFAA96212-E

A system call error occurred. (func = "aa....aa", errno = bbb) (E+M)

An error occurred in system call aa....aa.

aa....aa:

Name of system call in which the error occurred

bbb:

Error number

S:

Terminates processing.

Action:

Check in the OS documentation for the system call name and error number that are displayed, and then eliminate the cause of the error. If you cannot determine the corrective action to take based on the system call name and error number that are displayed, execute an adbinfoget command to collect troubleshooting information, and then contact the customer support center.

KFAA96213-E

An error occurred in the HADB function. (func = "aa....aa") (E+M)

An error occurred during database initialization processing.

aa....aa: Processing details

option file analysis: Control file analysis

system initialize: System initialization

cloud storage manager: Cloud storage management

create system table: Creation of a dictionary table (base table) or a system table (base table)

create system index: Creation of an index for a dictionary table (base table) or a system table (base table)

insert system table: Insertion of data in a dictionary table (base table) or a system tables (base table)

S:

Terminates processing.

Action:

Eliminate the cause of the error as indicated for the error message that was output prior to this message.

KFAA96216-E

Disk capacity is insufficient. (E+M)

There is not enough disk space.

S:

Terminates processing.

Action:

Take one of the actions described below, and then re-execute the command:

Increase the disk space.

If the disk has free space equal to the initialization size, check if the upper limit of the file system or the upper limit of the disk folder has been reached.

Reduce the initial allocation size for the file.

KFAA96217-E

A path is not a regular file or a symbolic link. (name = "aa....aa") (E+M)

The path indicated by aa....aa is neither a regular file path nor a symbolic link path.

aa....aa:

Path name

S:

Terminates processing.

Action:

Check and, if necessary, revise the specified DB area name and the attribute of the path that is displayed as the variable part.

KFAA96218-W

One or more block special files are not used. (name = "aa....aa") (M+S)

One or more block special files are not being used.

aa....aa:

DB area name

S:

Continues processing.

Action:

Carefully review the -i and -v options of the adbinitdbarea of the adbinit command (the adbinitdbarea that defines the DB area displayed in place of aa....aa). The number of data DB area files specified in the -i option differs from the number of block special files specified in the -v option.

KFAA96219-W

An attempt to delete the file "aa....aa" failed. (M+S)

An attempt to delete file aa....aa failed.

aa....aa:

DB area file name (if there is an extension, with the extension)

S:

Continues processing.

Action:

If the file displayed in place of aa....aa is not needed, delete it.

KFAA96220-E

The specified DB directory is root directory. (E+M)

The DB directory specified for the argument of the adbinit command is a root directory. The root directory cannot be used as the DB directory.

S:

Terminates processing.

Action:

Change the DB directory specified for the argument of the adbinit command.

KFAA96221-E

The path length normalized by a symbolic link resolution and so on is not fit into a permitted range. (path before normalization = "aa....aa", normalized path length = bb....bb, permitted range = cc....cc to dd....dd) (E+M)

The length of the path that is normalized by, for example, resolving the symbolic link is not in the allowable range.

aa....aa:

Path name before normalization

bb....bb:

Path length after normalization (bytes)

cc....cc:

Minimum path length after normalization (bytes)

dd....dd:

Maximum path length after normalization (bytes)

S:

Terminates processing.

Action:

Take action such as moving the file storage location for aa....aa to an upper layer so that the length of the absolute path to the aa....aa object is within the range from cc....cc to dd....dd. Then, re-execute the command. You can check the absolute path to the aa....aa object by using the OS's realpath command.

KFAA96222-E

The aa....aa bb....bb operation failed. (name = "cc....cc") (E+M)

The bb....bb processing on the aa....aa has failed.

aa....aa: Target of processing

file: File

directory: Directory

DB area: DB area

bb....bb: Type of processing

create: Creation processing

delete: Deletion processing

open: Open processing

close: Close processing

write: Write processing

readlink: Symbolic link target acquisition processing

initialize: Initialization processing

add: DB area addition processing

remove: DB area deletion processing

expand: DB area expansion processing

cc....cc:

Name of operation target

S:

Terminates processing.

Action:

Eliminate the cause of the error as indicated by the corrective action for the error message output prior to this message, and then re-execute the command.

KFAA96223-E

The aa....aa path is invalid. (reason = "bb....bb", path = "cc....cc") (E+M)

The aa....aa path specified is invalid.

aa....aa: Path type

directory: Directory

file: File

bb....bb: Cause of the error

too long: The path name specified exceeds the maximum length.

not directory: The specified path is not a directory.

not exist: The specified path name does not exist.

system call error: An error occurred in a system call.

duplicate: The path name specification was duplicated.

not block device: The specified path is not a block special file.

cc....cc:

Path name

S:

Terminates processing.

Action:

Correct the specification of the aa....aa path. Then, re-execute the command.

If bb....bb is duplicate, the same path has been specified for both of the files in one of the following file pairs:

Block special files

DB directory or data DB area file storage directory and a server directory

Initialization option file or DB area addition and modification option file, and a DB area file

Data DB area file storage location and a directory under the DB directory

Directory (other than a regular file or a symbolic link) and a data DB area file

For details about the directories under the DB directory, see Directories that are created under adbinit (Initialize the Database) in the manual HADB Command Reference.

KFAA96224-E

The aa....aa option bb....bb value is invalid. (name = "cc....cc") (E+M)

The value specified for bb....bb is invalid in aa....aa.

If bb....bb is an operand in the command format, the number of operands specified exceeds the upper limit.

aa....aa: Location of error

command: Command argument

set: set format operand

Other: Operand in the command format

bb....bb: Invalid specification

DB directory: DB directory name

control file: Initialization option file name or DB area addition and modification option file name

Other: Name of operand or option

cc....cc:

DB area name (An asterisk (*) is displayed if this is not an option of an operand in the command format)

S:

Terminates processing.

Action:

Correct the specified initialization option file or DB area addition and modification option file, and then re-execute the command.

KFAA96225-E

The aa....aa operand cannot be specified more than bb....bb. (E+M)

More than bb....bb aa....aa operands cannot be specified.

aa....aa: Name of the operand that exceeded the maximum number of specifications

adbinitdbarea: adbinitdbarea operand of the initialization option of the adbinit command

adbaddarea: adbaddarea operand of the DB area addition and modification option of the adbmodarea command

adbexpandarea: adbexpandarea operand of the DB area addition and modification option of the adbmodarea command

adbrmarea: adbrmarea operand of the DB area addition and modification option of the adbmodarea command

bb....bb:

Maximum number of aa....aa operands that can be specified + 1

S:

Terminates processing.

Action:

Change the number of specified aa....aa operands to be fewer than bb....bb. Then, re-execute the command.

KFAA96226-E

Another processing now using a database for the DB directory. (E+M)

Another process is using the DB directory specified in the adbinit command.

S:

Terminates processing.

Action:

Check the DB directory specified by the adbinit command. If there is no error in the specified DB directory, carefully review the setup and specifications to make sure that there are no problems that will prevent initialization of that DB directory. If there are no problems, re-execute the adbinit command after the process that is using that DB directory terminates.

KFAA96227-E

The number of aaaa bb....bb exceeds cccc. (E+M)

The number of data DB areas or data DB area files exceeds the maximum value.

aaaa: Type of DB area

data: Data DB area

bb....bb: Resource type

DB areas: DB area

DB area files: DB area file

cccc:

Maximum number of data DB areas or data DB area files

S:

Terminates processing.

Action:

If this message was issued while the adbinit command was executing, reduce the number of data DB areas defined.

If this message was issued while the adbmodarea command was executing (addition of DB areas), delete unneeded DB areas, and then add new DB areas. For details about the corrective action to take, see Steps to take when a data DB area can no longer be added in the HADB Setup and Operation Guide.

If this message was issued while the adbmodarea command was executing (expansion of DB areas), the number of DB area files exceeded the maximum value due to addition of DB area files. For details about the corrective action to take, see Steps to take when a data DB area can no longer be expanded in the HADB Setup and Operation Guide.

If you are using the cloud storage facility, this message will be displayed if the number of times the DB area is expanded exceeds the limit. In that case, add a new data DB area.

For details about the maximum numbers of data DB areas and data DB area files, see Maximum and minimum values related to system configuration in the HADB Setup and Operation Guide.

KFAA96228-E

The size of aa....aa exceeds bb....bb kilobytes. (required = cc....cc KB, max data page = dd....dd KB) (E+M)

The initial allocation size of the DB area file exceeded the upper limit.

aa....aa: Type that exceeded the initially allocated size

file: DB area file

bb....bb:

Upper limit of the file size (KB)

cc....cc:

Requested file size (KB)

dd....dd:

Maximum capacity of a segment (KB)

S:

Terminates processing.

Action:

Change the initial allocation size for DB area files to bb....bb or less, and then re-execute the command.

KFAA96229-E

An error occurred while initializing the DB area buffer pool. (E+M)

An attempt to initialize the global buffer has failed.

S:

Terminates processing.

Action:

Eliminate the cause of the error as indicated for the error message output prior to this message, and then re-execute the processing.

KFAA96230-E

An error was detected in the HADB system. (SQL code = aa....aa) (E+M)

An error occurred in SQLCODE aa....aa. If SQL error messaging has been set up, an SQL error message is output after this message.

aa....aa:

SQLCODE

S:

Terminates processing.

Action:

Access the message of the corresponding SQLCODE, eliminate the cause of the error, and then re-execute the processing.

KFAA96231-E

The aa....aa name is duplicated. (name = "bb....bb") (E+M)

The specification of aa....aa specified in the initialization option adbinitdbarea of the adbinit command has been duplicated.

aa....aa: Type of name that is duplicated

DB area: DB area

bb....bb:

Name that is duplicated

S:

Terminates processing.

Action:

Correct the specification of the bb....bb of adbinitdbarea.

KFAA96232-I

Writing of segments to file "aa....aa" was requested. (total segments whose write requests are complete/total write-scheduled segments = bb....bb/cc....cc) (M+S)

This message reports progress in creating the data DB area file. bb....bb writes have been requested among the cc....cc initially allocated segments of data DB area file aa....aa.

aa....aa:

Name of the data DB area file (if there is an extension, with the extension)

bb....bb:

Cumulative total number of segments for which writes have already been requested for the data DB area file

cc....cc:

Number of initially allocated segments of the data DB area file

S:

Continues processing.

KFAA96233-I

Initialization of file "aa....aa" is complete. (size = bb....bb KB, information = cc....cc) (M+S)

Initialization of data DB area file aa....aa has been completed.

aa....aa:

Name of the data DB area file (if there is an extension, with the extension)

bb....bb:

Size of the initialized area (KB)

cc....cc:

Maintenance information

S:

Continues processing.

KFAA96234-E

The mounted block device "aa....aa" is specified. (E+M)

A mounted block special file aa....aa was specified.

aa....aa:

Specified block special file

S:

Terminates processing.

Action:

Check if the data in this block special file is to be deleted. If the data is to be deleted, unmount the file, and then re-execute the command.

If this message is output while the specified block special file is not mounted, the block special file might have been registered to /etc/mtab by mistake. If this is the case, restore the contents of /etc/mtab using one of the following methods:

Use the umount command to delete an invalid registration.

Change the settings for /etc/fstab, if necessary, and then restart the OS.

KFAA96235-E

The block device "aa....aa" is allocated to the existing DB area file "bb....bb". (E+M)

DB area file bb....bb has already been created in the specified block special file aa....aa.

aa....aa:

Block special file name

bb....bb:

Name of the existing DB area file (if there is an extension, with the extension)

S:

Terminates processing.

Action:

A DB area file to be added must be allocated to an unused block special file. Take one of the following actions:

Change the block special file aa....aa specified in the -v option (specify an unused block special file).

If the DB area created in block special file aa....aa is not needed, delete that DB area.

KFAA96236-E

The adbmodarea command cannot connect to the HADB server because it is connected to an application. (E+M)

The adbmodarea command cannot be executed because an application program or a command is connected to the HADB server.

S:

Terminates processing.

Action:

Wait until the application program or command disconnects from the HADB server, and then re-execute the adbmodarea command.

KFAA96237-E

The DB area "aa....aa" cannot be bb....bb. (reason = "cc....cc") (E+M)

Processing bb....bb cannot be performed on DB area aa....aa.

aa....aa:

DB area name

bb....bb: Processing on the DB area

added: Adding the DB area

removed: Deleting the DB area

expanded: Expanding the DB area

cc....cc: Reason why the processing cannot be performed

exist: Specified DB area name aa....aa already exists.

not exist: Specified DB area name aa....aa does not exist.

unsupported: An attempt was made to perform unsupported processing on DB area aa....aa.

unique: An attempt was made to delete the last data DB area.

resource defined: An attempt was made to delete a DB area in which tables or indexes are stored.

file mixed: The DB area cannot be expanded because the DB area file contains both regular files and block special files.

S:

Terminates processing.

Action:

Check the DB area to be processed, and then re-execute the adbmodarea command.

For details about how to check the tables and indexes stored in DB areas, see Searching a dictionary table in HADB Setup and Operation Guide.

KFAA96238-E

The operand that cannot be specified at the same time as "aa....aa" is specified. (E+M)

The operand specified in the DB area addition and modification option of the adbmodarea command cannot be specified together with aa....aa.

aa....aa:

Name of the operand of the DB area addition and modification option

S:

Terminates processing.

Action:

Correct the operand specified in the DB area addition and modification option, and then re-execute the adbmodarea command.

KFAA96239-E

The command format operand is not specified in the modify control file. (E+M)

A command-format operand is missing in the DB area addition and modification option in the adbmodarea command.

S:

Terminates processing.

Action:

Specify a command-format operand, and then re-execute the adbmodarea command.

KFAA96240-E

The symbolic link "aa....aa" is invalid. (reason = "bb....bb") (E+M)

A symbolic link is invalid.

aa....aa:

DB area file name (if there is an extension, with the extension)

bb....bb: Cause of the error

too long: The path name of the target link exceeds 255 bytes.

mounted: A block special file for the target link is mounted.

duplicate: There is a symbolic link whose target link is duplicated.

S:

Terminates processing.

Action:

A symbolic link might have been modified erroneously. Either correct the symbolic link or restore the symbolic link file from its backup.

KFAA96241-E

The HADB server refused the request from the adbmodarea command. (E+M)

The HADB server refused an execution request from the adbmodarea command.

S:

Terminates processing.

Action:

Re-execute the adbmodarea command.

If the HADB server is in quiescence mode, release the quiescence mode, and then re-execute the adbmodarea command.

KFAA96242-E

You must initialize all DB areas because a DB area that is not allocated to a block special file exists. (E+M)

There is a DB area to which no block special file has been allocated, so you must initialize all DB areas.

S:

Terminates processing.

Action:

Execute the adbinit command. The initialization option is set differently depending on whether DB areas will be initialized.

If not initializing the DB areas

Specify all the initialization options that specify block special files (except for adb_init_wrk_blk_path).

If initializing the DB areas

Change the value specified in the initialization option adb_init_dbarea_initialize.

KFAA96243-I

The option -q for the operand aa....aa specified for the DB area bb....bb will be ignored because this DB area is composed of regular files. (M+S)

The DB area bb....bb is composed of regular files. Therefore, the -q option for the aa....aa operand specified for this DB area is ignored.

aa....aa: Either of the following operand names

Operand name specified for the initialization option of the adbinit command

Operand name specified for the DB area addition and modification option of the adbmodarea command

bb....bb:

DB area name specified for the -n option for aa....aa

S:

Continues processing.

KFAA96244-W

In the DB area file "aa....aa"(bb....bb), any disk space in excess of cc....cc KB is not used. (unused space = dd....dd KB) (E+M)

In the DB area file aa....aa (bb....bb), disk space exceeding cc....cc KB is not used.

aa....aa:

DB area file name (if there is an extension, with the extension)

bb....bb:

Name of the block special file to be allocated to aa....aa

cc....cc:

Size of available disk space (KB)

dd....dd:

Size of disk space that cannot be used (KB)

S:

Continues processing.

Action:

■ If you do not need to use space beyond cc....cc KB

No action is required.

■ If you want to use space beyond cc....cc KB

Take the following corrective actions:

Execute the adbmodarea command to delete the DB area in the DB area file displayed by aa....aa.

Add 4 GB or a greater value to cc....cc KB (or add dd....dd KB if the value of dd....dd is less than 4 GB).

Execute the adbmodarea command to add the DB area again you deleted in step 1. At this time, specify the value obtained in step 2 for the initial allocation size.

However, you cannot use the above procedure if all the following conditions are met:

This message is output during expansion of the DB area.

Necessary data is stored in the DB area to be expanded.

In this case, use the following procedure:

Execute the adbexport command to export data from the DB area.

Delete the expanded DB area by using the adbmodarea command.

Add the DB area again by using the adbmodarea command, and then re-allocate the necessary size.

Execute the adbimport command to import the data you exported in step 1.

Important

To allocate small-capacity and large-capacity block special files to a single DB area, you need to specify a different initial allocation size for each block special file, and then initialize the block special files. For details about the initialization procedure, see the description of the -i option of the adbaddarea operand in Format of DB area addition and modification options in the manual HADB Command Reference.

KFAA96245-I

The HADB system will use up to bb....bb KB of disk space in the block special file "aa....aa". (unused space = cc....cc KB) (M+S)

The HADB server uses a maximum of approximately bb....bb KB of disk space in the block special file aa....aa.

aa....aa:

Block special file name

bb....bb:

Approximate size of space that the HADB server uses (KB)

cc....cc:

Approximate size of space that the HADB server does not use (KB)

S:

Continues processing.

KFAA96246-Q

Block special files for which only part of the disk space might be used are included in the list of block special files to be newly allocated. Are you sure you want to continue processing ? (y/N) (M+S)

The list of block special files to be newly allocated includes block special files for which only part of the disk space might be used. Are you sure you want to continue processing?

S:

Continues or stops processing according to the response.

If processing is stopped, the return code of the command is 0 unless a warning message has been output.

Action:

See the KFAA96245-I message to check the size of space that might not be used. If processing can continue without causing any problem, specify y (or Y). If there is a problem, specify n (or N).

If you stop processing, revise the initial allocation size and the size of the block special file, and then execute the adbmodarea command.

KFAA96247-E

A specification related to DB area encryption is invalid. (error details = "aa....aa.") (E+M)

The specified DB area encryption is invalid.

aa....aa: Cause of the error

The DB area to be encrypted was not specified: The DB area to be encrypted is not specified.

No output path was specified for the HADB encryption key: The path name of the file to which the HADB encryption key is output has not been specified.

S:

Terminates processing.

Action:

Correct the initialization option based on the cause of error displayed in aa....aa. Once this is done, re-execute the command.

If aa....aa is The DB area to be encrypted was not specified

Specify one or more DB areas to encrypt.

If aa....aa is No output path was specified for the HADB encryption key

Specify the path name of the file where the HADB encryption key is output as an absolute path in the adb_init_dmkey_path operand.

KFAA96248-I

An area for the DB area "aa....aa" was created in cloud storage. (area size = bb....bb TB, size of objects = cc....cc KB, object names = "ADBDIRP/dddd/[eeeeeee-fffffff]/*") (M+S)

An area for DB area aa....aa has been created in the cloud storage.

aa....aa:

DB area name

bb....bb:

Size of created area (unit: terabytes)

cc....cc: Size written to the S3 bucket or container (unit: kilobytes)

In addition to the group of S3 objects or BLOBs output in object names, the size of S3 objects or BLOBs with area control number 8388609 or later is included.

dddd:

DB area ID of DB area aa....aa

eeeeeee:

Area control number in DB area aa....aa

fffffff:

Area control number in DB area aa....aa

S:

Continues processing.

Note

object names outputs the identification information of the group of S3 objects or BLOBs created by the HADB server.

Example:

object names = "ADBDIRP/0011/[0000001-0000003]/*"

The object names above indicate multiple S3 objects or BLOBs. The underlined parts refer to the range 0000001 to 0000003, and * refers to wildcards.

In the above example, this means the following S3 objects or BLOBs:

ADBDIRP/0011/0000001/xxxxxx

ADBDIRP/0011/0000002/xxxxxx

ADBDIRP/0011/0000003/xxxxxx

xxxxxx is an arbitrary string.

KFAA96249-I

Creation the DB area "aa....aa" has progressed to bb....bb percent. (M+S)

The progress rate for creating the area for DB area aa....aa is bb....bb percent.

aa....aa:

DB area name

bb....bb:

Progress rate of area creation (unit: %)

S:

Continues processing.

KFAA96250-I

Cloud objects that compose the DB area "aa....aa" will now be created. (object names = "ADBDIRP/bbbb/[ccccccc-ddddddd]/*") (M+S)

Create an S3 object or BLOB to store the data in DB area aa....aa.

aa....aa:

DB area name

bbbb:

DB area ID of DB area aa....aa

ccccccc:

Area control number in DB area aa....aa

ddddddd:

Area control number in DB area aa....aa

S:

Continues processing.

Action:

For details about object names, see the KFAA96248-I message.

KFAA96300-I

Usage: adbmodarea <modify-control-file-path> (M+S)

This message indicates the specification format of the adbmodarea command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96400-I

Usage: adbsql {[-u <user-name> [-p <password>]] [-V] [-d] [-z <client-definition-file-name>] | -u <user-name> -p <password> -s [-b] [-d] [-z <client-definition-file-name>]} (M+S)

This message indicates the specification format of the adbsql command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96401-I

The SQL execution command started. (M)

Processing of the adbsql command is starting.

S:

Continues processing.

KFAA96402-I

The SQL execution command ended. (M)

Processing of the adbsql command is terminating.

S:

Continues processing.

KFAA96403-I

SQL processing completed. (S)

SQL processing has finished.

S:

Continues processing.

KFAA96404-I

aa....aa rows were bb....bb. (S)

Indicates the number of rows to be processed for the executed SQL.

aa....aa: Number of rows to be processed

If the number of rows to be processed overflow, three asterisks (***) are output.

bb....bb: SQL processing

copied: Output processing of retrieval results to a file

deleted: Processing for deleting rows

inserted: Processing for inserting rows

selected: Processing for retrieving rows

updated: Processing for updating rows

S:

Continues processing.

KFAA96405-I

The B-tree index "aa....aa" will be used. (table name="bb....bb"."cc....cc" as "dd....dd") (M+S)

The B-tree index aa....aa of table bb....bb.cc....cc (correlation name dd....dd) will be used. If no correlation name has been specified, *** will be displayed for dd....dd.

aa....aa:

Index identifier

bb....bb:

Schema name

cc....cc:

Table identifier

dd....dd: Correlation name

If no correlation name has been specified, *** is displayed.

S:

Continues processing.

KFAA96406-I

Executing this SQL will create aa....aa work tables. (M+S)

Executing this SQL statement will create aa....aa work tables.

aa....aa:

Number of work tables created

S:

Continues processing.

KFAA96407-I

The table "aa....aa"."bb....bb" as "cc....cc" does not use an index. (M+S)

The index of table aa....aa.bb....bb (correlation name cc....cc) will not be used. If no correlation name has been specified, *** will be displayed for cc....cc.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc:

Correlation name

S:

Continues processing.

KFAA96408-I

The range index "aa....aa" will be used. (table name="bb....bb"."cc....cc" as "dd....dd") (M+S)

The range index aa....aa of table bb....bb.cc....cc (correlation name dd....dd) will be used.

aa....aa:

Index identifier

bb....bb:

Schema name

cc....cc:

Table identifier

dd....dd: Correlation name

If no correlation name has been specified, *** is displayed.

S:

Continues processing.

KFAA96409-I

The B-tree index "aa....aa" will be used by the index specification. (table name="bb....bb"."cc....cc" as "dd....dd") (M+S)

The B-tree index aa....aa will be used for retrieving the table bb....bb.cc....cc (correlation name dd....dd) based on the index specification.

aa....aa:

Index identifier

bb....bb:

Schema name

cc....cc:

Table identifier

dd....dd: Correlation name

If no correlation name has been specified, *** is displayed.

S:

Continues processing.

KFAA96410-I

The table "aa....aa"."bb....bb" as "cc....cc" does not use the B-tree index and text index by the index specification. (M+S)

A B-tree index or text index will not be used for retrieving table aa....aa. bb....bb (correlation name cc....cc) based on the index specification.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc: Correlation name

If no correlation name has been specified, *** is displayed.

S:

Continues processing.

KFAA96411-I

The index specification is disabled. (table name = "aa....aa"."bb....bb" as "cc....cc") (M+S)

The index specification for the table aa....aa.bb....bb (correlation name cc....cc) was ignored.

If a nonexistent index name or an invalid index name was specified in the index specification, that index specification is ignored. Check the index name specified in the index specification.

The following is a possible reason why the index specified in the index specification cannot be used:

If the specified index is a B-tree index

A B-tree index with null-value exclusion specification was specified and the index search range contains a null value.

If the specified index is a text index

The index specified by the index specification cannot be used when HADB cannot use the text index efficiently because, for example, the LIKE predicate that can be evaluated by the text index is not specified.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc: Correlation name

If no correlation name has been specified, *** is displayed.

S:

Continues processing.

KFAA96412-I

The access path was output. (S)

The access path has been output.

S:

Continues processing.

KFAA96413-I

The text index "aa....aa" will be used. (table name="bb....bb"."cc....cc" as "dd....dd") (M+S)

The text index aa....aa of the table bb....bb.cc....cc (correlation name dd....dd) will be used.

aa....aa:

Index identifier

bb....bb:

Schema name

cc....cc:

Table identifier

dd....dd: Correlation name

If no correlation name has been specified, *** is displayed.

S:

Continues processing.

KFAA96414-I

The text index "aa....aa" will be used by the index specification. (table name="bb....bb"."cc....cc" as "dd....dd") (M+S)

The text index aa....aa will be used for search of the table bb....bb.cc....cc (correlation name dd....dd) according to the index specification.

aa....aa:

Index identifier

bb....bb:

Schema name

cc....cc:

Table identifier

dd....dd: Correlation name

If no correlation name has been specified, *** is displayed.

S:

Continues processing.

KFAA96415-I

SQL processing time (aa....aa) : bb....bb sec. (S)

The time required for executing the SQL statement is output.

aa....aa: Performed processing

Fetch: Fetching rows

Execute: Executing the SQL statement

bb....bb: Time required for executing the SQL statement (seconds)

This value is displayed in the following format.

ssssssssssss.pppppp

ssssssssssss: Number of seconds. The valid number of digits is output and left aligned.

pppppp: Fractional seconds

S:

Continues processing.

KFAA96416-I

A character string displaying a null value was changed. (null value character = aa....aa) (S)

A character string that is displayed if the search result is a null value (the character string displaying a null value) is changed.

aa....aa: Information that is changed by #SET NULL of the adbsql subcommand

If neither REPEAT nor DELETE is specified, the specified 'character-string-displaying-a-null-value' is displayed.

If REPEAT is specified, (REP)'character-displaying-a-null-value' is displayed.

If DELETE is specified, the default value of the character string displaying a null value is displayed.

S:

Continues processing.

KFAA96417-W

A warning occurred. (M+S)

A warning occurred.

S:

Continues processing.

Action:

See the message output to the client message log file, and then take the corrective action.

KFAA96451-E

The command options are invalid. command name = adbsql, reason code = aa (S)

The command specification format is invalid. A message that explains the command specification format is output after this message.

aa: Cause of the error

01: A required option argument was not specified.

02: The specified value of an option argument is invalid.

03: An invalid option was specified.

04: The number of option arguments is invalid.

S:

Terminates processing.

Action:

Re-execute the command using the correct specification format.

KFAA96452-E

aa....aa is invalid. (S)

aa....aa is invalid for the adbsql subcommand whose execution with the adbsql command was attempted.

aa....aa: Invalid item

input data: Description of the input data

parameter: Argument of the adbsql subcommand

token: Invalid token

timestamp string literal: The time stamp literal

time string literal: The time literal

date string literal: The date literal

Items other than the above might also be output.

S:

Ignores the specification of this adbsql subcommand.

Action:

Correct the invalid item or the specification of the adbsql subcommand, and then retry the operation.

KFAA96453-E

The adbsql command is incomplete. (S)

The adbsql subcommand whose execution with the adbsql command was attempted terminated before completing execution.

S:

Ignores the specification of this adbsql subcommand.

Action:

Correct the specification of the adbsql subcommand, and then retry the operation.

KFAA96454-E

The length of the aa....aa literal exceeded 64,000 bytes. (S)

A literal that exceeds the upper limit value was specified in the SQL statement whose execution with the adbsql command was attempted.

aa....aa: Type of literal

character string: Character string literal

hexadecimal-format binary: Binary literal in hexadecimal format

S:

Ignores the specification of this SQL statement.

Action:

Correct the SQL specification, and then retry the operation.

KFAA96455-E

The SQL statement cannot be executed. (S)

SQL statements other than SELECT statements cannot be executed.

S:

Ignores this SQL statement.

Action:

Correct the SQL statement, and then retry the operation.

KFAA96457-E

Memory is insufficient. (size = aa....aa) (M+S)

There is not sufficient memory to process the SQL statement or adbsql subcommand whose execution with the adbsql command was attempted.

aa....aa:

Size of memory you attempted to allocate (bytes)

S:

Terminates processing.

Action:

Check memory usage in the OS as a whole. Wait a moment, and then re-execute the SQL statement or adbsql subcommand.

If you cannot re-execute the SQL statement after waiting a moment, use the procedure given below to resolve the memory shortage. Then, re-execute the SQL statement or adbsql subcommand.

Check for any unnecessary processes. If there are any unnecessary processes, shut them down.

If there is not enough memory after performing step 1, restart the OS, and then start the HADB server.

If there is not enough memory after performing step 2, change the kernel parameter setting to increase the amount of memory that processes can use. Restart the OS, and then start the HADB server.

KFAA96458-E

An SQL error occurred. (return code = aa....aa) (M+S)

The HADB server returned an error.

aa....aa:

Return code of the CLI function

S:

Ignores this SQL statement.

Action:

Eliminate the cause of the error as indicated for the other message that was output, and then retry the operation.

KFAA96460-E

The input data is outside the valid range for this column's data type. (S)

The length of the input data is invalid.

S:

Ignores this input data, and then sends out a request for re-entry of data.

Action:

Correct the input data.

KFAA96461-E

The length of an SQL statement exceeds 16,000,000 bytes. (S)

The length of an SQL statement exceeds 16,000,000 bytes.

S:

Ignores this SQL statement.

Action:

Correct the SQL statement, and then retry the operation.

KFAA96463-E

The length of an adbsql control statement exceeds 16,000,000 bytes. (S)

The length of the adbsql subcommand whose execution with the adbsql command was attempted has exceeded 16,000,000 bytes.

S:

Ignores the specification of this adbsql subcommand.

Action:

Correct the specification of the adbsql subcommand, and then retry the operation.

KFAA96464-E

The aa....aa is invalid. (reason = length over) (S)

The length of the specified authorization identifier or password is invalid.

aa....aa: Type of error

authorization_identifier: An authorization identifier error

password: A password error

S:

Terminates processing.

Action:

Correct the authorization identifier or password, and then retry the operation.

KFAA96465-E

The data type of number aa....aa input variable is not compatible. (S)

The specification format of the input aa....aa is invalid. Another possibility is that the length of the input aa....aa is invalid.

aa....aa:

Sequence number of error input parameter (sequence number of the dynamic parameter where the error occurred)

S:

Ignores this input data, and then sends out a request for re-input of data.

Action:

Correct the input data.

KFAA96467-E

Transaction was rolled back. (M+S)

The transaction was rolled back.

S:

Ignores this SQL statement.

Action:

Take corrective action as indicated for the message output immediately prior to this message. If no message was output immediately prior to this message, consult the client message log file.

KFAA96468-E

The adbsql command cannot be specified. (command = "aa....aa", reason = bb....bb) (S)

The adbsql subcommand cannot be executed.

aa....aa:

adbsql subcommand name

bb....bb: Reason

"-s"option: The -s option is specified.

S:

Ignores the specification of this adbsql subcommand, and then issues the input request again.

Action:

Do not specify this adbsql subcommand.

KFAA96469-E

The adbsql command "aa....aa" is used incorrectly. (reason = bb....bb) (S)

The specified adbsql subcommand "aa....aa" is invalid.

aa....aa:

adbsql subcommand name

bb....bb: Reason

null character length error: The length of the character string displaying a null value is invalid.

S:

Ignores the specification of this adbsql subcommand, and then issues the input request again.

Action:

If aa....aa is #SET NULL

Correct the length of the character string displaying a null value, and then re-execute the adbsql subcommand #SET NULL.

KFAA96499-I

aa....aa (S)

The following settings have been changed by the adbsql subcommand specification:

Display of search results in hexadecimal format using #SET DUMPMODE

Display of index information and work table information using #SET OPT REPORT

Output of the SQL statement execution time using #SET EXECTIME REPORT

Output of search results using #SET DISPLAY

aa....aa: Description of the setting change

DUMPMODE changed (a1 -> a2): Setting for the display method for search results in hexadecimal format

a1 is the setting before the change; a2 is the setting after.

OPT REPORT changed (a1 -> a2): Setting for the display method for index information and work table information

a1 is the setting before the change; a2 is the setting after.

EXECTIME REPORT changed (a1 -> a2): Change of the output of the SQL statement execution time

a1 is the setting before the change; a2 is the setting after.

DISPLAY changed (a1 -> a2): Change of the output of search results

a1 is the setting before the change; a2 is the setting after.

S:

Continues processing.

KFAA96600-I

Usage: adbimport -u <user-name> [-p <password>] [-d] [-k {<enclosing-character> | none}] [-s {<deliminator> | tab}] [-g <interval-at-which-progress-message-is-to-be-output>] [-w {<temporary-directory> | <temporary-directory-path-file-name>}] [-z <import-option-file-name>] [-e] [-b] [--status wait] [-m <chunk-comment>] [--force] [-r <column-structure-information-file-name>] [-f {csv | fix}] [--timeout <timeout-period>] <table-name> <input-data-path-file-name> (M+S)

Indicates the specification format of the adbimport command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96603-E

The option argument is invalid. command name = aa....aa, option = bb....bb, reason = cc....cc (E+M)

Processing was stopped because there was an error in the command's option argument.

aa....aa:

Name of the executed command

bb....bb:

Invalid option argument

If there is an option name

The option name is output.

If there is no option name

The arguments to be output in the Usage message of the command are output.

For example, if the Usage message outputs <table-name>, then bb....bb will output table-name.

cc....cc: Reason for the error

invalid length: The length of the option argument is invalid.

invalid value: The value of the option argument is invalid.

invalid combination: The combination of option arguments is invalid.

S:

Terminates processing.

Action:

Correct the specified option argument, and then re-execute the command.

For details about how to specify option arguments, see the description of options for each command in the manual HADB Command Reference.

KFAA96605-E

Memory is insufficient. (size of the insufficient memory = aa....aa, part number = bb....bb, part code = cc....cc) (E+M)

A memory shortage occurred.

aa....aa:

Size of memory you attempted to acquire (bytes)

bb....bb:

Maintenance information 1

cc....cc:

Maintenance information 2

S:

Terminates processing.

Action:

Use the procedure given below to resolve the shortage of memory. Restore the database if necessary, and then re-execute the command. For details about how to restore the database, see the actions to take for abnormal termination of each command in the manual HADB Command Reference.

Check for any unnecessary processes. If there are any unnecessary processes, shut them down. Then, re-execute the command. If there are processes that require large amounts of memory, wait for those processes to end, and then re-execute the command.

If there is not enough memory after performing step 1, restart the OS. After the HADB server has started, re-execute the command.

If there is not enough memory after performing step 2, change the kernel parameter setting to increase the amount of memory that processes can use, and then restart the OS. After the HADB server has started, re-execute the command.

If this message is output, consider the following corrective actions:

Check whether the amount of memory indicated by aa....aa can be allocated to the memory used by the environment in which processing is taking place.

Carefully review the column definitions of the table where the error occurred, and check if the size defined for any of the columns is significantly larger than the maximum size of the data to be stored. If it is, consider reducing the size defined for that column.

KFAA96606-E

The command options are invalid. command name = aa....aa, reason code = bb (E+M)

The command specification format is invalid. If the cause of the error bb is 01, a message that explains the command specification format is output after this message.

aa....aa:

Name of executed command

bb: Cause of the error

01: The specified option or command argument is invalid. Another possibility is that a required command argument is missing.

02: Other errors

S:

Terminates processing.

Action:

Correct the specification of the option, and then re-execute the command.

KFAA96607-E

The specified authorization identifier or password is invalid. (E+M)

The specified authorization identifier or password is invalid.

Possible causes are as follows:

The specified authorization identifier does not exist.

An incorrect password was specified.

The specified authorization identifier does not have the CONNECT privilege.

S:

Terminates processing.

Action:

Specify the correct authorization identifier or password, and then re-execute the command.

KFAA96608-E

The format of the path specified in the aa....aa argument of the bb....bb command is invalid. (reason = "cc....cc") (E+M)

The specification format of the path specified for the option argument of the bb....bb command is invalid.

aa....aa: Invalid option

-f: The specified directory path file name that specifies the storage directory for unload files is invalid.

-w: The specified name of the storage directory for temporary work files is invalid.

-m: The specification of the configuration file for changing chunk statuses in a batch is invalid.

output-destination-encryption-key-file-name: The output destination file name for the HADB encryption key to be created is invalid.

currently-used-encryption-key-file-name: The HADB encryption key file name in use is incorrectly specified.

new-encryption-key-file-name: The specification of the new HADB encryption key file name is invalid.

bb....bb:

Name of the command executed

cc...cc: Cause of the error

invalid path length: The specified path length is invalid.

not full path: The specified path meets one of the following conditions.

- The specified path does not begin with a slash (/).

- The specified path includes /../.

S:

Terminates processing.

Action:

Eliminate the cause of the error, and then re-execute the command.

KFAA96609-E

The aa....aa command timed out. (E+M)

The aa....aa command timed out.

aa....aa:

Command name

S:

Terminates processing.

Action:

If this message is output, check whether the KFAA30955-E message is output immediately after this message.

If the KFAA30955-E message is output, take the corrective action for the KFAA30955-E message.

If the KFAA30955-E message is not output, take the corrective action for the KFAA80204-I message.

KFAA96610-E

An error occurred while processing a command. command name = aa....aa, reason code = bbbb, details code = cc....cc (E+M)

An error occurred during command execution. Stops command processing.

aa....aa:

Name of executed command

bbbb:

Reason code

cc....cc:

Detail code

S:

Terminates processing.

Action:

Take the corrective action indicated for the reason code in the following table.

After taking the corrective action, restore the database, if necessary, and then re-execute the command. For details about how to restore the database, see the actions to take for abnormal termination of each command in the manual HADB Command Reference.

Note that this message might be output if the adbcancel command is executed immediately after the command indicated by aa....aa was executed.

Reason code

Detail code

Definition

Action to take

0001

For negative values

Data communication failed. Another possibility is that a failure occurred on the HADB server.

A problem occurred in an authorization identifier, table specification, or the like.

The detail code is SQLCODE.

Check the message of the corresponding SQLCODE, the console and the message log files.

Determine the cause of the error on the HADB server, and then eliminate it.#

Other than the above

Data communication failed. Another possibility is that a failure occurred on the HADB server.

The detail code is the maintenance information.

Check the console and the message log files. Determine the cause of the error on the HADB server, and then eliminate it.#

0002

For negative values

An error occurred on the HADB server.

The detail code is SQLCODE.

Check the message of the corresponding SQLCODE and the messages output to the message log files. Determine the cause of the error on the HADB server, and then eliminate it.#

Other than the above

An error occurred on the HADB server.

The detail code is the maintenance information.

Check the message log files. Determine the cause of the error on the HADB server, and then eliminate it.#

#

If a message was output immediately before this one, also eliminate the cause of the error described in that message.

KFAA96620-E

An error occurred while processing a command. (SQLCODE = aa....aa) (E+M)

An error occurred during the execution of the command. An SQLCODE is indicated by aa....aa.

aa....aa:

SQLCODE

S:

Terminates processing.

Action:

See the message corresponding to the indicated SQLCODE, and then eliminate the cause of the error. For details about messages corresponding to SQLCODEs, see 1.4 Interpreting SQLCODEs.

KFAA96621-E

An error occurred while processing a command. (E+M)

An error occurred during the execution of the command.

S:

Terminates processing.

Action:

See the error message that has been output to the message log file and eliminate the cause of the error. Once this is done, re-execute the command.

KFAA96700-I

Usage: adbidxrebuild -u <user-name> [-p <password>] [-g <interval-at-which-progress-message-is-to-be-output>] [-w {<temporary-directory> | <temporary-directory-path-file-name>}] [-z <index-rebuild-option-file-name>] [-i <index-identifier-file-name>] [{--create-temp-file | --force}] <table-name> (M+S)

Indicates the specification format of the adbidxrebuild command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96720-I

Usage: {adbdbstatus [-d {summary | used}] [-c {dbarea | table | index | archivechunk}] [-n {<DB-area-name> | <table-name> | <index-name>}] [-t] [-k <enclosing-character>] [-s {<delimiting-character> | tab}] [-S {K | M | G}] [-r <range>] [--shared-lock] [--timeout <timeout-period>] | adbdbstatus -d reorginfo -n <table-name> [-c <analysis-chunk-ID-list>] [-t] [-k <enclosing-character>] [-s {<delimiting-character> | tab}] [-S {K | M | G}] [--timeout <timeout-period>]} (M+S)

Indicates the specification format of the adbdbstatus command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96740-I

Usage: adbexport -u <user-name> [-p <password>] [-k {<enclosing-character> | none}] [-s {<deliminator> | tab}] [-g <interval-at-which-progress-message-is-to-be-output>] [-z <export-option-file-name>] {-q <SQL-statement-file> | -n <table-name> [-c <chunk ID>]} [--compress GZIP] [--with-column-name] <export-file-path> (M+S)

Indicates the specification format of the adbexport command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96760-I

Usage: adbstat [-c {sys | cnct | buf | sql}] [-n {<ap-name> | <global-buffer-name> | <connection-information>}] [-m <statistics-output-range>] [-q <SQL-serial-number>] [-t] [-k <enclosing-character>] [-s {<deliminator> | tab}] (M+S)

Indicates the specification format of the adbstat command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96763-E

The option argument is invalid. command name = adbstat, option = aa, reason = bb....bb (E+M)

An option argument specified for the adbstat command contains an error.

aa:

Option argument containing the error

bb....bb: Cause of the error

length of the option argument is invalid: The length of the option argument is invalid.

setting for the option argument is invalid: The value specified for the option argument is invalid.

option combination is invalid: A combination of options is invalid.

start time is later than the end time: The start time specified is later than the end time.

datetime specification format is invalid: The datetime specification format is invalid.

specified datetime does not exist: The specified datetime does not exist.

S:

Terminates processing.

Action:

Correct the incorrectly specified option.

KFAA96764-I

Processing to analyze the statistics log file aa....aa was skipped because new statistics log data overwrote the data in the file. (E+M)

Processing to analyze the statistics log file aa....aa was skipped because that file was overwritten by newly-output statistics log data.

aa....aa:

Statistics log file name

S:

Continues processing. For statistics log data output to the statistics log file aa....aa, analysis processing has finished up to the statistics log data immediately before the point from which overwrite started.

KFAA96780-I

Usage: adbmergechunk -u <user-name> [-p <password>] [-g <interval-at-which-progress-message-is-to-be-output>] [-w {<temporary-directory> | <temporary-directory-path-file-name>}] [-z <mergechunk-option-file-name>] [-m <chunk-comment>] [--purge-chunk {WAIT | NOWAIT}] [--timeout <timeout-period>] [--concurrency-prior] -c {<merge-the-original-chunk-ID> | ALL} <table-name> (M+S)

Indicates the specification format of the adbmergechunk command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96785-E

A chunk could not be deleted. Delete the chunk by using the PURGE CHUNK statement. (table = "aa....aa"."bb....bb", chunk ID = cc....cc) (E+M)

A chunk in table "aa....aa"."bb....bb" could not be deleted during processing to merge chunks.

The chunk with cc....cc remains as a deletion-pending chunk. If a deletion-pending chunk exists, the adbmergechunk command cannot merge chunks.

aa....aa:

Schema name

bb....bb:

Table identifier

cc....cc:

Chunk ID of the chunk that could not be deleted

S:

Terminates processing.

Action:

Delete the chunk with cc....cc by using the PURGE CHUNK statement.

KFAA96790-I

Usage: adbchgchunkcomment -u <user-name> [-p <password>] {-m <chunk-comment> | -d} [--timeout <timeout-period>] -c <chunk-ID> <table-name> (M+S)

Indicates the specification format of the adbchgchunkcomment command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96800-I

Usage: adbgetcst -u <user-name> [-p <password>] [-t <table-name> ] [-d] [-z <cost-information-collection-option-file-name>] [-g <interval-at-which-progress-message-is-to-be-output>] (M+S)

Indicates the specification format of the adbgetcst command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96820-I

Usage: adbchgchunkstatus -u <user-name> [-p <password>] [--timeout <timeout-period>] [-m <batch-changes-of-chunk-statuses-option-file-name>] [-w <ID-of-chunk-to-be-changed-to-wait-status>] [-n <ID-of-chunk-to-be-changed-to-normal-status>] [<table-name>] (M+S)

Indicates the specification format of the adbchgchunkstatus command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96830-I

Usage: adbarchivechunk -u <user-name> [-p <password>] [-g <interval-at-which-progress-message-is-to-be-output>] [-z <archive-chunk-option-file-name>] [-t] {-c <chunk-ID> | -r <range>} <table-name> (M+S)

Indicates the specification format of the adbarchivechunk command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96840-I

Usage: adbunarchivechunk -u <user-name> [-p <password>] [-g <interval-at-which-progress-message-is-to-be-output>] [-w {<temporary-directory> | <temporary-directory-path-file-name>}] [-z <unarchive-chunk-option-file-name>] [-t] {-c <chunk-ID> | -r <range>} [--force] <table-name> (M+S)

Indicates the specification format of the adbunarchivechunk command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96850-I

Usage: adbreorgsystemdata [-g <interval-at-which-progress-message-is-to-be-output>] [-w <temporary-directory>] [--timeout <timeout-period>] -c table -f <file-that-specifies-the-unload-file-directory> -n <table-name> (M+S)

Indicates the specification format of the adbreorgsystemdata command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96860-I

Usage: adbmkdmk -u <user-name> [-p <password>] <output-destination-encryption-key-file-name> (M+S)

Indicates the specification format of the adbmkdmk command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96870-I

Usage: adbupddmk -u <user-name> [-p <password>] <currently-used-encryption-key-file-name> <new-encryption-key-file-name> (M+S)

Indicates the specification format of the adbupddmk command. This message is displayed when command help is requested or when the command format is invalid.

S:

Terminates processing.

KFAA96871-E

The same file cannot be specified as both the current encryption key file and the new encryption key file. (E+M)

The same file cannot be specified for the HADB encryption key file in use and the new HADB encryption key file.

S:

Terminates processing.

Action:

Check the path name because either the HADB encryption key file in use or the new HADB encryption key file has been incorrectly specified. Once this is done, re-execute the command.

2.8 List of message output locations

The table below lists the message output locations.

In the table, the output level means the message output level that is specified in the ADBSYSLOGLV environment variable. For details, see Suppressing message output to syslog in the HADB Setup and Operation Guide.

Table 2‒1: List of message output locations

Message ID

Message output location

Output level

Standard output

Standard error output

syslog

Message log file

SQLException

ODBC diagnostic information

KFAA30101-E

Y

Y

Y

--

KFAA30102-E

Y

Y

Y

--

KFAA30103-E

Y

Y

Y

--

KFAA30104-E

Y

Y

Y

--

KFAA30105-E

Y

Y

Y

--

KFAA30106-E

Y

Y

Y

--

KFAA30107-E

Y

Y

Y

--

KFAA30112-E

Y

Y

Y

--

KFAA30113-E

Y

Y

Y

--

KFAA30114-E

Y

Y

Y

--

KFAA30117-E

Y

Y

Y

--

KFAA30118-E

Y

Y

Y

--

KFAA30119-E

Y

Y

Y

--

KFAA30120-E

Y

Y

Y

--

KFAA30121-E

Y

Y

Y

--

KFAA30122-E

Y

Y

Y

--

KFAA30123-E

Y

Y

Y

--

KFAA30124-E

Y

Y

Y

--

KFAA30125-E

Y

Y

Y

--

KFAA30126-E

Y

Y

Y

--

KFAA30127-E

Y

Y

Y

--

KFAA30129-E

Y

Y

Y

--

KFAA30131-E

Y

Y

Y

--

KFAA30137-E

Y

Y

Y

--

KFAA30142-E

Y

Y

Y

--

KFAA30144-E

Y

Y

Y

--

KFAA30145-E

Y

Y

Y

--

KFAA30149-E

Y

Y

Y

--

KFAA30154-E

Y

Y

Y

--

KFAA30166-E

Y

Y

Y

--

KFAA30177-E

Y

Y

Y

--

KFAA30183-E

Y

Y

Y

--

KFAA30186-E

Y

Y

Y

--

KFAA30187-E

Y

Y

Y

--

KFAA30188-E

Y

Y

Y

--

KFAA30189-E

Y

Y

Y

--

KFAA30192-E

Y

Y

Y

--

KFAA30194-E

Y

Y

Y

--

KFAA30195-E

Y

Y

Y

--

KFAA30197-E

Y

Y

Y

--

KFAA30201-E

Y

Y

Y

--

KFAA30202-E

Y

Y

Y

--

KFAA30203-E

Y

Y

Y

--

KFAA30204-E

Y

Y

Y

--

KFAA30205-E

Y

Y

Y

--

KFAA30206-E

Y

Y

Y

--

KFAA30208-E

Y

Y

Y

--

KFAA30210-E

Y

Y

Y

--

KFAA30211-E

Y

Y

Y

--

KFAA30213-E

Y

Y

Y

--

KFAA30214-E

Y

Y

Y

--

KFAA30220-E

Y

Y

Y

--

KFAA30229-E

Y

Y

Y

--

KFAA30239-E

Y

Y

Y

--

KFAA30257-E

Y

Y

Y

--

KFAA30264-E

Y

Y

Y

--

KFAA30302-E

Y

Y

Y

--

KFAA30312-E

Y

Y

Y

--

KFAA30318-E

Y

Y

--

KFAA30319-E

Y

Y

--

KFAA30322-E

Y

Y

Y

--

KFAA30323-E

Y

Y

Y

--

KFAA30324-E

Y

Y

Y

--

KFAA30326-E

Y

Y

Y

--

KFAA30361-E

Y

Y

Y

--

KFAA30401-E

Y

Y

Y

--

KFAA30402-E

Y

Y

Y

--

KFAA30403-E

Y

Y

Y

--

KFAA30404-E

Y

Y

Y

--

KFAA30405-E

Y

Y

Y

--

KFAA30406-E

Y

Y

Y

--

KFAA30407-E

Y

Y

Y

--

KFAA30408-E

Y

Y

Y

--

KFAA30410-E

Y

Y

Y

--

KFAA30411-E

Y

Y

Y

--

KFAA30413-E

Y

Y

Y

--

KFAA30414-E

Y

Y

Y

--

KFAA30415-E

Y

Y

Y

--

KFAA30416-E

Y

Y

Y

--

KFAA30417-E

Y

Y

Y

--

KFAA30418-E

Y

Y

Y

--

KFAA30419-E

Y

Y

Y

--

KFAA30420-E

Y

Y

Y

--

KFAA30421-E

Y

Y

Y

--

KFAA30424-E

Y

Y

Y

--

KFAA30425-E

Y

Y

Y

--

KFAA30437-E

Y

Y

Y

--

KFAA30447-E

Y

Y

Y

--

KFAA30448-E

Y

Y

Y

--

KFAA30450-E

Y

Y

Y

--

KFAA30453-E

Y

Y

Y

--

KFAA30454-E

Y

Y

Y

--

KFAA30458-E

Y

Y

Y

--

KFAA30459-E

Y

Y

Y

--

KFAA30460-E

Y

Y

Y

--

KFAA30464-E

Y

Y

Y

--

KFAA30465-E

Y

Y

Y

--

KFAA30467-E

Y

--

KFAA30501-E

Y

Y

Y

--

KFAA30502-E

Y

Y

Y

--

KFAA30505-E

Y

Y

Y

--

KFAA30506-E

Y

Y

Y

--

KFAA30512-E

Y

Y

Y

--

KFAA30547-E

Y

Y

Y

--

KFAA30548-E

Y

Y

Y

--

KFAA30549-E

Y

Y

Y

--

KFAA30550-E

Y

Y

Y

--

KFAA30551-E

Y

Y

Y

--

KFAA30552-E

Y

Y

Y

--

KFAA30555-E

Y

Y

Y

--

KFAA30556-E

Y

Y

Y

--

KFAA30559-E

Y

Y

Y

--

KFAA30560-E

Y

Y

Y

--

KFAA30561-E

Y

Y

Y

--

KFAA30562-E

Y

Y

Y

--

KFAA30563-E

Y

Y

Y

--

KFAA30564-E

Y

Y

Y

--

KFAA30565-E

Y

Y

Y

--

KFAA30566-E

Y

Y

Y

--

KFAA30572-E

Y

Y

Y

--

KFAA30575-E

Y

Y

Y

--

KFAA30577-E

Y

Y

Y

--

KFAA30579-E

Y

Y

Y

--

KFAA30601-E

Y

Y

Y

--

KFAA30602-E

Y

Y

Y

--

KFAA30604-E

Y

Y

Y

--

KFAA30607-E

Y

Y

Y

--

KFAA30609-E

Y

Y

Y

--

KFAA30612-E

Y

Y

Y

--

KFAA30613-E

Y

Y

Y

--

KFAA30614-E

Y

--

KFAA30616-E

Y

Y

Y

--

KFAA30617-E

Y

Y

Y

--

KFAA30619-E

Y

Y

Y

--

KFAA30629-E

Y

Y

Y

--

KFAA30630-E

Y

Y

Y

--

KFAA30632-E

Y

Y

Y

--

KFAA30650-E

Y

Y

Y

--

KFAA30651-E

Y

Y

Y

--

KFAA30652-E

Y

Y

Y

--

KFAA30653-E

Y

Y

Y

--

KFAA30655-E

Y

--

KFAA30656-E

Y

Y

Y

--

KFAA30657-E

Y

Y

Y

--

KFAA30659-E

Y

Y

Y

--

KFAA30661-E

Y

Y

Y

--

KFAA30664-E

Y

Y

Y

--

KFAA30665-E

Y

Y

Y

--

KFAA30667-E

Y

Y

Y

--

KFAA30670-E

Y

Y

Y

--

KFAA30673-E

Y

Y

Y

--

KFAA30677-E

Y

Y

Y

--

KFAA30678-E

Y

Y

Y

--

KFAA30692-E

Y

Y

Y

--

KFAA30695-E

Y

Y

Y

--

KFAA30704-E

Y

Y

Y

--

KFAA30705-E

Y

Y

Y

--

KFAA30706-E

Y

Y

Y

--

KFAA30720-E

Y

Y

Y

--

KFAA30722-E

Y

Y

Y

--

KFAA30723-E

Y

Y

Y

--

KFAA30724-E

Y

Y

Y

Y

--

KFAA30727-E

Y

Y

Y

--

KFAA30732-E

Y

Y

Y

--

KFAA30733-E

Y

Y

Y

--

KFAA30742-E

Y

Y

Y

--

KFAA30743-E

Y

Y

Y

--

KFAA30744-E

Y

Y

Y

--

KFAA30748-E

Y

Y

Y

--

KFAA30752-E

Y

Y

--

KFAA30756-E

Y

Y

Y

--

KFAA30758-E

Y

Y

Y

--

KFAA30798-E

Y

Y

Y

--

KFAA30800-E

Y

Y

Y

--

KFAA30801-E

Y

Y

Y

--

KFAA30802-E

Y

Y

Y

--

KFAA30803-E

Y

Y

Y

--

KFAA30805-E

Y

Y

Y

--

KFAA30808-E

Y

Y

Y

--

KFAA30811-E

Y

Y

Y

--

KFAA30812-E

Y

Y

Y

--

KFAA30821-E

Y

Y

Y

--

KFAA30824-E

Y

Y

--

KFAA30873-E

Y

Y

Y

--

KFAA30879-E

Y

Y

Y

--

KFAA30889-E

Y

Y

Y

--

KFAA30901-E

Y

Y

Y

--

KFAA30913-E

Y

Y

Y

--

KFAA30914-E

Y

Y

Y

--

KFAA30918-E

Y

Y

Y

--

KFAA30919-E

Y

Y

Y

--

KFAA30930-E

Y

Y

Y

--

KFAA30931-E

Y

Y

Y

--

KFAA30932-E

Y

Y

Y

--

KFAA30953-E

Y

Y

Y

--

KFAA30955-E

Y

Y

Y

--

KFAA30959-E

Y

Y

Y

--

KFAA30984-E

Y

Y

Y

--

KFAA30990-E

Y

Y

--

KFAA31120-E

Y

Y

Y

--

KFAA31121-E

Y

Y

Y

--

KFAA31123-E

Y

Y

Y

--

KFAA31124-E

Y

Y

Y

--

KFAA31125-E

Y

Y

Y

--

KFAA31126-E

Y

Y

Y

--

KFAA31127-E

Y

Y

Y

--

KFAA31128-E

Y

Y

Y

--

KFAA31129-E

Y

Y

Y

--

KFAA31131-E

Y

Y

Y

--

KFAA31132-E

Y

Y

Y

--

KFAA31135-E

Y

Y

Y

--

KFAA31137-E

Y

Y

Y

--

KFAA31201-E

Y

Y

Y

--

KFAA31202-E

Y

--

KFAA31203-E

Y

Y

Y

--

KFAA31204-E

Y

Y

Y

--

KFAA31205-E

Y

--

KFAA31206-E

Y

Y

Y

--

KFAA31207-E

Y

Y

Y

--

KFAA31208-E

Y

Y

Y

--

KFAA31209-E

Y

Y

Y

--

KFAA31210-E

Y

Y

Y

--

KFAA31212-E

Y

Y

Y

--

KFAA31213-E

Y

Y

Y

--

KFAA31214-E

Y

Y

Y

--

KFAA31215-E

Y

Y

Y

--

KFAA31216-E

Y

Y

Y

--

KFAA31217-E

Y

Y

Y

--

KFAA31218-E

Y

Y

Y

--

KFAA31219-E

Y

Y

Y

--

KFAA31223-E

Y

Y

Y

--

KFAA31224-E

Y

Y

Y

--

KFAA31226-E

Y

Y

Y

--

KFAA31227-E

Y

Y

Y

--

KFAA31234-E

Y

Y

Y

--

KFAA31235-E

Y

Y

Y

--

KFAA31239-E

Y

Y

Y

--

KFAA31240-E

Y

--

KFAA31241-E

Y

Y

Y

--

KFAA31242-E

Y

Y

Y

--

KFAA31243-E

Y

Y

Y

--

KFAA31245-E

Y

Y

Y

--

KFAA31255-E

Y

Y

Y

--

KFAA31256-E

Y

Y

Y

--

KFAA31257-E

Y

Y

Y

--

KFAA31260-E

Y

Y

Y

--

KFAA31261-E

Y

Y

Y

--

KFAA31262-E

Y

Y

Y

--

KFAA31263-E

Y

Y

Y

--

KFAA31264-E

Y

Y

Y

--

KFAA31265-E

Y

Y

Y

--

KFAA31266-E

Y

Y

Y

--

KFAA31267-E

Y

Y

Y

--

KFAA31268-E

Y

Y

Y

--

KFAA31269-E

Y

Y

Y

--

KFAA31270-E

Y

Y

Y

--

KFAA31271-E

Y

Y

Y

--

KFAA31280-E

Y

--

KFAA31301-E

Y

Y

Y

--

KFAA31306-E

Y

Y

Y

--

KFAA31307-E

Y

Y

Y

--

KFAA31310-E

Y

Y

Y

--

KFAA31371-E

Y

Y

Y

--

KFAA31372-E

Y

Y

Y

--

KFAA31373-E

Y

Y

Y

--

KFAA31375-E

Y

Y

Y

--

KFAA31376-E

Y

Y

Y

--

KFAA31377-E

Y

Y

Y

--

KFAA31378-E

Y

Y

Y

--

KFAA31379-E

Y

Y

Y

--

KFAA31380-E

Y

Y

Y

--

KFAA31405-E

Y

Y

Y

--

KFAA31420-E

Y

Y

Y

--

KFAA31424-E

Y

Y

Y

--

KFAA31425-E

Y

Y

Y

--

KFAA31436-E

Y

Y

Y

--

KFAA31470-E

Y

Y

Y

--

KFAA31471-E

Y

Y

Y

--

KFAA31476-E

Y

Y

Y

--

KFAA31515-E

Y

Y

Y

--

KFAA31524-E

Y

Y

Y

--

KFAA31550-E

Y

Y

Y

--

KFAA31551-E

Y

Y

Y

--

KFAA31552-E

Y

Y

Y

--

KFAA31553-E

Y

Y

Y

--

KFAA31554-E

Y

Y

Y

--

KFAA31555-E

Y

Y

Y

--

KFAA31556-E

Y

Y

Y

--

KFAA31557-E

Y

Y

Y

--

KFAA31558-E

Y

Y

Y

--

KFAA31562-E

Y

Y

Y

--

KFAA31563-E

Y

Y

Y

--

KFAA31564-E

Y

Y

Y

--

KFAA31565-E

Y

Y

Y

--

KFAA31566-E

Y

Y

Y

--

KFAA31600-E

Y

Y

Y

--

KFAA31602-E

Y

Y

Y

--

KFAA31603-E

Y

Y

Y

--

KFAA31648-E

Y

--

KFAA31650-E

Y

Y

Y

--

KFAA31651-E

Y

Y

Y

--

KFAA31652-E

Y

Y

Y

--

KFAA31653-E

Y

Y

Y

--

KFAA31654-E

Y

Y

Y

--

KFAA31655-E

Y

Y

Y

--

KFAA31656-E

Y

--

KFAA31657-E

Y

Y

Y

--

KFAA31658-E

Y

Y

Y

--

KFAA31659-E

Y

Y

Y

--

KFAA31660-E

Y

Y

Y

--

KFAA31661-E

Y

Y

Y

--

KFAA31662-E

Y

Y

Y

--

KFAA31663-E

Y

Y

Y

--

KFAA31664-E

Y

Y

Y

--

KFAA31665-E

Y

Y

Y

--

KFAA31666-E

Y

Y

Y

--

KFAA31667-E

Y

Y

Y

--

KFAA31668-E

Y

Y

Y

--

KFAA31669-E

Y

Y

Y

--

KFAA31670-E

Y

Y

Y

--

KFAA31673-E

Y

Y

Y

--

KFAA31675-E

Y

Y

Y

--

KFAA31678-E

Y

Y

Y

--

KFAA31679-E

Y

Y

Y

--

KFAA31684-E

Y

Y

Y

--

KFAA31685-E

Y

Y

Y

--

KFAA31686-E

Y

Y

Y

--

KFAA31687-E

Y

Y

Y

--

KFAA31688-E

Y

Y

Y

--

KFAA31696-E

Y

Y

Y

--

KFAA31711-E

Y

Y

Y

--

KFAA31713-E

Y

Y

Y

--

KFAA31714-E

Y

Y

Y

--

KFAA31719-E

Y

Y

Y

--

KFAA31727-E

Y

Y

Y

--

KFAA31728-E

Y

--

KFAA31729-E

Y

Y

Y

--

KFAA31730-E

Y

Y

Y

--

KFAA31733-E

Y

Y

Y

--

KFAA31734-E

Y

Y

Y

--

KFAA31735-E

Y

Y

Y

--

KFAA31736-E

Y

Y

Y

--

KFAA31737-E

Y

Y

Y

--

KFAA31738-E

Y

Y

Y

--

KFAA31739-E

Y

Y

Y

--

KFAA31740-E

Y

Y

Y

--

KFAA31741-E

Y

Y

Y

--

KFAA31742-E

Y

Y

Y

--

KFAA31743-E

Y

Y

Y

--

KFAA31744-E

Y

Y

Y

--

KFAA31820-E

Y

Y

Y

--

KFAA31821-E

Y

Y

Y

--

KFAA31822-E

Y

Y

Y

--

KFAA31893-E

Y

Y

--

KFAA31894-E

Y

Y

Y

--

KFAA31895-E

Y

Y

Y

--

KFAA31896-E

Y

--

KFAA31897-E

Y

Y

Y

--

KFAA31898-E

Y

Y

Y

--

KFAA31899-E

Y

Y

Y

--

KFAA32000-I

Y

--

KFAA32100-I

Y

--

KFAA32390-I

Y

--

KFAA34002-E

Y

Y

Y

--

KFAA34003-E

Y

Y

Y

--

KFAA34004-E

Y

Y

Y

--

KFAA34005-E

Y

Y

Y

--

KFAA34006-E

Y

Y

Y

--

KFAA34007-E

Y

--

KFAA34008-E

Y

Y

Y

--

KFAA34009-E

Y

Y

Y

--

KFAA40000-E

Y

--

KFAA40001-E

Y

--

KFAA40002-E

Y

--

KFAA40003-E

Y

--

KFAA40004-E

Y

--

KFAA40005-E

Y

--

KFAA40006-E

Y

--

KFAA40007-E

Y

--

KFAA40008-E

Y

--

KFAA40009-E

Y

--

KFAA40010-E

Y

--

KFAA40011-E

Y

--

KFAA40012-I

Y

--

KFAA40013-E

Y

--

KFAA40014-I

Y

--

KFAA40015-E

Y

--

KFAA40016-E

Y

--

KFAA40017-I

Y

--

KFAA40018-I

Y

--

KFAA40019-I

Y

--

KFAA40020-W

Y

Y

4

KFAA40021-W

Y

Y

4

KFAA40022-W

Y

--

KFAA40023-I

Y

--

KFAA40024-I

Y

--

KFAA40025-W

Y

Y

1

KFAA40026-E

Y

--

KFAA40203-E

Y

--

KFAA40204-E

Y

--

KFAA40205-E

Y

--

KFAA40207-E

Y

--

KFAA40208-E

Y

--

KFAA40212-E

Y

--

KFAA40213-E

Y

--

KFAA40214-E

Y

--

KFAA40215-E

Y

--

KFAA40216-E

Y

--

KFAA40220-E

Y

--

KFAA40289-E

Y

Y

--

KFAA40290-E

Y

Y

--

KFAA40291-W

Y

--

KFAA40292-E

Y

--

KFAA40293-E

Y

--

KFAA41000-W

Y

--

KFAA41001-E

Y

--

KFAA41100-W

Y

--

KFAA41101-W

Y

--

KFAA41103-W

Y

--

KFAA41105-W

Y

--

KFAA41106-W

Y

--

KFAA41200-E

Y

--

KFAA41201-E

Y

--

KFAA41202-E

Y

--

KFAA41205-E

Y

--

KFAA41206-I

Y

--

KFAA41207-E

Y

--

KFAA41208-W

Y

--

KFAA41210-E

Y

--

KFAA41212-I

Y

--

KFAA41213-W

Y

--

KFAA41220-W

Y

--

KFAA41221-I

Y

--

KFAA41222-I

Y

Y

5

KFAA41223-I

Y

--

KFAA41230-W

Y

--

KFAA41235-E

Y

--

KFAA41236-E

Y

--

KFAA41237-E

Y

--

KFAA41238-W

Y

--

KFAA41239-E

Y

--

KFAA41241-E

Y

--

KFAA41600-E

Y

--

KFAA50000-E

Y

--

KFAA50001-E

Y

--

KFAA50002-E

Y

--

KFAA50003-E

Y

--

KFAA50004-E

Y

--

KFAA50005-E

Y

--

KFAA50006-E

Y

--

KFAA50007-E

Y

--

KFAA50008-E

Y

--

KFAA50009-E

Y

--

KFAA50010-E

Y

--

KFAA50011-E

Y

--

KFAA50012-E

Y

--

KFAA50013-E

Y

--

KFAA50014-W

Y

--

KFAA50015-E

Y

--

KFAA50016-E

Y

--

KFAA50017-E

Y

--

KFAA50018-E

Y

--

KFAA50019-E

Y

--

KFAA50020-E

Y

--

KFAA50021-E

Y

--

KFAA50022-E

Y

--

KFAA50023-E

Y

--

KFAA50024-E

Y

--

KFAA50025-E

Y

--

KFAA50026-I

Y

--

KFAA50027-I

Y

--

KFAA50028-E

Y

--

KFAA50029-E

Y

--

KFAA50030-E

Y

--

KFAA50032-E

Y

--

KFAA50033-E

Y

--

KFAA50034-E

Y

--

KFAA50035-E

Y

--

KFAA50036-E

Y

--

KFAA50037-E

Y

--

KFAA50038-E

Y

--

KFAA50039-E

Y

--

KFAA50040-E

Y

--

KFAA50041-E

Y

--

KFAA50042-W

Y

--

KFAA50043-E

Y

--

KFAA50044-I

Y

--

KFAA50045-E

Y

--

KFAA50046-E

Y

--

KFAA50047-E

Y

--

KFAA50048-E

Y

--

KFAA50049-E

Y

--

KFAA50050-I

Y

Y

5

KFAA50051-W

Y

--

KFAA50052-E

Y

--

KFAA50053-E

Y

--

KFAA50054-E

Y

--

KFAA50055-I

Y

--

KFAA50056-I

Y

--

KFAA50057-W

Y

--

KFAA50058-E

Y

--

KFAA50059-E

Y

--

KFAA50060-W

Y

--

KFAA50061-E

Y

--

KFAA50063-I

Y

--

KFAA50064-E

Y

--

KFAA50068-E

Y

--

KFAA50069-I

Y

Y

5

KFAA50070-W

Y

Y

4

KFAA50071-W

Y

Y

4

KFAA50072-E

Y

Y

3

KFAA50073-I

Y

--

KFAA50100-E

Y

--

KFAA50101-I

Y

--

KFAA50102-E

Y

--

KFAA50103-E

Y

--

KFAA50104-E

Y

--

KFAA50105-E

Y

--

KFAA50108-I

Y

Y

Y

2

KFAA50112-E

Y

Y

--

KFAA50116-E

Y

Y

--

KFAA50117-E

Y

Y

--

KFAA50122-E

Y

Y

--

KFAA50123-E

Y

Y

--

KFAA50134-E

Y

Y

--

KFAA50135-E

Y

Y

--

KFAA50140-E

Y

Y

--

KFAA50143-I

Y

--

KFAA50144-E

Y

--

KFAA50150-I

Y

--

KFAA50151-I

Y

--

KFAA50152-I

Y

--

KFAA50153-E

Y

--

KFAA50154-E

Y

--

KFAA50156-E

Y

--

KFAA50157-E

Y

--

KFAA50158-E

Y

--

KFAA50159-W

Y

--

KFAA50160-I

Y

--

KFAA50161-I

Y

--

KFAA50162-E

Y

--

KFAA50163-E

Y

--

KFAA50164-E

Y

--

KFAA50165-E

Y

--

KFAA50166-E

Y

--

KFAA50167-I

Y

--

KFAA50168-I

Y

--

KFAA50169-I

Y

--

KFAA50171-I

Y

--

KFAA50172-W

Y

--

KFAA50201-E

Y

--

KFAA50202-E

Y

--

KFAA50203-E

Y

--

KFAA50204-E

Y

--

KFAA50205-E

Y

Y

--

KFAA50206-E

Y

--

KFAA50207-E

Y

Y

--

KFAA50209-E

Y

--

KFAA50210-E

Y

--

KFAA50211-E

Y

--

KFAA50212-E

Y

--

KFAA50213-E

Y

--

KFAA50214-E

Y

--

KFAA50215-E

Y

--

KFAA50216-E

Y

Y

--

KFAA50217-E

Y

--

KFAA50218-E

Y

--

KFAA50219-E

Y

--

KFAA50220-E

Y

--

KFAA50221-E

Y

--

KFAA50222-E

Y

--

KFAA50223-E

Y

--

KFAA50224-E

Y

--

KFAA50225-E

Y

--

KFAA50226-E

Y

--

KFAA50227-E

Y

--

KFAA50228-E

Y

--

KFAA50229-E

Y

--

KFAA50230-I

Y

--

KFAA50235-E

Y

--

KFAA50236-E

Y

--

KFAA50239-E

Y

Y

--

KFAA50243-E

Y

--

KFAA50244-E

Y

--

KFAA50245-E

Y

--

KFAA50246-E

Y

--

KFAA50247-E

Y

--

KFAA50248-E

Y

--

KFAA50250-E

Y

--

KFAA50251-I

Y

--

KFAA50252-I

Y

--

KFAA50253-I

Y

--

KFAA50254-I

Y

--

KFAA50255-I

Y

--

KFAA50256-I

Y

--

KFAA50260-W

Y

--

KFAA50265-E

Y

--

KFAA50266-E

Y

--

KFAA50267-E

Y

--

KFAA50280-E

Y

--

KFAA50281-E

Y

--

KFAA50282-E

Y

--

KFAA50284-E

Y

--

KFAA50285-E

Y

--

KFAA50286-E

Y

--

KFAA50287-E

Y

--

KFAA50288-E

Y

--

KFAA50289-E

Y

--

KFAA50290-E

Y

--

KFAA50291-W

Y

--

KFAA50292-E

Y

--

KFAA50293-E

Y

--

KFAA50294-E

Y

--

KFAA50295-E

Y

--

KFAA50296-E

Y

--

KFAA50297-E

Y

--

KFAA50298-E

Y

--

KFAA50299-E

Y

--

KFAA50300-E

Y

--

KFAA50301-E

Y

--

KFAA50303-E

Y

--

KFAA50304-E

Y

--

KFAA50305-E

Y

--

KFAA50306-E

Y

--

KFAA50307-E

Y

--

KFAA50308-E

Y

--

KFAA50309-E

Y

--

KFAA50310-E

Y

--

KFAA50311-E

Y

--

KFAA50313-I

Y

--

KFAA51000-I

Y

--

KFAA51001-E

Y

--

KFAA51002-E

Y

--

KFAA51003-I

Y

--

KFAA51005-I

Y

--

KFAA51006-I

Y

--

KFAA51007-E

Y

--

KFAA51008-E

Y

--

KFAA51009-E

Y

--

KFAA51010-W

Y

--

KFAA51011-W

Y

--

KFAA51012-E

Y

--

KFAA51013-E

Y

--

KFAA51014-E

Y

--

KFAA51015-E

Y

--

KFAA51016-E

Y

--

KFAA51017-E

Y

--

KFAA51018-E

Y

--

KFAA51019-E

Y

--

KFAA51111-W

Y

--

KFAA51121-W

Y

--

KFAA51130-W

Y

--

KFAA51200-W

Y

--

KFAA51202-W

Y

--

KFAA51204-W

Y

--

KFAA51210-E

Y

--

KFAA51212-E

Y

--

KFAA51213-E

Y

--

KFAA51214-E

Y

--

KFAA51216-E

Y

--

KFAA51217-E

Y

--

KFAA51218-E

Y

--

KFAA51221-E

Y

--

KFAA51223-E

Y

--

KFAA51224-E

Y

--

KFAA51230-W

Y

--

KFAA51231-W

Y

--

KFAA51232-I

Y

--

KFAA51240-I

Y

--

KFAA51241-I

Y

--

KFAA51242-I

Y

--

KFAA51243-I

Y

--

KFAA51244-I

Y

--

KFAA51245-E

Y

--

KFAA51246-E

Y

--

KFAA51247-I

Y

--

KFAA51253-E

Y

Y

--

KFAA51260-E

Y

--

KFAA51270-E

Y

--

KFAA51271-E

Y

--

KFAA51272-E

Y

--

KFAA51275-I

Y

--

KFAA51276-E

Y

--

KFAA51277-I

Y

--

KFAA51280-W

Y

--

KFAA51281-W

Y

--

KFAA51282-W

Y

--

KFAA51283-E

Y

--

KFAA51284-W

Y

--

KFAA51285-W

Y

--

KFAA51286-W

Y

--

KFAA51287-E

Y

--

KFAA51288-E

Y

--

KFAA51289-E

Y

--

KFAA51290-E

Y

--

KFAA51291-I

Y

--

KFAA51292-E

Y

--

KFAA51293-I

Y

--

KFAA51295-I

Y

--

KFAA51296-I

Y

--

KFAA51300-I

Y

--

KFAA51301-I

Y

--

KFAA51302-E

Y

--

KFAA51303-E

Y

--

KFAA51304-I

Y

--

KFAA51305-E

Y

--

KFAA51306-E

Y

--

KFAA51307-I

Y

--

KFAA51308-E

Y

--

KFAA51309-W

Y

--

KFAA51310-W

Y

--

KFAA51311-I

Y

--

KFAA51312-W

Y

--

KFAA51313-I

Y

--

KFAA51400-E

Y

--

KFAA51401-E

Y

--

KFAA51402-E

Y

--

KFAA51403-E

Y

--

KFAA51404-E

Y

--

KFAA51405-E

Y

--

KFAA51406-E

Y

--

KFAA51407-E

Y

--

KFAA51408-W

Y

--

KFAA51409-I

Y

--

KFAA51410-W

Y

--

KFAA51411-W

Y

--

KFAA51412-W

Y

--

KFAA51413-W

Y

--

KFAA51414-W

Y

--

KFAA51415-E

Y

--

KFAA51416-E

Y

--

KFAA51417-E

Y

--

KFAA51418-I

Y

--

KFAA51419-I

Y

--

KFAA51420-E

Y

--

KFAA51421-E

Y

--

KFAA51422-E

Y

--

KFAA51423-W

Y

--

KFAA51424-E

Y

--

KFAA51425-E

Y

--

KFAA51426-E

Y

--

KFAA51427-E

Y

--

KFAA51428-E

Y

--

KFAA51429-E

Y

--

KFAA51500-E

Y

Y

--

KFAA51501-E

Y

Y

--

KFAA51502-E

Y

Y

--

KFAA51503-E

Y

Y

--

KFAA51504-W

Y

Y

--

KFAA51505-E

Y

Y

--

KFAA51506-I

Y

Y

--

KFAA51507-I

Y

Y

--

KFAA51508-I

Y

Y

--

KFAA51509-I

Y

Y

--

KFAA51510-W

Y

Y

--

KFAA51511-E

Y

Y

--

KFAA51512-E

Y

Y

--

KFAA51513-E

Y

--

KFAA51514-E

Y

Y

--

KFAA51515-I

Y

Y

--

KFAA51516-I

Y

Y

--

KFAA51517-W

Y

Y

--

KFAA51518-W

Y

Y

--

KFAA51519-E

Y

Y

--

KFAA51520-W

Y

Y

--

KFAA51521-W

Y

Y

--

KFAA51522-E

Y

Y

--

KFAA51523-W

Y

Y

--

KFAA51524-W

Y

Y

--

KFAA51525-W

Y

Y

--

KFAA51526-I

Y

Y

--

KFAA51527-I

Y

Y

--

KFAA51528-I

Y

Y

--

KFAA51529-I

Y

Y

--

KFAA51530-E

Y

Y

--

KFAA51531-I

Y

Y

--

KFAA51532-I

Y

Y

--

KFAA51533-I

Y

Y

--

KFAA51534-I

Y

Y

--

KFAA51535-W

Y

Y

--

KFAA51536-E

Y

Y

--

KFAA51537-W

Y

Y

--

KFAA51538-W

Y

Y

--

KFAA51539-E

Y

Y

--

KFAA52000-I

Y

Y

--

KFAA52001-I

Y

--

KFAA52002-I

Y

--

KFAA52005-I

Y

Y

--

KFAA52100-E

Y

Y

--

KFAA52101-E

Y

Y

--

KFAA52110-E

Y

Y

--

KFAA52111-E

Y

Y

--

KFAA52112-E

Y

Y

--

KFAA52113-E

Y

Y

--

KFAA52200-E

Y

--

KFAA52201-W

Y

--

KFAA52202-E

Y

Y

--

KFAA52203-E

Y

Y

--

KFAA52204-I

Y

Y

--

KFAA60001-E

Y

Y

1

KFAA60002-E

Y

Y

1

KFAA60003-E

Y

Y

1

KFAA60004-E

Y

--

KFAA60005-E

Y

Y

1

KFAA60007-E

Y

Y

1

KFAA60008-W

Y

Y

1

KFAA60009-E

Y

Y

1

KFAA60010-W

Y

Y

1

KFAA60012-E

Y

Y

1

KFAA60013-E

Y

Y

1

KFAA60014-W

Y

Y

1

KFAA60100-E

Y

--

KFAA60200-W

Y

Y

--

KFAA60209-E

Y

Y

1

KFAA60284-E

Y

Y

1

KFAA60300-E

Y

Y

1

KFAA60302-E

Y

Y

1

KFAA61200-W

Y

Y

1

KFAA61205-W

Y

Y

1

KFAA61210-E

Y

Y

1

KFAA61211-E

Y

Y

1

KFAA61212-W

Y

Y

1

KFAA61213-W

Y

Y

1

KFAA61214-W

Y

Y

1

KFAA61220-E

Y

Y

1

KFAA61400-W

Y

Y

Y

1

KFAA61600-E

Y

Y

1

KFAA70000-I

Y

--

KFAA70001-I

Y

--

KFAA70002-I

Y

--

KFAA70003-I

Y

--

KFAA70004-I

Y

--

KFAA70005-I

Y

--

KFAA70006-I

Y

--

KFAA70008-E

Y

--

KFAA70009-I

Y

--

KFAA71002-E

Y

--

KFAA71017-E

Y

--

KFAA71202-E

Y

--

KFAA71203-E

Y

--

KFAA71204-E

Y

--

KFAA71206-E

Y

--

KFAA71209-E

Y

--

KFAA71210-E

Y

--

KFAA71211-E

Y

--

KFAA71212-E

Y

--

KFAA71218-E

Y

--

KFAA71222-E

Y

--

KFAA71223-E

Y

--

KFAA71301-E

Y

--

KFAA71446-W

Y

--

KFAA71447-W

Y

--

KFAA71448-E

Y

--

KFAA71449-E

Y

--

KFAA71450-E

Y

--

KFAA71452-E

Y

--

KFAA71453-E

Y

--

KFAA71454-W

Y

--

KFAA71562-E

Y

--

KFAA71563-E

Y

--

KFAA71564-E

Y

--

KFAA71565-E

Y

--

KFAA71566-E

Y

--

KFAA71567-E

Y

--

KFAA71569-E

Y

--

KFAA71570-E

Y

--

KFAA71571-E

Y

--

KFAA71680-E

Y

--

KFAA71681-E

Y

--

KFAA71682-E

Y

--

KFAA71683-E

Y

--

KFAA71687-E

Y

--

KFAA71690-E

Y

--

KFAA71691-E

Y

--

KFAA71692-E

Y

--

KFAA71701-E

Y

--

KFAA71704-E

Y

--

KFAA71705-E

Y

--

KFAA71706-E

Y

--

KFAA71707-E

Y

--

KFAA71708-E

Y

--

KFAA71709-E

Y

--

KFAA71710-E

Y

--

KFAA71711-E

Y

--

KFAA71712-E

Y

--

KFAA71713-E

Y

--

KFAA71714-E

Y

--

KFAA71715-E

Y

--

KFAA71716-E

Y

--

KFAA71717-E

Y

--

KFAA71719-E

Y

--

KFAA71721-E

Y

--

KFAA71722-E

Y

--

KFAA71727-E

Y

--

KFAA71730-E

Y

--

KFAA71731-E

Y

--

KFAA71732-E

Y

--

KFAA71733-E

Y

--

KFAA71735-E

Y

--

KFAA71736-E

Y

--

KFAA71737-E

Y

--

KFAA71740-E

Y

--

KFAA71741-E

Y

--

KFAA71801-E

Y

--

KFAA71903-E

Y

--

KFAA71908-E

Y

--

KFAA72000-E

Y

--

KFAA72001-W

Y

--

KFAA72002-E

Y

--

KFAA72003-E

Y

--

KFAA72004-E

Y

--

KFAA72005-W

Y

--

KFAA72006-E

Y

--

KFAA72007-E

Y

--

KFAA72008-W

Y

--

KFAA72009-E

Y

--

KFAA72099-E

Y

--

KFAA80000-I

Y

Y

2

KFAA80001-I

Y

Y

2

KFAA80002-I

Y

Y

2

KFAA80003-I

Y

Y

2

KFAA80004-I

Y

Y

2

KFAA80005-I

Y

Y

2

KFAA80006-I

Y

Y

2

KFAA80007-I

Y

Y

2

KFAA80008-I

Y

Y

2

KFAA80009-I

Y

Y

2

KFAA80010-I

Y

Y

2

KFAA80011-I

Y

Y

2

KFAA80012-I

Y

Y

2

KFAA80013-I

Y

Y

2

KFAA80014-I

Y

Y

2

KFAA80015-I

Y

Y

2

KFAA80016-I

Y

Y

2

KFAA80017-I

Y

Y

2

KFAA80018-I

Y

Y

2

KFAA80019-I

Y

Y

2

KFAA80020-I

Y

Y

2

KFAA80021-I

Y

Y

2

KFAA80023-I

Y

Y

2

KFAA80024-I

Y

Y

2

KFAA80026-I

Y

Y

2

KFAA80027-I

Y

Y

2

KFAA80028-I

Y

Y

2

KFAA80029-I

Y

Y

2

KFAA80030-I

Y

Y

2

KFAA80031-I

Y

Y

2

KFAA80032-I

Y

Y

2

KFAA80033-I

Y

Y

2

KFAA80034-I

Y

Y

2

KFAA80035-I

Y

Y

2

KFAA80036-I

Y

Y

2

KFAA80037-I

Y

Y

2

KFAA80038-I

Y

Y

2

KFAA80039-I

Y

Y

2

KFAA80040-I

Y

Y

2

KFAA80041-I

Y

Y

2

KFAA80042-I

Y

Y

2

KFAA80043-I

Y

Y

2

KFAA80044-I

Y

Y

2

KFAA80045-I

Y

Y

2

KFAA80046-I

Y

Y

2

KFAA80047-I

Y

Y

2

KFAA80048-I

Y

Y

2

KFAA80049-I

Y

Y

2

KFAA80050-I

Y

Y

2

KFAA80051-I

Y

Y

2

KFAA80052-I

Y

Y

2

KFAA80053-I

Y

Y

2

KFAA80054-I

Y

Y

2

KFAA80055-I

Y

Y

2

KFAA80056-I

Y

Y

2

KFAA80057-I

Y

Y

2

KFAA80058-I

Y

Y

2

KFAA80059-I

Y

Y

2

KFAA80060-I

Y

Y

2

KFAA80061-I

Y

Y

2

KFAA80062-I

Y

Y

2

KFAA80063-I

Y

Y

2

KFAA80064-I

Y

Y

2

KFAA80065-I

Y

Y

2

KFAA80066-I

Y

Y

2

KFAA80067-I

Y

Y

2

KFAA80068-I

Y

Y

2

KFAA80069-I

Y

Y

2

KFAA80070-I

Y

Y

2

KFAA80071-I

Y

Y

2

KFAA80072-I

Y

Y

2

KFAA80073-I

Y

Y

2

KFAA80074-I

Y

Y

2

KFAA80075-I

Y

Y

2

KFAA80076-I

Y

Y

2

KFAA80077-I

Y

Y

2

KFAA80078-I

Y

Y

2

KFAA80079-I

Y

Y

2

KFAA80080-I

Y

Y

2

KFAA80081-I

Y

Y

2

KFAA80082-I

Y

Y

2

KFAA80084-I

Y

Y

2

KFAA80085-I

Y

Y

2

KFAA80086-I

Y

Y

2

KFAA80087-I

Y

Y

2

KFAA80088-I

Y

Y

2

KFAA80089-I

Y

Y

2

KFAA80090-I

Y

Y

2

KFAA80091-I

Y

Y

2

KFAA80092-I

Y

Y

2

KFAA80093-I

Y

Y

2

KFAA80094-I

Y

Y

2

KFAA80095-I

Y

Y

2

KFAA80096-I

Y

Y

2

KFAA80097-I

Y

Y

2

KFAA80099-I

Y

Y

2

KFAA80201-I

Y

Y

Y

2

KFAA80202-I

Y

Y

Y

2

KFAA80203-I

Y

Y

--

KFAA80204-I

Y

Y

Y

2

KFAA80205-I

Y

Y

--

KFAA80206-I

Y

Y

--

KFAA80207-I

Y

Y

--

KFAA80208-I

Y

Y

--

KFAA80209-I

Y

Y

Y

2

KFAA80210-I

Y

Y

--

KFAA80211-I

Y

Y

--

KFAA80212-I

Y

Y

--

KFAA80213-I

Y

--

KFAA80215-I

Y

Y

--

KFAA80216-I

Y

Y

--

KFAA80217-I

Y

Y

--

KFAA80218-I

Y

Y

--

KFAA80219-I

Y

Y

--

KFAA80220-I

Y

Y

--

KFAA80222-I

Y

Y

--

KFAA80223-I

Y

Y

--

KFAA80227-I

Y

Y

--

KFAA80228-I

Y

Y

--

KFAA80229-I

Y

Y

--

KFAA80230-I

Y

Y

--

KFAA80231-I

Y

Y

--

KFAA80232-I

Y

Y

--

KFAA80233-I

Y

Y

--

KFAA80234-I

Y

Y

--

KFAA80235-I

Y

Y

--

KFAA80236-I

Y

Y

--

KFAA80237-I

Y

Y

--

KFAA80240-I

Y

Y

--

KFAA80241-I

Y

Y

--

KFAA80242-I

Y

Y

--

KFAA80243-I

Y

Y

--

KFAA80244-I

Y

Y

--

KFAA80245-I

Y

Y

--

KFAA80246-I

Y

Y

--

KFAA80247-W

Y

Y

--

KFAA80248-I

Y

Y

--

KFAA80249-I

Y

Y

--

KFAA80250-I

Y

Y

--

KFAA80251-I

Y

Y

--

KFAA80252-I

Y

Y

--

KFAA80253-I

Y

Y

--

KFAA80254-I

Y

Y

--

KFAA80255-I

Y

Y

--

KFAA80256-I

Y

Y

--

KFAA80257-I

Y

Y

--

KFAA80258-I

Y

Y

--

KFAA80259-I

Y

Y

--

KFAA80280-I

Y

Y

--

KFAA80281-I

Y

Y

--

KFAA80282-I

Y

Y

--

KFAA80283-I

Y

Y

--

KFAA80284-I

Y

Y

--

KFAA80285-I

Y

Y

--

KFAA80286-I

Y

Y

--

KFAA80287-I

Y

Y

--

KFAA80288-I

Y

Y

--

KFAA80291-I

Y

Y

--

KFAA80292-I

Y

Y

--

KFAA80295-I

Y

--

KFAA80296-I

Y

--

KFAA80297-I

Y

--

KFAA80300-I

Y

Y

2

KFAA80301-I

Y

Y

2

KFAA80500-I

Y

Y

2

KFAA80501-I

Y

Y

2

KFAA81000-I

Y

--

KFAA81001-I

Y

--

KFAA81002-I

Y

--

KFAA81003-I

Y

--

KFAA81004-I

Y

--

KFAA81200-I

Y

Y

6

KFAA81205-I

Y

--

KFAA81206-I

Y

--

KFAA81207-I

Y

--

KFAA81208-I

Y

--

KFAA81209-I

Y

--

KFAA81210-I

Y

--

KFAA81211-I

Y

Y

2

KFAA81214-I

Y

Y

2

KFAA81215-I

Y

Y

2

KFAA81220-I

Y

Y

2

KFAA81221-I

Y

--

KFAA81260-I

Y

Y

6

KFAA81261-I

Y

Y

6

KFAA81262-I

Y

Y

6

KFAA81263-I

Y

Y

6

KFAA81264-I

Y

Y

6

KFAA81265-I

Y

Y

6

KFAA81400-I

Y

--

KFAA81401-I

Y

--

KFAA81402-I

Y

--

KFAA82000-I

Y

--

KFAA82002-I

Y

--

KFAA82003-I

Y

--

KFAA82004-I

Y

--

KFAA90000-I

Y

Y

--

KFAA90001-I

Y

Y

--

KFAA90002-E

Y

Y

--

KFAA90003-E

Y

Y

--

KFAA90004-E

Y

Y

--

KFAA90005-E

Y

Y

--

KFAA90006-E

Y

Y

--

KFAA90008-Q

Y

Y

--

KFAA90009-E

Y

Y

--

KFAA90010-I

Y

--

KFAA90011-I

Y

--

KFAA90012-E

Y

Y

--

KFAA90013-Q

Y

Y

--

KFAA90014-E

Y

Y

--

KFAA90500-E

Y

Y

--

KFAA91000-E

Y

Y

--

KFAA91001-W

Y

Y

--

KFAA91100-I

Y

Y

--

KFAA91101-W

Y

Y

--

KFAA91102-E

Y

Y

--

KFAA91104-Q

Y

Y

--

KFAA91105-I

Y

Y

Y

2

KFAA91107-Q

Y

Y

--

KFAA91108-E

Y

Y

--

KFAA91109-I

Y

Y

--

KFAA91110-I

Y

Y

Y

2

KFAA91111-I

Y

Y

Y

2

KFAA91150-I

Y

Y

--

KFAA91151-W

Y

Y

--

KFAA91152-E

Y

Y

--

KFAA91153-Q

Y

Y

--

KFAA91154-I

Y

Y

Y

2

KFAA91155-I

Y

Y

--

KFAA91250-I

Y

Y

--

KFAA91251-Q

Y

Y

--

KFAA91252-E

Y

Y

--

KFAA91253-I

Y

Y

--

KFAA91254-E

Y

Y

--

KFAA91300-I

Y

Y

--

KFAA91301-E

Y

Y

--

KFAA91350-I

Y

Y

--

KFAA91400-I

Y

--

KFAA91401-I

Y

--

KFAA91402-I

Y

--

KFAA91403-E

Y

--

KFAA91404-I

Y

--

KFAA91405-E

Y

--

KFAA91406-I

Y

--

KFAA91407-I

Y

--

KFAA91408-I

Y

--

KFAA91409-I

Y

--

KFAA91410-I

Y

--

KFAA91411-I

Y

--

KFAA91412-E

Y

--

KFAA91413-I

Y

--

KFAA91414-I

Y

--

KFAA91415-W

Y

--

KFAA91450-I

Y

--

KFAA91451-I

Y

--

KFAA91452-I

Y

--

KFAA91453-E

Y

--

KFAA91500-I

Y

Y

--

KFAA91501-E

Y

Y

--

KFAA91502-I

Y

Y

Y

2

KFAA91503-E

Y

Y

--

KFAA91504-W

Y

Y

--

KFAA91550-I

Y

--

KFAA91551-I

Y

--

KFAA91552-I

Y

--

KFAA91553-E

Y

--

KFAA91554-Q

Y

--

KFAA91555-I

Y

--

KFAA91556-I

Y

--

KFAA91557-I

Y

--

KFAA91558-W

Y

--

KFAA91559-Q

Y

--

KFAA91560-I

Y

--

KFAA91561-I

Y

--

KFAA91580-I

Y

--

KFAA91581-E

Y

--

KFAA91582-I

Y

--

KFAA91583-E

Y

--

KFAA91584-W

Y

--

KFAA91585-Q

Y

--

KFAA91586-I

Y

--

KFAA91587-I

Y

--

KFAA91601-E

Y

Y

--

KFAA91602-I

Y

Y

Y

2

KFAA91603-E

Y

Y

--

KFAA91605-W

Y

Y

--

KFAA91650-I

Y

Y

--

KFAA91651-E

Y

Y

--

KFAA91652-E

Y

Y

--

KFAA91700-I

Y

Y

--

KFAA91701-I

Y

Y

Y

2

KFAA91702-E

Y

Y

--

KFAA91703-E

Y

Y

--

KFAA91704-E

Y

Y

--

KFAA91750-I

Y

Y

--

KFAA91800-I

Y

Y

--

KFAA91801-I

Y

Y

Y

3

KFAA91802-E

Y

Y

--

KFAA91803-E

Y

Y

--

KFAA91850-I

Y

Y

--

KFAA91851-I

Y

Y

Y

2

KFAA91852-I

Y

Y

Y

2

KFAA91853-E

Y

Y

--

KFAA91854-E

Y

Y

--

KFAA91855-W

Y

Y

--

KFAA91900-I

Y

Y

--

KFAA91901-E

Y

Y

--

KFAA91902-E

Y

Y

--

KFAA92000-E

Y

Y

--

KFAA92001-E

Y

Y

--

KFAA92002-I

Y

Y

--

KFAA92003-E

Y

Y

--

KFAA92004-E

Y

Y

--

KFAA92005-E

Y

Y

--

KFAA93001-I

Y

Y

--

KFAA93002-E

Y

Y

--

KFAA93100-I

Y

Y

--

KFAA93101-I

Y

Y

Y

2

KFAA93102-E

Y

Y

--

KFAA93103-W

Y

Y

--

KFAA96200-I

Y

Y

--

KFAA96201-I

Y

Y

--

KFAA96202-I

Y

Y

--

KFAA96203-E

Y

Y

--

KFAA96204-I

Y

Y

Y

2

KFAA96205-I

Y

Y

--

KFAA96206-I

Y

Y

--

KFAA96207-I

Y

Y

--

KFAA96211-E

Y

Y

--

KFAA96212-E

Y

Y

--

KFAA96213-E

Y

Y

--

KFAA96216-E

Y

Y

--

KFAA96217-E

Y

Y

--

KFAA96218-W

Y

Y

--

KFAA96219-W

Y

Y

--

KFAA96220-E

Y

Y

--

KFAA96221-E

Y

Y

--

KFAA96222-E

Y

Y

--

KFAA96223-E

Y

Y

--

KFAA96224-E

Y

Y

--

KFAA96225-E

Y

Y

--

KFAA96226-E

Y

Y

--

KFAA96227-E

Y

Y

--

KFAA96228-E

Y

Y

--

KFAA96229-E

Y

Y

--

KFAA96230-E

Y

Y

--

KFAA96231-E

Y

Y

--

KFAA96232-I

Y

Y

--

KFAA96233-I

Y

Y

--

KFAA96234-E

Y

Y

--

KFAA96235-E

Y

Y

--

KFAA96236-E

Y

Y

--

KFAA96237-E

Y

Y

--

KFAA96238-E

Y

Y

--

KFAA96239-E

Y

Y

--

KFAA96240-E

Y

Y

--

KFAA96241-E

Y

Y

--

KFAA96242-E

Y

Y

--

KFAA96243-I

Y

Y

--

KFAA96244-W

Y

Y

--

KFAA96245-I

Y

Y

--

KFAA96246-Q

Y

Y

--

KFAA96247-E

Y

Y

--

KFAA96248-I

Y

Y

--

KFAA96249-I

Y

Y

--

KFAA96250-I

Y

Y

--

KFAA96300-I

Y

Y

--

KFAA96400-I

Y

Y

--

KFAA96401-I

Y

--

KFAA96402-I

Y

--

KFAA96403-I

Y

--

KFAA96404-I

Y

--

KFAA96405-I

Y

Y

--

KFAA96406-I

Y

Y

--

KFAA96407-I

Y

Y

--

KFAA96408-I

Y

Y

--

KFAA96409-I

Y

Y

--

KFAA96410-I

Y

Y

--

KFAA96411-I

Y

Y

--

KFAA96412-I

Y

--

KFAA96413-I

Y

Y

--

KFAA96414-I

Y

Y

--

KFAA96415-I

Y

--

KFAA96416-I

Y

--

KFAA96417-W

Y

Y

--

KFAA96451-E

Y

--

KFAA96452-E

Y

--

KFAA96453-E

Y

--

KFAA96454-E

Y

--

KFAA96455-E

Y

--

KFAA96457-E

Y

Y

--

KFAA96458-E

Y

Y

--

KFAA96460-E

Y

--

KFAA96461-E

Y

--

KFAA96463-E

Y

--

KFAA96464-E

Y

--

KFAA96465-E

Y

--

KFAA96467-E

Y

Y

--

KFAA96468-E

Y

--

KFAA96469-E

Y

--

KFAA96499-I

Y

--

KFAA96600-I

Y

Y

--

KFAA96603-E

Y

Y

--

KFAA96605-E

Y

Y

--

KFAA96606-E

Y

Y

--

KFAA96607-E

Y

Y

--

KFAA96608-E

Y

Y

--

KFAA96609-E

Y

Y

--

KFAA96610-E

Y

Y

--

KFAA96620-E

Y

Y

--

KFAA96621-E

Y

Y

--

KFAA96700-I

Y

Y

--

KFAA96720-I

Y

Y

--

KFAA96740-I

Y

Y

--

KFAA96760-I

Y

Y

--

KFAA96763-E

Y

Y

--

KFAA96764-I

Y

Y

--

KFAA96780-I

Y

Y

--

KFAA96785-E

Y

Y

--

KFAA96790-I

Y

Y

--

KFAA96800-I

Y

Y

--

KFAA96820-I

Y

Y

--

KFAA96830-I

Y

Y

--

KFAA96840-I

Y

Y

--

KFAA96850-I

Y

Y

--

KFAA96860-I

Y

Y

--

KFAA96870-I

Y

Y

--

KFAA96871-E

Y

Y

--

Legend:

Y: Message output location

-- or blank: Not applicable

3 Output Codes

This chapter describes the abort codes output by HADB.

3.1 Abort codes

The following table lists the abort codes that indicate the reasons why HADB terminated abnormally.

Table 3‒1: List of abort codes

Abort code

Definition

Edd0001

Invalid database detected. Restore the database from a backup. If you cannot determine the cause of the invalid database, execute the command adbinfoget to collect troubleshooting information, and then contact the customer support center.

Eha0001

An internal conflict was found. Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Eharw01

Eharw02

Ehb0001

Ehb0002

Ehb0003

Ehb0004

Ehb0005

Ehb0006

Ehb0007

Ehb0008

Ehb0009

Ehb0010

Ehb0011

Ehc0001

Ehc0002

Ehc0003

Ehc0004

Ehd0001

The database is corrupted. Restore the database from a backup. If you cannot determine the cause of the database corruption, execute the command adbinfoget to collect troubleshooting information, and then contact the customer support center.

If this abort code is output on a secondary node or worker node in a multi-node configuration, it is possible that the DB area file update executed on the primary node is not reflected on the secondary node or worker node. Review the specified values of the server definition regarding the multi-node function and the placement and operation of the DB area file.

Ehd0002

An internal conflict was found. Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Ehd0003

Ehd0004

Ehd0005

The database is corrupted. Restore the database from a backup. If you cannot determine the cause of the database corruption, execute the command adbinfoget to collect troubleshooting information, and then contact the customer support center.

Ehd0006

An internal conflict was found. Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Ehd0007

The database is corrupted. Restore the database from a backup. If you cannot determine the cause of the database corruption, execute the command adbinfoget to collect troubleshooting information, and then contact the customer support center.

Ehd0008

Ehd0010

An internal conflict was found. Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Ehd0013

Ehd0020

The database is corrupted. Restore the database from a backup. If you cannot determine the cause of the database corruption, execute the command adbinfoget to collect troubleshooting information, and then contact the customer support center.

If this abort code is output on a secondary node or worker node in a multi-node configuration, it is possible that the DB area file update executed on the primary node is not reflected on the secondary node or worker node. Review the specified values of the server definition regarding the multi-node function and the placement and operation of the DB area file.

Ehd0021

The database is corrupted. Restore the database from a backup. If you cannot determine the cause of the database corruption, execute the command adbinfoget to collect troubleshooting information, and then contact the customer support center.

Ehd0022

An internal conflict was found. Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Ehf0001

Ehf0002

Ehf0003

Ehf0004

The operation of the cache file or the reuse information file failed. Take corrective action for the error message that was output to the message log file.

Ehf0005

S3 object or BLOB operation failed. Take corrective action for the error message that was output to the message log file.

Ehf0006

An operation on the file failed. Take corrective action for the error message that was output to the message log file.

Ehl0001

An internal conflict was found. Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Ehl0002

Ehl0003

Ehl0004

Ehl0005

Ehm0001

Ehm0003

The database is corrupted. Restore the database from a backup. If you cannot determine the cause of the database corruption, execute the command adbinfoget to collect troubleshooting information, and then contact the customer support center.

Ehm0004

Ehm0005

Ehm0006

Ehm0008

Ehm0010

Ehm0011

An internal conflict was found. Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Ehm0012

Ehm0016

Ehm0017

Ehm0018

Ehm0019

Ehr0001

Ehr0002

Ehr0003

Ehtbf01

Ehtbf02

Ehw0001

Ehw0002

Ehw0003

Ehw0004

Ehw0005

Ehw0006

The requested size could not be written. Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Ehw0007

The database is corrupted. Restore the database from a backup. If you cannot determine the cause of the database corruption, execute the command adbinfoget to collect troubleshooting information, and then contact the customer support center.

Ehw0008

An internal conflict was found. Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Ehw0009

Ehw0010

Ehw0011

Ehx0001

Ehx0002

Ehx0003

Ehx0004

Ehx0005

The database is corrupted. Restore the database from a backup. If you cannot determine the cause of the database corruption, execute the command adbinfoget to collect troubleshooting information, and then contact the customer support center.

Ehx0006

Ehx0007

Ehx0008

An internal conflict was found. Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Ehx0009

Ehx0010

Ehx0011

Ehx0012

The database is corrupted. Restore the database from a backup. If you cannot determine the cause of the database corruption, execute the command adbinfoget to collect troubleshooting information, and then contact the customer support center.

Ehx0013

The requested size could not be written. Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Ehx0014

An internal conflict was found. Execute the adbinfoget command to collect troubleshooting information, and then contact the customer support center.

Ehy0001

Ehy0002

Ehy0003

Ehy0004

Eic01

Eic02

Elc0001

Eli0001

Eli0002

Eqa0001

An attempt to write to the audit trail file failed. Take corrective action for the error message that was output to the message log file.

4 SQLSTATE Values

This chapter explains the SQLSTATE values that HADB outputs.

4.1 SQLSTATE output format

SQLSTATE is one of the return codes HADB returns after executing an SQL statement. An SQLSTATE value consists of five digits, where the first two digits indicate a class and the remaining three digits a subclass.

The following table lists the SQLSTATE classes.

Table 4‒1: List of SQLSTATE classes

Class

Meaning

00

Normal termination

01

Warning

02

No data satisfies the retrieval condition.

07

Dynamic SQL statement errors

08

HADB server connection errors

21

Cardinality violation

22

Data exception

23

Integrity constraint violation

24

Cursor status errors

40

Errors resulting in transaction rollback

42

Syntax errors or access rule violation

51

SQL function-specific errors (errors caused by specific nonstandard SQL functions)

52

Errors due to an execution environment status that prohibits SQL statement execution

53

Errors due to a system resource status that prohibits SQL statement execution (such as a memory or resource shortage)

54

Error caused by application program settings, processing, attributes, or statuses

56

Limit- or value-related errors

5B

User-requested cancellation

5C

Other system errors

5D

SQLSTATE cannot be obtained.

R2

JDBC driver-related errors

4.2 List of SQLSTATE values

The table below lists the SQLSTATE values that HADB outputs.

If an SQLSTATE value is returned, check the message provided in the Corresponding message column in the following table, and then take the appropriate action.

Table 4‒2: List of SQLSTATE values

SQLSTATE value

Summary of the contents

Corresponding message

00000

SQL statement execution has finished.

KFAA32000-I

The node in which to execute SQL statements is changed.

KFAA32390-I

01004

Data was truncated in data type conversion processing performed by the ODBC driver.

KFAA72005-W

01601

Processing of the SQL statement might require a long time because the SQL statement accesses data in all archived chunks.

KFAA51121-W

01J11

The result set type was changed because the result set type that allows scrolling with updated content is not supported.

KFAA71446-W

01J12

The concurrent processing type was changed for the result set, because updatable result sets are not supported.

KFAA71447-W

01J13

Because CLOSE_CURSORS_AT_COMMIT cannot be specified in the result set holdability, the result set holdability has been changed.

KFAA71454-W

01S07

Data was truncated in data type conversion processing performed by the ODBC driver.

KFAA72005-W

01S51

Characters that could not be converted during character encoding conversion were replaced with hash marks (#).

KFAA72001-W

02000

No rows match the conditions. Another possibility is that row fetching has terminated.

KFAA32100-I

07003

Queries cannot be executed with the CLI function a_rdb_SQLExecDirect(), which performs preprocessing and execution of SQL statements.

KFAA30506-E

07005

SQL statements other than queries whose SQL statement is preprocessed cannot be executed.

KFAA30512-E

07006

An error occurred in data type conversion version processing performed by the ODBC driver.

KFAA72004-E

KFAA72006-E

08002

A connection to the HADB server has already been established. Connection processing cannot be re-executed while there is a connection to the HADB server.

KFAA30752-E

08004

The HADB server is not running.

KFAA30723-E

08605

The character encoding of the HADB server and that of the HADB client do not match.

KFAA30990-E

08607

The sort order of the character string data is incorrect.

KFAA31897-E

08608

A command is running that cannot be executed concurrently with another command or application.

KFAA31898-E

08609

The CONNECT statement cannot be executed because the HADB server operation mode is in offline mode.

0860A

The CONNECT statement cannot be executed because a direct connection to a secondary node is being established.

KFAA31898-E

The CONNECT statement cannot be executed because a direct connection to a worker node is being established.

0860B

The CONNECT statement cannot be executed because an attempt to establish a connection to an HADB server-dedicated communication port is in progress.

KFAA31898-E

0860C

The HADB client cannot connect to the HADB server because the versions of the HADB client and HADB server are different.

KFAA30984-E

0860D

A connection to the HADB server cannot be established because the client or command belongs to a client group or command group whose maximum number of concurrent connections is zero.

KFAA31898-E

0860E

The CONNECT statement cannot be executed because the HADB server operation mode is maintenance mode.

08620

No more connections can be established to the HADB server because the number of connections has reached the maximum for simultaneous connections.

KFAA30932-E

08622

The sort order of the character string data is incorrect.

KFAA31897-E

08623

The CONNECT statement cannot be executed because the HADB client execution environment is invalid.

KFAA31898-E

08625

An attempt to load the public key file failed.

KFAA31899-E

21502

A cardinality violation occurred.

KFAA30450-E

22001

The input data length is invalid (the input data is longer than the column).

KFAA30404-E

The character string returned by scalar function TRANSLATE exceeded the permitted data length for execution results.

KFAA30421-E

The specified scalar function is invalid.

KFAA30453-E

KFAA31373-E

The processing of the LISTAGG set function exceeded the maximum length of the LISTAGG result character string in the data length of the aggregated data.

KFAA30802-E

An error occurred during string concatenation. The result of the scalar function CONCAT or the concatenation operation exceeded the maximum data length of the result.

KFAA31380-E

An error occurred while executing a scalar function.

KFAA31476-E

An error occurred in data type conversion version processing performed by the ODBC driver.

KFAA72006-E

22003

The input data falls outside of the range of values for the column's data type.

KFAA30302-E

The input data for a dynamic parameter is invalid.

KFAA30326-E

An error occurred while executing a scalar function.

KFAA30421-E

KFAA31476-E

The specified scalar function is invalid.

KFAA30453-E

KFAA31373-E

An overflow occurred in a numeric data operation.

KFAA30801-E

An overflow occurred while a set function or a window function was executing.

KFAA30802-E

The value range for a set function argument is invalid.

KFAA31375-E

An error occurred in data type conversion version processing performed by the ODBC driver.

KFAA72004-E

KFAA72006-E

22007

The input data for a dynamic parameter is invalid.

KFAA30326-E

An error occurred in data type conversion version processing performed by the ODBC driver.

KFAA72004-E

KFAA72006-E

22008

An overflow error occurred in datetime data.

KFAA30421-E

KFAA30801-E

KFAA31476-E

An error occurred in data type conversion version processing performed by the ODBC driver.

KFAA72006-E

22012

A division by zero error occurred while a scalar function was executing.

KFAA30421-E

KFAA31476-E

A division by zero error occurred during an arithmetic operation.

KFAA30800-E

22013

A value specified in the window frame value specification for a window frame border is invalid.

KFAA31301-E

22018

The specified scalar function is invalid.

KFAA30453-E

KFAA31373-E

An error occurred while executing a scalar function.

KFAA31476-E

An error occurred in data type conversion version processing performed by the ODBC driver.

KFAA72004-E

KFAA72006-E

22019

The data length of the value expression specified for the escape character is invalid.

KFAA30424-E

2201E

An error occurred while executing a scalar function.

KFAA30421-E

An out-of-range value was specified in the LN scalar function.

KFAA31476-E

2201F

An error occurred while executing a scalar function.

KFAA30421-E

An out-of-range value was specified in the POWER or SQRT scalar function.

KFAA31476-E

2202F

During processing of the ARRAY_AGG set function, the number of target data exceeded the maximum number of elements in an array-type column of 30,000.

KFAA30802-E

22505

The input data for a dynamic parameter is invalid.

KFAA30326-E

2250A

The data content of the value expression specified for the escape character is invalid.

KFAA30424-E

2250G

A character string representation used in the scalar function does not match the format specification.

KFAA30361-E

The format specification in a scalar function is invalid.

KFAA31213-E

A required element is missing from the format specification of the scalar function.

KFAA31214-E

2250H

An error occurred while executing a scalar function.

KFAA30421-E

An out-of-range value was specified in a scalar function.

KFAA31476-E

2250I

The data lengths of the arguments specified in the scalar function are different.

KFAA31217-E

22510

The value specified for row-count or offset in the LIMIT clause is invalid.

KFAA31301-E

22521

The indicator value of the input data for a dynamic parameter is invalid.

KFAA30326-E

22522

The specification format of a scalar function is invalid.

KFAA31373-E

22523

An error occurred during check of the path name of the file that will be the input data of the system-defined function.

KFAA31734-E

22524

22525

The data format of the file that will be the input data of the system-defined function is invalid.

KFAA31735-E

22527

An error occurred in the file that will be the input data of the ADB_CSVREAD function.

KFAA31736-E

22528

22529

2252A

An error occurred during check of the path name of the file that will be the input data of the system-defined function.

KFAA31734-E

2252B

2252C

2252D

An error was detected when accessing the Iceberg catalog. No resource corresponding to the search target was found.

KFAA31822-E

2252E

An unsupported file format is included in the Iceberg table.

KFAA31821-E

23503

An attempt was made to set a null value in a column for which null values cannot be set.

KFAA30210-E

23504

An attempt was made to update or add data that would have resulted in key values of a unique index being duplicated.

KFAA30803-E

24504

The cursor has not been opened.

KFAA30501-E

24505

An attempt was made to open a cursor that is already open.

KFAA30502-E

24506

Preprocessing was requested for a query that has a cursor open.

KFAA30505-E

24511

The cursor has not been closed.

KFAA31515-E

24512

There is a dynamic parameter for which no value is set.

KFAA31307-E

24513

An error has already occurred in the opened cursor.

KFAA31310-E

25006

The SQL statement could not be executed because the transaction access mode is read-only.

KFAA31524-E

28501

The specified password violates the password specification rules.

KFAA30560-E

28502

The specified authorization identifier or password is invalid.

KFAA30561-E

28503

User authorization failed.

KFAA31688-E

40503

No more pages can be created because the DB area file cannot be expanded.

KFAA30756-E

40508

An attempt was made to access an index that was in unfinished status.

KFAA30879-E

4050D

An attempt was made to access a table that is in non-updateable status due to a suspended command.

KFAA30889-E

4050G

An error occurred during lock processing.

KFAA30913-E

4050P

Processing to reserve a lock timed out.

KFAA30914-E

4050Q

An attempt was made to update or delete a row that is being updated or deleted by another transaction.

KFAA31713-E

40518

The row length of the work table has exceeded the upper limit.

KFAA30808-E

40528

An error occurred in processing on a file or directory.

KFAA30959-E

40529

Processing cannot continue because the S3 bucket or container operation has failed.

KFAA31738-E

40602

No global buffer has been assigned to the DB area.

KFAA30918-E

40701

Processing cannot continue because there are not enough buffer sectors.

KFAA30919-E

40704

The global buffer is temporarily unavailable.

KFAA30953-E

40801

No new table or index can be defined in the data DB area because the maximum number of chunks that can be managed by one data DB area was exceeded. Another possibility is that the maximum number of chunks for the table defined in the data DB area cannot be increased.

KFAA31727-E

40802

The specified chunk ID does not exist in the table.

KFAA31728-E

40803

The chunk ID of the current chunk cannot be specified in the PURGE CHUNK statement.

KFAA31729-E

40804

The ALTER TABLE statement cannot be executed because the maximum number of chunks specified in the ALTER TABLE statement is less than the number of chunks that have already been created in the table.

KFAA31730-E

40820

The number of user log files has reached its upper limit.

KFAA31711-E

40900

The number of base tables, foreign tables, indexes, viewed tables, or HADB users has exceeded the maximum number that can be defined for the system.

KFAA30811-E

40910

The number of tables or indexes has exceeded the maximum that can be stored in a single DB area.

KFAA30812-E

40920

The page being recovered for database update processing was accessed during the primary node switchover processing.

KFAA31733-E

42501

The length of a character string literal exceeds 32,000 bytes.

KFAA30102-E

42502

The length of a binary literal exceeds the maximum allowed value.

KFAA30145-E

42505

A character string literal is incomplete.

KFAA30106-E

42509

A binary literal specification is invalid.

KFAA30144-E

42510

An SQL statement contains an error such as one of the following:

A name contains a character that cannot be specified (such as a character encoding mismatch).

A name with a length of 0 exists.

The statement contains a character or keyword that is not allowed by the syntax.

KFAA30104-E

42511

The numeric literal that was specified is invalid.

KFAA30410-E

42512

The specification format of the floating-point numeric literal is invalid.

KFAA30103-E

42513

A numeric literal that is outside the specification range was specified.

KFAA30405-E

42520

The length of a name exceeds 100 bytes. Another possibility is that a keyword was specified incorrectly.

KFAA30107-E

42529

The length of the authorization identifier is outside the range of 1 to 100 bytes.

KFAA30564-E

42530

An SQL statement contains an error such as one of the following:

The first keyword of the SQL statement is invalid.

The only character is a separator character.

KFAA30104-E

42532

The following syntax error was found in the identifier specified for the national character set:

A double-byte space character was used.

KFAA30142-E

42539

The specified authorization identifier contains at least one of the following errors:

A character that is not an alphanumeric character was specified.

A character that cannot be specified with normal identifiers was specified.

KFAA30564-E

42550

A dynamic parameter is specified at an invalid location.

KFAA30418-E

42561

The specified predicate is invalid.

KFAA30114-E

42572

The specified ROW is invalid.

KFAA30149-E

42580

The value outside the specified range is specified as an array index or identification number for an array element reference.

KFAA30186-E

42581

There is an error in the maximum number of elements specified in the array-type column specified in the SQL statement.

KFAA30189-E

42590

The length, precision, or scale of a data type is invalid.

KFAA30604-E

42591

The fractional seconds precision specified for the datetime information acquisition function is invalid.

KFAA30131-E

425A0

The specified number exceeds the maximum allowed value.

KFAA30129-E

425A4

425A6

425A7

425A8

425A9

425AA

425AI

425AJ

425B0

425B1

425B2

The number of grouping columns specified in a GROUP BY clause exceeds the maximum allowed value.

KFAA30122-E

425B3

The number of specified sort keys exceeds the maximum allowed value.

KFAA30124-E

425B5

The specified value exceeds the maximum allowed value.

KFAA30129-E

425B6

425B7

425BB

425BC

425BG

The number of value expressions specified in a window partition clause exceeds the maximum allowed value.

KFAA30122-E

425BJ

The specified number exceeds the maximum allowed value.

KFAA30129-E

425BK

425BL

425BM

425C0

The number of columns in the table exceeds the upper limit of 4,000.

KFAA30602-E

425C1

The specified value exceeds the maximum allowed value.

KFAA30129-E

425C2

425C6

The number of columns in a multiple-column index exceeds the upper limit of 16. Another possibility is that the number of columns making up the primary key exceeds the upper limit of 16.

KFAA30617-E

425CA

The specified value exceeds the maximum allowed value.

KFAA30129-E

425CB

425CC

425CD

The number of columns constituting a foreign key exceeds the maximum of 16.

KFAA30617-E

425CF

The specified value exceeds the maximum allowed value.

KFAA30129-E

425CG

425CH

425CK

The number of specifications exceeds the maximum allowed.

KFAA31129-E

425CL

A delimited identifier that contains left or right parentheses can be specified only in the first query specification in the SELECT statement. However, a delimited identifier that contains left or right parentheses cannot be specified for a query specification in the WITH clause.

KFAA31131-E

425CM

Although NULL is specified in the selection expression in a query specification, an error occurred in the SELECT statement because the conditions of available specifications are not met.

KFAA31132-E

425D0

No column definition is specified in the CREATE TABLE statement or CREATE FOREIGN TABLE statement.

KFAA30678-E

425D4

An option was illegally specified more than once in a table or index definition.

KFAA30673-E

425D5

A value outside the valid range was specified for a table option in the CREATE TABLE or ALTER TABLE statement, or for an index option in the CREATE INDEX statement.

KFAA30705-E

425D7

A privilege specified in the GRANT or REVOKE statement is duplicated.

KFAA30572-E

425Q0

The specification of the maximum-number-of-recursions specification is invalid.

KFAA31135-E

425Q2

There is an error in the specification format of the specified syntax.

KFAA31137-E

42601

An extra character string exists after the SQL statement.

KFAA30104-E

42602

An SQL statement contains a syntax error.

KFAA30105-E

42603

An SQL statement is incomplete.

KFAA30106-E

42703

The value specified for labeled duration is invalid.

KFAA31405-E

42705

The data type or length of a column is invalid.

A value expression whose result has a data length of 0 was specified.

KFAA31205-E

42710

The aggregated argument specified in a set function is invalid. Another possibility is that the argument specified in a window function is invalid.

KFAA30112-E

42711

A set function is specified in an argument of a set function.

KFAA30113-E

42712

The data type of an aggregated argument in a set function is invalid. Another possibility is that the data type of an argument in an inverse distribution function is invalid.

KFAA30402-E

42713

The specified set function is invalid.

KFAA30403-E

42714

A set function or a window function is specified at an invalid location.

KFAA30120-E

42715

A subquery is specified at an invalid location.

KFAA30154-E

42716

The SELECT DISTINCT and DISTINCT set functions are both specified.

KFAA30127-E

42717

Multiple DISTINCT set functions containing different column names in the arguments are specified.

42718

Another DISTINCT set function is specified in addition to a DISTINCT set function specified in the value expression of an argument.

4271A

The length of the LISTAGG separator character string exceeds the specified maximum length of the LISTAGG result character string.

KFAA31224-E

4271B

The specified value of the maximum length of the LISTAGG result character string is outside the specifiable range.

4271C

The length of the truncated string suffix exceeds the specified maximum length of the LISTAGG result character string.

42720

The number of columns to be inserted does not match the number of values to be inserted.

KFAA30117-E

42721

In a specified set operation, the tables derived from individual query expression bodies do not have the same number of columns.

KFAA30195-E

42722

Two or more selection expressions have been specified for a retrieval item.

KFAA30192-E

42723

There is an error in the specified CREATE VIEW statement. The number of column names specified in the column name list differs from the number of columns for the table that is derived from the query expression.

KFAA30650-E

42730

A name is duplicated within a FROM clause.

KFAA30211-E

42731

An update column or insertion column is duplicated.

KFAA30121-E

42732

A column specification is duplicated.

KFAA30123-E

42733

A query name was specified more than once in a WITH clause.

KFAA30458-E

42734

A column name is duplicated in a viewed table.

KFAA30459-E

42736

A column used as a sort key specified in the ORDER BY clause is duplicated.

KFAA31123-E

42737

The specified viewed table has a view level that cannot be specified in the CREATE VIEW statement.

KFAA31219-E

42740

The qualifying table specification contains a name that is not valid to specify in an SQL statement.

KFAA30201-E

42741

The specified table or index has not been defined.

KFAA30204-E

42742

The specified column does not exist in any table of the SQL statement or query specification. Another possibility is that the name is invalid.

KFAA30202-E

The specified column was not found in a table, correlation name, or query in a FROM clause.

KFAA30205-E

There are no target candidates for the specified identifier within the valid range.

KFAA30239-E

42743

The sort item specification number specified in an ORDER BY clause is invalid.

KFAA30125-E

A column that is not specified in the selection expression cannot be specified in the ORDER BY clause due to one of the following reasons:

SELECT DISTINCT has been specified in a selection expression.

A set operator for the query specification, which is the first set operation operand in the set operation, is specified.

KFAA30208-E

42744

The table to which the specified column name belongs cannot be determined.

KFAA30203-E

There are two or more corresponding tables in a query with ROW specified.

KFAA30213-E

42745

A column specified in an ORDER BY clause is found more than once in a table derived as a result of a query.

KFAA30220-E

42746

The specified SQL statement contains the following error:

In a query using a GROUP BY clause or set function specification, the column specification in a selection expression, HAVING clause, or ORDER BY clause must be specified as an argument of the GROUP BY clause or set function.

KFAA30119-E

42750

ROW is specified for a table that is not a FIX table.

KFAA30214-E

42755

The specification location of the array data is invalid.

KFAA30183-E

42759

Array data cannot be specified for a selection expression or set function with a DISTINCT specification.

KFAA30187-E

4275A

The specified collection derived table is invalid.

KFAA30188-E

4275B

The derived column list cannot be specified.

KFAA31269-E

4275C

ADB_GENERATE_SERIES function specification is invalid.

KFAA31270-E

4275D

The column definitions of the foreign table specified in the CREATE VIEW statement differ between when the view table was defined and when the view table was retrieved.

KFAA31271-E

42767

The specification of the chunk ID is invalid.

KFAA31209-E

42768

42769

4276B

4276C

4276D

4276E

4276F

42770

A dynamic parameter is specified at an invalid location in a predicate.

KFAA30417-E

42771

A dynamic parameter is specified at an invalid location in an operation.

KFAA30419-E

4277E

The specification of the system-defined function is invalid.

KFAA30177-E

4277F

4277G

42780

A data type that cannot be specified in a datetime operation was specified with an arithmetic operator.

KFAA30413-E

Labeled durations can only be specified for the operands of addition and subtraction operations on datetime data.

KFAA30414-E

42782

The argument specified in the scalar function is invalid.

KFAA30425-E

42784

The specified CASE expression is invalid.

KFAA30448-E

42785

The argument specified in the scalar function is invalid.

KFAA30453-E

42786

The specification of the system-defined function is invalid.

KFAA30177-E

42787

The datetime format specified in a scalar function is not compatible with the time data.

KFAA31212-E

42788

The data type of an argument is invalid in the LTRIM, RTRIM, or TRIM scalar function.

KFAA31425-E

42789

The format specification in a scalar function is invalid.

KFAA31213-E

4278A

4278B

4278C

4278D

4278E

The data length of an argument in the REPLACE scalar function is invalid.

KFAA31425-E

4278G

The specification of the labeled duration is invalid.

KFAA30415-E

4278H

4278I

4278J

The specification method of the scalar function is invalid.

KFAA31235-E

4278K

4278M

4278N

4278O

The specified scalar function is invalid.

KFAA31234-E

4278P

4278Q

4278R

The length of the regular expression character string specified in the LIKE_REGEX predicate is invalid.

KFAA31424-E

4278S

The specified scalar function LTDECODE is invalid.

KFAA31226-E

4278T

The specified scalar function TIMESTAMPADD is invalid.

KFAA31227-E

4278U

42793

The table to be updated cannot be specified as a table from which data is to be retrieved.

KFAA30118-E

427A0

The depth of nesting of the operation exceeded 255. Another possibility is that the SQL statement could not be executed because of a restriction on system processing.

KFAA30101-E

427A2

The number of value expressions or row value constructors specified on the right side of an IN predicate has exceeded the upper limit of 30,000.

KFAA30137-E

427A3

CURRENT_USER_IS_DBA is specified, but this character string is not permitted.

KFAA31203-E

427A4

The insertion value specified in an INSERT statement is invalid.

KFAA31206-E

427A5

The null-value sort order specification cannot be specified in the sort specification list.

KFAA31126-E

427A6

The number of set operations specified in an SQL statement that include EXCEPT or INTERSECT exceeds the maximum of 63 that can be specified.

KFAA31210-E

427B2

For a query that uses a set operation, a column name qualified in the table specification cannot be specified as a sort key.

KFAA30194-E

427B3

A viewed table cannot be defined with another viewed table as its underlying table.

KFAA30655-E

The TRUNCATE TABLE statement cannot be executed on a viewed table or foreign table.

KFAA30677-E

427B4

The PURGE CHUNK statement cannot be executed on a single-chunk table, viewed table, or foreign table.

KFAA30677-E

427B5

No chunk ID is specified in the PURGE CHUNK statement.

KFAA31215-E

427B6

For a query that uses a set operation, no value expression can be specified in the ORDER BY clause.

KFAA30194-E

427B7

No more than one sort key can be specified in an inverse distribution function or LISTAGG set function.

KFAA31124-E

427B9

The specified inverse distribution function is invalid.

KFAA31127-E

427BA

427BB

427BC

A column in the table where chunks are to be deleted is specified in the PURGE CHUNK statement.

KFAA31215-E

427C5

The specified foreign server does not exist.

KFAA31556-E

427C6

The specified foreign server is already defined.

KFAA31557-E

427C7

A foreign server defined by another HADB users is specified.

KFAA31558-E

427D3

A WITH clause specification is invalid.

KFAA31204-E

427G0

A window function specification is invalid.

KFAA30257-E

427G1

427G2

427G3

427G4

427G5

427H0

A window function specification is invalid.

KFAA30264-E

427H1

427H2

427H3

A window function specification is invalid.

KFAA31120-E

427H4

The number of window functions specified in the query specification or the ORDER BY clause exceeds 64.

KFAA31125-E

427HA

The value expression in the following location contains no column specification.

Window partition clause

KFAA30166-E

427HC

The sort key specified in an ORDER BY clause is invalid.

427HD

Sort item specification numbers for ROW cannot be specified.

KFAA30126-E

427HE

For a query that specifies SELECT DISTINCT, no value expression can be specified in the ORDER BY clause.

KFAA30194-E

427I0

If AS column-name is specified in the GROUP BY clause, a value expression containing only column specifications cannot be specified in the GROUP BY clause.

KFAA31202-E

427I1

A FULL OUTER JOIN specification is invalid.

KFAA31128-E

427I2

427I3

The specified LIMIT clause is invalid.

KFAA31216-E

427I4

427I5

If AS column-name is specified in the GROUP BY clause, the grouping column name cannot be referenced from a subquery in the HAVING clause or selection expression.

KFAA31201-E

427I6

The specified LIMIT clause is invalid.

KFAA31216-E

427I7

Table names of table references specified in the query specification cannot be referenced from subqueries in ORDER BY clauses.

KFAA31207-E

427I8

A FULL OUTER JOIN specification is invalid.

KFAA31128-E

427I9

The specified multiset value expression is invalid.

KFAA30323-E

427IA

427J0

An argument specified in the ADB_CSVREAD function is invalid.

KFAA30324-E

427J1

427J2

427J3

427J4

427J5

427J6

427J7

427J8

427J9

427JA

The table function column list specified in the table function derived table is invalid.

KFAA31239-E

427K0

The specification of the table function derived table with the system-defined function specified is invalid.

KFAA31240-E

427K1

The argument specified in the system-defined function is invalid.

KFAA31241-E

427K2

427K5

A multiset value constructor by query cannot be specified as an argument of the ADB_AUDITREAD function.

KFAA31242-E

427K6

There is a problem with the audit trail file path names (that contain special characters) specified as the argument of the ADB_AUDITREAD function.

KFAA31243-E

427K7

427L0

The numbers of row value constructor elements specified in the row value constructors do not match.

KFAA31260-E

427M0

The specified row value constructor element is invalid.

KFAA31261-E

427M1

A dynamic parameter alone cannot be specified in a row value constructor element.

KFAA31262-E

427M2

Row value constructors and non-row value constructors are compared. Row-value constructors can only be compared to row-value constructors.

KFAA31263-E

427M3

The specified value of the row value constructor element is invalid.

427M4

The specified position of the predicate is invalid.

427M5

A comparison operator is invalid.

427M6

The specification method of the ALTER SERVER statement or CREATE SERVER statement is invalid.

KFAA31264-E

427M7

The specification method of the CREATE FOREIGN TABLE statement is invalid.

KFAA31265-E

427M8

The specification method of the table name of the foreign table is invalid.

KFAA31266-E

427MA

The specification method of the COPY statement is invalid.

KFAA31267-E

427MB

KFAA31268-E

427MC

The specification location of the structure data is invalid.

KFAA31255-E

427MD

KFAA31256-E

427ME

The specification method of the field reference is invalid.

KFAA31257-E

427N0

The recursive member contains an item that cannot be specified.

KFAA31470-E

427N1

The data type and data length of the column derived from the anchor member are different from those of the column derived from the recursive member.

KFAA31471-E

427N5

The specification of the recursive query is invalid.

KFAA30464-E

427N6

427N7

427N8

427P1

The specified array element reference is invalid.

KFAA31245-E

427P2

427P3

427P4

427P5

427P6

427P7

42801

The data types of the results of the value expressions and each row value constructor specified in a predicate cannot be compared to each other or converted.

KFAA30401-E

The data type of a value expression specified in a predicate is not character string data.

KFAA30407-E

42802

An invalid data type is specified in the operand of an operator.

KFAA30406-E

An invalid data type was specified in the first or second operand of a concatenation operation.

KFAA30411-E

The logical predicate specification is invalid.

KFAA30465-E

42803

The data type of the update value or insertion value is not a data type that can be converted.

KFAA30408-E

42804

A set operation specification is invalid.

KFAA30197-E

42806

The data types of the results of value expressions specified for THEN and ELSE in a CASE expression are not compatible.

KFAA30447-E

42807

The specified scalar function is invalid.

KFAA30453-E

4280F

A window function specification is invalid.

KFAA30257-E

42812

The maximum length of the result of an operation exceeds 32,000 bytes.

KFAA30420-E

42819

The data length of an argument specified in the scalar function exceeds the maximum byte length.

KFAA31420-E

42820

Permission to access the specified schema or schema object has not been granted.

KFAA30548-E

42849

A table function derived table with the system-defined function specified cannot be specified.

KFAA30467-E

42850

No dynamic parameter can be specified in a view definition.

KFAA30651-E

42870

An attempt was made to perform an operation that cannot be performed on a table.

KFAA30670-E

42875

A table that cannot be deleted, inserted, or updated is specified in the SQL statement.

KFAA31280-E

42876

A LISTAGG set function is specified in the window function.

42877

A ARRAY_AGG set function is specified in the window function.

42878

An array-type column is specified as the external reference column.

42879

The INSERT, UPDATE, and DELETE statements are specified when using the cloud storage facility.

4287A

A ORDER BY clause specified in the subquery is specified at an invalid location.

4287B

If an ORDER BY clause is specified for a subquery or WITH list element, the LIMIT clause must also be specified.

4287C

A STRUCT type column is specified as the external reference column.

428A3

A viewed table cannot be defined with a dictionary table or a system table as its underlying table.

KFAA30547-E

428F0

An index specification is invalid.

KFAA31208-E

428F1

428F2

428F5

The specified subquery processing method specification is invalid.

KFAA31223-E

428T0

The specified scalar function CONTAINS contains an error.

KFAA34002-E

428T1

428T2

A notation-correction-search specification cannot be specified because the character encoding used by the HADB server is Shift-JIS (if the value specified for the environment variable ADBLANG is SJIS).

KFAA34003-E

428T3

A regular expression specified for a regular expression character string in the LIKE_REGEX predicate is invalid.

KFAA34004-E

428T4

428T5

428T6

428T7

The synonym dictionary specified in the scalar function CONTAINS does not exist.

KFAA34005-E

428T8

The synonym dictionary specified in the scalar function CONTAINS does not support a correction search.

KFAA34006-E

428T9

A synonym search cannot be performed if the multi-node function is used.

KFAA34007-E

428TA

The specified scalar function CONTAINS contains an error.

KFAA34002-E

428TB

428TC

42929

A viewed table contains a column for which no derived column name has been set, and the column name specification was omitted.

KFAA30460-E

4292A

This viewed table cannot be accessed because it is invalidated.

KFAA30454-E

42932

The specified environment variable is invalid.

KFAA30724-E

429D9

The data type of row-count or offset in the LIMIT clause is invalid.

KFAA31301-E

42I01

An SQL statement contains an error similar to the following:

A viewed table or foreign table is specified in the ALTER TABLE statement.

A base table or foreign table is specified in the ALTER VIEW statement.

A viewed table or foreign table is specified in the CREATE INDEX statement.

A base table or viewed table is specified in the DROP FOREIGN TABLE statement.

A viewed table or foreign table is specified in the DROP TABLE statement.

A base table or foreign table is specified in the DROP VIEW statement.

KFAA30206-E

42I05

The specified schema object does not exist.

KFAA30437-E

42I08

The authorization identifier or schema name specification is invalid.

KFAA30549-E

42I13

The table name, index name, or constraint name specified in one of the following SQL statements is already in use:

ALTER TABLE statement

CREATE TABLE statement

CREATE INDEX statement

CREATE VIEW statement

KFAA30601-E

42I14

The following operations cannot be performed for a FIX table:

Define a column of the variable-length data type.

Specify the chunk-archive specification.

Define a table as a column store table.

KFAA30609-E

42I15

A column name has been used more than once.

KFAA30612-E

42I16

A column that cannot be defined for a B-tree index was specified as an indexed column for a B-tree index.

KFAA30614-E

42I18

An error occurred in an SQL statement because a column name was specified more than once.

KFAA30619-E

42I25

Since there is only one column defined in the table, that column cannot be deleted with the ALTER TABLE statement.

KFAA30632-E

42I26

The schema does not exist.

KFAA30656-E

42I27

The data type and data length specified in the ALTER TABLE statement CHANGE clause is invalid.

KFAA30659-E

42I29

An index with the same structure already exists.

KFAA30661-E

42I30

A schema with the same name already exists.

KFAA30664-E

42I31

Because the specified values before and after changing are the same, it is not possible to change the column attributes (maximum number of elements or data length) using the ALTER TABLE statement.

KFAA30665-E

42I32

The maximum number of elements specified in the CHANGE clause of the ALTER TABLE statement are invalid.

KFAA30667-E

42I44

An SQL statement was executed with RESTRICT specified for the drop behavior, but the SQL statement resulted in an error for one of the following reasons:

An attempt was made to delete base tables for which indexes or constraints were defined.

An attempt was made to delete schemas for which tables were defined.

An attempt was made to delete a table on which viewed tables depend.

An attempt was made to delete columns for which indexes or constraints were defined.

An attempt was made to delete a column of a table on which viewed tables depend.

An attempt was made to delete a foreign server used in a foreign table.

An attempt was made to delete a foreign table on which viewed tables depend.

KFAA30695-E

42I53

A foreign key cannot be defined because the referenced table has no primary key defined for it.

KFAA30742-E

42I54

The configuration of a foreign key differs from that of the primary key that the foreign key accesses.

KFAA30743-E

42I55

A foreign key cannot be defined for one of the following reasons:

The referenced table specified is not a base table

The referenced table is the same as the referencing table

KFAA30744-E

42I60

The null-value exclusion specification (EXCLUDE NULL VALUES) cannot be specified due to one of the following reasons:

The null-value exclusion specification is specified for an index that is not a B-tree index.

The indexed columns include a column for which the NOT NULL constraint is specified.

KFAA30758-E

42I72

A DEFAULT clause specification is invalid.

KFAA30798-E

42I75

A CREATE INDEX statement, an ALTER TABLE, a CREATE TABLE statement, or a CREATE FOREIGN TABLE statement cannot be executed.

KFAA31600-E

The data type of a column by ALTER TABLE statement cannot be changed.

KFAA31603-E

42I77

Multiple referential constraints that access the same primary key cannot be defined from the same column or from the same group of multiple columns (even if the column order is different).

KFAA31602-E

42I7A

The specification method of the ALTER SERVER statement is invalid.

KFAA31562-E

42I7B

The specification method of the CREATE SERVER statement is invalid.

KFAA31563-E

42I7C

The specification method of the CREATE FOREIGN TABLE statement is invalid.

KFAA31564-E

42I7D

An attempt to generate the column definitions for the foreign table failed.

KFAA31566-E

42I91

The data type of the column specified in the column definition of the CREATE FOREIGN TABLE statement is invalid.

KFAA30704-E

42IA6

An invalid option is specified in an index definition.

KFAA31650-E

42IA7

Multiple indexed columns are specified in an index definition.

KFAA31651-E

42IA8

A column for which a range index cannot be defined is specified as an range-indexed column.

KFAA31652-E

42IA9

An attempt is made to define a unique index for a multi-chunk table.

KFAA31653-E

42IAA

The specified table option is invalid.

KFAA31684-E

42IAB

The specified option is invalid.

KFAA31685-E

42IAC

A column with the NOT NULL constraint specified cannot be added to a base table to which segments for storing rows are assigned.

KFAA30630-E

42IAD

The maximum number of chunks was not specified in the chunk specification when the base table was defined by using the CREATE TABLE statement. Therefore, the ALTER TABLE statement cannot be used to change the maximum number of chunks.

KFAA31654-E

42IAE

The specified ALTER TABLE statement is invalid. Neither the maximum number of chunks nor the chunk-archive specification is specified.

KFAA31655-E

42IAF

If the chunk specification is specified, a primary key cannot be defined. Conversely, if a primary key is defined, the chunk specification cannot be specified.

KFAA31657-E

42IB0

The DROP INDEX statement cannot be used to delete the indexes that correspond to the primary key.

Alternatively, the DROP INDEX statement cannot be used to delete the range indexes that are automatically defined for archive range columns.

KFAA31658-E

42IB2

A text index cannot be defined for columns.

KFAA31659-E

42IB3

The following index option cannot be specified for an index other than a text index:

Notation-correction-search text-index specification

KFAA31660-E

42IB4

Columns of the following data types cannot be specified as archive range columns:

CHARACTER type with a definition length of 33 or more bytes

VARCHAR type

BINARY type

VARBINARY type

KFAA31665-E

42IB5

The length of the path name of the specified archive directory is not in the range from 1 to 400 bytes.

KFAA31666-E

42IB6

The specified archive directory is not an absolute path.

42IB7

The notation-correction-search text-index specification (CORRECTIONRULE) cannot be specified because the character encoding used on the HADB server is Shift-JIS (if the value specified for the environment variable ADBLANG is SJIS).

KFAA31667-E

42IB8

The specified ALTER TABLE statement is invalid. Change of the maximum number of chunks and the chunk-archive specification cannot be specified at the same time.

KFAA31668-E

42IB9

The chunk-archive specification in the ALTER TABLE statement cannot be specified for an archivable multi-chunk table.

KFAA31669-E

42IBA

The chunk-archive specification in the CREATE TABLE statement or ALTER TABLE statement is invalid.

KFAA31550-E

42IBB

The chunk-archive specification in the ALTER TABLE statement is invalid.

KFAA31551-E

42IBC

The NOT NULL constraint (NOT NULL) is not defined for the column specified for RANGECOLUMN in the chunk-archive specification in the ALTER TABLE statement.

KFAA31552-E

42IBD

The chunk-archive specification in the ALTER TABLE statement cannot be specified for a single-chunk table.

KFAA31553-E

42IBE

The column name cannot be changed by using the ALTER TABLE statement because the current column name is the same as the new column name.

KFAA31554-E

42IBF

The archivable multi-chunk table could not be changed to a regular multi-chunk table because an error occurred in the ALTER TABLE statement.

KFAA31555-E

42IC0

TEXT WORDCONTEXT is not specified for the index type. Therefore, a text-index delimiter specification cannot be specified.

KFAA31686-E

42IC1

The table for which you are attempting to define a text index is a column store table.

KFAA31653-E

42ICD

A field name has been used more than once.

KFAA31565-E

42K01

The table to be searched cannot be referenced because you do not have the required privileges.

KFAA30550-E

42K02

The SQL statement cannot be executed because the user who executed the SQL statement is invalid.

KFAA30551-E

42K03

The DBA privilege is required to perform the attempted operation.

KFAA30552-E

42K05

An attempt was made to revoke a privilege that cannot be revoked by that same user.

KFAA30555-E

42K06

The operation by a GRANT or REVOKE statement could not be performed.

KFAA30556-E

42K07

A nonexistent authorization identifier is specified.

KFAA30559-E

42K10

The schema definition privilege cannot be deleted because the HADB user having the authorization identifier specified in the REVOKE statement owns the schema.

KFAA30577-E

42K12

An attempted operation requires the schema definition privilege.

KFAA30579-E

42K14

Schema belonging to other HADB users cannot be changed.

KFAA30607-E

42K19

The HADB user having the authorization identifier specified in the DROP USER statement cannot be deleted.

KFAA30562-E

42K26

The privilege cannot be revoked because RESTRICT is specified for the drop behavior.

KFAA31436-E

42K30

An attempt is made to grant privileges that cannot be granted to the same HADB user.

KFAA31670-E

42K33

The password of an HADB user who has the audit privilege cannot be changed by other HADB users.

KFAA31673-E

42K35

You do not have the privilege required to perform operations relating to the audit trail facility.

KFAA31675-E

42K38

The audit target specified in the CREATE AUDIT statement is already defined.

KFAA31678-E

42K39

The audit target definition specified in the DROP AUDIT statement does not exist.

KFAA31679-E

42K43

The specified authorization identifier is already in use.

KFAA30566-E

42K44

The user authentication method of the HADB user having the specified authorization identifier cannot be changed.

KFAA31687-E

5100J

An error occurred when an SQL statement that uses hash tables was executing.

KFAA31372-E

5100K

An attempt to execute the DELETE statement for the archivable multi-chunk table caused an error because the specified search condition did not meet the execution condition of the DELETE statement.

Alternatively, an attempt to execute the UPDATE statement for the archivable multi-chunk table caused an error because the specified search condition did not meet the execution condition of the UPDATE statement.

KFAA31376-E

5100L

The number of recursions in the recursive query exceeds the maximum number of recursions.

KFAA31377-E

5100M

An error occurred when executing the SQL statement with the SQL parallel execution function applied.

KFAA31378-E

5100N

A failure occurred in communication between nodes when executing the SQL statements with the SQL parallel execution function applied.

KFAA31379-E

5100P

The data contained in the column derived by the outermost query specification in the query expression body of the COPY statement is invalid.

KFAA31740-E

An Apache Arrow API error occurred while executing the COPY statement.

KFAA31743-E

5100R

An Apache Iceberg API error occurred.

KFAA31820-E

5100S

A connection could not be established to the foreign server.

KFAA31744-E

52004

No SQL statements can be executed because the HADB server is being started or terminated.

KFAA30727-E

52011

The operation relating to the audit trail facility cannot be performed because the audit trail facility is disabled.

KFAA30575-E

5201F

An application program cannot connect to the HADB server on a kernel or OS version that is not supported by HADB.

KFAA31893-E

52020

The SQL statement cannot be executed because a uniqueness constraint violation occurred on a B-tree index between the time the preprocessing of the SQL statement began and the time the SQL statement was executed.

KFAA31714-E

52021

The size of the area required to store a row exceeds the capacity of one segment.

KFAA31737-E

52320

The connection to the HADB server was closed.

KFAA30722-E

52321

Invalid data was received from the HADB server.

52322

The address of the target host could not be acquired.

KFAA30723-E

52324

One of the following failures was detected:

A failure occurred on the network.

The HADB server terminated abnormally and the connection was closed.

The connection was closed because the HADB client version differs from the HADB server version.

52325

A security violation occurred in the JDBC driver.

52326

A timeout occurred while connecting to the HADB server or during data transmission.

52328

A system call error occurred during communication processing.

52330

An error occurred in the application program or command because HADB server processing did not terminate when the timeout period expired.

KFAA30732-E

52401

The SQL statement cannot be executed because another SQL statement or command has locked a resource that the SQL statement needs to execute.

KFAA31371-E

52402

The dictionary table (base table) cannot be accessed because a transaction is using the dictionary table (base table).

KFAA31648-E

52403

The specified operation cannot be performed because a locked resource is being used by another operation.

KFAA31656-E

52404

53021

You cannot use the ALTER TABLE statement to add or delete a column.

KFAA30613-E

You cannot use the ALTER TABLE statement to delete a column.

KFAA30629-E

53024

A definition SQL statement cannot be executed because the table definition information is in use.

KFAA30692-E

53026

The table-definition information for a secondary node or worker node could not be invalidated.

KFAA31661-E

53027

The SQL statement cannot be executed because the table is being referenced in the same transaction.

KFAA31662-E

53028

The SQL statement or the command cannot be executed due to contention of the locked resource.

KFAA31663-E

53029

The definition SQL statement cannot be executed because a ResultSet object exists.

KFAA31664-E

5302A

A directory that does not exist is specified as an archive directory.

KFAA31666-E

5302B

A directory that cannot be specified as an archive directory is specified.

5302C

A directory for which the HADB administrator does not have read, write, and execution permissions is specified as an active directory. Alternatively, the archive directory path contains a directory for which the HADB administrator does not have execution permission.

5302D

Link destinations for the symbolic link specified in the archive directory cannot be acquired.

5302E

An error occurred in a system call.

53030

The server message log file is full.

KFAA31896-E

53031

The client message log file is full.

53040

A descriptor shortage occurred.

KFAA30723-E

53041

Allocation of communication port numbers failed.

53050

An error occurred during operation on the synonym dictionary file.

KFAA34008-E

53051

Data retrieval by using the text index is not available. Alternatively, the text index cannot be updated.

KFAA34009-E

53201

A memory shortage occurred in a client library.

KFAA30723-E

An attempt to acquire enough memory to execute the SQL statement has failed.

KFAA30930-E

An attempt to acquire enough memory to access the foreign server has failed.

KFAA31741-E

54001

An argument of a CLI function is invalid.

KFAA30565-E

KFAA31306-E

54006

An analysis of the client definition has failed.

KFAA30824-E

54009

Execution of an SQL statement was requested before preprocessing of the SQL statement had terminated normally.

KFAA30901-E

54012

The following functions cannot be used on statement handles prepared for execution of statements other than DELETE, INSERT, and UPDATE statements:

Batch update functionality of the JDBC driver

Update using batch binding of dynamic parameters of the CLI function (a_rdb_SQLBindArrayParams())

KFAA30873-E

54013

An SQL statement is already executing on the same connection.

KFAA31898-E

54014

Transactions cannot be started because a read-only transaction is being executed on an HADB server in a multi-node configuration.

54016

Transactions cannot be started because a read/write transaction or command is being executed on an HADB server in a multi-node configuration.

54017

The transaction cannot be executed because a command is executing or because another transaction is being executed by an application program.

KFAA31719-E

54018

An update SQL statement or definition SQL statement cannot be executed because the HADB server operation mode is quiescence mode.

KFAA31898-E

54020

A retrieval SQL statement resulted in an error.

54024

The number of concurrent executions of SQL with the SQL parallel execution function has exceeded the maximum number of concurrent executions, so the retrieval SQL statement that uses the SQL parallel execution function cannot be executed any more.

54025

Because an SQL statement has already been executed on the same connection, you cannot execute a retrieval SQL statement that uses the SQL parallel execution function.

The SQL statement cannot be executed because a retrieval SQL statement that has already applied the SQL parallel execution function is being executed on the same connection.

54026

Because none of the SQL sub nodes could be allocated, the SQL parallel execution function cannot be applied to the retrieval SQL statement.

54027

Cannot execute the retrieval SQL statement that uses the SQL parallel execution function because a read/write transaction or a specific command is being executed on the primary node.

54201

An SQL statement cannot be executed because no connection has been established to the HADB server.

KFAA30563-E

54202

An SQL statement that uses this connection is already being executed.

KFAA30319-E

54203

The following items cannot be set because no connection has been established:

Transaction isolation level

Sort order of character string data

Transaction access mode

Additional user information

KFAA31897-E

54204

The following items cannot be set because the transaction has already started:

Transaction isolation level

Sort order of character string data

Transaction access mode

Additional user information

54205

The specified character string data sort order is invalid.

54206

The following items cannot be set because the cursor is already opened:

Transaction isolation level

Sort order of character string data

Transaction access mode

Additional user information

56001

The total length of data specified in a dynamic parameter exceeds 2 gigabytes. Another possibility is that the total length of data in the retrieval result exceeds 2 gigabytes.

KFAA30312-E

56006

The total memory required to execute the SQL statement exceeds 2 gigabytes.

KFAA30229-E

56007

The length of a B-tree index key exceeds the maximum value.

KFAA30616-E

56009

The CREATE TABLE or ALTER TABLE statement cannot be executed because the size of the area required to store a row exceeds the page size.

KFAA30657-E

5600B

The number of indexes that can be defined for a single table has exceeded the upper limit of 64.

KFAA30706-E

5600C

The number of foreign keys that reference a primary key exceeded 255.

KFAA30748-E

5600E

The SQL statement length has exceeded the upper limit of 16,000,000 bytes, or the length is invalid.

KFAA30821-E

The length of a CREATE VIEW statement exceeds 64,000 bytes.

KFAA31121-E

56020

An invalid statement handle is specified.

KFAA30805-E

56033

The number of statement handles has exceeded the upper limit of 4,095.

KFAA30931-E

56034

The total data length of dynamic parameters exceeds 32,000,000 bytes.

KFAA31218-E

58005

The DB area specified in the following SQL statements or the assumed DB area does not exist:

CREATE TABLE statement

CREATE INDEX statement

ALTER TABLE statement

KFAA30652-E

58006

The specified or assumed DB area is not a data DB area.

KFAA30653-E

58024

The data DB area for storing tables or indexes is not specified in the CREATE TABLE or CREATE INDEX statement.

KFAA31696-E

5B002

Processing of the SQL statement or command was canceled and the transaction was rolled back.

KFAA30955-E

5C002

A character encoding conversion error occurred.

KFAA72000-E

An error occurred in data type conversion version processing performed by the ODBC driver.

KFAA72004-E

KFAA72006-E

5C011

An internal conflict was found.

KFAA30318-E

KFAA30322-E

KFAA30720-E

5C015

Invalid data was received from the HADB server.

KFAA30733-E

5C034

Invalid data was received from an HADB client (including a JDBC driver) or command.

KFAA31895-E

5C035

An internal conflict was detected in the ODBC driver.

KFAA72099-E

5C036

The specified input data whose setting was requested is invalid.

--

An error occurred in data type conversion version processing performed by the ODBC driver.

KFAA72006-E

5C037

The specified input data whose setting was requested is invalid.

--

An error occurred in data type conversion version processing performed by the ODBC driver.

KFAA72004-E

5C038

There is an error in the area specified for receiving acquired result data.

--

An error occurred in data type conversion version processing performed by the ODBC driver.

KFAA72004-E

5C039

There is an error in the area specified for receiving acquired result data.

--

5C03A

The transaction was rolled back because an error occurred in one of the statement handles used in the transaction.

KFAA31894-E

5C041

A data type that is not supported by the ODBC driver was specified in an SQL statement.

--

5C051

The length of an SQL statement exceeded 16,000,000 characters.

KFAA72007-E

5C052

The versions of the ODBC driver and the HADB client are different.

KFAA72009-E

5D001

An error occurred in HADB, and neither the SQLSTATE value nor the message could be obtained.

KFAA72002-E

HY001

An error occurred in data type conversion version processing performed by the ODBC driver.

KFAA72004-E

HY003

HY004

HY009

HY013

KFAA72006-E

HY090

HY104

HYC00

R2411

The object was invalidated because its transaction has terminated (including any implicit rollbacks).

KFAA71002-E

R2412

The type of the table specified by the getTables method argument for the String-type array is invalid.

KFAA71017-E

R2413

Processing cannot be accepted because the Statement instance is already closed.

KFAA71202-E

R2414

Conversion of the character encoding failed.

KFAA71203-E

R2415

An attempt to read from the java.io.Reader or java.io.InputStream has failed.

KFAA71204-E

R2416

Processing cannot be accepted because the Connection instance is already closed.

KFAA71206-E

R2417

An attempt was made to execute a method that is not supported.

KFAA71209-E

R2418

Batch processing cannot be performed because this SQL statement returns a result set.

KFAA71210-E

R2419

An unsupported argument was specified in the setFetchDirection method.

KFAA71211-E

R2420

The value of an argument specified in the setFetchSize method is invalid.

KFAA71212-E

R2421

Processing cannot be accepted because the instance is already closed.

KFAA71218-E

R2423

Objects of the class specified by the unwrap method of the Wrapper interface cannot be acquired.

KFAA71222-E

R2424

An attempt to register the JDBC driver with the driver manager has failed.

KFAA71301-E

R2425

The scroll type value of the specified result set is an invalid scroll type that is not defined by ResultSet.

KFAA71448-E

R2426

The concurrent processing type value of the specified result set is an invalid concurrent processing type that is not defined by ResultSet.

KFAA71449-E

R2427

The escape clause of the specified SQL statement is invalid.

KFAA71450-E

R2428

The specified connection information is invalid.

KFAA71452-E

R2429

The value of the holdability of the specified result set is an invalid value that is not defined in the ResultSet class.

KFAA71453-E

R2430

A negative value is specified for the maximum selection row count that is specified with the setMaxRows method or setLargeMaxRows method.

KFAA71562-E

R2431

The specified SQL statement is a null value or a character string with a length of zero.

KFAA71563-E

R2432

A negative value is specified for the timeout value that is specified with the setQueryTimeout method.

KFAA71564-E

R2433

A negative value is specified for the maximum field length that is specified with the setMaxFieldSize method.

KFAA71565-E

R2434

The specified SQL statement cannot be executed by executeQuery.

KFAA71566-E

R2435

The specified SQL statement cannot be executed by the executeUpdate method or executeLargeUpdate method.

KFAA71567-E

R2436

The number of batch registrations exceeded the upper limit of 2,147,483,647.

KFAA71569-E

R2437

Parameters of this SQL data type cannot be specified.

KFAA71680-E

R2438

A required parameter has not been specified.

KFAA71681-E

R2439

The specified parameter is invalid.

KFAA71682-E

R2440

The value of the parameter index is invalid.

KFAA71683-E

R2441

The object that was specified with the setObject method cannot be converted to the specified SQL data type.

KFAA71687-E

R2442

The data cannot be converted to the data type of the table definition because the number of digits of the integer portion of the specified data exceeds the number of digits of the integer portion of the table definition.

KFAA71690-E

R2443

The data is a value that is outside the range of the data type at the conversion destination, or else it is in a format that cannot be converted.

KFAA71691-E

R2444

The data type of the dynamic parameter that corresponds to the specified parameter index cannot be used with this setXXX method.

KFAA71692-E

R2445

The column name specified with the getXXX method of the ResultSet class is invalid.

KFAA71701-E

R2446

The specified column data cannot be acquired with the getString method of the ResultSet class.

KFAA71704-E

R2447

The specified column data cannot be acquired with the getBoolean method of the ResultSet class.

KFAA71705-E

R2448

The specified column data cannot be acquired with the getByte method of the ResultSet class.

KFAA71706-E

R2449

The specified column data cannot be acquired with the getShort method of the ResultSet class.

KFAA71707-E

R2450

The specified column data cannot be acquired with the getInt method of the ResultSet class.

KFAA71708-E

R2451

The specified column data cannot be acquired with the getLong method of the ResultSet class.

KFAA71709-E

R2452

The specified column data cannot be acquired with the getFloat method of the ResultSet class.

KFAA71710-E

R2453

The specified column data cannot be acquired with the getDouble method of the ResultSet class.

KFAA71711-E

R2454

The specified column data cannot be acquired with the getBigDecimal method of the ResultSet class.

KFAA71712-E

R2455

The specified column data cannot be acquired with the getBytes method of the ResultSet class.

KFAA71713-E

R2456

The specified column data cannot be acquired with the getDate method of the ResultSet class.

KFAA71714-E

R2457

The specified column data cannot be acquired with the getTime method of the ResultSet class.

KFAA71715-E

R2458

The specified column data cannot be acquired with the getTimestamp method of the ResultSet class.

KFAA71716-E

R2459

The specified column data cannot be acquired with the getAsciiStream method of the ResultSet class.

KFAA71717-E

R2460

Processing cannot be accepted because the ResultSet instance is already closed.

KFAA71721-E

R2461

The specified column data cannot be acquired with the getCharacterStream method of the ResultSet class.

KFAA71722-E

R2462

The column index specified with the getXXX method of the ResultSet class is invalid.

KFAA71727-E

R2464

Data cannot be acquired with the getXXX method of the ResultSet class used because the data acquired from the database does not match the date data format.

KFAA71730-E

R2465

Data cannot be acquired with the getXXX method of the ResultSet class used because the data acquired from the database does not match the time data format.

KFAA71731-E

R2466

Data cannot be acquired with the getXXX method of the ResultSet class used because the data acquired from the database does not match the time stamp data format.

KFAA71732-E

R2467

Scrolling is not possible because the result set type of this ResultSet object is TYPE_FORWARD_ONLY.

KFAA71733-E

R2468

Zero was specified with the absolute method.

KFAA71735-E

R2469

The cursor is not on a valid row.

KFAA71736-E

R2470

An argument value is invalid.

KFAA71801-E

R2471

An invalid value is specified for an argument of the setLoginTimeout method.

KFAA71903-E

R2472

An invalid character string is specified in the argument of the setEncodeLang method.

KFAA71908-E

R2473

The length of an SQL statement exceeded 16,000,000 characters.

KFAA71223-E

R2474

The specified column data cannot be acquired with the getBinaryStream method of the ResultSet class.

KFAA71719-E

R2475

The data of the specified column cannot be converted to a class of the Java data type specified in the getObject method of the ResultSet class.

KFAA71737-E

R2476

A timeout occurred during execution of an SQL statement because processing to allocate a processing real thread was repeated.

KFAA71570-E

R2477

Processing was canceled during batch execution of SQL statements.

KFAA71571-E

R2484

The getArray method of the ResultSet class is being used with a column that is not an array-type column.

KFAA71740-E

R2485

You are trying to retrieve the result of an array-type column using a method other than the getArray or getObject method of the ResultSet class.

KFAA71741-E

Legend:

--: There is no corresponding message.

Note:

If the SQLSTATE value that is output is not listed above, see ODBC Programmer's Reference in MSDN library.

Publisher

Hitachi, Ltd.

6-6, Marunouchi 1-chome, Chiyoda-ku, Tokyo, 100-8280 Japan