Hitachi

Hitachi Advanced Database Messages


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.

Organization of this preface

■ Intended readers

This manual is intended for:

Readers of this manual must have:

■ 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):

#: 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:

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

■ Conventions: Method abbreviations

■ 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:

■ 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:

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.