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:
-
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))
-
HA Monitor Cluster Software Guide (for Linux(R) (x86) Systems) (3000-9-201(E))
-
Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide (3021-3-320(E))
-
JP1 Version 11 JP1/Base User's Guide (3021-3-A01(E))
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)
In references to the Job Management Partner 1/Automatic Job Management System 3 manual, this manual uses Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide in place of Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.
Example: Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide
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.
Example: JP1/Base User's 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 |
Linux |
Linux(R) |
Red Hat Enterprise Linux Server 6 |
Red Hat(R) Enterprise Linux(R) Server 6 (64-bit x86_64) |
|
Red Hat Enterprise Linux Server 6 (64-bit x86_64) |
||
Red Hat Enterprise Linux Server 7 |
Red Hat(R) Enterprise Linux(R) Server 7 (64-bit x86_64) |
|
Red Hat Enterprise Linux Server 7 (64-bit x86_64) |
||
HDLM |
Hitachi Dynamic Link Manager Software |
|
JP1/AJS3 |
Job Management Partner 1/Automatic Job Management System 3 |
|
JP1/Audit |
JP1/Audit Management - Manager |
|
Red Hat Enterprise Linux Server 6 (64-bit x86_64) |
Red Hat(R) Enterprise Linux(R) Server 6 (64-bit x86_64) |
|
Red Hat Enterprise Linux Server 7 (64-bit x86_64) |
Red Hat(R) Enterprise Linux(R) Server 7 (64-bit x86_64) |
■ Conventions: Acronyms
This manual also uses the following acronyms:
Acronym |
Full name or meaning |
---|---|
APD |
Application Parameter Descriptor |
API |
Application Programming Interface |
ARD |
Application Row Descriptor |
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 |
ER |
Entity Relationship |
HBA |
Host Bus Adapter |
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 |
JTA |
Java Transaction API |
LOB |
Large Object |
LRU |
Least Recently Used |
LV |
Logical Volume |
LVM |
Logical Volume Manager |
MSDN |
Microsoft Developer Network |
NFS |
Network File System |
NIC |
Network Interface Card |
NTP |
Network Time Protocol |
ODBC |
Open Database Connectivity |
OS |
Operating System |
PP |
Program Product |
RAID |
Redundant Array of Independent Disks |
RDBMS |
Relational Database Management System |
TLB |
Translation Lookaside Buffer |
URL |
Uniform Resource Locator |
VG |
Volume Group |
WWN |
World Wide Name |
■ 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:
|
Italics |
Italics are used to indicate a placeholder for some actual text to be provided by the user or system. For example:
Italics are also used for emphasis. For example:
|
Code font |
A code font indicates text that the user enters without change, or text (such as messages) output by the system. For example:
|
■ 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,0242 bytes.
-
1 GB (gigabyte) is 1,0243 bytes.
-
1 TB (terabyte) is 1,0244 bytes.
-
1 PB (petabyte) is 1,0245 bytes.
-
1 EB (exabyte) is 1,0246 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.